English ▾
Free, Fast & Secure Online Tools
You right-click an image on a web page, save it, and the file lands on your disk as something.jfif. Your photo editor will not open it. The preview is blank. It looks like you have been handed a format nobody has heard of.
You have not. A JFIF file is a JPEG. In almost every case the bytes are identical to what a .jpg would contain — the only thing that changed is the three letters after the dot.
There is a distinction behind the confusion, and it is worth understanding once.
JPEG is a compression method — a standard describing how to turn an image into a smaller amount of data. It says nothing about how that data should be stored in a file.
JFIF — JPEG File Interchange Format — is one answer to that second question. It is the wrapper that says “here is JPEG-compressed data, here is its resolution, here is the colour information needed to display it.” It was published in 1992 precisely because the JPEG standard had left the file format undefined, and different vendors were inventing incompatible ones.
So JFIF is not an alternative to JPEG. It is the container that made JPEG files interchangeable in the first place, and it is what the overwhelming majority of .jpg files on your disk already are.
This is a quirk, not a decision anyone made deliberately.
When a browser saves an image, it asks the operating system which extension belongs to the image’s declared type — image/jpeg. On Windows, that lookup can return .jfif instead of .jpg, because a registry entry maps the type that way. It is technically correct and practically unhelpful, and it is why this suddenly started happening to a lot of people who had never seen a .jfif before.
Nothing about the image is different. The server sent a JPEG, the browser saved a JPEG, and it labelled it with the other valid extension for a JPEG.
Normally, changing a file extension is bad advice. Renaming photo.webp to photo.jpg does not convert anything; it produces a WebP file that lies about itself, and software that trusts the name will fail in confusing ways.
JFIF is the exception, because there is nothing to convert. The file already is a JPEG. Renaming image.jfif to image.jpg changes the label on a file whose contents already match that label.
This also means renaming is lossless. No re-encoding happens, so none of the quality degradation that comes with converting a JPEG to a JPEG occurs. If a program refuses your file purely because of its extension — and many do judge by extension alone — renaming is the complete fix.
There is a genuine technical distinction, and it occasionally matters.
Most photographs from cameras and phones are not strictly JFIF — they are JPEG/Exif, a different wrapper that carries an EXIF block: camera model, exposure settings, date, GPS coordinates, and the orientation tag that tells software which way up the picture goes.
JFIF has no equivalent slot. A file that is genuinely JFIF-only carries no EXIF at all.
In practice the two are usually mixed — a file can contain both an Exif block and a JFIF header, and most do. But if you save an image from a website and find it has no camera information and no GPS, that is often not the site stripping it: it may simply be that the image was never Exif-carrying in the first place.
One consequence worth connecting: no EXIF means no orientation tag, so a JFIF cannot be the kind of image that displays sideways because of a rotation instruction. Its pixels are however they are.
Renaming solves the extension problem. Convert instead when you actually want something different:
And one caution that applies whenever a JPEG is involved: converting JPEG to JPEG loses quality every time. The compression is lossy, so each round discards a little more. If renaming solves your problem, prefer it — it is the only option here that costs nothing.
The behaviour comes from the operating system’s type mapping, not the browser, so it persists across browsers on the same machine. It can be changed by editing the registry entry that maps image/jpeg to an extension — which is a system-level change worth weighing against simply renaming the occasional file.
image/jpeg to .jfif.jpg is safe and lossless — unusual for an extension change