MCTOOLBOX
MC ToolboxMC TOOLBOX

Browser schematic tools

Minecraft Schematic Converter

Convert .litematic, .schem, .schematic, Java Structure .nbt, Axiom .bp and Bedrock .mcstructure files locally. Inspect layers and materials before downloading a real converted file.

Private: files never leave your browser

Drop a schematic here

.litematic · .schem · .schematic · .nbt · .bp · .mcstructure

Real binary conversion

Every download is written as the selected format, including gzip, VarInt, long-array packing and Bedrock little-endian NBT where required.

Known limits are visible

Entities and block-entity payloads are reported when an input contains data the normalized block model cannot safely carry across formats.

Large-file safety

Files are processed locally with a browser safety limit of 16,777,216 blocks to prevent a single tab from exhausting device memory.

Supported Minecraft schematic formats

Each format stores blocks differently. The converter first builds one coordinate-safe palette model, then writes the exact binary layout required by the selected target.

.litematic — Litematica

Named regions, modern Java block-state palettes and packed long arrays used by the Litematica mod.

.schem — Sponge schematic v3

Gzipped NBT with namespaced block states and VarInt block data used by modern WorldEdit-compatible tools.

.schematic — MCEdit schematic

The pre-flattening Java format built on numeric block IDs and metadata. Export is limited to blocks known in Minecraft 1.12.2.

.nbt — Java Structure

The vanilla Structure Block and data-pack format with a palette plus explicit block coordinates.

.bp — Axiom blueprint

Axiom blueprint data with metadata, compressed region data, 16-cubed chunks and padded block-state arrays.

.mcstructure — Bedrock structure

Little-endian NBT used by Bedrock Structure Blocks, add-ons and development tools.

How to convert a Minecraft schematic safely

Load and identify

Choose one of the six supported files. The parser detects the source structure, validates dimensions and builds a normalized palette without uploading the file.

Inspect before converting

Move through Y layers, compare the top-down view, review exact block states and replace incompatible blocks before export.

Export and verify in game

Pick the target format, read any compatibility warning, download the converted file and test it in a backed-up world before using it on an important build.

Which schematic format should you export?

Choose the format expected by the mod, editor or game edition that will load the build. Renaming a file extension does not convert its internal NBT layout.

TargetBest exportWhy
Litematica mod.litematicKeeps modern Java block-state strings in a format Litematica can load directly.
WorldEdit or FAWE.schem v3Uses the current Sponge palette and VarInt block-data layout.
Vanilla Java or data pack.nbtMatches the Java Structure Block palette and coordinate list.
Axiom Editor.bpWrites Axiom blueprint chunks and block-state palettes.
Bedrock Structure Block.mcstructureUses Bedrock little-endian NBT; review edition-specific blocks after conversion.
Minecraft 1.12 tools.schematicUses legacy numeric IDs and metadata; modern blocks without a mapping become air.

Use the previews as a build-planning tool

Check the footprint in 2D

A single Y layer makes hidden gaps, wall thickness and off-by-one placement easier to spot than a full 3D model. Top-down mode shows the highest visible block at or below the selected layer.

Inspect height ranges in 3D

Set minimum and maximum Y values to isolate floors, roofs or redstone sections. Click a rendered block to inspect its exact coordinates and complete block state.

Plan supplies by layer

Filter the material list to the current layer, switch between stacks and shulker boxes, check off gathered materials and export the visible list as CSV.

Follow the Build Book

The Build Book groups tall schematics into practical Y ranges. Each step shows a cumulative isometric view and only the materials added during that step.

Schematic converter FAQ

Does the converter upload my build?

No. Reading, previews, block replacement and binary export run in the browser. The selected schematic never needs to leave the device.

Why can a legacy .schematic lose blocks?

MCEdit .schematic stores numeric IDs from the pre-1.13 era. Blocks added later have no legacy ID, so the tool counts them and warns before replacing them with air.

Are Java and Bedrock block states identical?

No. Many simple names match, but directional properties, waterlogging and edition-only blocks can differ. Always inspect a Java-to-Bedrock conversion in a test world.

Are entities and chest contents converted?

No. Conversion preserves the normalized block model: dimensions, coordinates, palette entries and block states. Entity and block-entity payloads such as mobs, chest inventories and sign text are reported but are not written to the converted file.

Can I use a Resource Pack for the 3D preview?

Yes. Choose a local Resource Pack ZIP and matching block textures are used for simple cube previews. Complex block models, connected textures and mod-specific rendering rules are not reconstructed.

What does chunked export do?

It splits the build into X, Y and Z boxes and downloads a ZIP of coordinate-named schematic files. The included README explains that each filename records its offset from the original minimum corner.

Is the material checklist uploaded or synced?

No. Checklist and layer progress are stored in this browser for the exact local file. They are not attached to the schematic, uploaded to an account or synchronized to another device.

Why is there a block limit?

A malicious or accidental size field can make a browser allocate enormous arrays. The 16,777,216-block limit keeps conversion local while protecting the tab and device memory.