JFIF to JPG: Why Windows Saves JFIF and How to Stop It

You right-click a photo in Chrome or Edge, choose Save image as, and Windows hands you IMG_4821.jfif instead of the .jpg you expected. Then your photo editor, your CMS upload field or your printing kiosk says it doesn't recognise the file — even though the thumbnail looks perfectly fine in Explorer.

Here's the short version: that file is already a JPEG. Nothing is corrupted, nothing was re-encoded, and no quality was lost. Windows just picked an unusual file extension for it. Below is why it happens, how to stop it happening again with one registry edit, and the fastest safe ways to go from JFIF to JPG — by renaming, by command line, or online.

JFIF is JPEG — the extension is the only difference

JFIF stands for JPEG File Interchange Format. It's the container convention that virtually every JPEG on the internet already uses: the same FF D8 FF start-of-image marker, the same DCT compression, the same colour data. .jpg, .jpeg, .jpe and .jfif are four spellings of one format.

So why do some programs choke? Because a lot of software decides what a file is by looking at the extension, not the bytes. Older Photoshop versions, some e-commerce and job-application upload forms, photo kiosks and a few Android apps simply filter for .jpg/.jpeg and refuse anything else. If your jfif file won't open in Photoshop, that's almost always an extension filter, not a damaged image.

Why Windows saves .jfif: one registry value

When a site serves an image without telling the browser what to call it (no Content-Disposition: attachment; filename=... header), the browser has to invent a filename. It takes the MIME type from the response — Content-Type: image/jpeg — and asks Windows which extension belongs to that type.

Windows answers from this registry key:

HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg
    Extension  (REG_SZ)  =  .jfif

On many Windows 10 and Windows 11 installations that value is .jfif out of the box. Chrome and Edge both trust it, which is why the same photo saves as .jpg on a colleague's machine and .jfif on yours. Firefox builds its own filename differently, so it often escapes the problem entirely. It is not a Facebook bug, a Chrome bug or a virus — it's a default string in your registry.

Fix it permanently with Registry Editor

This takes about 60 seconds and stops future downloads from ever being .jfif again.

1. Press Win + R, type regedit, press Enter, and accept the UAC prompt.
2. Navigate to HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg.
3. Right-click the image/jpeg key and choose Export first — save it as jpeg-mime-backup.reg so you can undo everything with a double-click.
4. Double-click the Extension value. Change .jfif to .jpg and click OK.
5. Repeat for image/jpg and image/pjpeg if those keys exist and also point at .jfif.
6. Close Registry Editor and fully quit your browser (check the system tray — Chrome and Edge often keep running in the background), then reopen it.

Test it by right-clicking any photo on a news site and choosing Save image as. The suggested filename should now end in .jpg. If you'd rather not touch the registry, there is a manual workaround: in the Save dialog, type the full name yourself — holiday.jpg — and set Save as type to All files. The bytes are identical either way.

Don't edit keys you weren't told to. Everything above is a single string value per key, and the exported .reg file restores the original in one step.

Already have .jfif files? Rename, don't re-encode

Because JFIF and JPG are the same format, the cleanest conversion is a rename. It's instant and mathematically lossless — not one pixel changes.

First, turn on file extensions in Explorer: View → Show → File name extensions. Then press F2 on the file and change photo.jfif to photo.jpg. Click Yes when Windows warns the file may become unusable — it won't.

For a folder full of them, open Command Prompt in that folder and run:

ren *.jfif *.jpg

Or in PowerShell, which handles odd filenames more predictably:

Get-ChildItem *.jfif | Rename-Item -NewName { $_.BaseName + '.jpg' }

If you have ImageMagick installed, magick photo.jfif photo.jpg also works — but understand what it does: it decodes and re-compresses the image, so a 2.4 MB download can come out at 1.1 MB with slightly softer edges. Use it only when you actually want to change quality or dimensions, for example magick photo.jfif -quality 92 -resize 1600x photo.jpg. For a straight format fix, renaming wins.

The no-install route: convert JFIF to JPG online

On a work laptop with no admin rights, on a phone, or when you've got 40 Messenger downloads to clean up before an upload deadline, renaming by hand is tedious and the registry is off-limits. That's the moment to drop the files into our free JFIF to JPG converter — upload the batch, download standard .jpg files, done, no software installed.

It's also the right tool when the upload form rejects more than the extension — some portals cap files at, say, 5 MB, and a converter lets you re-encode a 7.8 MB camera JPEG down to roughly 1.5 MB in the same pass. If you're juggling PNG, HEIC or WebP from the same download folder, the wider image converter hub on File Convert Online covers those too.

Facebook, Messenger and WhatsApp downloads

A Facebook photo download producing a JFIF file is the single most common way people meet this problem, and it follows exactly the mechanism above. Facebook's CDN serves photos from URLs with no helpful extension and no download filename header, so Chrome falls back to the Windows MIME mapping and writes .jfif. Messenger, Instagram and Twitter/X behave the same way.

Two practical notes. If you use Facebook's own Download button on a photo (rather than right-click → Save image as), the site supplies a filename and you usually get a proper .jpg. And once you've fixed the registry value, the same right-click save on Facebook starts producing .jpg immediately — no need to clear anything.

One more gotcha: a messenger photo saved as .jfif that genuinely won't open anywhere may have failed mid-download. Check the file size — a 0 KB or 2 KB file is a truncated download, not a format issue. Download it again.

Your five-minute action plan

• Stop the bleeding: set HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg → Extension to .jpg and restart the browser.
• Clean up the backlog: run ren *.jfif *.jpg in your Downloads folder — lossless and instant.
• No admin rights or on mobile: batch them through the JFIF to JPG converter.
• Only reach for ImageMagick when you actually want to resize or shrink the file, since it re-compresses.

FAQ

Is JFIF the same as JPG? Yes, for practical purposes. JFIF is the standard container JPEG images use; the file content is a JPEG either way. Only the extension differs.

Does renaming .jfif to .jpg lose quality? No. Renaming changes zero bytes inside the file. Re-encoding through an editor or magick is what can cost quality.

Why won't my JFIF file open in Photoshop? Older Photoshop builds filter the Open dialog by extension. Rename to .jpg, or in Photoshop use File → Open As and pick JPEG manually.

Is a .jfif file safe? Yes — it's an ordinary image. Treat it with the same caution as any download from an unknown source, no more.

Will the registry edit break anything? No. You're only telling Windows which extension to suggest for image/jpeg downloads. Existing files and apps are unaffected, and the exported .reg backup reverses it.

Why do I get .jfif in Chrome but .jpg in Firefox? Firefox derives filenames from the URL and its own internal type list rather than the Windows MIME registry, so it sidesteps the mapping.