Why convert JFIF to HEIC then?

JFIF (JPEG File Interchange Format) is the original 1992 specification that defined how JPEG-compressed data is wrapped in a file - the file you call a .jpg is technically a JFIF-wrapped JPEG stream. Windows 10's October 2018 update changed the default save extension in Chrome, Edge, and Outlook from .jpg to .jfif for some image saves, which is why thousands of users found their downloads carrying an extension many apps refuse to open. The bytes are ordinary JPEG; only the wrapper naming differs.

Converting JFIF to HEIC is a genuine re-encode, not a rename: the JPEG data is decoded and re-compressed with HEVC, typically producing files 40-50% smaller at the same visual quality. That makes this conversion attractive for exactly the files JFIF tends to be - piles of images saved out of Outlook threads and browser sessions that you want to keep but not pay JPG-sized storage for. Once converted, the files behave as first-class photos on Apple devices and in Google Photos, with EXIF metadata carried across.

Because JPEG and HEVC are both lossy, the conversion inherits whatever compression artefacts the source already had and adds a small generational loss of its own - convert once at high quality and don't round-trip. If your actual problem is only the .jfif extension (an app whitelists .jpg and rejects .jfif despite identical contents), the cheaper fix is a simple rename to .jpg; reach for HEIC when you also want the storage savings or Apple-library integration. To go back the other way for a stubborn upload form, HEIC to JPG completes the loop.

Reasons to convert JFIF to HEIC usually come down to compatibility, file-size, or specific feature requirements. Common situations:

• An app or platform only accepts HEIC uploads.
• You need a feature unique to HEIC (e.g. transparency, vector scaling, animation, multi-page pages, etc.) that JFIF doesn't provide.
• You're optimising file size — modern formats often produce smaller files than the older format you started with.
• You need a single archival format across a project so files behave consistently in the same viewer.

1. Open the JFIF → HEIC tool on heic.now.
2. Drag your JFIF file onto the drop zone, or click Select files. You can drop a whole folder of files at once.
3. The output is fixed to HEIC. If the format supports extra options (page size, transparency background, quality, EXIF stripping), tweak them in the right-hand panel.
4. Click Convert. The job runs on our server and finishes in a few seconds for typical photos.
5. Download the result. Files stay in storage for 24 hours and are then permanently deleted.

The entire flow is free for the first 10 jobs per day with no signup required. A free account doubles that quota; a premium plan removes the limit entirely.

• This is a lossy-to-lossy re-encode - use a high quality setting and convert once, rather than bouncing files between JPEG and HEIC repeatedly.
• If you only need a different extension, rename .jfif to .jpg - the bytes are identical JPEG. Convert to HEIC when you want the ~50% storage saving too.
• Stop Windows creating JFIFs at the source: edit the registry at HKEY_CLASSES_ROOT > MIME > Database > Content Type > image/jpeg and set Extension to .jpg.
• EXIF metadata carries through the conversion - strip it first if the images come from an inbox and may embed sender-side GPS or device data.
• Heavily compressed JFIF sources (webpage saves at quality 60-70) gain less from HEIC - the artefacts are already baked in and re-encoding can't remove them.