Image Splitter
Slice an image into a grid of tiles and download them individually or as a ZIP. Processed entirely in your browser.
Drop an image or click to browse
Processed entirely in your browser — nothing is uploaded
How the Image Splitter works
Choose how many rows and columns you want, and the tool divides your image into an even grid using the HTML5 Canvas API — each cell is cropped and re-encoded as its own image file. This is handy for splitting a single graphic into an Instagram carousel grid, cutting up a large image into puzzle pieces, or breaking a banner into tiles for a CSS sprite sheet. The last row and column absorb any rounding remainder so every pixel of the source image is accounted for and no sliver is left uncropped.
Download tiles one at a time by hovering a tile and clicking its download icon, or grab everything at once as a single ZIP archive (built locally — no server round-trip). For the reverse operation, or to crop a single region instead of a full grid, try the Image Cropper.
Built and maintained by Meet Shah · Last updated
What this tool is used for
- Slicing an image into a grid for a social media carousel.
- Cutting a sprite sheet back into individual frames.
- Splitting a large scan into printable tiles.
- Producing tiles for a puzzle or a game asset.
- Cutting a panorama into segments for a layout.
Frequently Asked Questions
- What is splitting an image for?
- Instagram carousel grids, sprite sheets, tiled printing, and anywhere a single large image has to be delivered as several pieces. The split is exact — pixels are copied, not resampled — so reassembling produces the original.
- What happens when the dimensions do not divide evenly?
- The last row or column comes out smaller, because the remainder has to go somewhere. Cropping the source to a multiple of the tile count first avoids a strip of tiles that do not match the rest, which is visible immediately in a grid layout.
- Does splitting reduce quality?
- Only through re-encoding. PNG output is lossless, so the tiles are bit-exact. JPEG output re-compresses each tile independently, and because JPEG works in 8×8 blocks, a tile boundary that does not align to that grid introduces artefacts along the seam.
- Why do the seams show when I reassemble?
- Usually independent JPEG compression per tile, which quantises each one slightly differently. Using PNG for the split removes it entirely. A visible seam on a platform that re-encodes your upload is not something the split itself can prevent.
- What order are the tiles in?
- Left to right, top to bottom — reading order — which matters for a carousel where the platform posts them in filename order. Getting the order wrong is the most common way a grid post assembles into nonsense.
Common errors and gotchas
- Splitting a lossy image and re-encoding every tile, which adds artefacts to each.
- Choosing a grid that does not divide the dimensions evenly, leaving a partial row or column.
- Losing the tile order, without which the pieces cannot be reassembled.
- Assuming tiles are the same size when the source dimensions are not divisible.
- Splitting before resizing when the target tile size was fixed.