How to Convert HEIC to WebP (3 Free Methods)

Apple devices shoot in HEIC — great compression, rich color, but browsers outside Safari refuse to display it. Converting HEIC to WebP gives you the best of both worlds: modern compression efficiency paired with the format every browser actually supports. Here are three free ways to do it.

Why Convert HEIC to WebP?

HEIC and WebP are both next-generation image formats built on video codecs. HEIC uses HEVC (H.265) while WebP uses VP8/VP9. Both deliver significantly smaller files than JPG at equivalent visual quality.

The problem is support. HEIC works natively on Apple devices and Safari — and almost nowhere else. Chrome, Firefox, Edge, WordPress, Shopify, Squarespace, Slack, Discord, and most design tools reject HEIC uploads. You end up converting anyway.

WebP solves this. It matches HEIC's compression advantage over JPG (roughly 25-35% smaller at the same quality), adds transparency and animation support, and runs in every modern browser. If you're moving photos from your iPhone to the web, HEIC to WebP is the conversion that loses the least.

For a deeper look at each format individually, see What Is HEIC? and What Is WebP?.

Method 1 — Pixotter (Browser, No Upload, Instant)

Pixotter's HEIC to WebP converter processes everything client-side using WebAssembly. Your photos never leave your device — there is no upload, no server queue, and no file size cap.

1. Open Pixotter's Convert tool and select WebP as the output format.
2. Drop your HEIC files onto the page (batch supported — drop as many as you need).
3. Adjust the quality slider if desired. The default (80%) strikes a strong balance between file size and visual fidelity.
4. Click Convert and download your WebP files.

The conversion happens in milliseconds per image, powered by libvips compiled to WebAssembly. Metadata (EXIF, XMP) is preserved by default.

Why this beats online converters: Most browser-based tools upload your files to a remote server, process them, and send them back. That introduces privacy exposure, file size limits, and network latency. Pixotter's client-side approach eliminates all three. Your photos stay on your machine.

Method 2 — ImageMagick Pipeline

ImageMagick (Apache 2.0 license) is the standard command-line image processor. Version 7.1.x supports HEIC decoding through a libheif delegate.

Single file:

magick input.heic -quality 80 output.webp

Batch conversion (all HEIC files in a directory):

for f in *.heic; do
    magick "$f" -quality 80 "${f%.heic}.webp"
done

Setup note: ImageMagick 7.1.x must be compiled with libheif support for HEIC decoding. Verify with:

magick identify -list format | grep HEIC

If HEIC does not appear in the output, install the libheif delegate. On Ubuntu/Debian:

sudo apt install libheif-dev

On macOS with Homebrew:

brew install libheif

Then rebuild or reinstall ImageMagick so it picks up the delegate.

Quality tuning: WebP quality 75-85 is the sweet spot for photographs. Below 70, you start seeing compression artifacts around fine edges. Above 90, file sizes approach the original HEIC with diminishing visual returns.

Method 3 — Sharp for Node.js

Sharp (Apache 2.0 license, version 0.33.x) is the fastest Node.js image processing library, built on libvips — the same engine Pixotter uses client-side.

Single file:

const sharp = require('sharp');
await sharp('input.heic').webp({ quality: 80 }).toFile('output.webp');

Batch conversion:

const sharp = require('sharp');
const fs = require('fs');
const path = require('path');

const dir = './photos';
const files = fs.readdirSync(dir).filter(f => f.endsWith('.heic'));

for (const file of files) {
    const input = path.join(dir, file);
    const output = path.join(dir, file.replace(/\.heic$/i, '.webp'));
    await sharp(input).webp({ quality: 80 }).toFile(output);
    console.log(`Converted: ${file}`);
}

Install:

npm install [email protected]

Sharp 0.33.x bundles prebuilt binaries for macOS, Linux, and Windows — including libheif for HEIC input. No system dependencies to install.

This is the best option if you already have a Node.js build pipeline or want to integrate HEIC-to-WebP conversion into an automated workflow (CI/CD, CMS processing, asset pipeline).

HEIC vs WebP — Comparison Table

The takeaway: HEIC has a slight compression edge and supports deeper color, but WebP wins decisively on compatibility. For anything published to the web, WebP is the right output format. You keep most of HEIC's size advantage while gaining universal browser support.

For related format comparisons, see HEIC vs JPEG and PNG vs WebP.

Frequently Asked Questions

Does converting HEIC to WebP lose quality?

Both HEIC and WebP are lossy formats (though each supports lossless modes). Converting between them introduces one generation of re-encoding loss. At quality 80, the difference is imperceptible for photographs. For pixel-perfect preservation, use lossless WebP — but expect larger files (roughly on par with PNG).

Can I convert HEIC to WebP on iPhone?

Not natively — iOS has no built-in WebP export. Open Pixotter's converter in Safari on your iPhone, drop your photos, and download WebP files directly. No app install needed.

Is WebP smaller than HEIC?

Usually no. HEIC typically produces files 10-20% smaller than WebP at equivalent visual quality, thanks to the more advanced HEVC codec. But WebP is smaller than JPG by 25-35%, and it runs everywhere — which is why converting HEIC to WebP instead of JPG is the better choice for web publishing.

Do WebP files preserve EXIF metadata from HEIC?

Yes, when using tools that support metadata transfer. Pixotter, ImageMagick 7.1.x, and Sharp 0.33.x all preserve EXIF data (camera model, date, GPS, exposure) during the conversion. If metadata privacy matters, strip it with the -strip flag in ImageMagick or withMetadata(false) in Sharp.

Which quality setting should I use?

For photographs: 75-85 is optimal. Quality 80 gives a strong balance between file size and visual fidelity. Going above 90 inflates the file size with minimal visible improvement. Going below 70 introduces noticeable artifacts around edges and gradients. For screenshots and graphics with sharp text, use lossless WebP instead.

Should I convert HEIC to WebP or to JPG?

Convert to WebP if the images are going on a website, a web app, or anywhere displayed in a browser. WebP delivers 25-35% smaller files than JPG with equivalent quality, and browser support is universal. Convert to JPG if you need compatibility with older software, email clients that don't render WebP, or print workflows. See How to Convert HEIC to JPG if JPG is the better fit for your use case.

Can I batch convert hundreds of HEIC files to WebP?

Yes, all three methods support batch processing. Pixotter handles batch natively — drop all your files at once. ImageMagick and Sharp both support batch conversion through shell loops or script iteration (examples above). For large photo libraries (1,000+ files), the command-line methods give you more control over output directories and naming conventions.

Why not just convert HEIC to PNG?

PNG files are lossless but large — a typical iPhone photo saved as PNG weighs 8-15 MB compared to 300-500 KB as WebP. Unless you need lossless quality for editing or archival, WebP is the better web format. See How to Convert HEIC to PNG if lossless output is your goal.