Drop a PNG into the splitter above and it cuts a grid of tiles that stay PNG. Transparency is kept, nothing is recompressed, and every pixel in a tile is identical to the pixel it came from. The default is 3 by 3 and any grid up to 20 by 20 works.
Drop an image here
or , or paste with Ctrl+V
JPG, PNG, WebP, GIF, BMP and AVIF, up to 50 MB.
Drag any line to move a cut. Tab to a line and use the arrow keys to nudge it one pixel, or hold shift for ten.
Vertical cuts give side-by-side pieces. Horizontal cuts stack them.
The tool picks the rows and columns that keep the pieces closest to square.
A shared strip on each seam, so the sheets can be trimmed and taped.
Each piece is resized to the size this page targets before it is saved.
Your image never leaves your device. Splitting runs in your browser with the Canvas API.
| Quality | Lossless. PNG has no quality setting, so every piece is pixel for pixel what went in. |
|---|---|
| Transparency | Kept. Transparent pixels stay transparent in every piece. |
| Animation | Only the first frame. An animated GIF or WebP is split as a still. To keep every frame, use the GIF splitter. |
| Pieces | 9, in 3 rows of 3 |
| Pieces from a 1080 × 1080 Instagram square | 360 × 360 px |
| Pieces from a 1080 × 1350 portrait | 360 × 450 px |
| Pieces from a 4000 × 3000 phone photo | 1333 × 1000 px, last piece 1334 × 1000 px |
| Pieces from a 1920 × 1080 screenshot | 640 × 360 px |
PNG is the format to split when the pixels matter more than the file size.
It is lossless, so a tile written as PNG holds exactly the pixels that were in that part of the source. Split a PNG into nine tiles, put them back together, and you get the original file's pixels back with no drift. That is not true of JPG, where each round trip re-encodes and each re-encode changes something.
It also carries an alpha channel, which is the reason most PNG splits exist. Game sprites, UI assets, logos and cut-out artwork all rely on transparency, and any tool that quietly converts them to JPG replaces it with white. Tiles exported here stay PNG, and the transparent areas stay transparent.
What you pay for that is size. PNG compression works on runs of identical pixels, so it does very well on flat colour, type and interface screenshots, and quite badly on photographs. A photographic PNG can be several times the size of the same picture as a JPG. Nine tiles from a large photographic PNG can add up to a big ZIP.
A useful side effect: tiles are often smaller than a ninth of the source, because each one contains less variety than the whole picture did and compresses better on its own.
Processing runs on a canvas in this page. Nothing is uploaded.
Sprite sheets and UI atlases are almost always PNG because they need transparency. Splitting them back into individual assets has to preserve that alpha channel, or every sprite comes out on a white square. For sheets with padding or an offset before the first cell, use the sprite sheet splitter.
Artwork with a transparent background splits into tiles that keep it. That matters when the tiles are going to be placed over different backgrounds, which is usually the point of a cut-out in the first place. Nothing is flattened and no matte colour is added anywhere.
PNG is the right format for screenshots because flat colour and text compress well and stay sharp. Splitting a long capture into readable pieces keeps every letterform exactly as it was rendered, where a JPG export would soften the edges of small type.
Tile sets for map libraries and engines are usually PNG, since edges have to be exact and any compression artefact shows at a tile boundary. A lossless split means neighbouring tiles butt up with no visible seam. Split by tile size when the pixel dimensions are fixed by whatever loads them.
Drop the PNG into the splitter above and set the rows and columns you want, up to 20 by 20. The tiles are written as PNG by default, so transparency and every pixel value survive. Download them one at a time or take the whole set as a ZIP.
Yes, as long as the output format stays PNG or WebP, since both carry an alpha channel. Choosing JPG output flattens the transparent areas onto a solid background colour instead, because the JPG format has no way of storing transparency at all.
No. PNG is lossless, so each tile contains exactly the pixel values that were in that part of the source. There is no re-encoding penalty and no generation loss, which means you can split, edit and split again without anything degrading along the way.
PNG compresses runs of similar pixels, which works well on flat colour and badly on photographs. A photographic PNG is simply a big file, and splitting it does not change that. If the tiles do not need transparency, exporting them as JPG or WebP will cut the size considerably.
Yes. Choose JPG as the output format and every tile is encoded as JPG at quality 92, whatever the source format was. Any transparent areas are flattened onto a background colour of your choice first, since JPG cannot store an alpha channel.
Files up to 50 MB. Because tiles are processed one at a time rather than on a single large canvas, a big lossless PNG splits without exhausting browser memory. Sources past roughly 60 megapixels show a warning instead of failing part way through.