Convert JFIF to JPG
Edge or Chrome saved your picture as .jfif and the form only takes .jpg? Get a standard .jpg here, in batch, in your browser, and make Windows stop doing it.
Your images
Settings
Generated images
- Nothing uploaded
- Free, no sign-up
- Strips EXIF
- Batch files
You clicked Download on a photo in WhatsApp Web, saved an attachment preview from Outlook, or right-clicked a picture in Edge, and what landed in Downloads is photo.jfif. Now the claim form, the job application or the marketplace listing greys out the button or answers "allowed types: .jpg, .jpeg, .png". The picture itself is fine: a .jfif is a JPEG, byte for byte. Windows simply handed the browser a different extension.
This page reads the file and saves a new .jpg at the quality you set, a single file or an entire folder at once, downloaded singly or as a .zip. Fair warning before you start: if you have one file and it really is a JPEG, renaming it in Explorer works too. This page earns its keep when there are dozens of files, when the form also limits the kilobytes, or when the .jfif turns out to be a PNG or WebP in disguise.
The decoding and the new JPEG encoding both happen inside your browser, with no server in the loop, so the chat photos stay on your PC from start to finish. Further down you will find the registry value that makes Windows say .jfif, and how to set it back.
How it works
The format needs no attention here; the real decision is how hard to re-encode a picture that WhatsApp or a web server has already compressed once.
Drop in the .jfif files
Select the .jfif files in Downloads — Ctrl+A catches everything a WhatsApp Web session left there — and drag the selection onto the page, or click Choose images and multi-select. Loading ignores the name and opens the bytes, so a .jfif that secretly holds PNG or WebP data is decoded without complaint.
Keep JPG, set the quality
The output button sits on JPG when the page opens; leave it there. Quality starts at 82, plenty for a chat photo WhatsApp has already compressed; go up to 90–95 for a scan or a camera original that has to survive printing, and lower it toward 70 only when the form counts kilobytes as well as extensions.
Generate, compare, download
Press Generate images and each card keeps its file name, now ending in .jpg instead of .jfif, with before and after sizes on it. Compare puts the two versions under a slider if you want to inspect a face or a signature up close; then save cards singly or hit Download all for one .zip.
Why Windows saved it as .jfif in the first place
Edge, Chrome and other Chromium browsers ask Windows which extension belongs to image/jpeg whenever a download arrives without a usable file name, as WhatsApp Web photos and Outlook previews do. The answer sits in one registry key, HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg, whose Extension value reads .jfif on many Windows 10 and 11 PCs. Nothing is converted; the browser writes the bytes it received under the name Windows suggested.
Windows Photos and Paint open a .jfif fine. The trouble starts with upload fields whose allowlist reads .jpg, .jpeg, .png, and with Open dialogs that filter by extension until you pick All files.
Rename, paste or convert: which fix fits
Same download, same bytes: a rename is often the cheapest fix. Which route is enough depends on the file count and on what the form checks.
| Fix | Good for | Watch out |
|---|---|---|
| Rename in Explorer (F2) | One or two files that really are JPEG | Turn on View > Show > File name extensions first, or you get photo.jpg.jfif |
| Copy image, Ctrl+V here | One picture still open in the browser | The clipboard holds one image at a time |
| Convert on this page | Many files; a size cap; .jfif files that are really PNG or WebP | Lossy re-encode at the quality you pick; EXIF removed |
| Fix the registry value | Future downloads | Does nothing for files already on disk |
How to stop Windows from creating .jfif files
Press Win+R, type regedit, accept the administrator prompt and open HKEY_CLASSES_ROOT\MIME\Database\Content Type\image/jpeg. Double-click Extension, replace .jfif with .jpg, click OK and restart the browser. Edge and Chrome then save .jpg on that PC; files already in Downloads keep their old name.
Registry Editor locked at work? Type .jpg into the Save As name yourself, which the browser honors, or skip the disk: copy the picture in the browser, paste it here with Ctrl+V and download the .jpg.
Is a .jfif lower quality than a .jpg?
No. JFIF is the container most JPEGs use: open a .jpg in Notepad and a few bytes in you can read the letters JFIF. Phone cameras write an Exif header instead; many files carry both. The quality was fixed by whoever encoded the picture, and the extension has no say.
Converting here is a lossy decode and re-encode, invisible at 90–95. Whether the file shrinks depends on its source: a camera JPEG saved near 95 sheds about a third of its bytes at 82, but WhatsApp already squeezed a chat photo to about 1,600 px and quality 70–80, so a second pass at 82 lands roughly where it started, sometimes a shade above. For a hard kilobyte limit, use the Compress image to 100 KB page. Need the exact bytes? Rename instead.
- Output: a baseline JPEG starting with FF D8 FF, typed image/jpeg, EXIF stripped.
- Pixel size is untouched below 10,000 px on the longer side, far beyond a 12 MP shot's 4,032 × 3,024; bigger images are reduced to fit.
Frequently asked questions
Windows warns the file "might become unusable" when I rename .jfif to .jpg. Is that safe?
Yes, for a genuine JPEG. Explorer shows that dialog for any extension change and it says nothing about this particular file; the bytes inside are not touched, and Photos, the form and everything else read it as the JPEG it always was. Click Yes. If the thumbnail breaks afterwards, the file was never a JPEG.
Why does WhatsApp Web give me .jfif files when the phone app saves .jpg?
The phone app writes the name itself, IMG-20240915-WA0012.jpg, straight into its WhatsApp Images folder. WhatsApp Web names nothing: it passes your browser a stream marked image/jpeg, and on Windows the browser appends whatever extension is registered for that type. Copy the pictures off the phone over a USB cable, or share them from the phone's gallery, and they arrive as .jpg with nothing to convert.
Will the .jpg from this page get past a form that rejected the .jfif?
Yes. The output is a freshly written JPEG with a .jpg extension and the type image/jpeg, so it satisfies both kinds of validator: the ones that look only at the name and the ones that read the first bytes.
The WhatsApp Web photo is only about 1,600 px wide. Can converting it bring the full resolution back?
No. WhatsApp shrank the picture to roughly 1,600 px along its longer edge and re-encoded it before it reached your browser, and the pixels it dropped are gone; the .jpg keeps the 1,600 px it was given. Ask the sender to share it again as a document (paperclip, then Document) and the original arrives untouched: name, size and EXIF included.
I renamed the file to .jpg and it still will not open. What is it?
Probably not a JPEG at all: some servers send PNG or WebP data under an image/jpeg label, and the .jfif name hid it. Drop it here — the browser decodes by content and writes a real JPG.
Does the .jfif keep the photo's date and location, and what happens to them here?
A .jfif can carry an Exif block with camera model, timestamp and GPS coordinates. This page strips all of it, so the .jpg you download is clean; keep the original if you need that data.
These are private chat photos. Are they sent anywhere to be converted?
No. Everything happens inside the tab you have open: the browser reads the .jfif, redraws it and writes the .jpg with its own image code, and the site never receives a copy. The .zip is packed on your PC as well; switch Wi-Fi off once the page has loaded and the conversion still finishes.