Frequently asked questions

The vast majority of supported vanilla content, and every known limit is documented. Terrain and blocks (orientations, axes, slabs, stairs, doors, waterlogging), inventories and chests, 42 enchantments, 45 potion variants, durability, custom names and lore, 152 entity types (including 90 living creatures), villagers with their trades and discounts, tamed animals, supported furnaces/brewing stands/beacons/banners/signs and other block entities, in-hand maps (drawing, scale, centre), redstone (repeaters, comparators, observers, pistons, levers: direction is preserved), scoreboards, biomes, command blocks (commands translated), player data (inventory, XP, health, hunger, effects, respawn point), and world settings (seed, gamerules, difficulty, time, weather, generator type including void worlds). See the detailed, verifiable reference →

Very reliable. The engine converts 152 entity types, 42 enchantments and 45 potion variants, and it runs on real worlds of several hundred MB as well as on command-block maps. On an ordinary survival world, the essentials should remain faithful after conversion. What does not carry over falls in two groups: what has no general equivalent between editions (mods, unexplored terrain), and a few limits that are ours. The reference page names them one by one and tells you whose limit each one is. If you spot an imperfection, report it to bug@worldswitchapp.com with the position and conversion reference. Only attach the source world if the team asks or if you voluntarily choose to do so; it may then be reviewed for diagnosis.

WorldSwitch does not convert mods, data packs, behavior packs or resource packs together with the world. Their formats differ between editions and there is no general one-to-one equivalent, although specialised tools can adapt some simple packs. Statistics and advancements also use incompatible ID systems; exact player-head skins and NEVER-explored terrain are not transferred.

Then come a few limits that are ours, which we would rather show than hide: for instance, going Java → Bedrock, the internal label telling Minecraft "this chunk is part of a fortress" is not written back yet (the build and its contents do arrive intact; what it affects is /locate and structure-only spawns), and a trial interrupted mid-wave re-arms instead of resuming. Each one is named on the reference page and flagged "current WorldSwitch limit".

Every engine change re-runs automated tests, and real worlds are reconverted both ways and loaded in-game. Minecraft is still huge: if you spot a discrepancy, email bug@worldswitchapp.com with the position. Only send the source world if the team asks for it or if you voluntarily choose to attach it; it may then be reviewed to diagnose the issue.

Yes. The orientation of repeaters, comparators, observers, pistons (base + head), levers and torches is converted with the right conventions between editions, and dust signal is preserved. Your circuits keep their direction.

Yes, slot by slot: identity, count, enchantments (40+), durability, custom names and lore are transferred, including shulker boxes and the contents of containers stored in the inventory. The rare details of an item with no destination in the other edition (a Multishot crossbow keeps only one loaded projectile there, some Java 1.20.5 item components have no counterpart) are named in the conversion report, never removed silently.

They keep their "tamed" status but the EXACT player ownership cannot be transferred 100% (Mojang limitation: 128-bit Java UUID ≠ 64-bit Xbox UniqueID). In practice: your cat stays tamed but may reconsider its owner at first.

Yes, including recipes unlocked by profession level and cured-villager discounts, both ways. Java stores that discount per recipe and Bedrock stores it on the villager, in two tiers: when your recipes carried different discounts, the largest one applies, and the difference is named in the report.

Yes: the drawing is carried over cell by cell, with its scale, center and dimension. Going Bedrock to Java, a few tints are matched to the closest colour Java has: the drawing is the same, a shade may shift.

VANILLA command syntax is translated between editions: selectors (c=/r=/tag=/distance=/limit=…), /tellraw, /effect, /title, /replaceitem ↔ /item replace, /testfor → /execute if entity, /structure load → /place template, merged coordinates, § color codes, and a good share of Java 1.20.5+ item components (block states, can_place_on…). Whatever has no counterpart (commands from mods, components or predicates with no Bedrock equivalent, command-block timing that cannot be reproduced) is never copied over blindly: the command is disarmed and the report hands you its position and original text.

Yes: text, the 16 colors, bold, italic, wax and the glowing effect are preserved on BOTH sides (JSON text components ↔ § codes conversion). One exception: Java's underline and strikethrough no longer exist on Bedrock, those two codes now name material tints there (copper, redstone). The text and the rest of its formatting carry over, and the case is named in the report.

Yes. A void world is converted to a "void" generator on the target side: no terrain is generated around your builds. A FLAT world stays flat: that is a different generator, and the composition and thickness of your layers are kept.

Up to 10 GB per world, measured once the world is unpacked, not the size of the file you upload. That matters mostly on the Java side: a .zip expands about two to three times, so a 3.5 GB archive can already be over the limit. A Bedrock .mcworld barely compresses at all: its file size is already its real size. The file you upload cannot exceed 10 GB either: both caps apply. The free tier reads on that second quantity: a file of 70 MB or less is converted for free, no sign-up. Important: access to the file is cut off 24h after conversion, and deletion is triggered right away (final removal by our storage provider is asynchronous).

Email contact@worldswitchapp.com with your world's size and the direction of conversion: the 10 GB cap is the automated service's, not the engine's, and a bigger world can be handled by hand. It is not guaranteed up front — it depends on the direction and the actual size, because a conversion needs several times the world's volume in working space — but you will get a straight answer, either way, before committing to anything.

Yes, in one case: an archive that expands out of all proportion is refused, whatever its starting size. This is the protection against "decompression bombs" — tiny files that balloon until they fill the disk. In practice each upload gets an unpacking budget of 12× the archive size, with a floor of 512 MB and a ceiling of 48 GB; a normal Minecraft world is nowhere near that (a Java .zip expands two to three times, an .mcworld barely at all). A malformed archive, or one whose contents do not look like a world, is refused for the same reasons.

