Trim the dead space off a logo, shave an exact margin off any edge, or cut an image into halves, quarters or a grid — all in your browser.
Image Trimmer cuts the wasted space off the edges of an image — the transparent border around an exported logo, the white margin around a scan, the letterbox bars on a screenshot — and can also slice an image into halves, quarters or an even grid.
A logo exported from a design tool almost always carries a ring of empty pixels around it. That padding is invisible until you place the logo somewhere: then it refuses to sit flush, looks smaller than everything beside it, and no amount of nudging fixes it, because the file itself is mostly nothing. Auto-trim reads in from all four edges, finds the first row and column that are not background, and cuts there — so the file becomes exactly the shape of the artwork. You can then pad an even margin back on, or square the result up, which is what a profile picture or an app icon needs.
Exact edges does the opposite job: you say how much to take off each side, in pixels or as a percentage, and it obeys. That is the quick way to strip a watermark strip along the bottom, drop a fixed header off a batch of screenshots, or shave the black bars off a video still. Percentages make it safe across images of different sizes.
Split cuts one image into several. Halves, quarters, or any grid up to 20 by 20 — each piece comes out as its own file, numbered by row and column, and the whole set downloads as a single ZIP. It is how a tall graphic becomes an Instagram carousel, or how a sprite sheet gets taken apart.
Everything is drawn on a canvas inside this page, so the images never touch a server — and because the trim is a straight pixel copy, nothing is re-compressed unless you choose a lossy output format.
Yes. As well as JPEG, PNG, WebP, GIF, BMP, ICO and AVIF, this tool reads HEIC and HEIF from a phone, TIFF, Photoshop PSD and PSB, TGA, Netpbm, Apple ICNS, and camera RAW from every major brand — CR2, CR3, NEF, ARW, DNG, ORF, RAF, RW2 and the rest. Anything the browser cannot open by itself is decoded on your own device, in the page, before the tool touches it.
It samples the four corners of the image and treats that colour as the background, then walks in from each edge until it hits a row or column that differs by more than the tolerance you set. If the corners are transparent it trims on transparency instead. Transparent only forces that second behaviour, which is what you want for a logo that happens to have white corners you need to keep.
The preview opens on Result, which is the finished image — on a logo whose margin was already transparent, a trimmed result can look much like the original on screen because the empty space you removed was invisible to begin with. The size line under the preview is the proof: it reads, for example, 800 x 600 to 440 x 200, 82% of the area trimmed away. Switch to "What gets cut" to see the original with the discarded area dimmed and outlined.
The edges are not uniform enough. A photograph rarely has a flat border, and a JPEG of a white background often has faint speckle from compression. Raise the tolerance until the preview outline moves — around 10 to 15 percent handles most JPEG whitespace.
No. A trim is a straight copy of the pixels you keep, so nothing is resampled. Quality only changes if you choose JPEG or WebP as the output for an image that started as a PNG, because those formats re-encode.
Yes, as long as the output format keeps it. Auto and PNG both do. JPEG has no transparency at all and will fill the empty area with white, so the tool warns you before that happens.
Choose Split, then Left / right halves or Top / bottom halves. The cut lands at the exact midpoint, and if the image has an odd number of pixels the extra one goes to the first piece so nothing is lost.
Yes. Drop them all in and set the options once — they apply to every image. Percent-based edges are the reliable choice for a mixed batch, since a fixed pixel amount means something different on a small image than on a large one. Download everything as a single ZIP at the end.
There is no artificial limit. Images are processed one at a time on your own device, so the ceiling is your browser memory — very large images or very big batches will simply take longer.