Start with your game engine's own tile map tools when the whole level lives inside one project, and move to a standalone tile map editor when the person drawing levels needs a separate workspace or a specific export. Either way, judge it on one thing: can a designer change a room and a developer play that change without anyone redoing work by hand?
Tilemap Studio describes itself as a tilemap editor for Game Boy, GBC, GBA, NDS, SNES, Genesis or TG16 projects. That one line says a lot about this category. A tile map editor isn't a neutral drawing surface; it's shaped by where the finished map has to go, and the right one for a modern engine game can be the wrong one for a cartridge-era homebrew project.
So I've built this page around the questions that decide the choice, rather than a ranking. The tools themselves sit in the middle, each with a single line on what it does, and the second half is about testing one against a room from your own game.
What game makers ask before laying out a tiled level
What does a tile map editor do that a paint program can't?
It builds a level from tiles that belong to a tileset, placed on a grid, instead of painting pixels onto one big image. The editors on this list talk about tile layers, which means you can keep the floor, the walls and the decoration on separate layers and change one without touching the others. Test the payoff early: change the art for one tile and check it updates everywhere that tile sits in the map.
Should the map live inside my engine or in a separate editor?
If the level is made and played inside one project by the same small group, I'd start with the engine's own map tools. There's nothing to export, nothing to import and no second file format to keep in step. A standalone editor makes more sense when the person drawing levels wants their own workspace, or when the map needs to come out in a specific format for an engine, a framework or a console toolchain. It's a fork worth settling before you look at a single feature, because it decides which half of this list you're reading.
Does it matter who's drawing the levels?
More than anything else here. A programmer laying out test rooms will put up with clumsy menus if the data comes out clean. A level designer who spends whole days in the tool won't, and they're the one who'll feel every slow brush and every missing undo. Watch the person who'll use it build a room before you decide; their speed after twenty minutes tells you more than any feature list.
What should the export look like before I commit?
Check that the editor writes a format your engine or code can read without a converter you'd have to maintain yourself. Tilesetter, for example, says it builds and exports levels directly to Unity, Godot and GameMaker Studio 2. Whatever you pick, export a map, open it in your project, change the map and export again. Then check whether anything a developer added on the engine side survived the second export or got overwritten. That round trip is the part I'd test hardest.
Is a browser-based editor sensible for a team?
It can be, especially when designers are on different machines and you'd rather nobody installed anything. The things to test are the dull ones: where the map file is saved, whether you can download it in a format your engine reads, and what happens to your work if you close the tab halfway through. Don't assume any of these; try each one with a throwaway map first.
When does it help for the editor to draw the tiles as well?
When one person is making the art and the levels at the same time. A tool that pairs a tile and sprite editor with a map editor lets you fix a tile and see it across the level straight away. If you already draw in a dedicated art app, you may prefer to keep doing that and only lay out maps here. Test how the map editor picks up a tileset you've changed outside it.
What about retro console projects?
They're their own small world, and I wouldn't assume a general editor knows the target system's limits. An editor aimed at those systems is the type to look at; check that it lists the exact console you're targeting before you spend an evening learning it.
Nine editors for laying out tiled 2D levels
Tiled
A standalone 2D tile map editor built around multi-layer tile editing, so a map is stacked up from several tile layers at once.
OGMO Editor
Here, tile layers let designers construct each level from the tiles that belong to a chosen tileset.
Godot TileMapLayer
Godot's own route to tiled levels: designers build them from TileMapLayer nodes without leaving the engine.
Sprite Fusion
Runs in the browser and lets a level designer put together a two-dimensional map from tiles right there.
Tilemap Studio
Retro-minded and specific about it: a tilemap editor aimed at Game Boy, GBC, GBA, NDS, SNES, Genesis and TG16 projects.
Tilesetter
Levels built in this editor export straight to Unity, Godot or GameMaker Studio 2 projects.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Defold Tile Map Editor
Part of the Defold engine: a tile map component for assembling a map inside the game project itself.
Construct Tilemap
Inside Construct, the Tilemap object is there to make tile-based projects easier to design.
Tile Studio
Two jobs in one application: a bitmap editor for tiles and sprites, paired with a map editor for designing level maps.
One room from your own game, rebuilt tile by tile
You'll need a tileset before any of this. If you draw your own, my guide to the best pixel art apps will sort out the drawing first; if you want placeholder art while the real tiles are made, start with the AI sprite generators instead.
Do you make tile map editors? Tool makers can ask to be considered for a featured place on this list.
How do I test an editor against a room I already have?
Take one real room from the game you're making, not a demo map, and your own tileset image. Rebuild that room in the editor using at least two layers: ground on one, walls or props on another. Export it, load it into your project and walk a character through it. Then hand the map to whoever designs your levels, ask them to move one wall and add a doorway, export again, and play the change. If that loop took no hand edits on the engine side, you've learned more than a week of reading would tell you.
Keep the editor's own site open in another tab while you work. An engine's built-in map tool comes with the engine, so there's nothing extra to weigh there. For a standalone editor, find its pricing page and the licence terms for a commercial release, and read both before your test room turns into a whole level. Where neither is stated clearly, that's a question for the maker before you commit months of maps to their format.
What should I check when the art changes?
If your tileset is likely to grow during the project, a map that breaks every time it does is a map you'll end up redrawing. Add a few new tiles to the end of your tileset image, save it and reopen the map. Check that the tiles you'd already placed still point to the right art. Then try the riskier change, moving a tile to a different spot in the image, and see what the editor does with it.
Can AI tools fill in the tiles for me?
I'd keep AI on the art side, the tiles and sprites that go into a tileset, rather than expecting it from the map editor. That's a separate job with its own tools. Whatever made the tiles, the map editor still has to place them on a grid you control.
Six months in: what to look at again
The editor that suited a one-person prototype won't always suit the game half a year later, and the signs tend to be changes around the tool rather than in it. A tile map editor is the handover point in a 2D game: the artist's tileset goes in, the designer's rooms come out, and the developer's code has to read them. When any of those three people or formats changes, it's time to look at the choice again.
A dedicated level designer joining is the shift to watch for first. Rooms that a programmer was happy laying out inside the engine can feel slow to someone who does nothing else all day, and that's when a standalone editor with its own workspace starts to make sense. The reverse happens too: when the team shrinks back to one or two people, the export step that once kept designer and developer apart becomes overhead, and the engine's own map tools look better again.
A change of engine or a port to new hardware is the other big trigger. Check that the editor's export still lands in the new engine without a converter, and if the port is to an older console, look at an editor built for that exact system. Remote collaborators are a smaller one: when people join on different machines, a browser-based editor can save everyone an install, as long as the save and download test from earlier still holds.
Then look at the round trip itself. If someone on the team is fixing exported files by hand, converting formats with a script nobody wants to touch, or rebuilding rooms after every tileset change, the tool has stopped saving time. Switching mid-project hurts, so rebuild one finished room in a replacement before you move anything else across, and keep the old maps until the new ones play the same. The tools around the map change over these months too, and my round-up of AI tools for game development covers that wider set, from art to code to testing.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.


