1Drop in the picture
One at a time. It stays on your device — this tool uploads nothing at all.
2Set the grid
Choose how many across and down. The cut lines appear on the picture as you change them.
3Save the pieces
A zip of the tiles, numbered in order, with a page that shows them back in their grid.
Questions
How do I cut a photo into a 3x3 grid?
Drop it in, leave the grid at 3 by 3, and save. You get nine files numbered by row and column, plus a page that puts them back together so you can check the cut before you use them. If you want squares, crop the picture square first and then cut it — a 3 by 3 of a rectangular photo gives nine rectangles, not nine squares.
Does splitting lose any quality?
The cut itself moves pixels without altering them. What costs something is saving afterwards: a JPEG is re-compressed, so there is a small generational loss, while a PNG or a WebP is written back in the same format it came in and stays exact. A screenshot or a sprite sheet is almost always a PNG, which is the case where this matters and the case where nothing is lost.
Can I slice a sprite sheet into individual frames?
Yes, and that is one of the two reasons this exists. Set the columns and rows to the frame grid — twelve across and one down for a strip, four by four for a sheet of sixteen — and the tiles come out numbered in reading order with the numbers padded, so they stay in order in a file listing instead of jumping from frame 1 to frame 10.
Are the tiles all exactly the same size?
Within a pixel, and that is deliberate rather than sloppy. A width that does not divide evenly has to go somewhere: dividing and rounding down throws the remainder away and loses the last sliver of the picture, so instead each cut is placed at its own rounded position. The tiles then differ by at most one pixel, they abut exactly, and every pixel of the original ends up in exactly one of them.
Do my pictures get uploaded?
Not on this page. The cutting happens in your browser on your own device, so the picture is never sent anywhere and no copy of it is stored — there is nothing a server could do to a cut that the browser cannot do faster.