Make HEIF and HEIC Photos Easier to Share as JPG

HEIF stands for High Efficiency Image File Format. It is a container format designed to store images efficiently, and HEIC is a common filename extension for HEIF images encoded with HEVC. Apple devices often use HEIC for photos because it can store photographic images efficiently while retaining useful image detail. The format is supported by many modern devices and applications, but some older desktop programs, upload forms, office workflows and websites still request JPG or JPEG files.

JPG remains a practical delivery format when compatibility is more important than keeping the original high-efficiency encoding. A JPG copy can be attached to an email, added to a document, uploaded to a portal or opened by a wide range of image applications. The conversion process decodes the HEIF image and creates a new JPEG. JPEG does not preserve every feature of the original HEIF container, and a new lossy encode can change image data. Keep the original HEIF or HEIC file when it matters.

Current TinyImageResizer implementation note: the HEIF route has an input-validation defect. The subtool is configured with the format label `HEIF`, but the shared validator has a special-case check for `HEIC` and no matching `HEIF` extension or MIME map. As a result, HEIF/HEIC files can appear in the file picker's accepted types but are rejected by the validation step before conversion begins. The app does include the `heic2any` library and the processing code has a HEIC/HEIF conversion branch, but users cannot reliably reach that code through the current HEIF route until the validation mapping is fixed.

HEIF is the broader image container format name. HEIC is commonly used for HEIF images encoded with HEVC, and the two extensions are often mentioned together in phone-photo conversion workflows. The TinyImageResizer HEIF picker accepts `.heif` and `.heic` extensions and the matching HEIF/HEIC MIME types. The route is intended to create JPG output, but the validation mismatch currently prevents the normal upload flow from succeeding.

A file extension alone does not reveal every property of an image. HEIF containers can hold image sequences, auxiliary images and metadata in addition to a primary photograph. A simple conversion to JPG generally creates a conventional still image from the selected primary image. It should not be assumed to preserve every sequence, depth representation, edit instruction or auxiliary item from the original container.

This is the reliable workflow while the TinyImageResizer HEIF validator remains unfixed. Once the route accepts the HEIF format label correctly, its existing conversion branch can be retested and the instructions can be updated to reflect the verified behaviour.

A receiving service may restrict file types even when a browser or phone can display HEIF. Converting the photo can remove that format mismatch and produce a file that can be included in forms, office documents, email attachments and older software. JPG is also a convenient format for sharing photographs with people whose devices or apps have limited HEIF support.

Conversion is not an image-enhancement process. It does not automatically sharpen a photo, increase its pixel dimensions, remove compression artefacts or recover information that was lost earlier. The output's appearance depends on the source, the decoder and the JPEG encoding settings. The current code's HEIF processing branch requests JPEG output at a quality value of 0.92, but the route's validation defect prevents users from consistently reaching that step.

A HEIF image may contain capture information, orientation, colour data and additional image properties. A browser conversion pipeline decodes an image and draws the visible pixels to a canvas before exporting a new file. That creates a rendered image rather than a byte-for-byte copy of the original HEIF container. Do not assume that all original metadata, depth information, burst frames or editing instructions will be preserved in the JPG.

The intended conversion branch uses the `heic2any` JavaScript package to decode HEIC/HEIF input in the browser and then render the converted image. The library itself is designed for client-side HEIC/HEIF conversion. However, because the route currently rejects files in its validation stage, do not claim that the live HEIF page reliably processes local files until that defect is corrected and tested. When the tool is fixed, confirm whether the final deployed bundle loads the library locally and review the website's privacy policy before making broad privacy statements.

A complete fix should add `HEIF` to the format-validation extension and MIME maps, or normalize the HEIF subtool label to the existing HEIC validation path. Test `.heif` and `.heic` files separately, including files with empty MIME types, large images, portrait orientation and different phone generations. Verify that the output is a valid JPEG and that the extension and MIME type match. Test multiple files and the ZIP download as well.

Until that work is deployed, this page explains why a HEIF photo may need a JPG copy and how to export one with a compatible application. It should not promise that the current TinyImageResizer upload route completes the conversion. Keep the original HEIF photo and use the JPG as a separate compatibility copy.