Convert JFIF to JPG

Here is the secret this page is built on: a JFIF already is a JPEG. Same bytes, same format, different file extension — Windows just started naming some saved images .jfif and broke every upload form that filters on .jpg. So this tool does the only honest thing: it checks the bytes really are JPEG, and hands them back untouched under the right name. Zero quality loss, because nothing is re-encoded.

  1. Your JFIF files

    Drop your JFIF files here

    JFIFJPGPNGWebP

    Your files are never uploaded.

  2. What you want back

  3. Your files

How to convert JFIF to JPG

  1. Add your JFIF files

    One or a folder. They are read by your browser and never uploaded.

  2. Leave it on JPG

    The bytes pass through untouched. PNG and WebP are real conversions, one click away.

  3. Save the JPGs

    Individually, or the batch as a zip.

What you get

Byte-identical, and verified

Most converters decode your JFIF and re-encode it as a JPG — a lossy generation paid for a rename. Because JFIF is JPEG, this one verifies the bytes and passes them through byte-for-byte. The photo cannot get worse here, because it is not touched.

Fixes the upload form, not the photo

The .jfif extension breaks filters that check names instead of contents — job portals, CMSes, old forums. The file that comes back is the same image with the name those forms expect.

Checked, not assumed

The file's actual bytes are inspected first. A .jfif that is secretly something else — an HTML error page, a PNG in disguise — is refused with a reason instead of renamed into a broken .jpg.

Your photos are never uploaded

The check and the copy happen in this page. Nothing goes to a server, which for a folder of personal photos is the entire point.

Questions about JFIF

Is JFIF really the same thing as JPEG?
Yes. JFIF is the interchange wrapper JPEG images have shipped in since 1992 — most JPEGs on the web are JFIF under the .jpg name. Camera photos use the sibling Exif wrapper instead, but the JPEG inside is the same format either way; only the letters after the dot differ.
So why do other converters lose quality doing this?
Because they run every input through the same decode-and-re-encode pipeline regardless of whether it is needed. Re-encoding a JPEG as a JPEG costs a generation of quality — compression artefacts stack — and for this conversion it buys nothing at all. Passing the bytes through is both faster and strictly better.
Can I turn a JFIF into PNG or WebP instead?
Yes, on this same page — those are real conversions, decoded and re-encoded properly. PNG comes out lossless from here (and larger); WebP smaller. The pass-through trick applies only to JPG, where the formats are already the same.
Why does Windows save .jfif files at all?
A registry quirk: when certain apps save a JPEG without naming it, Windows picks the extension registered for the MIME type, and for image/jpeg that has sometimes been .jfif. Nothing is wrong with the files. The setting can be changed, but renaming the strays is usually less work.
Is it free, and is my file uploaded?
Free, no account, no limit on how many files. The check runs in your browser. Your files are never uploaded.

If the result needs to fit under an upload limit, resize it to a size in KB. Photos from an iPhone rather than the web? That is HEIC to JPG. Or see the rest of the image tools.