World (.mcworld) vs Template (.mctemplate): What's the Difference?

Last updated: 2026-06-25

Answer

.mcworld is one specific Bedrock world (the exact save you jump straight into after importing). .mctemplate is a "world template": every time you create a new world from it, the game generates a separate copy while the template itself stays unchanged. Under the hood both are just ZIP archives with a renamed extension and a very similar structure.

The difference in one line

.mcworld is one specific world. Once you import it into Bedrock, the save you jump into is exactly this one — with its fixed terrain, builds, and your progress.
.mctemplate is a “world template.” Its purpose is to create new worlds: each time you create a world from this template, the game copies out a separate copy, while the template itself stays unchanged.

Put simply, a world is “this one playthrough,” and a template is “the master copy that mass-produces new playthroughs.” If, after importing, you find that a brand-new world is generated every time and they don’t affect each other, it’s most likely a template rather than a world. To first understand what a world file itself looks like, see What is a .mcworld file.

They’re actually the same kind of “renamed ZIP”

Underneath, both .mcworld and .mctemplate are ZIP archives with a renamed extension, and their internal structures are very similar: typically both have level.dat (world metadata), db/ (LevelDB, storing chunk and block data), plus accessory files like a cover image. The difference is mainly in the internal markers and the purpose — a template is recognized by the game as “creation material,” while a world is recognized as “a save you can enter directly.”

Precisely because the structures are so similar, many people try to simply swap the extension to “convert” between them, but this won’t necessarily produce the behavior you want, and it can easily leave the file in a state that fails to import. Related to these Bedrock package files are resource/behavior packs (.mcpack / .mcaddon), which serve yet another purpose; for the difference, see What are .mcpack and .mcaddon.

What to do if you’re not sure which it is, or it won’t open

If you can’t tell whether your file is a world or a template, or it throws an error on import, you can use TopoBlocks for a free diagnosis on-device: it reads the file type, version, and internal structure and tells you directly whether it’s a .mcworld world or a .mctemplate template, and whether the structure is sound.

Simple structural problems are repaired for free. The most common import failure is an incorrect archive level (an extra nested folder, or key files not at the archive root); these simple structural repairs are free and produce a new file that imports correctly.
Complex corruption goes to advanced repair. This is a paid item; before you pay, it shows you the specific problem, the success probability, and the risks, with an automatic refund on failure. Prices are shown in the app.
It never overwrites your original file. Whether diagnosing or repairing, it always generates a new file and keeps the original traceable — it won’t touch the copy you have.

Note that structural repair only solves problems at the file and packaging level; it won’t fix non-file issues like game crashes, missing save data, or version incompatibility. To learn more about where save data lives and which files make it up, see Where are Minecraft saves stored.

FAQ

Can I just rename .mctemplate and .mcworld back and forth?

Both are ZIP archives underneath with very similar structures, but they serve different purposes: a template is treated by the game as "material for creating new worlds" and spawns a separate copy on each create, while a world is the exact save you import and play directly. Swapping the extension won't necessarily give you the behavior you expect, because internal markers still distinguish the two. To confirm which one your file actually is, TopoBlocks can read the file type and structure with a free, on-device diagnosis.

My imported template creates a brand-new world every time. Is something wrong?

No. That's exactly how .mctemplate is designed: it's meant to create new worlds over and over, generating a separate copy each time while the original template stays unchanged. If what you want is to "keep playing the same save," then you need a .mcworld world file, not a template.

What if my .mctemplate won't open or fails to import?

Just like with .mcworld, the most common cause is an incorrect archive structure (an extra nested folder, or key files not at the root). TopoBlocks can run a free, on-device diagnosis and do simple structural repairs, producing a new file that imports correctly — and it never overwrites your original. Only complex corruption goes to advanced repair; before you pay, it shows you the problem, the success probability, and the risks, with an automatic refund on failure. Prices are shown in the app.

Get it all done in one place at TopoBlocks

Create, repair, convert, protect, and deploy your worlds—free diagnosis, and we never overwrite your originals.

Get the App