Drop a WebP into the splitter above and it cuts a grid of tiles exported as WebP at quality 90. WebP tiles are usually smaller than JPG tiles of similar quality and can carry transparency. If your browser cannot encode WebP, the tool falls back to JPG automatically.
Drop an image here
or , or paste with Ctrl+V
JPG, PNG, WebP, GIF, BMP and AVIF, up to 50 MB.
Drag any line to move a cut. Tab to a line and use the arrow keys to nudge it one pixel, or hold shift for ten.
Vertical cuts give side-by-side pieces. Horizontal cuts stack them.
The tool picks the rows and columns that keep the pieces closest to square.
A shared strip on each seam, so the sheets can be trimmed and taped.
Each piece is resized to the size this page targets before it is saved.
Your image never leaves your device. Splitting runs in your browser with the Canvas API.
| Quality | 0.9 by default, which is 90 on the slider. Drag it down for smaller files. |
|---|---|
| Transparency | Kept. Transparent pixels stay transparent in every piece. |
| Animation | Only the first frame. An animated GIF or WebP is split as a still. To keep every frame, use the GIF splitter. |
| Pieces | 9, in 3 rows of 3 |
| Pieces from a 1080 × 1080 Instagram square | 360 × 360 px |
| Pieces from a 1080 × 1350 portrait | 360 × 450 px |
| Pieces from a 4000 × 3000 phone photo | 1333 × 1000 px, last piece 1334 × 1000 px |
| Pieces from a 1920 × 1080 screenshot | 640 × 360 px |
WebP sits between the two formats most people know. It compresses better than JPG at a similar visual quality, and unlike JPG it can carry transparency, which PNG does at a much larger file size.
That makes it a good output format for anything going on the web. Nine tiles exported as WebP will usually total less than the same nine as JPG, and considerably less than as PNG if the source has flat colour or an alpha channel.
The catch is encoding support. Reading a WebP is widely supported now. Writing one from a canvas is not universal, and some browsers quietly hand back a different format instead of failing. That is worse than an error, because you end up with files that have the wrong contents for their name.
So the tool checks. After each tile is encoded it inspects what actually came back, and if the browser did not produce WebP it re-encodes as JPG and names the file accordingly. You get working tiles either way, and the format shown in the download list is the format you actually have.
Quality defaults to 90. WebP holds up better at a given quality number than JPG does, so 90 here is roughly comparable to a higher JPG setting.
Sources in any supported format can be exported as WebP, not just WebP ones. All of it happens in your browser with nothing uploaded.
Tiles destined for a website benefit from WebP twice over: each file is smaller than the JPG equivalent and transparency still works. That matters most when a page loads many tiles at once, where the saving per file adds up to a meaningfully faster load.
A cut-out image split into tiles needs an alpha channel, and PNG makes that expensive on anything photographic. WebP keeps the transparency at a fraction of the size. Check that whatever displays the tiles supports WebP before committing to it.
The source does not have to be WebP. Drop in a JPG or a PNG and choose WebP output, and the tiles come out converted. That saves a separate conversion pass when you are preparing images for a site and splitting them at the same time.
WebP files downloaded from the web often will not open in older desktop software. Splitting one here and exporting the tiles as JPG or PNG is a practical way to get usable pieces out of a file your other tools refuse to read.
Drop the file into the splitter above and set the rows and columns, up to 20 by 20. Tiles are exported as WebP at quality 90 by default, and you can switch the output to PNG or JPG if the destination does not handle WebP.
The tool checks what actually came back from each encode. If the browser produced something other than WebP, it re-encodes the tile as JPG and names the file accordingly, so you never end up with a file whose contents do not match its extension.
Usually, at a comparable visual quality, which is the main reason to use it for images on a website. The saving varies with the picture: flat colour and graphics benefit most, dense photographic detail least. Export one tile in both formats and compare if the difference matters.
Yes. WebP carries an alpha channel the way PNG does, at a much smaller file size on photographic content. That makes it a good output format for splitting cut-out artwork and logos, as long as whatever ends up displaying the tiles supports WebP.
Yes. The output format is independent of the source, so any supported input can be exported as WebP. Converting a PNG to WebP keeps the transparency and usually cuts the file size sharply. Converting a JPG adds one more generation of lossy encoding.
Lossy WebP tiles are re-encoded once, the same way JPG tiles are, which at quality 90 is hard to see. Choosing PNG output avoids any further loss but produces much larger files. A single re-encode is the minimum any lossy split can cost.