fileformer
search⌘KtranslateENexpand_moreupload_fileConvert
Converters8 file families · 44 direct conversions
What changes in a conversionarrow_forward
home/image-tools/crop-image

Crop image

Crop an image to a free shape or an exact ratio, square for profiles, 4:5 for feeds, 16:9 for video, with composition guides, exact pixel input and a check that nothing you cropped out is left in the file.

imageloading sample… · 2400 × 1800
Image being cropped
1296 × 1620
ThirdsCentreOff
Drag the box or its corners, type exact pixels, or drop an image on the preview. Cropping and encoding run in your browser; it all stays on your device.
~/where-to-put-the-subject

Three framing rules that make crops look deliberate.

Rule of thirdsPlace the subject on one of the four points where the thirds lines cross. It feels balanced but alive, the most-used rule in photography.Use it for:portraits, landscapes, products.
Centre itPut the subject dead centre for symmetry and impact. Works best when the scene itself is symmetrical, or the subject is bold.Use it for:profile photos, logos, architecture.
Leave room to lookGive space in front of where the subject faces or moves. A face near the edge looking out of frame feels cramped.Use it for:people, animals, anything in motion.
~/how-much-you-keep

Cropping throws pixels away.

A crop doesn't blur anything, the pixels you keep are untouched. But the smaller the crop, the fewer pixels are left, and zooming back in later will look soft. Your current crop keeps 48.6% (2.1 MP) of the original.

Tip: for a 1080 px Instagram post, a crop needs at least 1080 px on its short side to stay sharp.

Original2400×1800
Your crop1296×1620
Tight 1:1 at 10401040×1040
Minimum for a 1080 post1080×1350
~/lossless-jpeg-crop

A JPEG can only be cropped losslessly on its block grid.

JPEG stores pixels in 8 × 8 blocks, grouped into MCUs of 8 or 16 pixels depending on colour subsampling. A crop whose top-left corner lands on that grid can keep the compressed blocks as they are. Anywhere else, every block has to be re-encoded, and the new block edges fall through the middle of the old ones. Below, a region of your crop is re-saved twice, once on the grid, once off it, and compared with the source pixels.

Source file
FormatJPEG
Chroma subsampling4:2:0
MCU (block grid)16 × 16 px
Estimated quality90 (exact IJG table)
Your top-left240, 90
Lossless cropoff grid by 0, 10
jpegtran -crop 1296x1620+240+90 -copy none -optimize in.jpg > out.jpgLossless block cropping applies to JPEG sources only. PNG crops are always lossless.
On the grid…
PSNR…
max error…
file…
Off the grid…
PSNR…
max error…
file…
scienceRunning the re-save experiment…
Error maps show |source − re-saved| summed over R, G and B, brightened 5×; pink lines mark the source file’s MCU grid. Both re-saves use the same encoder and quality, so the only difference is where the blocks fall. PSNR is measured over RGB against the decoded source.
~/what-a-crop-leaves-behind

The cropped-out part can still be in the file.

Viewers show the cropped image, but two well-known mistakes keep the original around: an editor that copies the old EXIF block (with its thumbnail of the full photo), and a tool that overwrites the file without shortening it (the 2023 “aCropalypse” bug). Both files below are built for real from your current crop, then taken apart byte by byte.

What viewers display
What viewers display…
no embedded thumbnailno embedded thumbnail
EXIF thumbnail inside the file…
info
OffsetSegmentBytesContents
JPEG files are walked marker by marker (ITU T.81), with EXIF read as TIFF IFDs (CIPA DC-008); PNG files chunk by chunk with each CRC-32 checked. Bytes after the end marker are scanned for PNG chunks whose CRC still validates.
~/reference

How each format crops.

Some formats crop by deleting pixels, some by re-encoding, and some only hide the edges behind a crop rectangle, which leaves the full picture in the file. Tool behaviour is from general knowledge of current documentation; check the docs for the version you use.

FormatCrop kindHowCatch
JPEGlossless on gridjpegtran -crop 1296x1620+240+80 -copy none in.jpg > out.jpgTop-left must sit on the 8 or 16 px MCU grid; jpegtran moves it up and left to the nearest boundary. Otherwise every block is re-encoded.
PNG · GIF · BMPlosslessmagick in.png -crop 800x600+40+20 +repage out.pngRe-encoding is lossless, but keep +repage or the old canvas size and offset stay in the file.
WebP (lossy)re-encodecwebp -q 85 -crop 40 20 800 600 in.png -o out.webpVP8 has no lossless crop; each re-save adds generation loss.
HEIF · AVIFhidden edgesclap (clean aperture) property on the image itemA viewer applies the crop rectangle, but the full coded image stays in the file.
TIFF · DNGhidden edgesDefaultCropOrigin / DefaultCropSize tagsRaw converters crop on display; the sensor data outside is kept.
PDFhidden edgespage /CropBox [x1 y1 x2 y2]Anything outside the CropBox is still in the content stream and can be extracted.
SVGhidden edgesviewBox="40 20 800 600"Shapes outside the viewBox remain in the markup.
H.264 · HEVC videore-encode or flagffmpeg -vf crop=1280:720:0:180 · SPS frame_croppingWith 4:2:0 chroma, crop width, height and offsets must be even; the SPS crop only hides edges.
Screenshots (any)depends on toolWrite to a new file, or truncate before overwritingOverwriting a longer file in place leaves its tail behind, the aCropalypse bug.
Timeline
1992ITU-T T.81 / ISO/IEC 10918-1 defines baseline JPEG and its 8 × 8 DCT blocks.
1995IJG libjpeg 6 ships jpegtran for lossless transcoding between JPEG variants.
1998Exif 2.1 standardises the IFD1 JPEG thumbnail embedded in the APP1 segment.
2003A widely reported case shows Photoshop-cropped photos whose EXIF thumbnails still held the uncropped original.
2009libjpeg 7 adds jpegtran -crop, snapping the corner to the iMCU boundary (approximate).
2015HEIF (ISO/IEC 23008-12) inherits ISOBMFF’s clap clean-aperture crop, applied on display.
2019Exif 2.32 published by CIPA and JEITA.
2020CSS image-orientation: from-image becomes the default in major browsers, so EXIF rotation is applied to images.
Mar 2023aCropalypse: Pixel Markup crops kept the original’s tail (CVE-2023-21036); Windows Snipping Tool had the same flaw (CVE-2023-28303).
2023Exif 3.0 (CIPA DC-008-2023) adds UTF-8 text fields.
2025W3C PNG Third Edition becomes a Recommendation, adding HDR signalling and formalising eXIf.