Convert JFIF to JPG — Free, Fast & Private
A .jfif file is not some exotic format you have never heard of — it is a plain JPEG wearing an unfamiliar extension. JFIF stands for JPEG File Interchange Format, and it describes the standard container that almost every JPEG on the internet already uses. Windows sometimes labels downloaded images .jfif instead of .jpg, and suddenly a perfectly ordinary photo gets rejected by upload forms, refuses to open in older software, and confuses everyone it is sent to.
The jfif to jpg conversion is therefore the gentlest job an image tool can do. MiniPx identifies files by their magic bytes rather than their extension, so a .jfif decodes exactly like any JPEG, then re-saves as a standard .jpg at Gentle quality (82%). Because the source and target use the same compression scheme, the output looks identical to the original at any normal viewing size. Everything happens locally in your browser — no server ever sees the file.
If you have a folder of them, drop several in at once. The free tier handles 5 files per batch with no daily quota, and each result card shows the input and output sizes before you save anything.
Why Windows saves images as .jfif
When you save an image from a web page, the browser asks Windows what file extension belongs to the MIME type image/jpeg. Windows keeps that mapping in its registry, and on many machines the registered answer is .jfif rather than .jpg — a technically defensible choice, since the file really is in JPEG File Interchange Format, but a practically annoying one. The image data is untouched; only the label differs. This is why the problem appears out of nowhere after an update or on a new PC, and why it mostly affects images saved from browsers rather than photos from a camera.
JFIF vs JPG: the actual technical difference
JPEG itself is a compression method, not a file layout. A file needs a container that says where the image starts, what resolution it has, and how the compressed data is arranged. JFIF is that container: it places an APP0 marker segment, tagged with the ASCII string "JFIF", immediately after the start-of-image marker. Camera photos typically use the sibling Exif container instead, which puts an APP1 segment in the same position to carry metadata like GPS and exposure settings. Both are JPEG files; both normally carry the .jpg extension. A .jfif file is simply one where the software that saved it chose to advertise the container in the extension. The pixels inside are encoded identically either way.
Why websites and uploaders reject .jfif
Upload forms rarely inspect file contents. Most validate the filename against a whitelist — .jpg, .jpeg, .png, maybe .webp — and anything else bounces with an "unsupported file type" error, even though a .jfif would decode perfectly if the server bothered to look. Job portals, government forms, CMS media libraries, and marketplace listing tools are the usual offenders. Converting to a real .jpg (or in a pinch, renaming — see the FAQ) resolves the rejection permanently, because the extension finally matches what the validator expects.
How to stop Windows creating .jfif files
The permanent fix is a registry edit. Open the Registry Editor and navigate to HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg, then change the Extension value from .jfif to .jpg. From then on, browsers that defer to Windows for the extension will save JPEGs as .jpg. If editing the registry feels risky, the low-tech alternative works too: keep saving as .jfif and run the files through this page whenever a form complains. For images already on disk, converting is faster than fixing the cause.
Quality: what changes and what does not
Since JFIF and JPG share the same encoding, there is no format-level quality penalty in this direction — nothing analogous to flattened transparency or a collapsed colour palette. MiniPx decodes the image and re-encodes it at Gentle (82%), a setting chosen for exactly this kind of re-save: the generation loss it introduces is below what the eye can pick up at normal viewing sizes, and the output is often meaningfully smaller than the input because browsers save web images at generous quality levels. If the file is headed for the web afterwards, consider going one step further and converting the JPG to WebP; if it needs to hit a size limit, the JPEG compressor gives you preset control. And if you need a lossless working copy instead of a compatible one, JFIF to PNG is the direction to take.