BLOCK.litematic, .schem, and .schematic compared
| Format | Typical use | Check before loading |
|---|---|---|
| .litematic | A Litematica blueprint for inspecting and following a build. | The Litematica release for your Java instance and its dependencies. |
| .schem | A Sponge schematic, used by modern WorldEdit. | Whether your editor reads the file’s particular format version. |
| .schematic | The older format associated with MCEdit and older WorldEdit releases. | Legacy import support and how older blocks are interpreted. |
| World archive | A world to explore with its saved surroundings. | The intended edition, version, archive contents, and import instructions. |
Litematica’s author documents loading schematics and configuring their placements. Use our Litematica guide for the building workflow and the project’s documentation for its controls. A displayed blueprint is a reference; loading it alone does not construct the building.
WorldEdit moved from .schematic to .schem with WorldEdit 7 and Minecraft 1.13. Its current documentation describes legacy .schematic import, but no longer writing that older format. Run //schem listformats to inspect your installation’s supported formats; extensions alone cannot establish support. See WorldEdit’s format and clipboard documentation.
A format version is not a Minecraft version
Two files ending in .schem can have different format revisions or contain blocks from different game versions. The Sponge schematic specification separates the format’s Version from Minecraft’s DataVersion. It also defines block states and optional information such as entities and biomes.
That distinction matters when diagnosing a failed import. “Unknown format” points toward the reader; missing or incorrect blocks require checking the game version and dependencies too. A successful file load is only the first check. Inspect stairs, doors, containers, and any machinery before accepting the result.
Can a Java schematic work in Bedrock?
Do not assume a Java download is ready for Bedrock because both editions contain similarly named blocks. Bedrock’s documented structure-block workflow uses .mcstructure files. Microsoft’s structure block guide also notes that the import and export buttons are limited to Windows, and that importing requires hosting the world.
Choose an explicitly compatible download when possible. For a cross-edition conversion, first check whether the chosen converter supports your source format, destination edition, and versions. Treat the output as a new candidate to inspect. A converter reporting success does not prove that a farm, redstone circuit, or inventory setup behaves as intended; use the technical build test checklist.
When a world download is the better starting point
A world download can help when you need to walk through rooms, understand landscaping, or inspect how several buildings connect. It is a different deliverable from a standalone schematic. Read the creator’s extraction instructions and open a separate copy; do not merge unfamiliar archive contents into your active save.
If you only want one building, determine whether you can select and export it with a tool supported in that world. Include the basement and roof overhang, then inspect the new selection before saving. Keep the creator’s source link and license with the extracted file; a different format does not change redistribution permission.
A conversion workflow you can check
- Keep the original. Save an untouched copy and record its author, source, edition, and listed game version. Give the output a distinct name.
- Confirm both ends. Check the tool’s documented import and export formats. If it cannot read the input or write your target, stop there; renaming the extension does not convert the data.
- Use a test world. If your route involves placing the source and saving it again, use a disposable world with the required blocks and dependencies. Our WorldEdit guide covers controlled placement.
- Compare the result. Check dimensions, orientation, visible block types, and important details against the original. Inspect any entity or container data you actually need.
- Test the intended use. Reopen the exported file in the destination tool. For a survival blueprint, check the placement and material list. For a machine, test its operation before connecting it to your main base.
Common format questions
Can I rename .litematic to .schem?
No. Changing the name changes the label, not the stored structure. Use a conversion path whose tools explicitly support the input and output.
Does a smaller file mean an easier build?
No. Compare dimensions, materials, and access requirements. Download size is not a construction budget; the survival build planning guide shows a practical estimate.
Why does a compatible file still look wrong?
Check missing dependencies, source version, placement rotation, and whether the export included everything you expected. Return to the first-build workflow for a systematic inspection before trying another download.