A .jfif file is a normal JPEG photo. The picture inside is exactly the kind of data a .jpg holds; only the ending of the file name is different. You did not download a strange new format, and nothing is wrong with the image.
The extension is what causes trouble. Windows often gives browser downloads the .jfif ending, while plenty of websites, apps and phones only recognise .jpg and .jpeg. This page explains where .jfif comes from, how to open it on each kind of device, and how to make Windows go back to .jpg.
Where the name comes from
JPEG is the way the picture is compressed. JFIF, short for JPEG File Interchange Format, is the standard layout that tells a program how to read that compressed data: the pixel density, the aspect ratio and how the colour is stored.
It was agreed at the end of 1991 by a group led by Eric Hamilton of C-Cube Microsystems, and version 1.02 was published on 1 September 1992. Because the original authors had moved on, Ecma International republished it as technical report TR/98 in 2009, and in May 2011 it became the international standard ITU-T T.871.
So JFIF is not new and not rare. Most of the .jpg files you have ever opened use it.
JFIF and Exif
Photos from cameras and phones usually use a related layout called Exif, which stores extra details such as the camera model, the date and sometimes the location. Both are JPEG underneath and both have the same media type, image/jpeg; many files carry both sections. You can see which one a file starts with in its first bytes:
| The file starts with (hex) | Meaning |
|---|---|
FF D8 FF E0 … 4A 46 49 46 ("JFIF") | JPEG with a JFIF header |
FF D8 FF E1 … 45 78 69 66 ("Exif") | JPEG with an Exif header |
anything not starting FF D8 FF | not a JPEG, whatever its name says |
That last row matters more than it sounds. While writing this page we found a file on a Mac that ended in .jpg but was really a PNG inside. A name is only a label; the first bytes are the truth. Our guide to renaming .jfif files shows how to read them on Windows and Mac.
Why your computer saves images as .jfif
When you save an image from a website, the browser knows its type, image/jpeg, but has to choose an extension for the file name. On Windows, Chrome, Edge and other browsers ask the system, and Windows answers from this registry entry:
HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpegIts Extension value says which ending goes with JPEG images. When it reads .jfif, every JPEG you save gets .jfif, whichever site it came from. That is why the problem appears in every browser at once, and why reinstalling the browser does not fix it.
What sets the value to .jfif in the first place is less clear. People on Microsoft's own forum have reported it since at least 2020, often saying it came back after a Windows update, and advisers there have blamed updates or other installed software. Microsoft has not published an explanation, so we cannot tell you which one it is on your computer.
How to stop it
- Press Win + R, type
regeditand press Enter. If you are unsure about editing the registry, choose File → Export first to save a backup. - Go to
HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg. - Double-click Extension and change
.jfifto.jpg. - Close and reopen the browser, then save any image from the web. If it arrives as .jpg, the fix worked.
To check the value without opening the editor, run this in Command Prompt:
reg query "HKCR\MIME\Database\Content Type\image/jpeg" /v ExtensionThe fix only affects new downloads. Files that are already .jfif stay that way. And because the value has been reported to change back, it is worth checking again after a large Windows update.
How to open a .jfif file
Windows. The Photos app and Paint open .jfif files, so double-clicking usually just works.
Mac. We tested on macOS 26: Finder lists a .jfif file as a plain "Document", not an image, and no app is set to open it, so double-clicking does not show the picture. Right-click the file, choose Open With → Preview, and it opens normally. Renaming it to .jpg makes Finder treat it as an image everywhere.
iPhone, iPad and Android. We have not tested these yet, so we will not guess. If a phone will not show the file, converting it to .jpg in the browser works on any device.
Websites and apps that reject it. Many upload forms decide by extension alone. WordPress, for example, accepts jpg, jpeg and jpe for JPEG images by default, and jfif is not on that list, so it refuses a file it could display perfectly well. Some older photo editors behave the same way.
Rename it, re-save it or convert it?
- Rename
.jfifto.jpgwhen you have a few files and can see file extensions. It is instant and changes no image data. - Re-save or convert when a renamed file is still refused. That usually means the file is not JPEG inside, or something else is wrong; the four common reasons are worth a quick look.
- Use a converter for many files at once, on a phone, or when you would rather not touch file extensions. The converter on our home page checks the first bytes of every file, copies real JPEG data unchanged under a .jpg name, and only re-encodes files that turn out to be something else. It runs in your browser, so nothing is uploaded.
In short
A .jfif file is a JPEG photo with an unusual name. Windows gives it that name because of one registry value, which you can change back. Existing files can be renamed or converted without losing quality, and if a renamed file is still rejected, look at what is really inside it.
