From the shop Need battlemaps to split? Browse 600+ hand-drawn maps
Visit Etsy
Tools / Maps / Map splitter
Maps · Free tool

Slice a battlemap into printable tiles.

Upload one big map, choose a grid, get a zip of evenly-sized tiles. Optional overlap for taping printed sheets together. Mirror of the stitcher.

Drop a battlemap here
or click to browse · PNG, JPG, WEBP up to 30 MB
No image loaded
Renders locally · nothing uploaded
2
2
0px
#A33D2A
Tip
For printable poster tiles, use 2 × 2 or 3 × 2 with about 30px overlap. For VTT scene shards, leave overlap at 0.

Field notes

Splitting battlemaps for print and VTT.

The two reasons you ever want to split a map are mechanical, not aesthetic. Either the map is too large to print on one sheet, or it is too large to load comfortably into a virtual tabletop. Both problems have the same shape: take one big image, cut it into evenly-sized tiles, and let the user reassemble the pieces in their preferred medium.

Printing across A4 or US Letter sheets

A standard battlemap intended for the table is around 24 by 36 inches. No home printer handles that on a single sheet. A 3 × 2 split at A4 gets you 6 sheets that, taped together, make a poster-sized map. Add a small overlap (20 to 40 pixels) so you have margin to glue or tape over the cut, then trim the white edge of every sheet before assembly.

Splitting for VTT scenes

Some VTTs, especially older Roll20 sessions, struggle with very large background images. Splitting a 8000 × 6000 dungeon into a 4 × 3 grid of smaller scenes loads faster and lets the DM teleport players between scenes as the party moves. Use 0 overlap and name the tiles by row/column so transitions stay coherent.

Picking the grid

The chip presets cover the common cases. Use the columns and rows sliders for irregular splits. For example, a long corridor map probably wants 4 × 1 rather than 2 × 2. The preview shows the cut lines overlaid on your image so you can see exactly where the splits will fall before downloading.

Privacy and limits

The image is loaded into a local canvas and split entirely in the browser. No upload happens, and nothing is stored after you close the tab. The practical limit is around 8000 × 8000 pixels, which is the standard browser canvas cap. For larger sources, scale down first or run two passes.

FAQ

No. Splitting happens entirely on the client using the HTML5 Canvas API. The image is never uploaded; closing the tab clears everything.

Two main reasons. For VTTs, splitting a huge map into smaller scenes keeps load times sane. For printing, splitting lets you tile a poster-sized map across A4 or US Letter sheets that you can tape together.

Overlap adds a strip of pixels from the neighbouring tile on each edge. Useful for printed maps that you want to glue or tape, since the overlap gives you a margin that hides any cut imperfection.

PNG. The zip is named with the original file stem and grid dimensions, and tiles inside are named row-column for easy ordering (e.g., r1c1.png, r1c2.png).

Not in this tool. Each tile is the same size, because the source image is divided evenly. If your map needs irregular cuts, do it in an image editor instead.

Around 8000 × 8000 pixels comfortably. Beyond that, browser canvas limits start to bite. For very large maps, downscale first or split in two passes.