You saved an image from the web and it landed as mypic.jfif instead of .jpg. Some apps open it, some do not, and you just want a normal JPG. Good news: a JFIF file is a JPEG — the fix is trivial.
We measured this ourselves. The numbers make the point better than any explanation: running our three test images through the JFIF-to-JPG page changed the file sizes by −4%, −1% and −6%. Essentially nothing happened, because JFIF is JPEG. What that page really gives you is a file the rest of your software will open, not a smaller one. see the full measurements
The measurement that tells you not to bother converting. A .jfif file is already a JPEG. Through our JFIF → JPG page our test photo went 330.2 KB → 315.6 KB (-4%) — and that -4% is not a saving, it is the cost of decoding and re-encoding. Renaming the extension to .jpg is free and lossless. Going to PNG instead costs 330.2 KB → 2.07 MB (+542%), so only do that if you are about to edit the image.
So what is JFIF?
JFIF stands for JPEG File Interchange Format. It is the standard container that almost every “JPEG” already uses. In other words, .jfif and .jpg hold the same lossy image data — only the file extension differs. There is no quality difference and nothing is wrong with the file.
Why did my download become a .jfif?
This is usually a Windows quirk. A registry setting can make Chrome, Edge and other apps save JPEGs with the .jfif extension instead of .jpg. It is harmless, but annoying because:
- Some older programs and upload forms only recognise
.jpgor.jpeg. - Thumbnails and “open with” defaults can behave oddly.
How to convert JFIF to JPG (or PNG)
Because the data is identical, converting is instant and lossless in practice. These tools run entirely in your browser — nothing is uploaded:
- JFIF to JPG — rename it to the extension everything accepts.
- JFIF to PNG — if you specifically need a lossless PNG copy.
Drop the file in, download, done — now it opens and uploads everywhere.
What the conversion actually costs is worth seeing, because it is not a saving. Through our JFIF → JPG page a screenshot went 45.2 KB → 44.8 KB (-1%) and a flat illustration 25.6 KB → 24.2 KB (-6%). Those small drops are the price of decoding and re-encoding, not a gain — the bytes barely move because the file was already a JPEG.
How to stop getting JFIF files
If it keeps happening on Windows, you can change the file association so JPEGs save as .jpg again (via a registry edit for the .jfif MIME type). If you would rather not touch the registry, just run each download through JFIF to JPG — it takes a couple of seconds and keeps your files tidy.
Can I just rename .jfif to .jpg?
Yes — and this is the fastest fix of all. Because the bytes inside are already a standard JPEG, renaming photo.jfif to photo.jpg changes nothing about the image: there is no re-encoding and no quality loss. On Windows you first need to see the extension:
- Open File Explorer and go to the View menu.
- Turn on File name extensions (Windows 11: View → Show → File name extensions).
- Right-click the file, choose Rename, and change
.jfifto.jpg.
For many files, or if you would rather not edit names by hand, the converter does the same job in one step.
The measurement backs up the advice: renaming is free, converting is not quite. And if you go to PNG instead of JPG, the cost stops being negligible — the same screenshot became 45.2 KB → 72.8 KB (+61%), because a lossless format has to store the JPEG artefacts too.
The claim that renaming is enough has a measurable answer. We ran the three JFIF files from our test corpus through the JFIF to JPG converter:
| Test image | Input | Output | Change |
|---|---|---|---|
| Photo | 330.2 KB | 315.6 KB | -4% |
| Screenshot | 45.2 KB | 44.8 KB | -1% |
| Illustration | 25.6 KB | 24.2 KB | -6% |
The rename question has a precise answer, and it is not the one we first wrote here. The source files really are identical: in our corpus photo.jfif and photo.jpg are both 338083 bytes — the same file under two names. That is why renaming works at all, and renaming is genuinely lossless. But this converter does not rename. It decodes the image and re-encodes it as JPEG, so the output is not the input: the photo came out 315.6 KB (-4%), the screenshot 44.8 KB (-1%) and the illustration 24.2 KB (-6%). Those differences are a second lossy pass, not a saving. So if all you need is the extension, rename the file yourself. Reach for a converter when a program rejects the file outright, or when you have a folder full of them and want drag-and-drop batching without uploading anything.
Other extensions you might see for the same image
A JPEG can legitimately carry several endings — all the same underlying format:
.jpgand.jpeg— the everyday names (.jpgdates back to the old 8.3 filename limit on DOS/Windows)..jfif,.jfi,.jif— variants that point at the JFIF standard..jpe— a rarer old spelling.
Treat them as interchangeable. If a program refuses one, rename or convert it to .jpg.
The technical bit: what JFIF adds
Raw JPEG only defines how to compress the pixels, not how to store practical details. JFIF (published in 1992) is the small wrapper that fills the gaps: it adds an APP0 marker, records the resolution/DPI and pixel aspect ratio, and can hold a thumbnail. Photos from cameras and phones often use Exif instead — a different metadata wrapper in the same slot, carrying things like the date, camera model and GPS. Either way, the compressed image underneath is a normal JPEG.
FAQ
Does converting or renaming reduce quality?
No. The data is identical, so both are lossless — you are relabelling the file, not re-compressing it.
Is JFIF worse than JPG?
No. There is no quality or compatibility difference in the image itself; the only issue is the unfamiliar extension. For how JPEG stacks up against other formats, see PNG vs JPG.