Convert JFIF to JPG
You saved an image and Windows handed you a file ending in .jfif that half your software refuses to touch. It is not a corrupted download and it is not an obscure format — a JFIF file is a JPEG. Same compression, same bytes, same everything. Only the extension differs.
Files are decoded and re-encoded inside this browser tab. Nothing is uploaded — you can disconnect from the internet after this page loads and conversion still works.
This tool re-encodes it as a conventional .jpg so that every application recognises it. Everything runs in your browser, with no upload.
How to convert JFIF to JPG
- Drag your JFIF files onto the box above, or click it to browse.
- Each file converts in place — no upload, no queue.
- Download them one by one, or grab the whole batch as a ZIP.
What JFIF actually is
JFIF stands for JPEG File Interchange Format, and it is the specification that defines how JPEG-compressed image data is packaged into a file. Practically every .jpg you have ever opened is a JFIF file internally. The format is not unusual; it is the norm, wearing an unfamiliar name.
The reason you are suddenly seeing the extension is a Windows registry quirk. The association between the MIME type image/jpeg and a file extension is stored in the registry, and certain Windows updates, Office installations and browser versions have set that mapping to .jfif instead of .jpg. When you then save an image from a browser or from Outlook, Windows dutifully names it with the extension the registry told it to use.
So nothing is wrong with the image. The file just has a name that a lot of software was never taught to recognise.
Renaming works too, and it is worth knowing why
Because the contents are already a valid JPEG, simply renaming photo.jfif to photo.jpg will make it open in almost anything. If you only have one file, that is the quickest fix available and you do not need this or any other converter.
This tool is more useful in two situations. When you have dozens of files, since renaming them individually is tedious and Windows will warn you about changing the extension every time. And when the software you are feeding them to inspects the file rather than trusting the name — some upload forms and older applications reject anything they cannot positively identify, and a clean re-encode removes any doubt.
Fixing the cause on Windows
If you would rather stop the problem at the source, the registry key controlling it is under HKEY_CLASSES_ROOT in the MIME database, where the extension associated with image/jpeg can be set back to .jpg. Editing the registry is not something to do casually, and if you are not comfortable with it, converting the occasional file is the safer path.
A gentler alternative: when saving from a browser, type the filename with .jpg on the end yourself in the save dialog. The browser will honour what you type rather than falling back to the registry default.
Frequently asked questions
Is JFIF the same thing as JPEG?
Effectively yes. JFIF is the container specification that standard JPEG files use. A .jfif file and a .jpg file with the same image inside are byte-for-byte identical; only the extension differs.
Can I just rename the file to .jpg?
Usually, yes — and for a single file that is the fastest solution. Use this converter when you have many files, or when software is rejecting the file based on its contents rather than its name.
Why did Windows save my image as .jfif?
A registry entry maps the image/jpeg MIME type to a file extension, and some Windows and Office updates have set that to .jfif. When you save an image from a browser or email client, Windows uses whatever that entry says.
Does converting lose quality?
The image is re-encoded at quality 0.92, so there is a small theoretical loss. It is not perceptible at normal viewing sizes. If you want a genuinely lossless result, rename the file instead of converting it.
Are my files uploaded anywhere?
No. The conversion runs entirely in your browser and no image data is transmitted.