JFIF to JPG Converter
Drop .jfif files, get .jpg back — 100% in your browser. Fast rename is byte-identical: zero quality loss, zero re-encoding. File data never leaves your device.
Byte-identical fast renameFile data stays on deviceFree · no accountBatch up to 20 files
JFIF and JPG are the same JPEG data, so renaming alone fixes most rejections. Re-encode mode is lossy, drops EXIF data, and JPG has no transparency (a JFIF has none anyway).
Drop JFIF files here
or — multiple files welcome
Up to 25 MB per file · up to 20 files per batch · file data never leaves your device
Privacy proof — verify it yourself
This page processes your images entirely on your device. Your file data never leaves the device — the only third-party requests are the site’s own analytics, which load at page open and never see your files.
External requests while you use this page: 0 (zero — as it should be)
- Press F12 to open developer tools, then open the Network tab.
- Drop a JFIF file above and let it convert.
- Watch the Network tab: no file uploads while it works — the only requests are the site’s analytics, which load at page open. The counter above shows the same number live.
How to convert JFIF to JPG without uploading it
- Pick a mode — fast rename (the default: byte-identical, instant, zero quality loss) or re-encode (a fresh JPEG at your chosen quality, with an optional maximum width). The mode applies to files you add after choosing it.
- Set quality and size — in re-encode mode, JPG quality from 50% to 100% (default 85%) and an optional maximum width. Both are ignored in fast rename mode, because nothing is re-encoded.
- Drop your JFIF files above — or paste one straight from your clipboard. You can add up to 20 at once. Each file is checked by its real contents (magic bytes), not just its name, and each card shows its dimensions and sizes.
- Download each file, or grab everything as one ZIP. Your originals are untouched and your file data never leaves your device.
Why Windows saves .jfif files — and the fix at the source
JFIF — JPEG File Interchange Format — is the standard container for a JPEG-compressed photo, defined in 1991 so that JPEG images could be exchanged reliably between programs. The important fact is simple: a .jfif file is a JPEG. It holds the same compressed pixels you would find in a .jpg file, plus a small header describing resolution and colour information. Renaming it to .jpg usually works, because the image data itself is identical — only the label differs.
So why does Windows keep producing them? When you save an image from a browser on Windows, the browser asks the operating system which extension to use for JPEG data, and Windows has historically answered .jfif. Edge and Chrome on Windows both did this for years, which is why so many Downloads folders are full of .jfif files that look broken everywhere except the browser. The file was never corrupt — the programs that reject it simply check the extension before they look at the contents, and .jfif is not on their list.
You can also stop Windows producing them: open the Registry Editor, go to HKEY_CLASSES_ROOT, then MIME, then Database, then Content Type, then image/jpeg, and change the Extension value from .jfif to .jpg — after that, Edge saves images as .jpg. Only change that key if you are comfortable editing the registry, and back it up first. Files already saved as .jfif still need converting — that is what the tool above does, in seconds.
Fast rename vs re-encode
Fast rename (default)
The original bytes are copied unchanged and saved with a .jpg extension. Byte-identical output, exactly the same size, zero quality loss, EXIF and metadata preserved. Instant — no decoding at all. This is the right choice whenever a site simply refuses the .jfif extension.
Re-encode
The browser decodes the picture and saves a fresh JPEG at the quality you choose, optionally resized. Use it when you need a smaller file or a different size. It is lossy — a new JPEG generation — and EXIF and metadata are dropped. Orientation is applied, so a sideways photo comes out upright.
Honest limitations
- Renaming only fixes the extension — a corrupt or misnamed file stays corrupt or misnamed. This tool checks the magic bytes and tells you what the file really is (PNG, GIF, WebP, AVIF or BMP) instead of guessing.
- Re-encoding is lossy — even at 100% quality, a fresh JPEG throws away a little detail. Do not convert a JPG back and forth repeatedly; keep the original JFIF.
- Metadata is dropped in re-encode mode — EXIF and other metadata in the JFIF is not carried into the new JPG. In rename mode it is preserved byte-identically.
- JPG has no transparency — but a JFIF has no transparency to carry over in the first place, so nothing is lost on that front.
- Converting cannot add detail — the JFIF already contains lossy JPEG data, and the detail JPEG compression discarded is gone for good. A JPG wrapper cannot bring it back.
- Estimates are estimates — the size shown while converting in re-encode mode is a rough model; the real size is shown once conversion finishes. In rename mode the size is exact: it is the input size.
A worked example
Say you saved a product photo from a supplier's website and it arrived as chair-2048.jfif (412 KB), but your marketplace listing form only accepts JPG or PNG. Drop it here in fast rename mode and you get chair-2048.jpg at the same 2048 × 1536 pixels — still 412 KB, byte-identical, because nothing was re-encoded. Upload the JPG: the form accepts it, the photo looks identical, and the EXIF data is untouched. If instead the form had a 200 KB upload limit, switch to re-encode mode at 70% quality and the same photo comes out around 250 KB — then lower the quality a little more, or set a maximum width, until it fits.
Mistakes to avoid
Re-encoding when a rename would do
If the only problem is the .jfif extension, re-encoding throws away quality for nothing. Rename first — it is instant and lossless — and only re-encode when you genuinely need a smaller file or a different size.
Renaming a file that is not a JPEG
Renaming changes only the label, not the contents. A PNG file renamed to .jpg is still PNG data wearing a .jpg name, and most software will refuse it. This tool reads the magic bytes and names the real format instead of guessing.
Expecting better quality
Neither mode can restore detail JPEG compression already removed. Blockiness, ringing and colour smearing in the JFIF survive untouched. The rename's promise is that things get no worse — not that they get better.
Converting back and forth
Every JFIF-to-JPG re-encode adds another generation of compression damage. Rename is free — it adds none — but once you re-encode, keep the result and do not re-encode it again.
Want a PNG instead of a JPG? Our JFIF to PNG Converter converts the same files losslessly to PNG. iPhone photos in HEIC format belong on the HEIC to JPG Converter.
Frequently asked questions
Can I just rename a .jfif file to .jpg?
Yes — and that is exactly what this tool's fast rename mode does for you. JFIF and JPG are the same JPEG data, so changing the extension fixes most rejections: upload forms, design tools and older editors that refuse .jfif will accept the same file as .jpg. The rename is byte-identical, so there is no quality loss and no re-encoding. If you would rather do it by hand, rename the file in your file manager — just be sure the file really is a JPEG first, which this tool checks for you.
Is the fast rename really lossless?
Yes. Fast rename copies the original bytes unchanged and only changes the file name from .jfif to .jpg, so the output is byte-identical to the input — same size, same pixels, same EXIF data and metadata. No pixels are decoded and no pixels are re-encoded, so there is nothing to lose. You can check it yourself: the tool shows the original and converted sizes side by side, and in rename mode they are always exactly equal.
When should I re-encode instead of renaming?
Re-encode when you need something a rename cannot do: a smaller file, a lower quality to fit an upload limit, or a resized image for a profile picture or a listing. Re-encode mode decodes the picture and saves a fresh JPEG at the quality you choose (50–100%, default 85%), with an optional maximum width that never upscales. If all you need is for a site to accept the file, rename is the better choice — it is instant and loses nothing.
Does re-encoding lose quality?
Yes. Re-encoding is lossy: the browser decodes the JPEG and saves it again as a new JPEG, which throws away a little more detail with every generation — even at 100% quality. That is why rename is the default. Use re-encode only when you need a smaller file or a different size, keep the original JFIF, and do not re-encode the same file back and forth.
Why does Windows save images as .jfif instead of .jpg?
When you right-click and save an image in a browser on Windows, the browser asks Windows which extension to use for JPEG data, and Windows has historically answered .jfif. The file itself is a normal JPEG — only the name is unusual. That is why the image opens fine in your browser but is refused by upload forms, design tools and older editors that check the extension before they look at the contents. You can also fix it at the source in Windows: open the Registry Editor, go to HKEY_CLASSES_ROOT, then MIME, then Database, then Content Type, then image/jpeg, and change the Extension value from .jfif to .jpg — then Edge saves images as .jpg. Only change that key if you are comfortable editing the registry, and back it up first.
What happens to EXIF data and metadata?
In fast rename mode, everything is preserved exactly, because the file bytes are copied unchanged — camera settings, date, orientation and any other metadata stay as they were. In re-encode mode, EXIF and other metadata are dropped: the browser decodes only the pixels and encodes a fresh JPEG, so the new file carries no camera data. Orientation is still applied in re-encode mode, so a sideways photo comes out upright.
Does JPG support transparency?
No — JPG has no transparency, and a JFIF has no transparency to carry over in the first place, so nothing is lost on that front. A JFIF photo is always fully opaque. If you need transparency, convert to PNG instead: our JFIF to PNG Converter does that in your browser too.
Is there a file size or daily limit?
No daily limit, no account. A 25 MB cap per file, a 50 megapixel cap per image, and 20 files per batch apply, because browsers cannot safely hold larger images in memory. Photos saved from the web are normally well under 1 MB, so the cap rarely matters.
Do my images leave my device when I convert them here?
No. Your browser already knows how to read JFIF and JPEG files, so this tool either copies the file bytes unchanged (fast rename) or asks the browser to decode and re-encode them (re-encode mode) — all with JavaScript running on your machine. Your file data never leaves your device — the only third-party requests are the site's own analytics, which load at page open and never see your files. You can verify this in your browser's Network tab, or disconnect your internet after the page loads and convert anyway.