Java ↔ Bedrock conversion · Java & Bedrock · Intermediate

How to Keep Your Player Inventory and Ender Chest After Java ↔ Bedrock Conversion

Converting a Minecraft world between Java and Bedrock editions often leaves you spawning at the world origin with an empty inventory. This happens because the two editions track singleplayer identity using completely different internal tag structures and database keys. By mapping your UUID data and LocalPlayer tags in the browser-based NBT Editor, you can safely transfer your inventory, Ender Chest, and exact coordinates without uploading any files.

What you need

  • A complete backup copy of your world folder or .mcworld archive before making any edits
  • Your converted world folder or .zip generated by the Java ↔ Bedrock Converter
  • Your player identifier (your 36-character Java UUID or your Bedrock Player Data file)
  • Access to the NBT Editor on our site

Step by step

  1. 1Back Up and Convert Your World

    Always duplicate your original world folder before altering any files so you have a clean restore point. Open the Java ↔ Bedrock Converter on our site, select Open world folder or .zip, and run the conversion for your target edition. Because the tool runs locally in your browser, the converted package generates directly on your device; keep this converted folder or archive ready for inspection.

    Tip: If you are unsure whether the converter automatically matched your singleplayer profile, load the world once in Minecraft first to see if you spawn with an empty inventory.

  2. 2Locate Your Source Player Data in the NBT Editor

    Open the NBT Editor on our site and click Open world folder or .zip to load your newly converted world. If you converted to Java Edition, look inside the level.dat file under the Data compound for the Player tag, and also check the playerdata/ folder for files named after 36-character UUIDs (like a1b2c3d4-e5f6-...). If you converted to Bedrock Edition, check the root level.dat or the LevelDB database keys for the ~local_player entry and any remote player keys formatted as player_server_ followed by an ID.

    Tip: Look inside the Inventory list tag and EnderItems list tag of each profile to verify which record actually holds your gear, as empty profiles will show 0 entries.

  3. 3Map Your Profile for Java Edition (Bedrock to Java)

    In Java Edition, singleplayer worlds prioritize the Player compound tag embedded directly inside level.dat, while also saving a matching file in the playerdata/ folder using your account's UUID. If your converted items ended up inside a generic UUID.dat file in the playerdata/ folder instead of level.dat, copy the Inventory, EnderItems, Pos, and Dimension tags from that file into the Data -> Player compound of level.dat using the NBT Editor. Additionally, rename that .dat file in the playerdata/ folder to match your exact Java Edition UUID so multiplayer or LAN sessions recognize you.

    Tip: You can find your exact Java UUID by checking the logs of a recent game session or looking at the filename generated when you create and save a brand-new singleplayer Java world.

  4. 4Map Your Profile for Bedrock Edition (Java to Bedrock)

    Bedrock Edition always loads the host player's inventory and position from a dedicated internal record named ~local_player. When converting from Java, if the converter mapped your UUID profile into a multiplayer key (such as player_server_...) rather than the local host slot, your singleplayer session will ignore it. In the NBT Editor, locate the converted player data containing your populated Inventory and EnderChestInventory lists, copy those lists along with Pos and PlayerLevel, and paste them directly over the corresponding tags inside the ~local_player entry.

    Tip: Make sure you also copy the DimensionId tag (0 for Overworld, 1 for Nether, 2 for End) so your Pos coordinates do not place you inside solid blocks in the wrong dimension.

  5. 5Save Changes and Load the World

    Once your Inventory, Ender Chest, and Pos tags are properly placed into the target singleplayer profile, click Save in the NBT Editor to download your updated files. Replace the old level.dat or playerdata files in your converted world directory with the newly edited ones. Move the world folder into your game's local saves directory (saves/ for Java, minecraftWorlds/ for Bedrock) and launch the game to confirm your items are restored.

How it works

Java Edition and Bedrock Edition use fundamentally different schemas to determine who owns a singleplayer world. In Java Edition, singleplayer mode looks inside the compressed level.dat file under Data -> Player to load the active host's state. When the world saves, Java also writes this data to playerdata/<UUID>.dat. If you open a world where the Data -> Player tag is missing or mapped to a different UUID than the active account, the game treats you as a brand-new player.

Bedrock Edition stores player profiles inside its LevelDB key-value database rather than individual folder files. The person hosting or playing the world locally is always assigned the literal database key ~local_player, while visiting players are indexed using Xbox Live or server identifiers. Furthermore, Java names its Ender Chest tag EnderItems while Bedrock names it EnderChestInventory, and item IDs must be translated during conversion before mapping the profile tags.

