Convert JFIF to JPG online, free

Why your download suddenly came out as .jfif

The culprit is a well-known Windows quirk involving the registry. When Chrome or Edge saves an image, Windows decides the file extension from the registry association for the image/jpeg MIME type. It looks under HKEY_CLASSES_ROOT in the MIME\Database\Content Type\image/jpeg key and reads the Extension value, which is supposed to be .jpg.

On some machines that Extension value is wrong, missing, or has been overwritten by another program. When it is broken, the browser has nothing sensible to use, so it falls back to the format's other registered name and writes the download as .jfif instead of .jpg. The image is untouched; only the chosen extension changes.

The usual trigger is saving a photo from a website with right-click and Save image as. That is why the problem feels random: most of your downloads are .jpg, then one day a saved photo lands as .jfif and your photo viewer shows an unfamiliar icon or an unknown-file warning.

Nothing about the file is corrupt. The bytes are a valid JPEG and any tool that reads the contents rather than the name will open it fine. The .jfif label is the only thing out of place, which is exactly why a rename or a re-save resolves it instantly.

Why apps and forms refuse to open it

Most upload forms and a lot of desktop apps decide what they accept by matching the file extension, not by inspecting the bytes. A form configured for .jpg, .jpeg, and .png will reject a .jfif on sight, even though the data inside is the same JPEG it would happily accept under a different name.

This is purely a string comparison. The validator sees the characters after the dot, does not find .jfif in its allowed list, and stops there. It never decodes the image, so it never learns that the file is a normal JPEG. The picture is fine; the extension just is not on the guest list.

Older programs and import dialogs behave the same way. A photo kiosk, a legacy editor, or an app's file picker that only lists .jpg files will treat your .jfif as invisible or unsupported, throwing an unsupported-format message that makes the file look damaged when it is not.

The fix follows directly from the cause. Because the rejection is about the extension and not the contents, giving the file a .jpg extension, by renaming or by re-saving it here, is all that is needed for the same image to sail through.

Rename versus re-encode: the honest difference

Because a .jfif already is a JPEG, the most literal fix is a rename. Change the extension from .jfif to .jpg in your file manager and the file works as-is, with no decoding and no quality change. This is genuinely lossless and instant, and on a desktop it takes a couple of seconds per file.

The snag with renaming is visibility. Windows hides file extensions by default, so you have to enable Show file name extensions in File Explorer's View settings before you can edit them, and on phones or tablets renaming is awkward or impossible. For a single file that is a minor chore; for a folder of them it gets tedious fast.

This tool takes the other route. It decodes the JFIF and re-encodes a clean, standard baseline JPG at quality 90, then hands you a file with the correct .jpg extension. That is technically one extra JPEG generation, but at quality 90 it is visually identical to the source, and you never touch the registry or fiddle with hidden extensions.

So pick by situation. Rename by hand when you want a strictly zero-loss result and have one or two files on a desktop. Use this tool when you want a guaranteed standard JPG with the right extension, when you are converting many files at once, or when you are on a device where renaming is a pain. Both end with a file that every app accepts.

How imgkilo converts a JFIF locally

The pipeline runs entirely in your browser. When you drop a .jfif, the browser recognises it as the JPEG it actually is and decodes it into raw pixels, exactly as it would for any .jpg. There is no special JFIF handling needed, because there is nothing special about the data.

Those pixels are then drawn onto an HTML canvas at full resolution. The canvas is re-encoded as a standard baseline JPG at quality 90, producing a clean file that carries the conventional structure any extension-checking app expects. The output name keeps your original filename with a proper .jpg ending.

Nothing leaves your device at any point. The original JFIF and the new JPG both stay in local memory, so private documents, ID scans, and personal photos never touch a server. The page behaves the same whether you are online or not once it has loaded, because the conversion is all local.

If you have a stack of them, the same pipeline runs in parallel. Drop up to 100 files, each is decoded and re-encoded across your machine's cores, and the results come back as a single ZIP. For a one-off file, the download starts the moment encoding finishes.

Stopping Chrome and Edge from saving .jfif at the source

If you keep getting .jfif downloads, you can fix the cause rather than convert every file. The root problem is that broken registry Extension value for the image/jpeg MIME type, and correcting it makes the browser save .jpg again going forward. This is a real fix, but editing the registry is for confident users, so back it up first.

Open the Registry Editor and navigate to HKEY_CLASSES_ROOT, then into MIME\Database\Content Type\image/jpeg. Look at the Extension value in that key. If it reads anything other than .jpg, or is missing, that mismatch is what makes your browser choose .jfif when it saves a JPEG.

Set the Extension value to .jpg exactly, including the leading dot, and confirm. Close the editor and restart Chrome or Edge so they pick up the change. From then on, saved JPEG images should land with the .jpg extension and the .jfif surprises should stop.

If you are not comfortable in the registry, do not force it. Keep using this converter, or rename files by hand, and leave the registry alone. The conversion approach has no risk and reaches the same result, just one file at a time rather than fixing it once at the source.

When you need more than an extension fix

Sometimes the .jfif is only your first problem. If an upload form also caps the file size, convert here first and then run the JPG through the compress to a KB target tool, which iterates the quality to land under a limit like 100 KB or 200 KB without you guessing at settings.

If the file is simply too large and you want quality-based shrinking rather than an exact size, the compress JPEG tool reduces it with a single quality control. That pairs naturally with this converter when a saved web photo is both wrongly named and heavier than you need.

If you have a mixed pile of formats, not just .jfif, the bulk image converter handles a folder of different types in one drop. Use this dedicated page when everything is JFIF and you want the cleanest, most predictable JPG output.

And if you actually need a different format rather than a JPG, that is a separate job. To open a saved image somewhere that wants WebP, or to get a JPG from a PNG screenshot, reach for the matching converter; this page is specifically the extension-and-clean-resave fix for files that are already JPEG.