Free plan: 1 conversion/hour, 1 file at a time
Go Unlimited →

Crop JFIF

Free Online JFIF Cropper

Indicate your files

*Files deleted after 24 hours

Convert up to 1 GB files free, Pro users can convert up to 100 GB files; Sign up now

Uploading

0%

How to Crop JFIF

1 Upload your JFIF images and wait for the preview to appear.
2 Drag out the region you want to keep, or lock the selection to 1:1, 4:3 or 16:9 and drag freely inside that ratio.
3 Confirm the crop — the same rectangle is applied to every file you uploaded, which is how a set ends up genuinely consistent.
4 Download the cropped JFIF file, with everything outside the frame discarded.

Crop JFIF FAQ

How does Crop JFIF select and cut the area?
+
Concretely, the crop is applied to the decoded image and the result is re-encoded, so it costs one generation; where the crop happens to land on 8-pixel MCU boundaries the encoder can keep the original blocks and the cost disappears. You drag the region you want directly on the preview, or type exact pixel coordinates if you already know them.
Yes. Lock the selection to 1:1, 4:3, 16:9 or any custom ratio and drag freely inside that constraint — which is how you get a set of images that all fit the same layout slot without measuring anything.
It can. JFIF is a plain JPEG bitstream under the original 1992 interchange header, which is why some viewers show it as a generic image and cameras still emit it. That decides whether the crop is a pure pixel operation or whether the file has to be rebuilt around it.
Yes — many editors silently rewrite a JFIF as an ordinary JPEG on save, so keep the original if the .jfif extension itself matters to whatever consumes the file. That is the sort of detail that only shows up after you have overwritten the original.
Cropping before resizing. Crop first from the full-resolution original, then resize the result — doing it the other way round means the region you keep has already lost detail it did not need to lose.
Yes, and that is the case worth doing here rather than in an editor: the same rectangle is applied across the batch, which is how a set of product shots ends up genuinely consistent instead of approximately consistent.
Anything in the lossy raster family — JPG, JPEG, JFIF and WebP — plus the lossless formats (PNG, BMP, TIFF) if you want to mix them in one batch. The format is read from the file header, not the extension, so a photo saved with the wrong suffix still goes through.
Yes: free accounts process images up to 25 MB each, which covers essentially every camera JPG and phone photo; the work is done by libjpeg-turbo and libwebp, the same libraries a desktop editor links against. Larger files are the one thing the free tier will stop you on, and the limit is per file rather than per batch.
A lossy source is already the result of one quantisation pass, and any operation that has to re-encode adds a second. Where the job can be done without touching the pixel data we do that instead, and where it cannot you choose the quality factor yourself rather than getting a fixed default.
Yes. Drop the whole set into the upload area and they queue in parallel with identical settings — that is the main reason to do this in a browser rather than one file at a time in an editor. Free accounts run one file per batch; a pass lifts that.
Camera EXIF (ISO, shutter, lens, GPS) and the embedded ICC profile are carried across by default, because dropping the profile is what makes colours shift on re-import. Use the privacy option to strip metadata before download if you are about to publish the file.
No. Crop JFIF is free with no account, no watermark on the output and no signup wall in front of the download. Uploads are deleted automatically a short time after the job finishes.

Rate this editor

5.0/5 - 0 votes
ns6.com — Free WHOIS privacy, DNS and SSL on every domain.
Or plop your files here