Schematic formats
Import structures from Minecraft, WorldEdit, Litematica and older exporters.
Supported files
Section titled “Supported files”| Format | File extension | Supported versions |
|---|---|---|
| Vanilla structure | .nbt | Native structure data, with alternative palettes when present. |
| Sponge / WorldEdit | .schem | 1 to 3 |
| Litematica / Forgematica | .litematic | 1 to 7 |
| Legacy Alpha / MCEdit | .schematic | Legacy format with resolvable registry/name data. |
The reader detects file contents rather than relying only on the extension. Multiple or negative Litematica regions, packed states and offsets are supported. Conflicting overlapping regions and unresolved historic numeric metadata are reported rather than guessed.
Where do files come from?
Section titled “Where do files come from?”Use an exporter you already have, such as Minecraft’s structure blocks, WorldEdit, Litematica or Forgematica. Put the result in your active instance’s schematics/ library. Simple Schematics imports files; schematic export is outside its implemented import path.
Files that need conversion elsewhere
Section titled “Files that need conversion elsewhere”Palette-less global-ID Sponge files, Classic schematic format and Bedrock conversion are outside the implemented path. A future Minecraft DataVersion, missing historical registry map or removed mod property remains a diagnostic.
If an old file cannot resolve an ID, use a suitable external exporter or converter that understands the source format and mods. Renaming the extension does not fix its contents.
Missing blocks
Section titled “Missing blocks”Install the matching source mod where appropriate, pick replacement blocks, or mark missing content for manual placement. Installed mods must still agree on the meaning of their saved data. The compatibility guide explains that boundary.