HEIC vs WebP
How the two formats differ, why only one belongs on a website, and how to turn iPhone photos into fast-loading WebP images.
Capture format versus delivery format
HEIC and WebP both promise smaller files than JPG, so they get compared a lot. In practice they sit at opposite ends of a photo's life. HEIC is a capture and storage format: your iPhone writes it, your photo library keeps it. WebP is a delivery format: it was created by Google in 2010 specifically to make images on web pages load faster, and nearly every browser now displays it.
That framing answers the most common question straight away. If you are putting iPhone photos on a website, a blog, an online store or a WordPress site, you want WebP (or JPG), not HEIC. Most browsers cannot display HEIC at all. The rest of this guide explains the technical differences and walks through preparing photos for the web.
Side-by-side comparison
| Feature | HEIC | WebP |
|---|---|---|
| Created by | MPEG (HEIF standard), adopted by Apple in 2017 | Google, 2010 |
| Compression basis | HEVC (H.265) | VP8 for lossy; a separate lossless mode |
| Size versus JPG | Often around half | Often 25 to 35 percent smaller |
| Bit depth | 8 or 10 bits, higher possible | 8 bits only |
| HDR | Yes | No |
| Transparency | Possible | Yes, in both lossy and lossless modes |
| Animation | Image sequences | Yes, widely supported |
| Maximum size | Very large, through tiling | 16383 by 16383 pixels |
| Chrome, Edge, Firefox | Not displayed | Displayed |
| Safari | Recent versions only | Displayed on current versions |
| Best use | Storing photos on your devices | Photos and graphics on web pages |
Browser support is the deciding factor
A format can be brilliant at compression and still useless on the web if visitors cannot see it. WebP crossed that line years ago: Chrome, Edge, Firefox, Opera and Safari all display it, and Safari's support arrived in 2020 with Safari 14. You can check the current details on caniuse.com.
HEIC never made the jump. Chrome, Edge and Firefox do not decode it in web pages, a gap widely attributed to the patent licensing that surrounds HEVC. Recent Safari releases on Apple devices can show HEIC, but a site that relied on that would show broken images to the majority of visitors.
The practical upshot is simple. HEIC is something you convert from, never something you publish.
File size and image quality
On compression alone, HEIC usually comes out ahead. Its HEVC engine is newer and more sophisticated than the VP8 technology behind lossy WebP, so at the same visual quality a HEIC is often smaller than a WebP of the same photo. WebP, in turn, is commonly 25 to 35 percent smaller than a JPG at similar quality, which is what makes it worthwhile for web pages.
WebP also has a few limits worth knowing:
- 8 bits per channel. Smooth gradients such as dusk skies can show faint banding at lower quality settings.
- Reduced color resolution. Lossy WebP always stores color at a lower resolution than brightness. Fine for photos, but saturated red text or thin colored lines can look slightly soft.
- A size ceiling. WebP images cannot exceed 16383 pixels on either side. Regular iPhone photos are well within that, but very wide panoramas can exceed it; pick a resize preset for those.
None of these matter much for typical website photos, especially once they are resized to sensible display dimensions.
What WebP leaves behind
Converting from HEIC to WebP is a one-way trip for some of the extras an iPhone stores. WebP has no place for HDR brightness information, depth maps or multiple independent images, and HEIC to PIC produces 8-bit output in any case.
Metadata is the other change. Converted files from HEIC to PIC carry no EXIF data, so the capture date, camera details and GPS coordinates do not end up on your website. That is a quiet benefit for anyone publishing photos taken at home. The guide to what iPhone photo metadata reveals explains why that matters.
Preparing iPhone photos for a website
Here is a workflow that produces fast-loading, good-looking images without any image editing software:
- Pick the right photos first. Crop and straighten on the iPhone if needed, since that is quicker than doing it later.
- Open the HEIC to WebP converter and add the HEIC files, or drag in a whole folder.
- Choose a resize preset by where the image will appear. 1920 pixels on the longest edge suits full-width banners, 1280 is plenty for images inside an article or product description, and 800 works for thumbnails and cards.
- Lower the quality slider a little. The default of 90 is generous; somewhere between 75 and 85 is common for web photos and noticeably reduces file size.
- Set a filename template. Descriptive names help both you and search engines. A template like
oak-dining-table-{index}producesoak-dining-table-1.webp,oak-dining-table-2.webpand so on. - Download all as a ZIP, unzip, and upload to your site.
Resizing does more for page speed than any format choice. A 1280 pixel WebP is a small fraction of the size of a full-resolution one, and on a phone screen nobody can tell the difference.
Why image weight matters for your site
On most pages, images are the heaviest thing a visitor downloads. A full-resolution iPhone photo dropped straight onto a page can easily outweigh all of the page's text, styles and scripts combined. On a phone with a weak connection, that is the difference between a page that appears instantly and one that visitors abandon.
Search engines pay attention too. Google's Core Web Vitals include Largest Contentful Paint, which measures how long the biggest visible element takes to appear, and on many pages that element is a photo. Smaller, correctly sized images help that number directly. Converting from HEIC is the moment to fix this, because you are creating a new file anyway: choosing WebP, a sensible resize preset and a slightly lower quality setting all happen in the same step.
Making several sizes for responsive images
If you build pages by hand or with a static site generator, you can serve different image widths to different screens with the srcset attribute, so phones download a small file and large monitors get a sharper one. You need a few versions of each photo for that, and the converter can produce them quickly:
- Add your HEIC files and choose WebP.
- Set the resize preset to 800 and the filename template to
{name}-800, then download the ZIP. - Change the preset to 1280 and the template to
{name}-1280. Everything re-converts automatically; download again. - Repeat for 1920 if you have full-width layouts.
You end up with neatly named sets, such as IMG_4821-800.webp and IMG_4821-1280.webp, ready to list in your markup. Content management systems like WordPress generate these sizes for you, so this step is only needed when nothing else does.
WordPress and other site builders
WordPress has accepted WebP uploads since version 5.8. When you upload an image, WordPress creates several resized copies for different layouts, and to do that with WebP it needs the server's image library to support the format. Most current hosts do. If yours does not, the upload may fail with a message that the server cannot process the image, and a JPG upload is the easy workaround.
WordPress also scales down very large uploads by default, which is another reason to resize before uploading: you control the result instead of the server. Uploading at 1920 or 2048 pixels is a good middle ground for most themes.
Hosted website builders and online store platforms generally accept WebP now, but some re-encode every upload into their own formats and sizes anyway. If your platform does that, uploading a high-quality JPG can give its pipeline better material to work from than an already compressed WebP. When in doubt, test one image both ways and compare.
If you manage a large catalog, convert in batches rather than all at once; the guide to batch converting HEIC covers how to keep big jobs running smoothly, and the same approach applies to WebP.
Where WebP can still trip you up
WebP is safe inside web pages, but a few places around a website are less predictable:
- Link preview images. The image a site supplies for previews when a page is shared in chat apps or social feeds is fetched by many different services, and support for WebP there has historically been uneven. A JPG is the cautious choice for that one image.
- Downloads for customers. If visitors save images to use elsewhere, such as press kits or printable files, older desktop software may not open WebP. Offer JPG for anything meant to be downloaded.
- Email newsletters. Email apps vary widely in what they display. JPG remains the dependable format for images inside emails.
- Soft-looking product photos. If fine detail matters, such as jewelry or fabric texture, raise quality toward 85 or 90 rather than relying on the lowest setting that looks fine at a glance.
A note on Safari
The WebP conversion in HEIC to PIC uses your browser's built-in image encoder. Chrome, Edge and Firefox can all write WebP. Safari may not, and if it cannot, the converter shows an error and suggests JPG instead. If you are on a Mac or iPhone and want WebP output, open the converter in Chrome, Edge or Firefox, or use JPG, which every site accepts.
When to choose something other than WebP
WebP is the right default for most website photos, but not every time:
- AVIF usually compresses photos even further than WebP and is supported by all current major browsers. Encoding is slower, so it suits a few key images better than a huge batch. The HEIC to AVIF converter handles it.
- JPG is still the choice for email, upload forms and anything outside a web page, where WebP support is less certain. Use the HEIC to JPG converter for those.
- PNG is better for screenshots, diagrams and images with text, where WebP's lossy mode can soften edges.
For a fuller picture of how WebP stacks up against AVIF and JPEG XL as well as HEIC, read the four-way format comparison.
Frequently asked questions
Can I use HEIC images directly on my website?
Not reliably. Chrome, Edge and Firefox do not display HEIC in web pages, so most visitors would see broken images. Convert to WebP or JPG before uploading.
Does WordPress accept WebP uploads?
Yes, WordPress has supported WebP uploads since version 5.8, as long as the server's image library can process WebP. If an upload fails, use JPG instead or ask your host about WebP support.
Should I resize iPhone photos before putting them on my site as WebP?
Yes. Full-resolution iPhone photos are far larger than any screen needs, so choose a resize preset by placement: about 1920 pixels for full-width banners, 1280 for images in articles and 800 for thumbnails.
Why does WebP conversion fail in Safari?
The converter relies on the browser's own WebP encoder, and Safari may not provide one. Use Chrome, Edge or Firefox for WebP output, or choose JPG in Safari.
Is WebP smaller than HEIC?
Usually not. HEIC's HEVC compression is typically more efficient than lossy WebP, but HEIC cannot be displayed by most browsers, so WebP is the practical choice for the web.