Initializing... drag & drop files here
Supports: HEIC
Almost everyone who lands here has been handed a requirement rather than a preference: a form, a portal or an old application asks for a .jfif file and will not take the HEIC an iPhone produced. The good news is that JFIF is not an exotic format at all — it is the JPEG File Interchange Format, standardised as ITU-T Recommendation T.871 in May 2011, and the bytes inside a .jfif file are ordinary JPEG data. This tool decodes the HEIC and writes a JPEG-coded image with the .jfif extension, which is exactly what those systems are looking for.
| Property | HEIC | JFIF |
|---|---|---|
| Standard | HEIF — ISO/IEC 23008-12 (MPEG-H Part 12) | JPEG File Interchange Format — ITU-T T.871 |
| Image coding | HEVC (H.265) intra-coded pictures | Baseline JPEG, the same coding a .jpg uses |
| Compression | Lossy, roughly half the size of a comparable JPEG | Lossy, and the yardstick everyone else is measured against |
| Colour depth | 8-bit, or 10-bit for HDR captures | 8-bit per channel |
| Transparency | Can carry an alpha channel | None — alpha must be flattened onto a colour |
| Multiple images | Yes: bursts, image sequences, depth maps | One image per file |
| Native browser support | Safari 17 and later only | Every browser ever shipped decodes JPEG |
| Where it comes from | The default iPhone camera format since iOS 11 (2017) | Windows and some browsers save JPEG downloads with this extension |
.jfif among its accepted uploads..jfif extension and you want consistency..jfif extension. In that case use HEIC to JPG: identical image data, an extension every program recognises on sight..jfif even though they can decode it perfectly..heic files onto the page or click "Add Files". The whole batch converts with the same settings, and the output extension is fixed to .jfif — there is nothing to choose..jfif. Files are uploaded over an encrypted connection, processed on our servers and deleted automatically after a few hours — no sign-up, no watermark.| Quality Preset | JPEG quality value |
|---|---|
| Highest | 100 |
| Very High (Recommended) — default | 95 |
| High | 90 |
| Medium | 80 |
| Low | 70 |
| Very Low | 60 |
| Lowest | 50 |
Every preset also enables optimised Huffman coding, which shaves a few per cent off the file with no effect on the picture. Above about 95 the extra bytes buy very little visible quality, so the default is deliberately placed there rather than at 100.
For practical purposes, yes. Both hold JPEG-compressed image data; JFIF is the interchange format that defines how that data is packaged, and it has been the de facto wrapper for JPEG files since the early 1990s. A typical .jpg file on your disk contains a JFIF header segment too. The difference you actually experience is the extension, and therefore which programs agree to open the file without argument.
Usually, yes — the bytes are JPEG either way, so renaming is enough for most viewers and editors. The reason to convert rather than rename is the other direction: your source here is HEIC, which is not JPEG data at all and cannot be fixed by renaming. Once you have the .jfif from this tool, renaming it to .jpg is a safe extra step if some program insists on the more familiar extension.
Because of how Windows maps the image/jpeg content type when saving downloads. For years, saving a JPEG image from a browser on Windows could produce a .jfif file rather than a .jpg, which is why the extension turns up in download folders belonging to people who have never heard of it. The file was always a normal JPEG; only the name looked unfamiliar.
Some, unavoidably. HEIC is already lossy, and JPEG is a different lossy codec, so the image is decoded and re-encoded rather than repackaged — there is no way to carry HEVC-coded data into a JPEG file untouched. At the default quality of 95 the loss is very hard to see on a photograph. If you are going to edit the result heavily afterwards, use Highest, or convert to PNG and work from that.
Because HEIC is the newer and much more efficient codec. HEVC intra-coding typically stores a photograph in around half the bytes JPEG needs for comparable quality, so going from HEIC to any JPEG-based format normally roughly doubles the file size. That is the price of a format everything can open. Lowering the Quality Preset or setting a specific file size brings it back down at the cost of visible detail.
It is matted onto the Background Color, which defaults to White and offers a palette of named colours in the dropdown. JPEG has no alpha channel, so something has to fill the transparent pixels; picking the colour yourself avoids the black backgrounds that appear when a converter silently defaults to it. Most iPhone camera photos are fully opaque, so this only matters for images that have been edited.
Choose "Specific file size" under Image Compression and enter your limit. The converter re-encodes the photo repeatedly, narrowing in on the highest JPEG quality that still fits under the target. Leave Auto Scale enabled if you also allow the dimensions to shrink — for aggressive targets such as a few hundred kilobytes from a 12-megapixel photo, quality reduction alone will not get there and a smaller frame size is the only honest way to reach it.
Yes. Queue as many HEIC files as you like and they are all converted with the settings you chose, then downloaded together. Because the settings are shared across the batch, it is worth converting one photo first to check the Quality Preset looks right before you push a few hundred through.
They are uploaded over an encrypted connection, converted on our servers and deleted automatically after a few hours, along with the JFIF files produced from them. Nothing is published, shared or indexed, there is no account to create, and no watermark is added to the output.