Aseprite Tilemap Guide: Grid Size, Modes, and Workflow Tips for Pixel Artists
Aseprite’s tilemap feature is powerful — it’s just not obvious
The tilemap layer in Aseprite was built to let pixel artists draw and reuse tiles without leaving their main workflow. Set up right, you design tiles once and place them across a canvas like a mini level editor, all inside the same file you used to draw the art. The problem most people hit isn’t that the feature is weak — it’s that the documentation glosses over several setup decisions you have to get right from the very beginning.
Creating a tilemap layer: the decision that locks you in
Go to Layer > New > New Tilemap Layer (or press Space+N). Aseprite will ask for a tile width and tile height. This is the moment that matters most. The grid size you set here is fixed for the life of that layer — there is no menu option to change it after creation.
If you’ve already built a layer with the wrong grid size, the cleanest path is to delete it and start over. One partial workaround: if you need to expand the canvas, use Sprite > Canvas Size (not Sprite Size). Canvas Size respects the tile grid alignment and won’t produce a misaligned partial tile at the edge. Sprite Size scales the whole image and will break your grid. The distinction matters.
The three tileset modes
Once a tilemap layer exists, you work in one of three tileset modes. These control how Aseprite reacts when you draw on the canvas — and switching between them changes behavior completely.
Manual mode
You control the tileset entirely. Drawing on the canvas modifies individual tile content without creating or reordering anything in the tileset. Use this when your tileset is already finished and you don’t want Aseprite touching its structure. It’s the most predictable mode for artists working from a pre-designed tile sheet.
Auto mode
Aseprite watches what you draw and generates new tiles automatically. Paint a unique pixel pattern into a cell, and a new tile appears in the tileset. This is the fastest way to build a tileset from scratch — just draw and let Aseprite catalog the tiles as you go. The downside is you can end up with a lot of near-duplicate tiles if you’re not deliberate.
Stack mode
Similar to Auto, but Aseprite tries to group related tiles together, clustering ones that share pixel data or transformations. Less common for everyday work, but useful when your tileset follows strict visual rules like terrain transitions or corner pieces that need consistent organization.
Pixels mode vs Tiles mode
This toggle is responsible for a huge portion of tilemap confusion. When a tilemap layer is selected, you can switch between two sub-modes using Space+Tab or the small icon at the top-left of the canvas area.
- Tiles mode: clicking and painting places tiles from the tileset onto the map grid. You’re arranging tiles, not drawing pixels.
- Pixels mode: your tools draw actual pixel data into the tile’s content. This is how you edit or correct individual tiles.
Most day-to-day confusion comes from being in the wrong one. Drawing in Tiles mode stamps the wrong tile; drawing in Pixels mode edits a tile when you meant to place a different one. Check the mode indicator before troubleshooting anything else.
Why artists keep recommending Tiled instead
Tiled (mapeditor.org) is a dedicated tile map editor. It handles multi-layer maps, object layers, custom properties per tile, and exports formats like TMX and JSON that game engines read directly. Aseprite’s tilemap was built for a different job: drawing and animating tiles inside the same file you use for your sprites. These two tools are not really competing.
A common workflow for indie developers: draw and animate tiles in Aseprite, then build levels in Tiled. The reason artists reach for Tiled for level design isn’t that Aseprite fails — it’s that Tiled was built exclusively for that task and carries years of level-design-specific features that Aseprite isn’t trying to replicate. They solve different problems.
Getting tiles into a game engine
Aseprite can export tilemap data. File > Export Sprite Sheet generates a flat spritesheet PNG from your tileset, and most engines — Godot, Unity, GameMaker — can import that directly. For full map layout data, Aseprite’s native .aseprite format can be parsed by community-built loaders, and there are Lua scripts available that export to formats like LDtk or Tiled’s TMX if your engine expects those.
The documentation gap is real
The official docs cover the feature, but they assume you already understand the underlying model. The grid-size lock, the mode confusion, the Pixels/Tiles toggle — you’ll hit all of these in the first session and piece together the answers from community threads rather than from any single clear guide. A structured video walkthrough from the Aseprite team would cut the learning curve significantly. Until that exists, the GitHub docs source and community forums are where the practical answers actually live.
Sources