Crop images in your browser with a draggable rectangle and 1:1, 4:3, 16:9 aspect locks — downloaded at full source resolution, with zero uploads. Runs entirely in your browser — your numbers never leave this device.
No image loaded yet. Cropping happens on this device at the image's full resolution — the preview is scaled to fit, but the download is cut from the original pixels.
| Aspect | Width : Height | Common use |
|---|---|---|
| Free | Any | Cutting out exactly the region you frame |
| 1:1 | 1 : 1 | Profile pictures, avatars, Instagram posts |
| 4:3 | 4 : 3 | Classic photo prints and older displays |
| 3:2 | 3 : 2 | DSLR / 35 mm photo proportions |
| 16:9 | 16 : 9 | Video frames, thumbnails, wallpapers |
| 9:16 | 9 : 16 | Stories, reels and phone wallpapers |
The cropper shows your image scaled to fit the page, but the rectangle you drag is tracked in source pixels — the readout under the image reports the rectangle's x, y, width and height in the original image's own coordinates, and the download is cut from the full-resolution pixels, never from the scaled preview. Dragging inside the rectangle moves it, the corner handle resizes it, and dragging on the image outside it starts a new rectangle; every movement is clamped so the rectangle can never leave the image or shrink below one pixel.
Aspect locks hold the rectangle's shape while you work: Free allows any proportions, while 1:1, 4:3, 3:2, 16:9 and 9:16 hold width ÷ height at that ratio — switching to a lock reshapes the current rectangle to the ratio, and resizing then grows or shrinks it in shape. That is the workflow behind most real crops: lock 1:1 for a profile picture, position the square over the subject, resize from the corner, and download. Output is PNG, JPEG or WebP, encoded from the cut region at its true size — a 2000 × 2000 crop downloads as a 2000 × 2000 file.
The image is decoded on your device with its EXIF orientation applied, so what you see is upright and the coordinates you read are the upright image's coordinates. Nothing is uploaded at any stage: decoding, cropping and encoding all run in your browser's memory, no copy of your photo reaches a server, and the tool works offline once loaded.
No. The photo is decoded, displayed, cropped and encoded entirely in your browser — it never leaves your device, is never stored anywhere, and the tool works with the network off. The page you loaded is the whole tool.
Yes. The on-screen image is a scaled preview (at most 720 px wide) so it fits the page, but the rectangle is tracked in source pixels and the output canvas is built at the rectangle's true w × h from the decoded original. The live readout shows those source-pixel numbers, and the download's dimensions match them exactly.
Because crop rectangles are clamped inside the image: the size is first limited to the image's dimensions, then the position is pulled back so the whole rectangle fits. A crop can therefore never include pixels that do not exist — there is no padding or empty border option, deliberately.
Yes, deliberately. Phone cameras often store the pixels sideways with an EXIF orientation flag saying how to display them. The cropper reads that flag and applies it on load, so you crop the picture as you see it, and the coordinates and output both refer to the upright image.
PNG for an exact, lossless cut of a screenshot or graphic (and the only choice that keeps transparency); JPEG for photographs destined for sharing or upload size limits; WebP for photographs staying on the web, where it usually produces the smallest file of the three.
More in Image Tools · Browse all tools