Documentation
Everything I could fit in writing about how GridCraft works.
GridCraft is a tile-map editor. It runs in your browser at gridcraft.dev, and there's a desktop build for Mac, Windows, and Linux. You don't need an account to open the web editor and start painting. You do need one to save to the cloud or to use the desktop app.
Web vs desktop
The web editor and the desktop app share the same code. Same tools, same exporters, same plugin API. The desktop build adds: local file system access without the browser's save-dialog dance, drag and drop to open a file, built-in Git, the MCP server for AI agents, and LAN hosting for local collaboration.
The web build runs in any current browser with WebGL. No install. Use Open to load a .tmx or .tmj and start editing.
Free vs paid
The web editor itself is free. Sign in and you get:
- 3 cloud-saved maps.
- 25 MB of total cloud storage.
- 1 bound desktop device.
- Cloud sync across that device and the browser.
Real-time collaboration is included from the free plan (up to 3 people per map). Paid plans raise the storage and map limits, add version-history backups, and increase your collaboration seat count. Pricing lives on the pricing page.
Where to start
- New to GridCraft? Read tile layers first, then tilesets.
- Coming from Tiled? Open a .tmx file and skim Open a Tiled file.
- Shipping to an engine? Pick the format from the Export section.
- Building integrations? The API reference has the routes.
A note on these docs
GridCraft is still in active development. Some sections of the editor change between releases. Where a doc page describes a thing that isn't shipped yet, you'll see “Coming soon” on it. If a page doesn't match what you see in the editor, the editor wins, and please tell us at [email protected].