Choose a HEIC photo
Drop a .heic or .heif file. The local decoder loads only when first needed.
ImgIng downloads a HEIC decoder—not your photo. Decoding, resizing and output encoding happen on your device, with no account, queue or image upload.
These facts describe the current product, not unshipped roadmap work.
Reviewed by the DataDance product and engineering team · Published · Updated
Confirm important settings before export; the processing location is always disclosed.
Drop a .heic or .heif file. The local decoder loads only when first needed.
Use JPG for broad compatibility, or WebP / AVIF for modern web delivery.
Review dimensions, quality and the original/result split view before saving locally.
HEIC is efficient and common on iPhones, but many websites, office tools and older devices still expect JPG. A correct conversion decodes the pixels, respects orientation and colour, then encodes a real target file—it does not merely rename the extension.
The decoder is delivered by ImgIng, while your photo is never sent to ImgIng. HEIC decoding, resizing and JPG encoding run inside the browser. HEIC writing remains a clearly labelled server-side capability because of HEVC encoder size and patent constraints.
Updated 2026-08-20 · Live capability detection inside the tool is authoritative
These visible answers match the current product behaviour and structured data.
No. The full build uses libheif WASM to decode HEIC locally, so the source pixels stay on your device.
JPG is lossy. Use the quality control to balance size and detail. The UI value 100 maps to an actual encoder quality of 99 to avoid extreme size with negligible visual gain.
Yes. WebP is a strong compatibility/size balance for modern sites; AVIF can be smaller but takes longer to encode.
Each task page documents real settings, limits and format advice—not keyword-swapped duplicates.