1Upload your JFIF images and wait for the preview to appear.
2Drag 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.
3Confirm the crop — the same rectangle is applied to every file you uploaded, which is how a set ends up genuinely consistent.
4Download the cropped JFIF file, with everything outside the frame discarded.
Crop JFIF FAQ
Does my source format change how a crop behaves?
+
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.
Anything specific to JFIF worth knowing before I crop?
+
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.
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.
Can I crop to a fixed aspect ratio?
+
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.
What happens to EXIF and colour profile data?
+
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.
What can I upload to Crop JFIF?
+
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.
Is there a file size limit on Crop JFIF?
+
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.
Will Crop JFIF lower the quality of my JFIF images?
+
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.
Why would a modern-format site run Crop JFIF?
+
WEBP.to is built around the modern replacement for both of the old defaults: one format that does lossy, lossless, alpha and animation, and reliably lands smaller than the JPEG or PNG it came from. People arrive here having decided the old defaults are costing them bandwidth, and that decision immediately raises the rest: what size, what quality, what happens to the transparency. Crop JFIF is on the same upload and the same account so those questions get answered in one place.
Once Crop JFIF has run, what is worth doing next?
+
The converter on this site moves images to and from WebP, PNG, JPG and AVIF, which is where you decide whether a smaller file is worth losing the older browsers. Doing it in that order matters: pick the pixels first and the container afterwards, because the container is the cheap decision and the pixels are the expensive one.
Do the sibling sites run something different?
+
The engines are identical — same libraries, same workers, same caps. What is different is the opinion attached, and the opinion here rests on a property of the format this site is named after: the same .webp extension can hold a lossy VP8 frame, a lossless one, or an animation, so the sensible processing path is decided per file rather than per extension.
What happens to my file, and is an account required?
+
No account, and nothing is retained: uploads are deleted from the workers shortly after the job finishes, and nothing is inspected, listed or indexed. Accounts exist for history and batch size only.
