Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Converting HEIC to WebP takes iPhone photographs into a format the whole web reads, at roughly a third less weight than the equivalent JPG. Drop the files above — a hundred at once is fine — and they convert inside your own browser, so a camera roll is never uploaded anywhere.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
HEIC to WebP
Most people escaping HEIC go to JPG, and for a photograph headed into an email or a document that is the right answer — it opens on absolutely everything, including software that has not been updated this decade.
For anything going on the web it is leaving a third of the file size on the table. WebP reaches the same visible quality in roughly 25 to 35 per cent fewer bytes, which is the kind of margin that shows up in a page speed score and on a mobile connection. It also keeps transparency and handles flat colour without the smearing JPG produces around hard edges, so one format covers photographs and graphics alike.
HEIC and WebP are closer relatives than either is to JPG. Both came out of video compression research, both use techniques JPEG predates by twenty years, and both are lossy in similar ways. That matters in practice: WebP is not struggling against artefacts the source introduced, the way JPG sometimes does when re-compressing something already compressed.
The result is that the default quality setting is genuinely sufficient here. What is worth raising it for is a photograph that will be cropped hard or printed, where you are effectively enlarging part of the image and any softness enlarges with it.
Nobody has one HEIC. They have four hundred, because the phone has been producing them since iOS 11 and the format only becomes a problem when the photographs need to go somewhere else.
Drop up to a hundred at a time; each converts independently with its own progress, and once several have finished a single button offers them all as a ZIP. Nothing queues behind anyone else because there is no shared server — the work happens on your own machine. Through a site that uploads, the same job is a hundred uploads, a wait, and usually a daily cap designed to sell you a subscription.
An iPhone photograph is not only an image. It usually holds the exact coordinates where it was taken, the date and time, the device model, and often the camera settings. That travels with the HEIC file wherever it goes.
The WebP produced here does not include any of it. For photographs destined for a website, a forum or a marketplace listing, that is almost certainly what you want — published images have leaked home addresses more than once. If you specifically need the metadata preserved, this conversion is the wrong tool, and you should know that before rather than after.
WebP has a lossless mode, and for a photograph out of a phone it is the wrong choice: it faithfully preserves an image that was already compressed, at several times the size.
It earns its place for screenshots and graphics, which a phone can also produce as HEIC. If the source is a picture of a screen rather than a picture of the world, lossless is worth trying.
A Live Photo is a still with a short video attached. What converts is the still, because the WebP produced here holds one frame — the video stays behind in the original file.
A burst behaves as what it is, a set of separate stills, so dropping the whole set converts each one. Nothing is quietly discarded except the motion, and only where there was motion to discard.
In browsers, effectively everywhere, and for years. Outside them it is uneven: some older image viewers, a few editors, certain systems that process attachments, and upload forms that judge by extension alone.
Which is why the division is worth stating plainly. WebP for your own pages; JPG for anything going to a person whose software you do not know.
A HEIC is already efficient, so the WebP will not be dramatically smaller and may even be slightly larger. The comparison that matters is against JPG, not against the HEIC you started with.
Against a JPG at the same visible quality, expect 25 to 35 per cent fewer bytes. That is the margin this conversion exists for, and it is why the destination — a web page — decides whether the exercise makes sense at all.
This reads HEIC and HEIF and writes WebP, JPG, PNG and the rest. The reverse does not exist on this site, and that is a licence question rather than a missing feature: the encoder required comes on terms that do not fit the ones this site holds its dependencies to.
In practice it should not matter. HEIC earns its place when an Apple device is saving storage, and that is settled in the camera settings rather than by converting files afterwards.
| HEIC | WebP | |
|---|---|---|
| Full name | High Efficiency Image Container | WebP Image |
| File extension | .heic | .webp |
| Media type | image/heic | image/webp |
| Compression | Lossy — file size is bought with quality | Either, depending on the setting |
| First published | 2015 | 2010 |
| Published by | MPEG | |
| Specification | ISO/IEC 23008-12 | RFC 9649 |
| Licensing | Published, not standardised | Open standard |
| Standing today | Current | Current |
| Bit depth | 10 | 8 |
| Colour it can describe | YCbCr, wide gamut | RGB, YCbCr |
| Largest image | — | 16,383 px per side |
| Opens in a browser | Some browsers | Every browser |
| Considered instead | JPG, AVIF | AVIF, JPG, PNG |
WebP holds one page. A multi-page HEIC converts a page at a time rather than in one file.
WebP has nowhere to put the GPS coordinates, so that goes no further than the HEIC. Worth checking before the original is deleted, and worth knowing if the point was to strip it.
HEIC carries up to 10 bits per channel and WebP stores 8. The extra precision is what survives heavy correction without banding, so the conversion is best made after the editing rather than before it.
Transparency survives. Both HEIC and WebP store an alpha channel, so a cut-out stays cut out and nothing is filled in behind it.
Animation survives. HEIC and WebP both hold multiple frames, so the result moves rather than freezing on the first one.
WebP opens in every current browser. HEIC has narrower browser support than that. If the file is going onto a web page or into a form, that is usually the whole reason for the conversion.
The usual programs do not overlap: HEIC opens in Apple Photos and Adobe Lightroom, WebP in Adobe Photoshop, GIMP and Squoosh — so whoever receives the result needs something from the second list.
The result is larger than the original and no better. HEIC has already discarded detail, and WebP stores what is left without discarding more — it prevents further loss rather than undoing the first one.
The two are aimed at different work: HEIC at phones and photography, WebP at the web and handing a finished file over. That is worth weighing before converting, because the reason one exists is usually the reason the other is awkward.
HEIC is MPEG's format, published in 2015. It records 10 bits per channel.
WebP comes from Google and dates from 2010, specified as RFC 9649. Adobe Photoshop, GIMP and Squoosh all read it.
Size, mostly. WebP is typically 25 to 35 per cent smaller than JPG at the same visible quality, which is the difference between a page that feels quick and one that does not. It also keeps transparency, which JPG cannot, and handles flat colour and photographs equally well. Every browser in use has read it for years.
Some, and less than you would fear. Both are modern lossy formats built on similar ideas, so WebP is not fighting the source the way JPG sometimes does. At the default setting the difference is not visible at normal sizes. Raise it if the photograph is going to be printed or cropped heavily.
Yes. Drop up to a hundred files and each converts on its own, then take the results as a single ZIP. This is the case where converting in the browser stops being a privacy point and becomes a practical one: a hundred photographs through a site that uploads them is a hundred uploads and a daily limit.
It is not carried over. iPhone photographs usually contain the coordinates where they were taken, the time, and the device — and the WebP produced here does not include any of it. For photographs going onto a public website that is almost always what you want, and it is worth knowing rather than discovering.
No. HEIC is decoded and WebP encoded inside your browser. Nothing is sent, which is the point when the files are a camera roll: personal photographs are the single worst category of file to hand to an unknown website in bulk.
The claims this page makes about HEIC and WebP are checkable, and these are the documents that settle them.