Format guide · Legacy MCEdit

Open legacy MCEdit .schematic files

Preview older MCEdit schematics and map supported legacy numeric block IDs to modern Minecraft block names.

Supported input.schematic

Maximum source file size: 200 MB. Practical browser memory limits vary by device.

What is preserved

Built for accurate
inspection.

  • 01Legacy numeric block IDs
  • 02MCEdit dimensions and offsets
  • 03Conversion-ready 3D inspection

Where the format comes from

The legacy .schematic format comes from MCEdit-era tools and stores numeric block IDs and damage values. It predates the namespaced block-state palette introduced in Java Edition 1.13, so reading it means mapping old numbers to modern names.

What Schematic Studio keeps · and its limits

Recognised IDs are mapped to modern equivalents. Ambiguous, modded or unknown numeric IDs cannot always be reconstructed faithfully and may appear as placeholder blocks.

How to use it.

01

Choose your file in the viewer or converter.

02

Review dimensions, origin and block totals before rendering.

03

Inspect layers, materials and camera angles · or export a selected world area.

Common questions.

Why do some blocks look different after conversion?

Old files use numeric IDs. Where no dependable modern equivalent exists, the block cannot be reproduced exactly.

Will a converted file work in 1.13+?

The .schem output uses modern block names, so recognised blocks paste correctly in current Java versions.

Why does a large file fail to open?

Dense builds can exceed browser memory or GPU capacity even below the 200 MB limit. Close other heavy tabs, try a smaller selection, or see Troubleshooting.

Private
by default.

File parsing starts in your browser. Nothing appears in Explore unless you deliberately publish it from a verified creator account.

All format guides