Split an Image Into a Grid of Tiles
Slice one photo into a rows × columns grid and download every tile as its own image. Exact pixel boundaries, no gaps, no upload.
What this page does
Cuts a picture into a grid of equal tiles, with any remainder pixels distributed at the right and bottom edges so no pixel is lost. Each tile is a separate download.
How to use it
Choose a file, set the options and press Render. Example: a 1200 × 800 PNG split into 2 columns and 2 rows becomes four 600 × 400 PNGs, named tile-r1-c1 to tile-r2-c2.
How it works
Column and row boundaries are computed as floor(i × width / columns), so every tile but the last few is the same size and the total still equals the source. Each tile is copied with putImageData, never resampled.
What it refuses
Zero rows or columns, a grid larger than the pixel count allows, a tile smaller than one pixel, or an image over the cap is refused by name.
Where it runs
The picture is decoded and redrawn on a canvas in this tab: there is no upload, no network request and no model, so the pixels never leave your device. It opens PNG, JPEG, WebP, GIF, BMP and AVIF up to 16,000,000 pixels (16 MP) and 25 MB per file; anything larger is refused with its measured size rather than drawn blank.
Cuts a picture into a grid of equal tiles, with any remainder pixels distributed at the right and bottom edges so no pixel is lost. Each tile is a separate download.
Column and row boundaries are computed as floor(i × width / columns), so every tile but the last few is the same size and the total still equals the source. Each tile is copied with putImageData, never resampled. The picture is decoded and redrawn on a canvas in this tab: there is no upload, no network request and no model, so the pixels never leave your device.
Worked example: a 1200 × 800 PNG split into 2 columns and 2 rows becomes four 600 × 400 PNGs, named tile-r1-c1 to tile-r2-c2.
How to use the split an image into a grid of tiles
Choose an image file, set the options, and press Render. The result appears below the form.
Example: a 1200 × 800 PNG split into 2 columns and 2 rows becomes four 600 × 400 PNGs, named tile-r1-c1 to tile-r2-c2.
The picture is decoded and redrawn on a canvas in this tab: there is no upload, no network request and no model, so the pixels never leave your device.
- Columns — 1 to 12
- Rows — 1 to 12
- Output format — one of png, jpeg, webp
- Quality (JPEG and WebP) — 1 to 100
What the canvas draws
Cuts a picture into a grid of equal tiles, with any remainder pixels distributed at the right and bottom edges so no pixel is lost. Each tile is a separate download.
Column and row boundaries are computed as floor(i × width / columns), so every tile but the last few is the same size and the total still equals the source. Each tile is copied with putImageData, never resampled.
- Every option is declared by this page, so an unknown choice or an out-of-range number is refused by name before any pixel is drawn.
- The preview and the download are the same canvas: what you see is the file you get.
What it refuses, and what it leaves out
Zero rows or columns, a grid larger than the pixel count allows, a tile smaller than one pixel, or an image over the cap is refused by name.
It opens PNG, JPEG, WebP, GIF, BMP and AVIF up to 16,000,000 pixels (16 MP) and 25 MB per file; anything larger is refused with its measured size rather than drawn blank.
- Not the right page for: computing sprite-sheet frame rectangles from typed numbers, which is the sprite splitter
- Not the right page for: cutting along a custom path
What to Expect
Best for
- making an Instagram grid from one picture
- cutting a poster into printable tiles
- splitting a sprite sheet you already have
Not ideal for
- computing sprite-sheet frame rectangles from typed numbers, which is the sprite splitter
- cutting along a custom path
What this tool keeps
- Every source pixel, exactly once
- The row and column order in the file names
- Transparency in PNG and WebP
What may need cleanup
- Reassembling the tiles in order
- Using a JPEG output only when the tiles have no transparency
Common errors
- A tile count larger than the pixel count is refused
- A remainder is given to the last column and row, so tiles can differ by one pixel
- JPEG output flattens transparency
Example use cases
- A 3 × 3 Instagram grid
- Tiled printing of a large poster
Sample input
a 1200 × 800 PNG split into 2 columns and 2 rows
Sample output
four 600 × 400 PNGs, named tile-r1-c1 to tile-r2-c2
Who this is for
- Social media managers
- People printing a large image on a small printer
Frequently asked questions
Does my image get uploaded anywhere?
The picture is decoded and redrawn on a canvas in this tab: there is no upload, no network request and no model, so the pixels never leave your device.
What is the maximum image size?
It opens PNG, JPEG, WebP, GIF, BMP and AVIF up to 16,000,000 pixels (16 MP) and 25 MB per file; anything larger is refused with its measured size rather than drawn blank. The limit exists because a browser tab has to hold the decoded bitmap in memory.
What happens if the file cannot be decoded?
The page refuses it by name — unsupported type, decode failure, zero pixels, or above the pixel cap — and shows the measured size rather than drawing a blank canvas. The file you chose stays selected so you can correct one option and try again.
Will the tiles line up when I put them back together?
Yes. The boundaries partition the width and height exactly, so the tiles' pixel counts add up to the source. A column that does not divide evenly gives its extra pixel to the last tile.
How many tiles can I download at once?
Up to 144 (12 by 12). Each tile is rendered as its own image in this tab; the page lists a download button per tile and never posts anything.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.