Cut one large picture into a set of smaller pieces for a social grid, a carousel or a print layout. Set equal columns and rows, or type your own weights when the design needs a wide banner and two narrow panels.
Every piece is sliced from the original file at full resolution, with numbered filenames so the order stays obvious. All processing runs locally in your browser. Your data is not uploaded to any server. 100% Local
Tiles are numbered left to right, then top to bottom, like words on a page. Tile 1 sits in the top-left corner, tile 4 is the first piece of the second row in a three-column grid, and the last tile is bottom-right. The downloaded filenames repeat that position as tile-row-column, so you can rebuild the picture later without guessing which piece belongs where.
Weights let one image feed different layout slots. Typing 50,30,20 creates three columns where the first is half the width and the other two split the rest. Row weights of 60,40 make a tall header band above a shorter footer band. Values are normalised, so 3,2 and 30,20 produce the same result; any positive numbers work, and invalid or missing entries fall back to an equal grid.
A single square image can be divided into nine posts that form one picture on a profile page. Start with a 1080 by 1080 source, choose three columns and three rows, and check the guides so faces and text stay inside their own tiles. Each piece is 360 by 360. Upload in reverse order when the grid fills from the newest post backwards.
Tall infographics rarely fit a single social post. Split the artwork into three or four horizontal bands with row weights that follow natural section breaks, then publish the bands as a carousel. Keep the top band slightly taller if it carries the title, and avoid cutting through a sentence or a chart label. PNG keeps thin lines and small type crisp.
Vertical comics are read panel by panel, but print and archive copies often need equal page sizes. An uneven grid lets you keep a wide splash panel intact while ordinary panels stay uniform. Work from the highest-resolution source available, leave a few pixels of margin at each boundary, and export PNG so line art does not pick up compression noise.
Print shops and wall-display projects often want an image divided into physical panels of identical size. Choose the number of panels that matches your frames, verify that each tile keeps enough resolution for the print size, and download the set in order. For a seamless wall piece, avoid JPG at low quality and use PNG or a high-quality WebP instead.
Yes. Each tile is drawn from the loaded source image at its original pixel size, not from the smaller preview on screen. A 2400 by 1800 photo split into three columns and three rows produces nine pieces of roughly 800 by 600 pixels each, with no downscaling before the cut.
Pixel boundaries must be whole numbers, so a remainder is distributed across the cuts. Splitting 1000 pixels into three columns gives widths of 333, 334 and 333. The difference is a single pixel and is invisible in normal use, but it explains why the exported files can differ by one pixel.
No archive is created. The browser saves each tile as a separate file with a short pause between downloads, because only a page can trigger those saves. Allow multiple downloads when the browser asks, and check your downloads folder for files named by row and column.
Start with a square source such as 1080 by 1080 pixels, set three columns and three rows, and keep the guides visible while you confirm the crop. Each tile comes out at 360 by 360 pixels, which fits the feed grid. Upload the pieces in reverse order if your profile grid fills from the bottom left.
Only the first frame is used, so the tiles are still images. Animated output would need a frame-by-frame pipeline that this tool does not provide. For static GIF, JPG, PNG and WebP files the split behaves normally, and PNG is the safest choice when tiles contain text or sharp edges.