Chunker 1.19.6

  • Fixed an issue where exporting worlds to Bedrock 1.20 would lead to incorrect blending (creating odd gaps).
  • Fixed an issue when downgrading tall worlds to lower than 1.17 which would lead to them crashing.
  • Fixed an issue where potted plants were missing states required for the plant when exported to Bedrock.
  • Fixed an issue where item_frames were missing states when exported to Bedrock.

Chunker 1.19.4

  • Added support for Bedrock 1.20.0
  • Added support for Java 1.20
  • Doubled the upload limit on Chunker.app, we now support worlds of up to 1GB in size.
  • Fixed several missing default states on Bedrock & Java.
  • Fixed an issue on Java where Beds may fail to be coloured. 
  • Fixed an issue where cauldrons did not correctly convert liquid from Java to Bedrock.
  • Fixed an issue with the direction of the bells.
  • Fixed an issue with fences converting from Bedrock to Java not connecting.

Chunker 1.19.2

  • Added support for Bedrock 1.19.80.
  • Fixed an issue where bed colours from Java were not being handled.
  • Fixed an issue where the pruning preview did not show the region correctly.
  • Added new advanced feature: Preloaded settings
    • When uploading a world, it will load any Chunker settings files in the main world directory. This is helpful for those who regularly upload the same world or need to use the same settings across multiple worlds being converted through Chunker.
    • How do I export my current Chunker settings?
      1. You can export the current settings as files using Advanced Mode -> Converter Settings -> Export Settings for Preloading -> Download .zip
      2. Open the .zip file it downloaded and copy all the ".chunker.json" files into the root of your input world (where the level.dat is located).
      3. Upload your world to Chunker and you'll find that your settings have been preloaded.

This update continues support for experimental blocks where possible (e.g. cherry blocks), however, these blocks may change with future Minecraft updates.

Chunker 1.19.1

  • Added support for Bedrock 1.19.70.
  • Added support for Java 1.19.4.
  • Improved NBT conversion support for CanDestroy and CanPlace.
  • Fixed an issue in Java where invalid entities led to chunks being discarded.


This update continues support for experimental blocks where possible (e.g. chiseled_bookshelves), however, these blocks may change with future Minecraft updates.

Chunker 1.19.0

  • Added support for Bedrock 1.19.60.
  • Improved parsing on Bedrock for Caudrons & Comparators when data is missing.
  • Improved messaging when a world can't be read when it's unreadable/encrypted. 
  • Fixed an issue where skull rotation was 180 degrees off from Java to Bedrock.
  • Fixed an issue where lit smokers & lit blast furnaces would not convert to the lit variant.
  • Fixed an issue where several legacy names were not being upgraded to newer identifiers when converting from Bedrock.
  • Fixed an issue where residual identifiers from Bedrock (frame/glow_frame/moving_block) would not be correctly removed.
  • The Identifier Validation option is no longer marked as experimental; this option is useful if you need to ensure block & item identifiers are compatible with your world.


This update does provide support for experimental blocks where possible (e.g. chiseled_bookshelves), however, these blocks may change with future Minecraft updates.

Chunker 1.18.0

  • Initial support for Bedrock 1.19.50.
  • Initial support for Java 1.19.3.
  • Legacy bedrock block identifiers should now be upgraded when converting old worlds.

Chunker 1.17.4

  • Fixed an issue where item damage values wouldn't be correctly converted to Bedrock.
  • Sign colors should now correctly convert where possible between Java & Bedrock.
  • Fixed an issue where maps would convert incorrectly as locked.

Chunker 1.17.2

  • Added support for Java 1.19.1 (compatible with 1.19.2).
  • Added support for Bedrock 1.19.20.
  • Java legacy chunks (older than 1.13) should retain more block data when incompatible data is loaded.
  • Fixed a minor issue when reading NBT integer tags which were not the correct tag type.
Show Previous EntriesShow Previous Entries