Why Chrome downloads a JFIF
The .jfif in Downloads is almost always a normal JPEG that Windows labeled from the MIME database. Convert it to a .jpg on Tinolia when Outlook or a form refuses the extension. Files are deleted within 1 hour.
https://cdn.example.com/photo.jpg
Save asphoto.jfif
JFIF is a JPEG label, not a new picture format
JFIF means JPEG File Interchange Format. The pixels are the same family of JPEG data Photos, Word, and most editors already know. What changed on your PC is the filename ending Windows attaches when a program asks for the default extension of image/jpeg.
That is why the file often opens in Photos and still fails an upload that only lists JPG or JPEG. The allowlist is reading the extension string, not inventing a second codec.
Why Chrome and Edge write .jfif on this Windows
Chrome does not invent .jfif on its own. On Windows it asks the MIME database what extension belongs to image/jpeg. When that key says .jfif, Save image as and many downloads land with that ending even though the URL still shows .jpg.
Edge behaves the same way because it shares the same Windows mapping. A Windows update, or another app that rewrites the key, can flip the extension back to .jfif after you thought you fixed it.
Rename can work. Re-encode is safer for picky forms
If Photos already opens the file, renaming photo.jfif to photo.jpg often is enough for Explorer and for a site that only checks the suffix. Show file extensions first so you are not sticking .jpg on top of a hidden .jfif.
Some portals still sniff the name in a way that fails, or hide .jfif in the file picker. When rename does not clear the error, write a fresh .jpg with JFIF to JPG instead of arguing with the field.
- In Explorer, turn on File name extensions under View.
- Rename one .jfif to .jpg and try the upload.
- If the form still rejects it, drop the originals on JFIF to JPG and download .jpg files.
Registry edits fix the next download and bring risk
The key people change is under HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg, the Extension value from .jfif to .jpg. That can make future Chrome saves use .jpg. It does nothing for the files already in Downloads, and a later Windows update or another program can flip the value back.
Editing the registry on a work laptop can also violate IT policy. Converting the files you have avoids touching the machine and still satisfies Outlook or an HR portal that only lists JPG.
Convert when Outlook or a form rejects .jfif
Outlook attachments and older upload fields treat an unknown extension as an unknown type. The error rarely says what would have worked. JFIF to JPG writes a standard .jpg that those fields already expect. Up to 10 files, 20 MB each, over HTTPS, deleted within 1 hour.
- Drop the .jfif files. Up to 10 files, 20 MB each.
- Download the .jpg files, or a ZIP for a batch.
- If the form also names a size cap, follow with a 200 KB target.
If Chrome saved a WebP, that is a different download
When the file lands as .webp while the URL still ends in .jpg, the server answered with image/webp because Chrome advertised it. That is a real format change, not a Windows extension map. Start at Chrome WebP.
A .webp Windows will not preview at all is WebP on Windows. Stay on this page when the bytes are JPEG and only the ending says JFIF.
Questions
Is a JFIF file the same as a JPG?
A .jfif from Chrome on Windows is almost always JPEG data with a different extension. Photos usually opens it. Upload forms that only list JPG may still refuse the name.
Is renaming .jfif to .jpg enough?
Renaming often works when the bytes are already JPEG. If the portal still rejects the file, or the picker hides .jfif, write a fresh .jpg with JFIF to JPG.
Why does Chrome download JFIF instead of JPG?
Chrome asks Windows which extension belongs to image/jpeg. When that MIME entry says .jfif, the saved name follows it even if the URL showed .jpg.
Does changing the registry keep working after Windows Update?
The Extension value under image/jpeg can flip back after an update or another installer. Treat registry edits as temporary for future saves, not as a fix for files you already have.
Will Photoshop open a .jfif?
Current Photoshop builds usually open .jfif the way they open JPEG. Older plugins and batch scripts that filter on .jpg may still skip the file until you rename or convert.
Will an HR portal reject a .jfif upload?
Many Workday-style and older HR uploaders only list JPG or JPEG. If rename does not clear the reject, write a fresh .jpg with JFIF to JPG.
Can I convert a whole folder of JFIF downloads?
Drop the batch on JFIF to JPG and download a ZIP of .jpg files. That leaves the Windows registry alone.
WhatsApp Web will not attach my .jfif. Why?
WhatsApp Web often filters the picker to common image extensions. A .jpg from JFIF to JPG shows up in that list and attaches like any other photo.
More guides like this
- Open iPhone HEIC photos on WindowsWindows ships no HEVC decoder for stills, so Explorer draws nothing. Install the two Store packages to look, or send JPEG to the portal that refused it.
- Insert HEIC into PowerPointPowerPoint Insert Pictures needs HEIF and often HEVC on Windows. When Insert fails or the deck must open elsewhere, convert the iPhone still to JPEG first.
- Why the upload rejects your SVGJob portals and marketplaces often allowlist PNG or JPEG only. SVG is vector XML, so the field fails until you rasterize a PNG for the upload.