JFIF to JPG without a converter: rename it, and stop Chrome saving .jfif

A .jfif file is a JPEG with an unusual label

JFIF stands for JPEG File Interchange Format. It is not a different image format; it is a standard for how a JPEG file is packaged, published as ITU-T Recommendation T.871 and ISO/IEC 10918-5. A JFIF-style JPEG starts with the bytes FF D8 (start of image), followed by an FF E0 segment whose identifier reads JFIF. The compressed picture after that is ordinary JPEG data.

Windows treats it that way too. On the Windows 11 PC used for this guide, the registry entry for .jfif has the content type image/jpeg and the perceived type image - exactly the same as .jpg and .jpeg. Paint (11.2605.81.0) and the Photos app (2026.11080.24002.0) both list .jfif among the formats they open, which is why double-clicking the file usually works fine.

That chart is the point in one picture. Whether a JPEG starts with a JFIF marker, an Exif marker or neither, it is still a JPEG, and Windows names all of them .jpg. The .jfif extension is simply a second name that some systems map to the same image/jpeg type.

Fix 1 - Rename it to .jpg (that is the whole conversion)

If File Explorer hides extensions, turn them on first: View -> Show -> File name extensions. Then rename the file and change only the part after the dot.

1. 1Right-click the file and choose Rename (or select it and press F2).
2. 2Change photo.jfif to photo.jpg and press Enter.
3. 3Windows warns that changing the extension might make the file unusable. For JFIF that warning does not apply - click Yes.

To be sure nothing else was happening, I copied three JPEG files to .jfif names, took their SHA-256 hashes, renamed them back to .jpg and hashed them again. The hashes matched exactly, and the sizes (542,091, 518,265 and 1,033,330 bytes) did not move by a byte. A rename does not touch the contents, and for a JFIF file the contents were never the problem.

Fix 2 - Rename a whole folder in one line

If your Downloads folder is full of them, PowerShell renames them all at once. Open PowerShell from the Start menu and run this, changing the path to your folder.

Get-ChildItem "$env:USERPROFILE\Downloads\*.jfif" | Rename-Item -NewName { $_.BaseName + '.jpg' }

I ran it on a test folder. It also caught a file named C.JFIF in capitals, since Windows file matching ignores case. One case needs care: if a.jpg already exists next to a.jfif, PowerShell reports Cannot create a file when that file already exists. and leaves that one file alone while renaming the rest. Rename the conflicting file by hand, for example to a (2).jpg.

Why Chrome saves some images as .jfif

Most of the time Chrome keeps the name the website gave the file. The .jfif name only appears in one situation, and Chromium's source code spells it out. When Chrome builds a download name, it first takes the last part of the address. If that part already has an extension, such as photo.jpg, it keeps it. If it has none - common with image servers that use addresses like .../media/abc123?format=jpg - Chrome has to pick an extension for the image/jpeg type.

For that, Chromium asks the operating system first and uses its own built-in table only as a fallback. On Windows the question goes to the registry key HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg, value Extension. Whatever is written there becomes the file's extension. Chromium's built-in fallback for image/jpeg would be .jpeg.

I reproduced this with a small local web server and Chrome 153 on this PC, where the registry value is .jpg. The server sent the same JPEG under different addresses, without a file name, so Chrome had to choose one itself.

The extension-less JPEGs came out as .jpg, not .jpeg, so the name came from the registry rather than Chromium's fallback table. The files themselves started with FF D8 FF E0 and the word JFIF, and were still named .jpg - more proof that the name comes from a lookup, not from what is inside. Edge is built on the same Chromium code, so the same lookup applies there.

On PCs where the value reads .jfif, the same downloads come out as .jfif. Users on Microsoft's Q&A forum describe exactly this: the value had become .jfif, setting it back to .jpg fixed their saves, and some reported it changing back after Windows updates. Those are user reports rather than an official explanation, but they match the code path above.

Fix 3 - Make new downloads come out as .jpg

First check what your PC says. This only reads the value and changes nothing:

(Get-ItemProperty 'Registry::HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg').Extension

If it prints .jpg, your registry is fine and any .jfif files came from somewhere else (a file sent to you, or another program). If it prints .jfif, change it in Registry Editor:

1. 1Press Windows + R, type regedit and press Enter. Allow the administrator prompt.
2. 2Go to HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg (you can paste the path into the address bar at the top).
3. 3Double-click Extension on the right, change .jfif to .jpg, and click OK.
4. 4Close and reopen Chrome or Edge. Newly saved images use .jpg; files already saved keep their names.

Why some sites reject .jfif

Upload forms often decide by name. A file picker set to accept .jpg,.jpeg,.png filters by extension, and many servers check the extension against a list before looking inside. .jfif is not on those lists, so the file is refused even though the picture is identical. After renaming it passes, because the name now matches and the contents really are JPEG - which is exactly what fails when you try the same trick with WebP.

When you do need a real conversion

Renaming covers 'I need a JPG'. It does not help when you need a different format or a smaller file. For those, re-saving is the right tool:

• Need PNG or WebP - open the file in Paint and use Save as, or drop it into the browser converter linked above.
• Need a smaller file - reduce the pixel dimensions; that shrinks a JPEG far more than changing format does.
• Need the original quality - just rename it. Every re-save of a JPEG compresses it again.

FAQ