How to use a Minecraft schematic file
7 min read
A schematic is a saved copy of a build, not something Minecraft opens on its own — you need a mod or plugin to read the file and stamp it into the world. Which one depends on the file extension, and that is the part most people get stuck on. A .litematic needs Litematica, a client-side mod that shows the build as a hologram you fill in yourself. A .schem or .schematic needs WorldEdit, which pastes the whole build instantly and normally runs on a server or in single-player with the mod installed.
Guide result
A downloaded schematic placed in your world, in the right position, with the blocks it was built with.
Recommended path
- Check the file extension you downloaded — .litematic goes to Litematica, .schem or .schematic goes to WorldEdit.
- Install the matching mod or plugin for the Minecraft version you play.
- Move the file into that tool's schematics folder while the game is closed.
- Load the schematic in-game and position it before placing anything.
- Place the build, then fix the usual problems: wrong version blocks, missing permissions, or a paste that landed off-target.
Which file did you download?
The extension decides everything else, so start there. Every build on this site lists its format in the details table next to the download button.
- .litematic — Litematica. A client-side mod: it projects the build as a coloured hologram and you place the blocks by hand, so it works in survival and on servers where you have no build permissions.
- .schem — the modern WorldEdit (Sponge) format. Pastes the whole build at once.
- .schematic — the older WorldEdit (MCEdit) format, used by builds saved in Minecraft 1.12 and earlier. Recent WorldEdit still reads it.
- .nbt — a vanilla structure block file. No mod needed, but it only works up to 48x48x48 and has to go in a datapack or the world's generated/structures folder.
Litematica: .litematic files
Litematica needs the Fabric or Forge loader plus MaLiLib, the shared library it depends on. Install both for the exact Minecraft version you play — a Litematica build for 1.20 will not load on 1.21.
With the game closed, put the .litematic file in the schematics folder inside your Minecraft directory (.minecraft/schematics on Windows). Create the folder if it is not there yet.
- In game, press M to open the Litematica menu, choose "Load Schematics", pick the file and click "Load Schematic".
- The build appears as a hologram. Use the Litematica menu's placement options to move and rotate it before you start — moving it afterwards means taking it apart.
- Place the blocks yourself. The hologram shows what is missing; blocks you place correctly stop being highlighted.
- In creative, "Easy Place" mode (in Litematica's settings) lets you fill the hologram by right-clicking, which is far faster than matching it block by block.
WorldEdit: .schem and .schematic files
WorldEdit runs either as a server plugin (Bukkit, Spigot, Paper) or as a client mod in single-player. Either way the file goes in the same place relative to the installation: the schematics folder inside the WorldEdit folder — plugins/WorldEdit/schematics on a server, config/worldedit/schematics for the mod.
You need operator rights, or the worldedit.clipboard.load and worldedit.clipboard.paste permissions, before any of the commands below will run.
- Run //schem list to confirm the file is where WorldEdit can see it, and to get the exact name to type.
- Run //schem load <name> — no extension. This puts the build in your clipboard.
- Stand where you want the build, then run //paste. The build appears relative to where it was copied from, which is rarely where you are standing.
- Use //paste -o to paste at the original coordinates instead, or //paste -a to skip air blocks so the build does not carve a hole in the terrain around it.
- If it lands wrong, //undo reverses the whole paste in one step.
When it does not work
Almost every failure is one of four things, and they look different enough to tell apart quickly.
- Version mismatch — a build saved in an older version can load with blocks missing or replaced. Each build here lists the version it was saved in; that is the minimum, and newer versions generally read it fine.
- "No file matching" — the file is in the wrong folder, or you typed the extension. WorldEdit wants the name only.
- Nothing happens on //paste — you are missing permissions, not the file. Check operator status first.
- The build appears offset or underground — that is the copy origin, not a bug. Undo, move, and paste again, or use -o to place it at its original coordinates.
- A partly-placed Litematica hologram is normal in survival: it only shows what to build, it never places blocks for you.
Ship the copied artifact
Use this guide to produce the artifact a player or map maker will actually run: a copied command, ordered Project pack, or datapack resource. The final review should happen on that copied output, not only on the editable builder state.
When the workflow is version-sensitive, label the target version beside the command. When it uses selectors, scoreboards, bossbars, tags, loot tables, or project order, test those dependencies in a clean world before publishing the setup.
- Copy from Output for one command and from Project for ordered packs.
- Keep Java, Bedrock, and snapshot variants separate.
- Test destructive selectors with harmless output first.
- Update related presets when the guide becomes the canonical workflow.
Related guides and presets
FAQ
Do I need mods to use a Minecraft schematic?
Yes, for .litematic, .schem and .schematic files — vanilla Minecraft cannot read them. Only .nbt structure files work without a mod, through structure blocks.
Can I use schematics in survival?
With Litematica, yes: it shows the build as a hologram and you gather and place the blocks yourself, so nothing is spawned in. WorldEdit pastes blocks directly, so it is a creative or server-admin tool.
Will a schematic saved in an older version still work?
Usually. A schematic works in the version it was saved for and later ones, because the loaders upgrade old block data. Going the other way does not work — a build saved in a newer version can contain blocks an older world has no id for.
Why did my build paste in the wrong place?
WorldEdit pastes relative to the point the build was originally copied from, not to where you are standing. Use //paste -o for the original coordinates, or //undo and reposition.
When should this guide become a Project pack?
Use Project when the workflow needs more than one command, has setup and cleanup order, or must be edited again after testing. One-off commands can stay in Output.