Image Splitter
Cut one image into rows and columns of equal tiles. Every pixel of the original ends up in exactly one tile, and you can save them all in one zip.
How to use it
- Choose a picture and pick a layout, or type the number of columns and rows.
- The preview shows where the cuts fall.
- Save one tile at a time, or take them all in a single zip.
Nothing is lost at the edges
Not every picture divides evenly. A 1000-pixel width cut into three is 333.33 pixels a tile, and there is no such thing as a third of a pixel. The careless answer is to make every tile 333 wide and quietly drop the last pixel; do that on both axes and you have lost a strip along two edges without saying so.
Here every cut is placed at the nearest whole pixel to where it belongs, so the tiles differ from each other by at most one pixel and together they cover the picture exactly. Put them back side by side and you get the original, pixel for pixel.
For a carousel
Cut the picture into columns — three across, say — and post the tiles in order, left to right. Swiping through then pans across the original, which is why a panorama looks so good split this way. The layouts marked across are for exactly this.
For a profile grid, the order is backwards
A grid of posts shows the newest first, at the top left. So to make the finished grid read as one picture, the tile that belongs at the bottom right has to be posted first, and the top left one last. The second file-naming option numbers the tiles that way, so file 01 is the first to post and you can simply upload them in name order.
What no page can tell you is how a given service crops each thumbnail in its grid, and services have changed that before. Post one tile and look at how it displays before you commit the rest.
Quality
Each tile is copied straight out of the original at full resolution — nothing is shrunk. Splitting a small picture into many tiles makes small tiles, and no tool can add detail that was not captured. If each tile has to be a certain size, work backwards: the original needs to be that size times the number of tiles.
Frequently asked questions
Are any pixels lost when it does not divide evenly?
No. Every cut is placed at the nearest whole pixel, so tiles differ by at most one pixel and together cover the picture exactly. Nothing is trimmed off the edges.
In what order should I post a profile grid?
Newest posts appear at the top left, so post the bottom-right tile first and the top-left tile last. Choose 'posting order' for the file names and 01 is the first to post.
How big should the original be?
As big as each tile needs to be, multiplied by the number of tiles. Three tiles across that each need to be 1080 wide means an original 3240 wide. Splitting a small picture gives small tiles - detail that was not captured cannot be added.
Why a zip instead of separate downloads?
Browsers will not let a page start a dozen downloads in a row without asking about each. One zip is a single download, and each tile also has its own button if you only want one.
Is my picture uploaded?
No. The tiles are cut out and packed into the zip by your own browser. Nothing is sent to a server.
Is my text sent anywhere?
No. Everything happens in JavaScript inside your own browser. Nothing is uploaded and nothing is saved - close the tab and it is gone.