NoCloud Media

Image tool

HEIC to JPG Converter

Drop one or more HEIC files. They convert to JPG locally, in your browser. Photos never reach our servers — they don't need to leave the tab to convert.

JPEG quality

How it works

  1. 1

    Drop your HEIC files

    Drag one or more HEIC/HEIF photos onto the converter, or click to pick them. Holding Shift selects a range; Ctrl/Cmd-click adds individual files.

  2. 2

    Pick a quality preset

    Small file (50%), Balanced (75%, the recommended default), High (90%), or Maximum (100%). The Balanced preset typically halves file size with no visible loss for screen viewing.

  3. 3

    Convert in your browser

    Each file decodes via libheif (the open-source library Apple's own Preview app uses) and re-encodes as JPEG using your browser's native encoder. Files are processed one at a time so phone memory stays under control.

  4. 4

    Download as JPG

    Each converted photo gets a download button. Or hit “Download all” when the queue finishes.

Why use HEIC to JPG?

Your photos never leave the browser tab. Most other HEIC-to-JPG converters upload your image to a server, run the conversion there, and serve it back — your photo lives on a stranger's disk for days. This tool runs the whole conversion locally; the file never goes anywhere.

Bulk drop. Pick a vacation gallery's worth of HEIC files at once and let them convert sequentially. The converter remembers each one's state — converted, queued, failed — so you can keep using your phone while the rest finish.

Works on every platform. iPhone, Android, Windows laptop, Linux, Chromebook — anywhere that runs a modern browser. No app install, no signup, no ad-watching gate.

No watermarks, no ads on the output, no quality cap until you pay. The Maximum quality preset really does mean maximum.

Common use cases

  • Convert iPhone-shot vacation photos to JPG for sharing on Windows or Android
  • Batch-convert a whole folder of HEIC images for upload to Reddit, LinkedIn, or Etsy
  • Send photos to a relative whose email or phone doesn't open HEIC files
  • Attach an iPhone photo to a Google Docs report that won't accept HEIC
  • Convert screenshots from your iPhone to JPG before posting on a forum
  • Migrate years of Photos.app exports off your Mac to JPG for long-term archival
  • Get HEIC photos into an older photo-editing app that doesn't recognise the format
  • Prepare iPhone product photos for an e-commerce store that requires JPG

About HEIC and JPG

HEIC (High Efficiency Image Container) is the format iPhones since iOS 11 shoot in by default. It's based on HEIF (High Efficiency Image Format) and uses the HEVC codec inside — a format Apple, Microsoft, and Samsung adopted for its ~50% smaller files vs JPEG at the same visual quality. The drawback: many older apps, websites, and platforms still expect JPG. JPEG (Joint Photographic Experts Group, 1992) is the universal compromise — slightly larger files, but every device on Earth opens it. This tool decodes HEIC via libheif (the same library Apple's Preview, GIMP, and the macOS Quick Look use) and re-encodes as JPEG using your browser's built-in encoder. The decode-then-encode roundtrip is lossy — JPEG has no lossless mode — but the Balanced preset (75% quality) typically produces a JPG that's visually identical to the original HEIC for normal viewing, at roughly half the file size of the original HEIC's compressed form.

Frequently asked questions

Are my photos uploaded anywhere when I convert them?
No. The HEIC decode runs in your browser using libheif compiled to WebAssembly. The JPEG encode runs through your browser's own native encoder. Neither step touches a server — your photo stays in this tab from the moment you drop it until you download the JPG. We don't have analytics on file contents or filenames.
Why do most other online HEIC-to-JPG converters require an upload?
Until recently, browsers didn't have a way to decode HEIC locally — the format requires the HEVC codec, which is patent-encumbered and not built into Chrome or Firefox. The workaround was to upload the file to a server that has libheif installed. WebAssembly changed that: libheif now compiles to a WASM bundle that runs anywhere, so the conversion can happen entirely in your browser. This tool uses that approach.
Why does the Balanced preset produce a smaller file than the original HEIC?
It often does, despite HEIC's reputation for compression. Two reasons: (1) iPhones encode HEIC at very high quality (close to lossless), so the source file is bigger than it strictly needs to be. (2) Browser JPEG encoders at 75% quality are well-tuned for photographic content and produce an output that's visually equivalent to the source for screen viewing. If you need to preserve every pixel detail (printing, archival, further editing), pick High or Maximum.
What happens with Live Photos or burst-mode HEIC files?
iPhone Live Photos and burst sequences are stored as multi-image HEIC containers. This converter takes the primary still frame — the one that shows up as the main image when you view the photo. The motion data and other frames are dropped, since JPG doesn't have a multi-image format. If you specifically need the secondary frames, an iPhone-side export tool can pull each one out as a separate file before you bring them here.
How big a HEIC can I convert?
The converter caps individual files at 100 MB to keep memory predictable on phones — a 50 MP iPhone HEIC decodes to ~150 MB of pixel data in RAM during conversion. You can drop dozens of normal-sized iPhone photos (3-5 MB each) at once without issue; they convert sequentially. If a single file exceeds 100 MB you'll get a clear rejection notice.
Does this work on iPhone Safari? Doesn't iOS support HEIC natively?
Yes, it works on iPhone Safari. iOS does support HEIC natively for viewing, but Safari doesn't expose a native HEIC-to-JPG export from a web page — the browser-level Save Image as JPG option you'd find in Photos.app isn't available to JavaScript. This tool runs the same libheif decode path on iPhone as elsewhere, so iPhone users converting their own photos for upload to a non-HEIC service get the same in-browser pipeline.
Will the converted JPG keep the photo's date taken / GPS / EXIF metadata?
Most metadata is dropped during the HEIC → RGBA pixels → JPEG re-encode roundtrip. The browser's native JPEG encoder doesn't preserve EXIF tags from the source. If you need to keep date taken, GPS coordinates, or camera info on every photo, consider a desktop tool like macOS Photos.app's export or Windows Photos. We'll add an EXIF-preservation option here if there's enough demand — it requires re-injecting metadata after the encode.
Which browsers handle HEIC conversion?
Any modern browser with WebAssembly support: Chrome, Edge, Firefox, Safari 15+, and the major mobile browsers (Chrome Android, Safari iOS, Samsung Internet). The libheif WASM bundle is around 2 MB and downloads on first conversion (cached after). No SharedArrayBuffer requirement, unlike our video tools — HEIC conversion is single-threaded and works on any HTTPS site without cross-origin isolation.

Related tools