Grid-building plugins for Godot 4 compared: build mode vs editor tools
What the Godot 4 grid placement options actually are, what each one covers, and which fits a runtime build mode. Verified against each project's own documentation.
Search "Godot grid placement" and you get two completely different categories of tool mixed together, which is the main reason people buy the wrong thing. So the criteria first, before any scoring — then what each option actually does.
Decide which of these you need
- Runtime build mode — your player places objects in the game: ghost preview, validation, save/load.
- Editor placement tooling — you place objects while building the level: palettes, snapping, scattering.
An editor tool cannot do a build mode, and a build-mode plugin will not help you dress a level. Nearly every mis-purchase in this space is that mismatch.
The rest of this page compares runtime options. I build one of them, so treat the criteria and the limits as the part to check hardest — every competitor claim below is quoted from that project's own store page or repository on 2026-10-28, and the links go straight to the source.
The roll-your-own baseline
Godot already gives you the pieces: GridMap for 3D cells, TileMapLayer for 2D, and
PhysicsDirectSpaceState queries for collision checks. Free, and you own every line.
What you write yourself, in roughly the order it bites:
- multi-cell footprints and rotation that actually swaps width/height
- per-cell validation that reports which cells are blocked, not just "invalid"
- occupancy bookkeeping that survives demolishing from any cell of a multi-cell object
- save/load that still lines up after JSON turns every integer into a float
- an input mode layer that does not fight your existing camera and selection code
That is not a reason to avoid it — for a single-cell, one-grid game it is often the right call. It is a reason to price the weeks honestly before comparing against a $40 plugin.
The runtime options
Grid Placement (this site)
Paid, $40, commercial licence with full editable GDScript. Godot 4.5+.
- 2D and 3D in one plugin:
TileMapLayerandGridMap - square, isometric, and hex grids
- placement, validation, previews, move/rotate/demolish, terrain brushes (single cell, line, rectangle, outline, flood fill)
- game-economy hooks: costs, unlocks, optional demolish refunds
- save/load hooks you wire to your own format
- a styled build UI you restyle from one theme file
- five demo projects (top-down, isometric, hex, platformer, 3D) and a GdUnit4 suite over placement behaviour
- free browser demos, so it can be judged before buying
Its honest limits: it is a placement layer, not a game framework. No tech tree, no multiplayer, no economy simulation — the cost rules call into your inventory, they do not replace it. If your game needs one flat 2D grid and nothing else, it is more than you need and you should read the next entry.
Place Lite (Mikuji)
Commercial, on itch. Godot 4.2 or newer, pure GDScript, no C# or GDExtension.
- 2D grid placement with a ghost preview that keeps the object's own colour
- per-cell refusal marks the exact blocked cells, with a cross as well as red (colour-blind readable)
- rotation with a footprint that swaps, so a 1×3 fits a one-wide corridor upright and refuses on its side
- drag to place a line; remove from any cell of a multi-cell object
- blocked terrain filled from your own
TileMap - custom rules through one callable,
func(cell, def_id) -> bool, feeding the same per-cell highlight - versioned save/load dictionary that survives a JSON round trip
- 17 tests / 81 checks run from the command line, including the cells-left-of-origin truncation bug
Its honest limits: stated by its own page — no resources, no build costs, no tech tree, no roads, no terrain painting, no isometric projection, no multiplayer. It is the placement layer only, and deliberately small.
Build Placement Template (flatymen)
Commercial, on itch. Godot 4.3 or newer.
- grid-based object placement with ghost preview and placement validation
- per-object resource costs checked before placement, wired to your inventory through a documented interface
- destroy and move, with a configurable refund percentage
- build menu with automatic buildable discovery and folder-based categories
- navigation blocking and inventory interfaces, five methods to implement
- full demo project and documentation
Its honest limits: by its own description it has no rotation system and no terrain painting, and is not a city-builder framework. The core loop is preview → validate → build → move → destroy.
Godot In Game Building System (MarkoDM)
Free, MIT, on GitHub — 94 stars.
- grid building and free-form building in the same starter kit
- save/load with optional encryption
- event bus, menus and building UI, auto-generated docs
- explicitly a starter kit:
BuildingSystem→BuildingSystemGrid→GridCell→BuildableInstance
Its honest limits: the repository's last push was 2024-05-13, so it has not tracked Godot 4.3–4.5 changes. Read the code before adopting it for a 4.5 project; a starter kit is also a starting point, not a drop-in plugin. Free and MIT make that trade reasonable — just budget the integration.
The editor tools, so you can rule them out quickly
These come up in the same searches and do a different job:
- GoPlacer — free, MIT, editor palette placement with floor/rotation snapping. Level blockout, not player build mode.
- AssetSnap — MIT, editor asset library with snapping, scattering and array modifiers. Same category. Last push 2025-02-04.
- Tile to Gridmap — MIT, draws a 3D GridMap from 2D TileMap layers. Terrain generation from tiles, not placement rules for players. Last push 2026-08-06.
- TileMapLayer3D — editor painting of 3D tile-based levels from tilesheets.
- Godot's own
GridMap+TileMapLayer— the baseline above.
None of these implement a player-facing build mode, and that is fine: they are not trying to.
Side by side
| Grid Placement | Place Lite | Build Placement Template | In Game Building System | |
|---|---|---|---|---|
| Cost | $40 | commercial | commercial | free, MIT |
| Godot | 4.5+ | 4.2+ | 4.3+ | 4.x, last push 2024-05 |
| 2D / 3D | both | 2D | not stated as 3D | both |
| Grids | square, iso, hex | square (2D) | grid | grid + free |
| Per-cell validation | yes | yes | yes | in starter kit code |
| Rotation | yes | yes, footprint swaps | no | starter kit |
| Terrain painting | yes, 5 brush modes | no | no | no |
| Resource costs | hooks | no | yes | starter kit |
| Save/load | hooks | versioned dict | not stated | yes, optional encryption |
| Full source | yes, GDScript | yes, GDScript | yes | yes, MIT |
| Test suite | GdUnit4 | 17 tests / 81 checks | not stated | not stated |
| Browser demo | yes | no | no | no |
Which one
- One flat 2D grid, smallest possible scope — Place Lite, or roll your own if it is single-cell.
- Base-building loop with costs and refunds, 2D — the flatymen template covers that loop directly.
- Free, willing to integrate — the MIT starter kit, after checking it against your Godot version.
- Square + isometric + hex, 2D and 3D, terrain brushes, a shipped build UI — Grid Placement.
If you are still deciding, the free browser demos on the Grid Placement page run the actual plugin in a real project, which is a faster read than any table.