HEIC to WebP Converter
WebP keeps the quality and drops the weight — ideal for websites and stores.
Drop your HEIC or HEIF files here
or choose files — up to 100 at once, 100 MB each
No upload. Files are processed in your browser.
Files never leave your device · EXIF and GPS removed
Works on Chrome, Safari, Firefox and Edge · No installation
HEIC to WebP gives you a web-ready image that is usually 25–35% smaller than JPG at the same visual quality. It is the better format for websites and stores, but not for forms or desktop apps that still expect JPG.
WebP is supported by every modern browser and typically produces files 25–35% smaller than JPG at matched quality. If you are publishing product photos, blog images or a portfolio, it is the better default than JPG.
Note that WebP is a web format. Some desktop apps, older design tools and a few upload forms still expect JPG or PNG, so keep a JPG copy if the file is going anywhere beyond a browser.
Last reviewed November 2026
Why WebP instead of JPG?
Smaller at the same quality
Better compression means faster pages and lower bandwidth bills.
Wide support
Chrome, Safari, Firefox and Edge all render WebP natively.
Good for shops
Shopify, WordPress and most CMSs accept WebP uploads directly.
How to convert HEIC → WebP
- Add your HEIC files. Up to 100 per batch, processed locally.
- Set quality. 85 is a strong default for WebP; 75–80 for thumbnails.
- Download. Single files or a ZIP archive.
What settings actually change
| Quality | Typical size vs JPG | What it looks like | Use it for |
|---|---|---|---|
| 90 | 25–30% smaller | Indistinguishable side by side | Hero images, product shots |
| 85 (default) | 30–40% smaller | Indistinguishable at 100% | Everything on a website |
| 75 | 45–55% smaller | Slight softening in fine detail | Thumbnails, blog images |
| 60 | Around 60% smaller | Visible on gradients and skies | Placeholders, previews |
| 100 | Often larger than the JPG | No loss — WebP switches to lossless | Almost nothing; see below |
Why WebP is smaller, and where that stops being true
WebP is two codecs behind one file extension. Lossy WebP is a single VP8 keyframe; lossless WebP is VP8L, a completely different compressor. Moving the quality slider decides how much VP8 may discard — but at 100 the browser switches to the lossless path, which is why file size jumps instead of creeping upward. If a WebP comes out larger than the JPG you started from, this is almost always why.
The 25–35% advantage over JPEG comes from better entropy coding and from storing the alpha channel separately rather than pre-multiplying it into the colour data. It is a real advantage on photographs, and it holds across browsers: Chrome, Safari 14+, Firefox and Edge all decode WebP natively.
The output is still 8-bit sRGB, and still a single frame. An iPhone photo in 10-bit HDR is flattened, and a Live Photo or animated source keeps only its first frame — the same limitation as the JPG path, for the same reason: the canvas has no concept of either.
Where the advantage disappears: very small images, where the container header dominates, and very noisy images, where both codecs more or less give up. A 50 × 50 pixel avatar will not get smaller. A photo of dense foliage at ISO 3200 will not get much smaller either.
If the WebP is not behaving
Most WebP complaints are one of three things: the lossless switch, a desktop app, or the platform re-encoding the file anyway.
| Symptom | What causes it | What to do |
|---|---|---|
| The .webp is bigger than the JPG it came from | Quality was left at 100, which selects lossless VP8L | Drop to 85 — that is where the size advantage lives |
| Word, Pages or Preview will not open the file | WebP is a delivery format; office suites generally do not decode it | Keep a JPG copy for documents and use WebP only on the web |
| Photoshop says it cannot open the file | WebP support arrived in Photoshop 23.2 in 2022; older versions have no decoder | Edit as PNG, export WebP at the end of the pipeline |
| The image is blank in an old iPhone browser | iOS before 14 has no WebP decoder | Rare now. If it matters, serve JPG to that traffic |
| The Live Photo lost its motion | Only the still frame can be encoded into WebP | Export the motion as a video from Photos first |
| Uploaded to a shop and the image looks worse than the file | The platform re-compressed it on ingest | Nothing to fix here — quality 85 is already more than it keeps |
Where a .webp upload will be accepted
Browser support for WebP is universal; upload-form support is not. Check this list before you convert a whole folder.
| Destination | Accepts WebP? | Note |
|---|---|---|
| WordPress 5.8+ and most CMSs | Yes | Modern WordPress also generates WebP variants itself |
| Shopify, Squarespace, Wix | Yes | Served as-is to browsers |
| Instagram, Facebook, X | Yes, then re-encoded | The platform recompresses anyway, so quality 85 is plenty |
| Gmail, Outlook | Attached, not previewed | The file arrives; the preview pane shows a broken tile |
| Word, PowerPoint, Pages | No | Use JPG or PNG inside documents |
| Print shops | Rarely | Ask for JPG or TIFF |
Rule of thumb: WebP for anything a browser will render, JPG for anything a human will open in an application.
Questions
Is WebP smaller than JPG?
Usually yes — typically 25–35% smaller at the same visual quality.
Can every device open WebP?
All current browsers can. Some older desktop apps and a few upload forms still cannot, so use JPG when compatibility matters more than size.
Does WebP support transparency?
Yes, but HEIC photos rarely contain alpha, so this mostly matters for graphics.
Is WebP better than JPG?
For delivery over the web, usually yes — 25–35% smaller at matched quality, with transparency support. For anything that has to open in a desktop app or pass an upload filter, JPG is still the safer choice.
Why did my WebP file get bigger at quality 100?
At 100 the browser switches from lossy VP8 to lossless VP8L. Lossless WebP of a photograph is typically larger than a high-quality JPG, because it cannot discard anything.
Does converting HEIC to WebP lose the HDR data?
Yes. Canvas output is 8-bit sRGB, so 10-bit sources and HDR gain maps are flattened. The image looks correct on an SDR screen and flatter on an HDR one.
Related converters
Same engine, different formats — all processed locally.