Files & Images Runs locally Ready to use Built-in examples No tracking

Image Grid Cutter

Slice one image into grid tiles locally: 3×3, 2×2 and other row/column combos from 2 to 6, with per-tile sizes shown. Tiles download one by one and nothing leaves your device.

A square social post wants a grid: cut one wide picture into tiles, post them in order, and the timeline shows a single continuous image. Three by three, two by two or four by four — the rows and columns are yours to choose, and when the size does not divide evenly the leftover pixels are absorbed into the edge tiles, so the grid still reassembles seamlessly.

When the dimensions do not divide by the grid, the remainder goes to the last row and column and is drawn inward, so the tiles fit back together exactly. The tiles are always lossless PNG, which means a JPG source will grow (run it through a compressor afterwards if that matters). Images with a centred subject and some margin work best; faces or text running to the edge may be cut, so preview each tile before posting.

—
—

How to use

  1. Load the image to slice.
  2. Choose the grid: rows and columns from 2 to 6.
  3. Check the per-tile sizes that are shown.
  4. Download the tiles and post them in order.

How it works

Cut in three steps

Choose an image, pick the grid (default 3x3) and press cut — the tile dimensions appear below, then download the nine tiles one by one; post them in numbered order.

How remainder pixels are absorbed

When the image's width or height doesn't divide evenly by rows/columns, the remainder pixels are absorbed inward by the last row/column, so all tiles reassemble seamlessly with no black edges or gaps.

Posting order matters

When posting to a feed, select images strictly left-to-right, top-to-bottom (the app keeps selection order); add no captions between tiles or the full-picture effect breaks.

Which photos cut well

Photos with a centered subject and generous margins cut best; faces or text hugging the edges may split across tiles — preview each tile before posting.

Code example

JavaScript 9-grid tiles (last row/column absorbs the remainder) 

// the catch: when width/height do not divide evenly the last tiles take the remainder
function gridCut(img, rows, cols) {
  const tileW = Math.floor(img.width / cols);
  const tileH = Math.floor(img.height / rows);
  const tiles = [];
  for (let r = 0; r < rows; r++) {
    for (let c = 0; c < cols; c++) {
      const x = c * tileW;
      const y = r * tileH;
      // last column / last row swallow the remainder
      const w = c === cols - 1 ? img.width - x : tileW;
      const h = r === rows - 1 ? img.height - y : tileH;
      const canvas = document.createElement('canvas');
      canvas.width = w;
      canvas.height = h;
      canvas.getContext('2d').drawImage(img, x, y, w, h, 0, 0, w, h);
      tiles.push({ row: r + 1, col: c + 1, canvas });
    }
  }
  return tiles;
}

Python Tiling with Pillow 

from PIL import Image

img = Image.open('photo.jpg')
rows, cols = 3, 3
tile_w, tile_h = img.width // cols, img.height // rows

for r in range(rows):
    for c in range(cols):
        x, y = c * tile_w, r * tile_h
        w = img.width - x if c == cols - 1 else tile_w
        h = img.height - y if r == rows - 1 else tile_h
        img.crop((x, y, x + w, y + h)).save(f'tile-{r + 1}-{c + 1}.jpg', quality=92)

FAQ

Are images uploaded when cutting?

No. Coordinate math and pixel cropping happen in your browser, and the nine tiles go straight to download — nothing leaves your machine, and closing the page erases everything.

Why aren't all tiles the same integer size?

When dimensions don't divide evenly (say a 320-pixel height across 3 rows: 106 each with 2 left over), the last row/column absorbs the remainder — the whole still assembles seamlessly.

Can I cut 2x2 or 4x4?

Yes. Rows and columns each span 2-6, composing 2x2 four-tile, 3x2 six-tile, 4x4 sixteen-tile layouts; the 3x3 grid is the feed classic.

What format are the tiles?

Uniformly PNG — lossless and universally supported. JPG sources decode then save as PNG: slightly larger but pixel-perfect; run the site's image compressor afterwards if size matters.

My feed posted in the wrong order — what now?

The app orders images by selection sequence. Filenames carry numbers (assigned at download), so select in numeric order; a mistake means delete and repost.

Can very large images be cut?

Keep within 30 MB and 8,000 pixels per side. Bigger ones may fail to decode on device memory — downscale with system tools first; after cutting, each tile still has ample resolution.

Is this the same as cropping?

No. Cropping shrinks the picture to one region; grid cutting divides one image into equal tiles that reassemble into the original. They combine well — crop the composition first, then cut.