Toolvore

Image Splitter

Split an image into grid tiles with no gaps or lost edge pixels, then download the tiles as a ZIP.

This tool runs entirely in your browser. Your data is never uploaded, never stored, and never leaves your device.

Image Splitter divides one still image into up to 100 PNG tiles with exact pixel coverage, individual downloads and a ZIP containing a coordinate manifest.

How to use it

  1. 1Select one supported still PNG or JPEG.
  2. 2Choose one to ten rows and columns and inspect the preview grid.
  3. 3Split the image, then download individual tiles or the ZIP with manifest.json.

Example

Input
7 × 5 PNG; 2 rows × 3 columns
Output
6 tiles covering 35 pixels, plus a JSON manifest

Widths are 2, 2, 3 and row heights are 2, 3; no edge pixels are dropped.

What happens to your data

The image is decoded, cropped, encoded and packaged in this browser. No source or filename upload is required. The downloaded manifest deliberately includes the original filename and tile coordinates; check it before sharing.

Last updated October 2026

Divide one image into a grid of separate PNG tiles. Choose rows and columns, inspect the grid preview, then download individual tiles or one ZIP containing all tiles and a JSON coordinate manifest. The source is partitioned without resizing, overlap or missing edge pixels.

This is useful when a large visual needs to be handled as smaller pieces, when preparing tiles for a layout, or when a precise grid is easier to work with than repeated manual crops. Rows are numbered from the top and columns from the left, with predictable filenames such as row-01-col-02.png.

How it works

Select one still PNG or ordinary 8-bit JPEG up to 10 MiB, 12 million pixels and 8,192 pixels per side. The tool inspects the actual container before decoding; animated PNG, compound JPEG, 16-bit PNG and other formats are rejected. Supported transparency is retained in each PNG tile. The browser's displayed orientation determines the coordinate system, so a rotated JPEG can have a different displayed width and height than its raw encoded frame.

Choose one to ten rows and one to ten columns, with a maximum of 100 tiles. There cannot be more columns than source pixels across or more rows than source pixels down: every tile must contain at least one pixel. Grid boundaries use floor(column × width ÷ columns) and floor(row × height ÷ rows). This divides the complete raster even when the width or height is odd. Tiles in the same dimension differ by at most one pixel; they are not padded or stretched to become identical sizes.

For a 7 × 5 image split into two rows and three columns, the column widths are 2, 2 and 3 pixels, and the row heights are 2 and 3 pixels. All six PNG files together cover the original 35 pixels exactly once. The preview outlines show those boundaries but are not painted into the exported files. Each tile is encoded as PNG, and combined output is limited to 60 MiB.

The ZIP also contains manifest.json with the source filename and decoded dimensions, chosen grid, and each tile's name, row, column, x, y, width and height. Pixel coordinates start at zero in the top-left corner; row and column numbers start at one. Use these coordinates to reassemble or place the pieces. The manifest includes the source name, so review it before sharing. PNG export does not retain original metadata or color profiles, and browser rendering may normalize colors. For an arbitrary single crop use Crop Image; for a grid of multiple source photographs use Image Contact Sheet; use ZIP Extractor to inspect the resulting archive.

Worked example: Split an odd-sized image without losing edge pixels

Input
7 × 5 PNG; 2 rows × 3 columns
Result
6 PNG tiles; widths 2, 2, 3 and heights 2, 3

ZIP includes manifest.json; the tile areas sum to all 35 source pixels.

Common use cases

  • Dividing a diagram into reproducible grid pieces
  • Preparing image tiles with coordinates for a document or layout
  • Splitting odd-sized artwork without silently trimming an edge
  • Producing numbered PNG crops and a manifest for later reassembly

Frequently asked questions

What happens when the image dimensions do not divide evenly?+

The tool uses integer boundaries across the entire source. Some tiles become one pixel wider or taller than others. No pixels are discarded, duplicated, stretched or padded to force equal tile dimensions.

What is included in the image splitter ZIP?+

Every tile is a PNG named by its one-based row and column. The archive also contains manifest.json with the original filename, decoded dimensions, grid settings and exact zero-based crop coordinates for each tile.

Do the grid lines appear in the downloaded tiles?+

No. Dashed lines belong to the on-page preview only. The PNG files contain their source crop, including supported transparency, without a line or border added around it.

Can I reassemble the original image from the tiles?+

The manifest provides each tile's x and y position and dimensions, so placing them on a canvas of the reported source size reconstructs the browser-rendered raster. It does not reconstruct the original compressed file, metadata, profiles or higher source precision.

Does this automatically publish a social media grid?+

No. It prepares files locally and does not connect to an account or publish anything. Platform cropping, image order and supported aspect ratios are separate requirements that you should check at the destination.