Aseprite Tilemap: What the Docs Don’t Tell You About Grid Sizes, Modes, and Workflow
The Grid Size Is Locked — and That’s Not a Bug
If you’ve spent time clicking through Aseprite’s grid settings trying to resize a tilemap layer’s grid and nothing’s changing, here’s why: the tile dimensions are fixed at the moment of creation. No amount of poking at View > Grid > Grid Settings will change them after the tilemap layer already exists. You’re not missing a step. The option just isn’t there post-hoc.
The only reliable fix is to delete the tilemap layer and create a new one with the correct grid size. Annoying, but knowing it upfront is half the battle. The practical habit is to draw a single test tile on a regular layer first, measure the pixel dimensions you actually need, and then create the tilemap layer. Commit to those numbers before you build anything.
What Aseprite’s Tilemap Actually Is
Aseprite has had a proper tilemap system since version 1.3. A tilemap layer works similarly to an indexed color layer: instead of color indices pointing to a palette, each grid cell holds a reference to a tile stored in an associated tileset. Edit a tile in the tileset and every cell that references it updates simultaneously. That’s the core payoff — consistency across the whole canvas without redrawing.
The tileset is the collection. The tilemap is the arrangement.
Two Drawing Modes, Three Submodes
With a tilemap layer active, Aseprite puts you in one of two main modes. Toggle between them with Space+Tab:
- Draw Pixels mode — you edit the pixel contents of individual tiles. Every instance of that tile on the canvas reflects your changes instantly.
- Draw Tiles mode — you place and remove tiles on the grid without touching their pixel contents. This is where map layout happens.
Inside Draw Pixels mode, three submodes control how Aseprite manages the tileset as you paint:
- Manual (Space+1) — full user control. Nothing is auto-created or deleted. You decide which tile you’re editing.
- Auto (Space+2) — the default. Aseprite watches what you paint, generates new tiles for unique patterns, and prunes tiles no longer in use. It tries to behave like a normal paint layer. This is also the source of most unexpected tileset reshuffling.
- Stack (Space+3) — each unique brush stroke generates a new tile without removing existing ones. Tiles accumulate. Good for quickly building up a varied tileset.
A lot of tilemap confusion comes from not knowing which submode is active. Auto mode in particular can feel chaotic until you understand it’s reorganizing the tileset as you draw.
Canvas Size vs. Sprite Size — Don’t Mix Them Up
To expand your working area, go to Sprite > Canvas Size, not Sprite Size. Sprite Size scales the entire image — tile pixel contents and all. Canvas Size just adds room around the edges. Use multiples of your tile dimension (if your tiles are 16×16, expand in increments of 16) to keep the grid aligned.
The Tile Editor and Symmetry
When you click into a tile to edit it, every instance of that tile on the canvas updates at the same time. Pair this with Aseprite’s symmetry mode and it becomes genuinely useful: set a symmetry axis at the center of a tile and left-right mirroring applies to the whole tile automatically. For repeated elements like walls or doorways this saves significant time.
If the symmetry guide line blends into your tileset colors, the grid color is adjustable at Edit > Preferences > Grid.
Aseprite and Tiled Aren’t Actually Competing
When artists recommend Tiled, they’re usually comparing different things. Aseprite’s tilemap is built for creating and organizing tiles within the same tool you use for spriting and animation. It’s not a level editor. Tiled is a dedicated map editor built for assembling large levels, adding object and collision layers, and exporting to game engines in formats they understand.
Most practical pipelines use both. Aseprite handles tile creation, pixel editing, and animation. Tiled handles map assembly, object placement, and engine export. Aseprite’s tilemap feature is genuinely useful for keeping a tileset organized and seeing tiles in context while you draw — it just was never meant to replace a purpose-built level editor.
Practical Workarounds for the Grid Size Problem
If you’re stuck with the wrong grid size after already building out tiles, the cleanest path is:
- Export the existing tileset as a flat PNG spritesheet.
- Delete the tilemap layer.
- Create a new tilemap layer with the correct dimensions.
- Recreate or reimport the tiles into the new tileset.
There’s also a community extension called Resize Grid on itch.io that adds keyboard-shortcut-driven grid adjustment. It works around the limitation rather than removing it, but it can speed things up for some workflows.
The real takeaway: lock in your tile size before you start. 16×16 covers most retro-style work. 8×8 for very small assets. 32×32 when you want more detail per tile. The tilemap system is structured around that decision being made first — everything downstream depends on it.
Sources