Drop your HEIC or HEIF files in
Drag-and-drop one photo or a hundred. The file picker also accepts .heif β same format, different extension β and decodes them identically to .heic.
Loadingβ¦
Your iPhone shoots in HEIC, but the upload form, photo contest, or CMS you're dealing with only accepts .jpg. Convert HEIC to JPG right in your browser β quality you control, EXIF intact, nothing uploaded to a server.
HEIC to JPG is a specific trade: you accept a tiny, imperceptible loss in exchange for dramatically smaller files and compatibility with every tool on Earth.
A 4032Γ3024 iPhone photo lands at ~12 MB as lossless PNG and ~1.2 MB as JPG at quality 85. For email attachments, web-upload forms, and social uploads, smaller wins β JPG's lossy DCT compression was designed for exactly this.
Insurance portals, job application systems, school submission tools, WordPress media uploaders, print shops β many predate HEIC (released 2015, iOS default 2017). If a form silently rejects a photo, JPG is the near-universal fallback.
When you attach a HEIC photo to an email from iPhone, Apple's own Mail app silently converts it to JPG β because the recipient's system probably can't open HEIC. We do the same transcode, just in one place for a whole batch.
Mail yourself, export one-by-one, run a terminal command, upload elsewhere, or convert in-browser. Here's what each route actually costs.
| Method | Install Needed | Bulk Support | Speed | Privacy | Ease of Use | Best For |
|---|---|---|---|---|---|---|
Email to yourself (iOS auto-converts) | Built-in | Tiny batches only | Slow β network round-trip | Routes via Apple + mail server | Easy | One or two photos |
macOS Preview β Export As JPEG | Built-in (Mac only) | No β one file at a time | Slow in aggregate | Local | Moderate | Single photo on a Mac |
Terminal: sips -s format jpeg | Built-in (Mac only) | Yes | Very fast | Local | Developer-only | Scripting HEIC batches on a Mac |
Upload-based online converters | No | Sometimes β with daily caps | Depends on upload speed | Uploaded to a third-party server | Easy | Occasional one-off use |
This browser-based converterRecommended | No | Yes + ZIP, no daily cap | Runs on your CPU β scales with your machine | Files never leave your device | Drag, drop, download | Any modern browser, any OS, any photo count |
A note on quality: JPG uses the discrete cosine transform (DCT) with chroma subsampling, which discards information the human eye has a hard time resolving. Quality 90 ends up around 1/10 the bytes of lossless PNG at equivalent visual fidelity β which is exactly why anyone converts HEIC to JPG in the first place.
Three steps, no account, no desktop install. The conversion happens inside your browser using WebAssembly β nothing is uploaded.
Drag-and-drop one photo or a hundred. The file picker also accepts .heif β same format, different extension β and decodes them identically to .heic.
Quality 85β90 is the sweet spot for photographs: visually lossless to most eyes, roughly 40% the bytes of quality 100. Push to 95 for print. Drop to 75 for chat thumbnails. Below 60, blocking artifacts start showing up on smooth gradients.
One photo downloads as a single file. Batches bundle into a ZIP that preserves original filenames β IMG_1234.heic becomes IMG_1234.jpg.
Drag-and-drop one photo or a hundred. The file picker also accepts .heif β same format, different extension β and decodes them identically to .heic.
Quality 85β90 is the sweet spot for photographs: visually lossless to most eyes, roughly 40% the bytes of quality 100. Push to 95 for print. Drop to 75 for chat thumbnails. Below 60, blocking artifacts start showing up on smooth gradients.
One photo downloads as a single file. Batches bundle into a ZIP that preserves original filenames β IMG_1234.heic becomes IMG_1234.jpg.
Designed around real iPhone camera rolls, not toy demos. Drop 100 HEIC photos, step away for 20 seconds, download a single ZIP.
Conversion happens in your browser's own CPU and memory. 100 HEIC files take as long as your hardware takes β not 10 minutes of slow upload like a server-side converter.
Every JPG in the download preserves its source filename. Unzip the archive and the order matches exactly what you dropped in. No randomized hashes, no lost context.
Convert as many HEIC to JPG as you need, as often as you need. No free-tier limit, no "upgrade to convert more" modal, no hidden watermark baked into the output.
Yes β different extensions, same format. "JPEG" is the standards body (Joint Photographic Experts Group) and its specification (ISO/IEC 10918-1). ".jpg" and ".jpeg" are both valid file extensions pointing at the identical byte format; ".jpg" became common because older DOS and Windows filesystems limited extensions to three characters. This converter outputs ".jpg" by default β if a specific tool insists on ".jpeg", just rename the file.
A little β JPG is a lossy format by design, which is the whole point (much smaller files). But lossy does not mean visibly worse. At quality 85β90, a JPG is indistinguishable from the HEIC to almost any eye on almost any photograph. If you need pixel-exact preservation (screenshots, illustrations, anything with sharp text or hard edges), a HEIC to PNG conversion is the better fit β PNG is lossless.
Quality 90 β our default β is the right answer about 95% of the time: visually lossless for photographs, meaningfully smaller than quality 100. Push to 95 if the photo is going to print or professional retouch. Drop to 75 if it's a web thumbnail or chat attachment where every kilobyte counts. Below quality 60, JPG's blocking artifacts and color banding start showing up, particularly on skies and skin tones.
Because HEIC is already heavily compressed. Apple uses HEVC (H.265) inside the HEIC container, which is newer and more efficient than JPG's DCT. When you convert a strongly-compressed HEIC to JPG at high quality, you are re-encoding into a less efficient format β so the file can grow. It's still a reasonable trade: JPG is universally supported, HEIC often isn't. Drop the quality slider if file size matters more than the last 1% of fidelity.
If you toggle "Preserve EXIF metadata" in Advanced Settings, yes β date taken, GPS coordinates, camera make and model, shutter speed, ISO, and lens data all carry over into the output JPG. If you want to share a photo publicly but strip your home address, enable "Remove GPS location" as well β everything else stays, only the GPS block is wiped.
Only if you've set it to. Settings β Camera β Formats β Most Compatible switches new photos to JPG. But that toggle only applies to future shots β it does not touch anything already sitting in your Camera Roll. For existing HEIC files you need a converter (like this one); for new ones, flip the iPhone setting. Most people ultimately do both β convert the backlog, change the default going forward.
Both. HEIC and HEIF share the same container and the same HEVC encoding β HEIC is just Apple's brand name for HEIF images. This tool decodes ".heic" and ".heif" identically and produces the same JPG output in either case.
At quality 95 and above, yes β for photo prints up to poster size, a JPG at quality 95 is indistinguishable from the source. Professional printers often prefer TIFF or a lossless format for archival work, but for standard photo prints (4Γ6 through 16Γ20), Instagram portfolios, photo books, and most client deliverables, JPG at quality 90β95 is industry standard.
Yes. The conversion runs entirely inside your browser using JavaScript and WebAssembly. Nothing is uploaded to HeicToPng or any third party β you can disconnect WiFi after the page loads and keep converting offline. This is the whole reason this tool exists: uploading personal photos (with GPS, timestamps, and faces embedded) to a stranger's server is not a trade most people would make if the alternative is this simple.
Drop your iPhone photos in β JPGs come out in seconds.