Drop a JPG into the splitter above and it cuts a grid of tiles, 3 by 3 to start with and up to 20 by 20. Each tile is written once at quality 92, which you can raise or lower. Nothing is uploaded and the split runs in your browser.
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 | 0.92 by default, which is 92 on the slider. Drag it down for smaller files. |
|---|---|
| Transparency | Dropped. JPG has no alpha channel, so transparent areas come out filled in. |
| 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 |
JPG is what almost every photo arrives as, so this is the format most splits start and finish in.
The thing to understand about splitting a JPG is that the tiles are new files. A JPG cannot be cut without being decoded to pixels and encoded again, so each tile goes through exactly one re-encode. At the default quality of 92 that is very hard to see on photographic content, and one generation is the least it can possibly be. What causes visible damage is doing it repeatedly: splitting a tile, editing it, saving it, splitting again. Each pass costs a little.
The quality slider is there for the cases where the default is not right. Push it up toward 100 for a tile that is going to be edited further, or down if the tiles are going somewhere that will recompress them anyway.
One thing that does not survive: metadata. The tiles are drawn on a canvas and written fresh, so EXIF from the original, camera model, exposure, GPS, is not carried into them. That is a privacy advantage more often than a loss, but if you need the metadata, keep the source file.
Rotation is handled properly. A photo shot sideways carries an orientation flag, and it is applied when the file is decoded, so the tiles come out the right way up.
Nothing is uploaded.
Feed posts are JPG at the far end whatever you upload, so exporting JPG tiles at quality 92 costs nothing visible and keeps the files small enough to upload from a phone. Use the Instagram presets if you also want the square crop, the 4:5 padding and the posting order.
A 24 megapixel JPG is unwieldy to send and slow to open. Splitting it into tiles gives pieces that are quick to handle while keeping the original resolution in each one, since nothing is scaled down during the split. Only the pixel count per file changes.
Tiles are written fresh from a canvas, so EXIF including GPS coordinates and camera details does not carry over. If you are sharing pieces of a photo and would rather not share where it was taken, splitting to JPG removes that as a side effect of how the export works.
JPG at high quality is fine for photographic prints and much smaller than PNG. For anything going across several sheets of paper, use the print splitter instead, which works from a physical size and adds the overlap and cut marks that taped sheets need.
Drop the file into the splitter above and set the rows and columns, up to 20 by 20. The tiles appear in the preview immediately and are exported as JPG at quality 92 by default. Download them separately or take the whole set as a single ZIP.
Each tile is decoded from the source and encoded once, which at quality 92 is very hard to see on photographic content. One generation is the minimum any JPG split can cost. Repeated split-edit-save cycles are what accumulate visible damage, not a single pass.
92 suits almost everything. Go higher, toward 100, if the tiles will be edited and saved again, since each save adds another generation of loss. Go lower only if file size is the constraint and the destination will recompress the images anyway.
No. Tiles are drawn on a canvas and written as new files, so camera model, exposure settings and GPS coordinates from the original are not carried over. Keep the source file if you need that data. For sharing, the removal is usually welcome.
They should not here. Cameras often store a photo in the sensor's own orientation and record the rotation separately as a flag, and tools that ignore that flag produce sideways tiles. This one applies the flag when it decodes the file, so what you see in the preview is what you get.
Yes. Choose PNG as the output format and each tile is written losslessly, with no further JPG compression applied on top. The tiles come out considerably larger than JPG ones would, and they cannot recover any detail the original JPG had already thrown away.