Instagram Grid Maker and Image Splitter

Pick the shape first: three columns wide by one, two, three or four rows, which is three, six, nine or twelve posts. Load your photo and the tool fits it to a canvas of 1,080 pixels per tile, so a three by three grid is cut from 3,240 by 3,240 pixels. Each tile is written out at 1,080 by 1,080 and numbered by the order you post it, with tile 1 at the bottom right. Download them all, then post them one at a time from 1 upward. Nothing leaves your browser at any point: the file is read locally and cut on a canvas, so there is no upload step, no account and no queue.

From tile 1 upward, and tile 1 is the bottom right of your picture. Instagram places your newest post at the top left of the profile grid and pushes everything already there down and to the right, so the piece you want at the bottom right has to be the oldest, which means posting it first. The top left piece goes last. It is the one thing people get wrong, and not only people: of the fifteen splitters we read in August 2026, five state the rule correctly, two state it backwards and eight say nothing at all. Numbering the tiles by posting order removes the step where you have to reverse anything.

At least 1,080 pixels for every column, so 3,240 pixels wide for a three column grid. Instagram keeps a shared photo at up to 1,080 pixels wide (Instagram Help Center, image resolution, August 2026), and each tile becomes its own post, so each one wants its own 1,080 pixels. Below that the tiles are enlarged rather than cut from real detail. The readout under the grid prints the number: it names your source dimensions, how many pixels are trimmed to fill the canvas, and how many pixels of your original sit behind each tile. If that last number is under 1,080, the export is an enlargement and the tool says so.

Because that is Instagram's documented ceiling. Its help article on image resolution says a photo shared at a higher resolution is sized down to a width of 1,080 pixels, and one shared below 320 pixels is enlarged to 320 (August 2026). Exporting a tile at 2,000 pixels wide therefore buys nothing, because Instagram resamples it anyway, and exporting at 720 gives away detail you had. Meta's paid specs for a feed image recommend 1,440 by 1,800 pixels, which is a different surface with a different pipeline, and that mismatch is where a lot of the conflicting advice online starts. For an organic grid post, 1,080 is the number that applies.

PNG is the default here because it is lossless: the tile you download is exactly what the canvas drew, with no fresh compression stacked on top of whatever your original already carried. JPEG at quality 92 is the alternative and gives much smaller files, which matters when you are moving twelve tiles onto a phone. Either way Instagram re-encodes on upload, so the choice affects your own copies more than the published result. One documented detail decides it for some people: Instagram's own publishing API accepts JPEG only, so if you are pushing tiles through a scheduler rather than the app, export JPEG (Instagram Platform, content publishing, August 2026).

No. The file is read by your browser with FileReader, drawn onto a canvas and written back out as a data URL, all inside the page. There is no server call in this widget at all, which you can confirm for yourself by opening your browser's network tab while you cut a photo. That check is worth running on any tool you use. Of the fifteen splitters we tested in August 2026, one posted the image file to a server through a multipart form, and the number of third-party hosts each page contacted while the photo sat on screen ran from zero to thirty-one. Contacting a host is not the same as sending your photo, but it is the part you can actually measure.

No. It is arithmetic and a canvas. The tool works out a crop rectangle from your image dimensions and the grid shape you picked, draws each rectangle into a 1,080 by 1,080 canvas and hands you the result. The same photo with the same settings gives the same tiles every time, with no model in the loop, no queue and no usage limit, which is also why it keeps working with the page open and nothing else. Where a splitter could plausibly use a model is deciding where to crop around a face or a horizon, and this one deliberately does not: it centres the crop and tells you how many pixels that cost.

The profile grid shows each post in a frame taller than a square, so a 1:1 tile is displayed with its left and right edges cropped, while the full square is still what opens when someone taps it. For a puzzle grid the seams still line up, because every tile loses the same proportion. What you lose is detail sitting near a tile's outer edges, so keep faces, logos and text nearer the middle of each one. The crop arithmetic, and exactly what it takes off a square post, is worked through on the Instagram feed planner, which previews a whole profile instead of cutting one photo.

Not as a grid. Each tile is an ordinary post, so you can archive or delete individual tiles, but deleting one leaves a hole and every piece around it shifts up, which breaks the picture. Editing a caption is safe. Removing or adding a post is not. Two practical consequences follow. First, cut and check the whole run before you publish anything, because the preview here costs nothing and a republished grid costs your audience nine notifications. Second, publish the run in one sitting, since a half built grid is what every visitor sees until the last tile goes up.