How to divide an image into tiles
Choose a static JPG, PNG or WebP from your device. The file must be at most 20 MiB, 20 megapixels and 8192 pixels on either side. Its dimensions are read automatically; you do not need to type the source size.
Set Rows and Columns and inspect the grid on the original image. Choose Split image to generate the actual PNG tiles. Check the tile previews and dimensions, then Download ZIP to save them all. Each tile can also be saved individually. Grid lines and the transparency checker are preview aids and never appear in the saved PNGs.
How the pixel boundaries work
The image is divided without resizing or discarding edge pixels. When a dimension is not divisible by the number of parts, tile sizes can differ by one pixel. Integer boundaries divide the original width and height, so adjacent tiles meet with no duplicated or missing row or column.
Tiles are numbered from left to right across the first row, then through each following row from top to bottom. A filename such as tile-005-r02-c02.png records its sequence, row and column. Browser-applied image orientation is used for both preview and export. The visible pixels are retained; original EXIF metadata and color profiles are not copied to the PNG tiles.
Two concrete examples
A 1200 × 900 image split into 3 rows and 4 columns makes 12 tiles, each 300 × 300 pixels. Rows divide height; columns divide width. To make only two vertical strips, use 1 row and 2 columns.
A 101 × 67 image split into 3 rows and 4 columns makes column widths of 25,25,25,26 pixels and row heights of 22,22,23 pixels. The first tile is 25 × 22 and the last is 26 × 23. Their combined coverage still contains every original pixel. Transparent areas stay transparent in PNG output.
Limits, output and recovery
Use positive whole numbers for both settings, with at most 100 tiles in total. A tile must contain at least one pixel. For example, a two-pixel-wide source cannot be divided into three columns. The output limit is 100 MiB. A large compressed source may still use substantial memory; reduce its dimensions if the device cannot finish.
Animated PNG and animated WebP are rejected rather than silently exporting the first frame. GIF, SVG, HEIC and other formats are outside this tool’s scope. A filename extension alone is not enough: the image structure is checked before decoding. Damaged files may still be rejected by the browser.
All output is PNG, including when the source is JPEG or WebP. ZIP groups these files without recompressing them. It is not a promise of smaller files. This tool does not add bleed, overlap, print-page margins or social-network posting order. Use the row and column labels to arrange the tiles for your own destination.
Changing Rows, Columns or the file immediately discards the previous generated output, while the grid preview follows the current settings. Remove clears the source but keeps settings. Cancelling discards unfinished output. Files are processed in the tab and are lost on reload unless you download them.
Frequently asked questions
Are all tiles exactly the same size?
Only when both dimensions divide evenly. Otherwise adjacent sizes differ by at most one pixel so no boundary pixels are lost.
Is the transparent background preserved?
Yes, PNG output keeps decoded transparency. The checker pattern is not part of the image. JPEG sources have no transparent channel to recover.
Will joining the tiles restore the source file?
It restores the decoded image’s pixel layout when tiles are placed without gaps. It does not restore original metadata, compression bytes or an embedded color profile.
Why does a file fail even under 20 MiB?
Pixel count, side length, animation, damage and browser decoding support also matter. The file-size limit alone does not guarantee a valid image.