Initializing, please wait a moment

HEIC vs JPG vs WebP - when to use each image format


Three image formats dominate everyday photography and web delivery: HEIC (default on iPhones since 2017), JPG (the universal fallback), and WebP (Google’s smaller-file replacement for JPG and PNG). Each encodes photos differently, and the right pick depends on where the file is going to be used. This guide walks through what each format actually does, the practical trade-offs, and the exact conversion steps for the four situations people hit most.


What each format is (and isn’t)

HEIC (High Efficiency Image Container) wraps photos encoded with the HEVC codec — the same codec used for H.265 video. Apple made it the iPhone default because the files are roughly half the size of JPG at the same visual quality, and HEIC can carry multiple images, depth maps, and live-photo metadata in a single wrapper. The catch: HEVC is patent-encumbered, so Windows, older Android, most browsers, and a lot of web services do not decode HEIC out of the box.

JPG (JPEG) has been the default web photo format since 1992. It uses DCT-based lossy compression, ships in every image library on every platform, and has zero compatibility surprises. Files are larger than HEIC or WebP at matched visual quality, but if something needs to open the image reliably — email, contracts, print, archival — JPG is the safest bet.

WebP is Google’s answer to “smaller than JPG, better quality than PNG”. It ships both lossy and lossless modes, supports transparency (unlike JPG), and is decoded natively in every current browser (Chrome, Firefox, Safari 14+, Edge). It remains less widely supported in email clients and some older desktop tools, so it’s not yet a universal replacement.


Side-by-side size and quality comparison

ScenarioHEICJPGWebP
iPhone 12MP photo at default quality~1.5–2.5 MB~3.5–5 MB~2–3 MB
UI screenshot (1080p)~150–250 KB~300–500 KB~80–180 KB (lossless)
Website hero imageN/A (browsers reject)~250–600 KB~120–350 KB
Transparency supported?YesNoYes
Email attachment friendly?No (sender must convert)Yes (universal)Partial (modern clients only)

When to pick each format

Pick JPG when: you’re emailing a photo, sending a document to a contract/legal system, printing, uploading to a service that rejects anything else (bank, government, insurance portals), or archiving a photo long-term where you can’t guarantee future decoder support for HEIC or WebP.

Pick WebP when: the image is going on your own website and you control the server. WebP cuts the page-weight budget significantly — important for Core Web Vitals and mobile-data users. Modern browsers all decode it; the server can still serve a JPG fallback via the <picture> element for the <1% of visitors on ancient clients.

Keep HEIC when: the photos stay in the Apple ecosystem (Photos app, iCloud, Messages between iPhones, AirDrop between Macs). The files are half the size, quality is pristine, and there’s no conversion step to introduce artifacts. The moment you need to send them outside Apple, convert to JPG or WebP first.


Fast conversion paths for the four common situations

iPhone photo → email or web upload. Use HEIC to JPG — drop the .heic file, download the .jpg, attach. You can also configure iPhone Settings → Camera → Formats → Most Compatible to save future photos as JPG by default.

iPhone batch → WebP for a website. Convert HEIC → JPG first, then JPG → WebP with Compress JPEG or a build-time pipeline. A two-step conversion is still far smaller than the original HEIC when delivered over HTTP.

PNG screenshot → WebP. Use SVG to PNG in reverse via ImageMagick or paste into ImageMagick Online with -define webp:lossless=true. Lossless WebP of UI screenshots typically cuts size by 25–45%.

HEIC with transparency layer → WebP or PNG. JPG will drop the alpha channel, so avoid it for any image with transparency. HEIC to JPG flattens the alpha to white; export to PNG instead if transparency matters, or to WebP (lossless) for the best quality/size balance.


Browser and device support at a glance

Chrome / Edge: WebP (since 2014), HEIC no. Firefox: WebP yes, HEIC no. Safari (macOS): WebP since 14, HEIC native. Safari (iOS): WebP since 14, HEIC native. Windows Explorer: HEIC requires the paid Microsoft HEVC Video Extension; WebP native since Windows 10. Android Photos: WebP native, HEIC native since Android 10. Email clients: JPG is the only format guaranteed to render in Gmail, Outlook, Apple Mail, ProtonMail, and enterprise webmail. Plan accordingly.


Summary decision tree

1. Is the file going outside your control (email, portal, legal system, print)? → JPG.
2. Is it going on a website you control with modern-browser traffic? → WebP (JPG fallback via <picture>).
3. Staying inside Apple (Photos, iCloud, iMessage)? → HEIC.
4. Transparency required? → WebP (lossless) or PNG; never JPG.


Related tools


← Back to Image Converter Tools

Why trust these tools

  • Ten-plus years of web tooling. The freetoolonline editorial team has shipped browser-based utilities since 2015. The goal has never changed: get you to a working output fast, without an install.
  • Truly in-browser — no upload. Every file-processing tool on this site runs in your browser through modern Web APIs (File, FileReader, Canvas, Web Audio, WebGL, Web Workers). Your photo, PDF, audio, or text never leaves your device.
  • No tracking during tool use. Analytics ends at the page view. The actual input you paste, drop, or capture is never sent to any server and never written to any log.
  • Open-source core components. The processing engines underneath (libheif, libde265, pdf-lib, terser, clean-css, ffmpeg.wasm, and others) are public and audit-able. We link to each one in its tool page's footer.
  • Free, with or without ads. All tools are fully functional without sign-up. The Disable Ads button in the header is always available if you need a distraction-free run.