Skip to content

Export and import

Exporting saves the current world as files used by the server and the game. In one go you can create a resource pack, a server registry, a .npbuild, a .schem and a Minecraft world folder. Importing reads a .schem schematic or a range of a Minecraft world into the editor and pastes it.

WhatWhere
Export windowBuild › Export: Resource pack piece · .npbuild (Ctrl+Shift+E)
Save directly as a Minecraft worldBuild › Save as Minecraft world…
Resource pack onlyBuild › Build resource pack (Resource pack and HUD)
markers.jsonBuild › Export: markers.json (server markers)
Import .schemFile › Import: .schem (Sponge schematic), or Import .schem in the export window
Import a worldImport world in the export window
  1. Open the export window with Ctrl+Shift+E.
  2. Under Target, check what to create (resource pack · server registry · .npbuild · .schem · world save (.mca)).
  3. Choose the Target version (default 1.21.11).
  4. Choose the Region (Whole world · split regions / Whole world · single file / Selection only).
  5. Click Export.
  6. Open the output folder with the Open folder icon. The Log shows the created files and warnings.
  1. Click Build › Save as Minecraft world… and choose a folder.
  2. Copy the created <name>_world folder into %APPDATA%\.minecraft\saves\.
  3. Open it from the Minecraft single-player list. It is a Creative world with time fixed at noon and no mobs.
TargetWhat it createsWhere it is used
Resource packComplete resource pack (standalone) or fragment zipServer resource pack
Server registry<name>_registry_vN.jsonServer plugin (custom blocks · props · items)
.npbuildInstall file for the server build module — block entities · props · groups, markers.json with Include markers, scene.json with Include sceneServer plugin
.schemSponge v3 schematicWorldEdit · FAWE
World save (.mca)level.dat + region/*.mca + entities/*.mcaSingle player · server world
  • scene.json holds scene actors, animations and world logic rules. It is not exported as a separate file; it goes inside the .npbuild (scene.json format).
  • If there are sound emitters or block sounds, <name>_sounds_server_vN.json is also created when you export the server registry.
ContentsNotes
Block statesOrientation preserved
Sign textBoth sides · color · glow · wax
Banner patterns · container names—
Items in containersContents read from imported worlds and schematics
Propsitem_display (1.21.4+) — the same way as the server
Custom blocksSubstitute block (magenta wool by default) or note block states (resource pack required)
FieldValuesMeaning
Target version1.20.1 – 1.21.11The basis for .schem DataVersion, the .npbuild header and block checks.
Block listAutomatic if emptyThe server jar report blocks.json.
Missing blocksWarning table only (keep) · Replace as suggested · Don’t exportWhat to do with blocks and properties not in the target version
RegionWhole world · split regions / Whole world · single file / Selection onlyThe selection is carried over automatically.
Region sizeDefault 256 (multiple of 16)Side length when splitting regions.
Air cellsClear (match editor) · Keep (overlay)How air cells are handled when installing on the server
Include markersOnPuts markers within the range into the .npbuild.
Include sceneOnPuts scene.json into the .npbuild.
.schem customAir (vanilla only) · Note block statesHow custom blocks are written in .schem
Load budget checkOnAsks if there are chunks over the limit.
Ignore errorsOffCreates files even with errors (for review).
FieldValues
Position offsetWrites shifted by X · Y · Z.
Below floorEmpty · Fill with stone (bedrock at bottom)
Outer terrainEmpty sky (buildings only) · Flat
Custom blockSubstitute block + warning · Note block states (resource pack required)
Substitute blockDefault minecraft:magenta_wool
Block entitiesWrites contents such as sign text, banners and container names (on by default)
PropWrites props as item_display (on by default, 1.21.4+)
Verify after writeReads back after writing and verifies cell by cell (on by default)
FieldMeaning
Output folderIf empty, <project>/export.
File nameThe start of the file name. If empty, the world name.
RP to mergeExisting resource pack to merge into in fragment mode (read only).
ImportFieldsResult
.schemFile · Note blocks to custom (on by default)Reads Sponge v1–v3 and hands it to the paste tool.
WorldWorld folder (the folder with level.dat) · Range start · Range end (Minecraft coordinates)Pastes the blocks, block entities and props in that range.
  • Signs, banners, container names and container items are read too.
  • Unknown blocks are kept as placeholders and reported in a list.
  • item_display props placed by the editor or the server are turned back into editor props.
  • Other entities (mobs, item frames, etc.) are not imported.
  • Only worlds from 1.18 or later are read. If the range is too large, it is refused with “Range too large”.
VersionWorld save
1.20.1 · 1.21.1Supported. Props are not written.
1.21.4 – 1.21.11Supported. Props are written too. 1.21.11 is the default.
1.18.2No export (import only). If chosen, warns and writes in 1.20.1 format.
26.xWritten in 1.21.11 format; the game upgrades it.

More about versions is in Minecraft versions.

  • Exports never overwrite. If the same name exists, _v2 · _v3 … is appended.
  • A complete resource pack gets a version number, as in <name>_rp_vN.zip.
  • The world folder is <name>_world.
KeyAction
Ctrl+Shift+EExport window
EscClose the export window
  • If there are errors, no files are created. Fix the [오류] lines in the Log first.
  • For accurate prop sizes, check the resource pack too. Otherwise props are written at size 1 with a warning.
  • If you export container items across format eras (before/after 1.20.5), names and enchantments are dropped and only type and count remain.
  • Upload the resource pack and server registry according to the server’s plugins folder settings. The resource pack SHA-1 lines are in .sha1.txt.