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

Resize JFIF

Free Online JFIF Resizer

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 Resize JFIF

1 Upload the JFIF images you want resized — work from the largest original you have rather than from a copy you already shrank once.
2 Type a target width, a target height or a percentage, and leave the aspect-ratio lock on unless you deliberately want stretching.
3 Run the resize; every file in the batch is taken to the same target in a single pass.
4 Download the resized JFIF file, or the whole set together as one archive.

Resize JFIF FAQ

How does Resize JFIF change the dimensions?
+
Concretely, the image is resampled with a Lanczos filter and then re-encoded, which means a resize is also a re-compression — so do it once from the largest original you have rather than in stages. You give it a target width, a target height or a percentage, and it works from the original rather than from a previously resized copy.
Both. Lock the ratio and one dimension is derived from the other, which is what you want almost always. Unlock it and you get exactly the numbers you typed, at the cost of stretching — useful for a fixed slot, wrong for a photograph.
It does. 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 is what decides whether shrinking the file is purely a question of pixels or also a question of re-encoding.
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. Worth checking before you resize a file you will not be able to regenerate.
Upscaling. Enlarging cannot invent detail that was never captured, so the result is a soft version of the original at a bigger size. Always resize down from the largest source you have, and resize once rather than in stages.
Match the slot it will live in. A full-width web hero rarely needs more than 1920 pixels wide, a content image 1200, a thumbnail 400, and doubling those numbers covers high-DPI screens. Anything beyond that is bytes nobody sees.
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. Resize 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 — 800+ domain extensions. Find your perfect name.
Or plop your files here