What is a JFIF file, and why won't it open?

You saved a picture from a website or an email and Windows called it IMG_2481.jfif. The photo editor will not touch it, the upload form rejects it, and nothing on the machine seems to know what it is.

The file is fine, because it is a JPEG already.

JFIF is the JPEG's proper name

JFIF stands for JPEG File Interchange Format, the 1992 standard describing how JPEG image data is wrapped into a file. Every ordinary .jpg on your computer follows it. The two are the same format wearing different labels: rename a .jfif to .jpg and the picture opens, byte for byte unchanged.

That is the whole trick, and it is why the problem feels absurd. Most of your software has read this format for thirty years and is pretending not to recognise it.

Why Windows picked that name

When a browser saves an image, it asks Windows which extension belongs to that type of file. The answer lives in the registry, and on a good number of machines the entry for image/jpeg reads .jfif instead of .jpg. Edge follows that entry. Chrome and Firefox usually do not.

Which is why it looks random. Same site, same image, different browser, different extension.

Where it breaks

• Upload forms. Job applications, insurance claims, listing sites and government portals check the extension before anything else. The rejection message rarely mentions the format.
• Photo editors. Photoshop, Paint.NET and most phone galleries filter by extension when they open a folder, and the file is invisible rather than broken.
• Anything expecting a photo. Printing services, CMS uploaders, email clients that preview attachments.

Windows Photos will usually open it, which adds to the confusion: the file works in the one place you did not need it to.

Four fixes, permanent first

1. Change the registry entry so it stops happening. Open Registry Editor, go to HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg, and change the Extension value from .jfif to .jpg. Downloads land as .jpg from then on. Back the key up first, and skip this one if editing the registry makes you uneasy - the other three fixes cost nothing and break nothing.

2. Rename the file. In File Explorer, View, then Show, then File name extensions. Change .jfif to .jpg and accept the warning. The image data is untouched, because there was never anything to convert.

3. Convert a folder at once. Renaming forty files by hand is miserable. JFIF to JPG hands each file back with the new extension and identical bytes. Nothing is recompressed and no quality is lost.

4. Send it somewhere else entirely. If the destination wants a PNG, JFIF to PNG redraws it losslessly. If it needs a document, JFIF to PDF places the picture into one page at its own size.

The question worth asking

Does converting lose quality? Only in fix 4. Renaming changes the label on the box. The picture inside is identical and the metadata survives with it. Converting to PNG or PDF redraws the image, which is lossless in itself, though it cannot restore detail the original JPEG compression discarded years ago.

If a form has rejected your file and you need it fixed in the next minute, use fix 2. If this is the third time this month, use fix 1.