You save a picture from your browser, expect a normal .jpg, and instead get a file ending in .jfif that half your apps refuse to touch. If you have wondered why Windows saves images as JFIF, the cause is a small file-type setting hidden in the system, and the good news is you can fix it permanently. Meanwhile, for any .jfif files you already have, our free JFIF to JPG converter turns them into standard JPGs in seconds.

This is one of the most common annoyances on Windows 10 and 11, and it is not your fault. Let us look at exactly what is happening and how to make future saves land as .jpg.

Why Does Windows Save Images as JFIF Instead of JPG?

The reason Windows saves images as JFIF comes down to a single file-type association stored in the Windows registry. Every image format has a MIME type — for JPEG photos this is image/jpeg — and Windows keeps a table that maps each MIME type to a default file extension. On many Windows installations, the entry for image/jpeg is set to .jfif rather than .jpg.

Because JFIF (JPEG File Interchange Format) is the technically correct name for how JPEG data is packaged, this mapping is not wrong exactly — it is just inconvenient. When a program asks Windows what extension to use for a JPEG image, Windows dutifully answers .jfif, and the file gets saved with that name. The image data is completely normal JPEG; only the label is unexpected.

Which Programs Trigger the JFIF Save?

Not everything on Windows produces .jfif files, which is why it can seem random. The behaviour tends to show up in specific situations:

  • Chrome and Edge image saving. Right-clicking an image on a web page and choosing Save image as often defaults to .jfif, because the browser asks Windows for the JPEG extension and receives .jfif.
  • Paint and Photos exports. Some versions offer JFIF as a save option or default to it.
  • Certain email clients. Saving an attached photo can produce a .jfif file for the same reason.
  • Copy-and-paste saves. Pasting an image into an app and exporting it can inherit the .jfif extension.

In every case the pattern is the same: the app defers to the Windows setting, and the Windows setting says .jfif.

How to Stop Windows Saving JFIF: The Registry Fix

The permanent solution is to change the registry entry so that image/jpeg maps to .jpg. This is a one-time edit and it makes future saves land correctly across your browsers and apps. Editing the registry is safe when done carefully, but because you are changing a system setting, take your time and follow the steps precisely.

  1. Press Windows key + R, type regedit, and press Enter. Approve the security prompt to open the Registry Editor.
  2. Navigate to the following key by pasting this path into the address bar at the top: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MIME\Database\Content Type\image/jpeg
  3. On the right, find the value named Extension. Double-click it.
  4. Change its data from .jfif to .jpg and click OK.
  5. Close the Registry Editor and restart your browser. New images you save should now use the .jpg extension.

If you are cautious about the registry, you can right-click the image/jpeg key and choose Export first to back it up before making the change. That way you can restore the original setting if you ever want to.

A Simpler Alternative If You Would Rather Not Edit the Registry

Not comfortable in regedit? You do not have to touch it at all. You can simply convert or rename each .jfif file as it appears:

  • Rename in File Explorer. Turn on file extensions via the View menu, then change the ending from .jfif to .jpg. Because the data is already JPEG, the file opens normally afterward.
  • Convert online. Drop the file into our JFIF to JPG converter for a properly re-saved JPG. This is the most reliable route and also handles batches.

These do not stop future .jfif files from appearing the way the registry fix does, but they clear up the ones in front of you without any system changes.

Fixing the JFIF Files You Already Have

The registry edit only affects images you save from now on. Any .jfif files already sitting in your folders keep their old extension, so you will want to convert those too. The quickest way is to handle them in bulk:

  1. Open the JFIF to JPG converter.
  2. Select all your existing .jfif files, or drag the whole group onto the page.
  3. Download the converted JPGs and replace the originals wherever you need them.

Since JFIF already contains JPEG data, this conversion is effectively lossless — you are relabelling and re-saving the same photo, not re-compressing it, so nothing about the image quality changes. If you need transparency or are working with graphics rather than photos, our JFIF to PNG converter is the counterpart tool.

Why This Setting Exists at All

It is natural to wonder why Windows would default to an extension that causes so much friction. The honest answer is a mix of history and technical correctness. JFIF is the formal specification that describes how JPEG files are laid out, so from a standards point of view, .jfif is an accurate extension for the format. The trouble is that the wider world — websites, apps, and everyday users — standardised on .jpg and .jpeg decades ago, so the technically-correct label ends up being the practically-inconvenient one. If you want the deeper background, our explainer on what a JFIF file is and our comparison of JFIF vs JPG vs JPEG both cover the story in plain language.

Put JFIF Headaches Behind You

Windows saves images as JFIF because of one small registry mapping that sends JPEG photos to the .jfif extension, and browsers like Chrome and Edge simply follow that lead. Change the setting once and future saves land as proper .jpg files. For everything already saved, our free JFIF to JPG converter cleans them up in seconds, with no quality loss and nothing to install — so those rejected uploads and unopenable photos become a thing of the past.