Back to blog

Project Zomboid Support And Export READMEs

July 6, 2026 · 2 min read

Project Zomboid exports are now supported, and game exports now include clearer README instructions plus machine-readable maptoplay.json metadata.

Project ZomboidExportsREADMEAttributionOpenStreetMap

Project Zomboid is now supported in MapToPlay. The export path is built around the official Project Zomboid Modding Tools workflow: MapToPlay creates a WorldEd-ready project, source maps, vegetation and zombie spawn maps, a mod skeleton, and building footprint guides, then you finish the map in WorldEd or TileZed.

This is an authoring export, not a magic finished map. You still place real Project Zomboid buildings and finish the map with the official tools. But the boring starting structure is now there, and the export tells you what to do next.

Export READMEs

Exports now include a README written for people, not for archeologists. It explains the next step for the target game: where to open the files, what editor or game workflow to use, and what still needs manual work.

For Project Zomboid, that README is explicit that buildings are not automatically placed as game-ready structures. MapToPlay gives you the terrain sources and footprint guides; you use the Project Zomboid tools to place the actual buildings and generate lots.

maptoplay.json

Exports also include a machine-readable `maptoplay.json` file. This is meant to preserve the important facts about the export so they do not disappear once a zip is downloaded.

It contains things like exporter name and version, export date, map center, selected size, playable size where relevant, rotation, output details, and source/provider metadata for terrain, imagery, and vector data.

  • Exporter name and version
  • Export date
  • Map center and size
  • Target-game output details
  • DTM, imagery, and vector provider metadata

Please Attribute The Data Providers

A reminder because it matters: MapToPlay can help you create exports, but it does not remove the licenses or attribution requirements of the data you use.

If your export uses DTM providers, OpenStreetMap data, satellite imagery, aerial imagery, MapTiler previews, or any other external provider, you must respect the provider terms and attribution requirements. Check the README and `maptoplay.json`, then credit the data providers properly wherever your project requires it.

You do not need to attribute MapToPlay. You can if you want to, and I will obviously appreciate it, but you are not obligated to credit MapToPlay just because you used the export tools.

Stan, Developer of MapToPlay