Expect roughly 1 to 5 minutes for a 100 MB world, 4 to 22 minutes for 500 MB, and up to 2 h 21 min for a world at the maximum size of 10 GB unpacked. For a given FILE size, Java → Bedrock takes longer, because a Java world expands two to three times more. You don't have to guess: as soon as you drop your file, the wizard shows the range computed for YOUR world and your direction; the same calculation as these figures.

No: Java and Bedrock use different world generators. Only ALREADY-explored terrain (generated chunks) is transferred. Never-visited areas will be generated by the target edition with its own algorithm. This is inherent to both editions.

WorldSwitch does not convert them together with the world. Their formats differ between editions and there is no general one-to-one equivalent, although specialised tools can adapt some simple packs.

Reset. The ID systems differ between the two editions.

Yes. Conversion is automated: no human reviews your world during normal processing. If you voluntarily send it to support to diagnose a bug, authorised staff may however review it for that purpose. Files are encrypted in transit (HTTPS) and stored temporarily: access is cut off exactly 24h after conversion and deletion is triggered right away, its finalisation by our storage provider being asynchronous. Deleting your account immediately starts deletion of remaining files and metadata; if a technical step fails, the automatic retention sweep acts as a safety net. Existing accounting records remain stored and detached from the WorldSwitch account, without being described as strictly anonymous.

No. Your worlds are used ONLY to be converted. No reuse, no resale, no marketing analysis.

No, not of your world. Access to the file is cut off 24h after the conversion and its deletion is triggered right away (final removal by our storage provider is asynchronous). What outlives it is not your world: it is the conversion record. It carries technical metadata read from the world — world and level name, spawn coordinates, icon, player identifiers (Java UUID, XUID/MSA) — cleared by the automatic sweep once the conversion has finished and its record is more than 7 days old. Deleting your account triggers that cleanup immediately; if the operation fails, the sweep remains the safety net. What is left afterwards says nothing about your world's contents: the conversion reference, its direction, its size, its tier, its price, its status, its dates, and the billing line. The detail, processing by processing, is in the privacy policy.

Here is what you can check for yourself: every processing activity states its legal basis and retention period, every processor is named (hosting, storage, database, payment, email), and your rights — access, rectification, erasure, portability, objection — are exercised by a simple email, answered within one month. The details are in our Privacy Policy; if anything is missing or contradictory, write to us and we will fix it.

No. No subscription. You pay ONCE per conversion when the file you upload exceeds 70 MB. Below that it is free, no sign-up or card required.

Payment goes through Stripe, and the methods shown on the payment page are what counts: Stripe builds that list at payment time, from what is enabled on our Stripe account and from your country, your currency and your device. You will usually find card payment there, sometimes alongside Apple Pay, Google Pay or a local method. Anything not listed on that page is not accepted, and nothing is charged until you confirm it.

On the size of the file you upload (.mcworld or .zip), the one your file explorer shows. The exact price therefore appears as soon as you drop your world, before a single byte is sent, and that is the amount charged, never more.

If the conversion fails due to a technical problem on our side, the refund is triggered automatically, usually a few minutes after the failure. You don't have to ask: the system detects the failure, records the debt and settles it with Stripe on its own, retrying until it clears. How long the money takes to reach your payment method depends on your bank: Stripe generally quotes 5 to 10 business days. If your world is rejected for what it contains (unreadable archive, unsupported format), nothing is charged at all.

And if something goes wrong anyway (refund that never lands after that delay, wrong amount, payment taken twice) write to contact@worldswitchapp.com with your conversion reference (or just the date and the amount). We take it from there by hand.

Yes, as long as your conversion has not finished. Before paying, you ask for the conversion to be carried out right away, during the 14-day withdrawal period: your right of withdrawal only ends once the service has been fully performed, meaning your converted file is available to download. Before that point, a simple email to contact@worldswitchapp.com with your conversion reference is enough: you get a full refund, no deduction, no reason needed. After that, the conversion is done — but the legal guarantee of conformity still applies (Terms art. 8).

Not for now: WorldSwitch is for private individuals, for private use (Terms art. 5). Since 2026, an invoice to a Belgian VAT-registered business must be a structured electronic invoice (Peppol network), and we do not issue those yet — better to say so than to sell you a document your accounting cannot use. For a consumer payment, Stripe does create an invoice: when Stripe provides its link, it appears in your dashboard and we attempt to include it in the confirmation email. Business invoicing is planned; write to us if that is what you need and we will let you know.

Yes. Write to contact@worldswitchapp.com with your links (YouTube / Twitch / TikTok). From 5,000 subscribers we set up two things: a €30 credit on your account, which pays in full for any conversion it covers — nothing is charged to your card then —, and a personal code to hand to your community: subscribers who enter it at payment time get 20% off their conversion. There is no part-credit, part-card payment: if the balance does not cover a whole conversion, that conversion is paid for as usual and the credit stays untouched for a smaller world. The remaining balance is shown in your dashboard.

The price you see before paying is the total amount due: nothing is added, no fees, no tax. The publisher’s VAT status: Not registered for VAT — no VAT is charged and no VAT identification number has been issued. Should VAT be due based on your country of residence, it would be included in the displayed price and borne by the publisher.

Yes for the supported properties: WorldSwitch reconstructs the beam, primary and secondary effects, and pyramid level so the converted beacon resumes working when loaded.

If your circuit used dust on GLASS on the Bedrock side, Java refuses that configuration (architectural). Replace the glass support with a full block before converting.

Email bug@worldswitchapp.com with the exact position and conversion reference. Only attach the source world if we ask for it or if you choose to share it for diagnosis; authorised staff may then review it.

Email: contact@worldswitchapp.com. Usually answered within 24h. To report a bug with a specific world: bug@worldswitchapp.com.