Because our Java ↔ Bedrock Converter already translates the item IDs, slot numbers, and enchantment formats between the two engines, you do not need to manually rebuild individual items. You only need the NBT Editor to ensure the converted tag lists reside under the exact host identifier (~local_player for Bedrock, or level.dat -> Data -> Player and your UUID.dat for Java) that your game client queries on startup.

Common mistakes

  • Copying raw item tags directly from an unconverted Java world into a Bedrock world without running the Java ↔ Bedrock Converter first, which fails because the two editions use different item naming conventions and tag structures.
  • Updating the playerdata/<UUID>.dat file in Java Edition while forgetting to update or clear the Data -> Player compound inside level.dat, causing level.dat to overwrite your UUID file with an empty inventory upon loading.
  • Transferring the Pos (position) tag without checking the Dimension or DimensionId tag, which can spawn your player at Nether coordinates inside the Overworld.
  • Forgetting to include the hyphen characters when renaming a Java playerdata/<UUID>.dat file (Java requires the standard 8-4-4-4-12 hyphenated format, not the 32-character undashed string).

FAQ

Why not just put all my items in a normal chest before converting the world?

Putting gear into a standard block chest at spawn is a great preventative workaround, as block entities convert directly with chunks. However, if you already converted a world, deleted the original installation, or received a world download from a server where you couldn't access a chest first, remapping the player NBT tags is the only way to recover your inventory and Ender Chest.

How do I tell which UUID file in the playerdata folder is mine if there are several?

Open the world in our NBT Editor and inspect each .dat file inside the playerdata/ folder. Check the Inventory list tag and the Pos list tag; you can easily identify your profile by recognizing the specific items, custom tool names, or coordinates where you last logged out.

Will my experience levels and advancements transfer too?

Your experience levels are stored right alongside your inventory (in XpLevel and XpP on Java, or PlayerLevel and PlayerLevelProgress on Bedrock) and will transfer when you map the player compound. Advancements and statistics are stored in separate JSON files in Java and do not have a direct one-to-one equivalent in Bedrock world saves.

By using the Java ↔ Bedrock Converter to translate your world's item formats and the NBT Editor to align your UUID or ~local_player tags, you can seamlessly carry your full inventory, Ender Chest, and position across editions.

More java ↔ bedrock conversion guides

Java ↔ Bedrock conversionHow to Convert a Minecraft Bedrock (.mcworld) Save to Java EditionMoving a world from Minecraft Bedrock Edition to Java Edition requires translating the entire underlying database structure. Using our browser-based Java ↔ Bedrock Converter, you can easily transform a Bedrock world folder or .mcworld archive into Java-compatible Anvil files. Because the tool runs locally in your browser, your save files are processed quickly and never leave your computer.Java & BedrockBeginner5 steps
Java ↔ Bedrock conversionHow to Trim a Huge World Before Converting Between Java and BedrockConverting a multi-gigabyte Minecraft world between Java and Bedrock editions can easily exceed your web browser's memory limit. Because our tools process everything locally on your device without uploading files, the smartest approach is to prune unexplored chunks first. Combining the Chunk Trimmer with the Java ↔ Bedrock Converter reduces conversion time from hours to seconds while keeping all your builds completely intact.Java & BedrockIntermediate5 steps
Java ↔ Bedrock conversionHow to Unpack, Edit, and Repackage Bedrock .mcworld ArchivesA Minecraft Bedrock .mcworld file is simply a standard ZIP archive with a custom file extension used for easy one-click world importing across Windows, iOS, Android, and consoles. However, repackaging an edited world incorrectly will cause Minecraft to throw an import failure error. This guide shows you how to safely unpack, modify, and repackage .mcworld archives using the correct internal folder structure, or automate the process entirely inside your browser.BedrockBeginner5 steps
Java ↔ Bedrock conversionJava vs Bedrock World Conversion: What Transfers and What Gets LostConverting a Minecraft world between Java Edition and Bedrock Edition is more than just changing a file extension; it requires translating two fundamentally different game engines. This guide explains exactly what happens to your blocks, entities, inventories, and redstone mechanics during conversion, and how to use our browser-based Java ↔ Bedrock Converter safely. Because all processing runs locally in your browser without uploading files, you can quickly test and inspect your converted worlds with complete privacy.Java & BedrockIntermediate4 steps