Chrome Saves Images as .JFIF Instead of .JPG

You right-click an image, choose Save image as, and the file that lands in your Downloads folder is called photo.jfif instead of photo.jpg. Nothing you did caused it, it happens on some Windows machines and not others, and it is mildly infuriating: an upload form rejects the file, an older image editor will not open it, and Windows Explorer will not even draw a thumbnail for it.

The file is fine. .jfif is a JPEG - the bytes inside a .jfif and a .jpg are the same JFIF bitstream, and the only thing wrong is the three letters after the dot.[1] That is also why the fix is so much smaller than the annoyance suggests.

Why Chrome and Edge do this

When a browser saves an image, it has to pick a file extension. Chrome and Edge on Windows ask the operating system: what extension goes with the type image/jpeg? Windows answers from a single value in its registry, at HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg.

On most machines that value is .jpg. On some - after a particular Windows update, or an image app that rewrote the association during install - it is .jfif, and from then on every JPEG the browser saves inherits it.

Two things narrow the problem down:

• It is Windows-only. Chrome on macOS always writes .jpg.
• It is Chromium-only. Firefox ignores that registry value and always writes .jpg, on the same Windows machine where Chrome writes .jfif. If you have Firefox installed, saving the odd image through it is a zero-effort workaround.

Fix 1: rename the file

Because the contents are already a valid JPEG, renaming photo.jfif to photo.jpg produces a working .jpg with nothing lost. This is the one case where changing a file extension by hand is genuinely safe rather than a way to break things.

The friction is real, though:

• Windows Explorer hides known extensions by default, so you first have to turn on View - Show - File name extensions before you can edit the .jfif part at all.
• It is one file at a time. Save ten images and it is ten renames.

For a file you needed once, this is the fastest fix. For a habit, it is not.

Fix 2: edit the registry

You can change the association Windows hands the browser, so the problem stops at the source:

1. Press Win + R, type regedit, press Enter.
2. Go to Computer\HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg.
3. Double-click Extension and change .jfif to .jpg.
4. Restart the browser, or reboot.

This works, and after it every future save is a .jpg. The costs: it is a system-wide change that needs an administrator account, it has to be redone on every Windows account and every machine you use, and some Windows updates reset it. Most people are not comfortable in the registry, and telling a colleague to edit theirs is not advice that travels well.

Fix 3: re-save it in Paint

Open the .jfif in Paint (or Photos, or any editor), choose Save as - JPEG, and you get a .jpg. It works anywhere, with software you already have.

What it costs you: Paint re-encodes the image on the way out. JPEG is lossy, so the copy is slightly softer than the file you started with, and you have done a full open-edit-save for what should have been a rename. One file at a time, again.

Fix 4: stop the .jfif at the source

All three manual fixes are working around the save. The save itself is the thing to change, and Save Image As Type does it two ways.

It renames the download for you. With the extension installed, a JPEG you save through Chrome or Edge’s own Save image as on Windows is written as .jpg instead of .jfif. It is on by default, and the first time it happens you get a one-time notification saying so, with a switch to turn it off in Settings under Filename. Nothing changes on macOS or in Firefox, which already write .jpg.

Or pick its own menu item. Instead of Chrome’s Save image as, choose Save Image As Type - Save as JPG. This works on every platform and browser, and it does more than rename:

• If the image on the page is actually a WebP or a PNG rather than a JPEG - which is common now, and a separate headache - it converts the file properly rather than just relabelling it. That runs on your own device using the browser’s Canvas API; the image is never uploaded. It is the same engine behind saving a WebP as JPG.
• A real JPEG saved as JPG is written straight through with its metadata stripped and no re-encode, so unlike the Paint route it costs no quality.

Set JPG as your default format in Settings and a single Save Image as JPG entry sits at the top of the right-click menu with no submenu to open.

Which fix should you use?

Renaming and the registry edit are free and need nothing installed. They just do not scale past a handful of files or a single machine. If saving images is part of your day, changing what the save does is the fix that stays fixed.

The same root as the WebP problem

The .jfif problem and the WebP problem come from the same place: the file a browser hands you is named and formatted for the browser’s convenience, not yours. .jfif is the mild version - the bytes are right and only the label is wrong. A WebP that will not open in Windows Photos is the same story one step worse.

If the filename itself is the thing that bothers you - download.jpg, image_1024x768_final(3).jfif - the extension can build the name from the page’s own description of the image as it saves, so the .jpg you get is also called something you can find later.