HEIC to WebP Converter

Light, web-ready WebP images from your iPhone photos, sized and compressed in your browser for faster pages.

1 Add files → 2 Set options → 3 Download
Drop your HEIC photos here
or drag a whole folder. Conversion starts automatically.
Options
Resize
Free, no signup Nothing uploaded Batch and folders No watermark

WebP is made for photos on web pages

If your iPhone photos are headed for a blog post, a portfolio, a product page or a recipe site, WebP is usually the best output. Images tend to be the heaviest part of a page, and lossy WebP is typically 25 to 35 percent smaller than a JPG of similar visual quality. Lighter images load faster, especially on phones using mobile data, and page speed shapes both how readers experience your site and how search engines assess it.

Uploading the HEIC itself is not an option. Chrome, Edge and Firefox do not display HEIC images, and most content management systems will not accept them. Every current major browser displays WebP, and Safari has done so since version 14; caniuse.com tracks the details.

WordPress and other site builders

WordPress has accepted WebP in its media library since version 5.8, so converted files go straight into a post. Most current hosted site builders and shop platforms take WebP too, but older themes, plugins and some marketplace listing tools still expect JPG. Upload one test image before you convert a whole shoot.

Check one more thing first. Many platforms, image CDNs and optimization plugins already create WebP versions of whatever you upload. If yours does, give it a high-quality JPG from the HEIC to JPG converter and let it handle WebP itself. Feeding it a WebP you already compressed means the photo gets compressed twice.

WordPress also scales down very large uploads by default (anything over 2560 pixels on its longest side), so sending full-resolution iPhone photos mostly costs you upload time. And because converted files carry no EXIF data, publishing them does not expose the GPS coordinates your phone recorded. What iPhone photo metadata reveals explains why that matters.

Quality and size settings for web images

Screens are forgiving, so web images do not need the default quality of 90. A setting between 75 and 85 keeps photos clean while keeping files lean, and 80 is a good place to start. Move toward 85 for shots full of fine detail like fabric or leaves, and toward 75 for simple scenes and thumbnails.

Pixel dimensions matter even more than quality. A full-resolution iPhone photo has several times the pixels a page can show, and the browser downloads every one of them anyway. Match the resize preset to where the image will appear:

  • 1920 px for full-width hero images and banners.
  • 1280 px for images inside an article column. That is roughly double a typical column width, so photos stay crisp on high-density phone and laptop screens.
  • 800 px for thumbnails, gallery grids and sidebars.

Reach for 2048 only when photos open in a full-screen lightbox. Original is rarely the right call for a web page.

From camera roll to published post

  1. Drop your HEIC photos on the converter above. WebP is preselected on this page, and conversion starts immediately.
  2. Dial in quality and size. Set quality to around 80 and pick the 1920 or 1280 preset. The batch re-converts with the new settings.
  3. Give the files descriptive names. A filename template such as lemon-tart-{index} produces lemon-tart-1.webp, lemon-tart-2.webp and so on. Names that describe the picture keep your media library tidy and give search engines a small extra clue.
  4. Download the ZIP and upload the files to your CMS.
  5. Write alt text for each image as you place it. It helps readers who use screen readers and tells search engines what the photo shows.

The Safari caveat

Creating a WebP file relies on the image encoder built into your browser. Chrome, Edge and Firefox include one. Safari may not, and when it cannot produce WebP the converter shows an error that suggests JPG instead. Displaying WebP is a separate ability: Safari shows WebP images perfectly well, it just may not be able to make them.

On an iPhone or iPad, most browsers run on the same WebKit engine as Safari, so switching apps on the phone may not help. The dependable route is a computer running Chrome, Edge or Firefox: copy the HEIC files across and convert them there.

When JPG is still the safer bet

WebP is a web format first. Outside the browser, support is less certain.

  • Email newsletters. Some email clients, older desktop ones in particular, do not display WebP. Stick with JPG in campaigns.
  • Printing. Photo labs and print services expect JPG or TIFF.
  • Sending files to people. A relative's older photo app or a client's document workflow may refuse WebP.
  • Upload forms and marketplaces that list only JPG and PNG.

If you are choosing formats for a modern site, AVIF usually compresses further but is much slower to encode here; HEIC to AVIF lays out that trade. For a format-level comparison, see HEIC vs WebP.

Troubleshooting WebP on your site

The CMS rejects the .webp file

An outdated CMS version, theme or upload plugin is the usual cause. Update it if you can. If you cannot, or the platform simply does not take WebP, switch the format to JPG and convert again; nothing else about the workflow changes.

Photos look soft once published

Either the theme displays the image wider than its pixel width, or the platform recompressed your upload. Check the column or banner width your theme uses, then pick the next resize preset up. If the platform recompresses everything anyway, raise the quality toward 85 so its second pass has more to work with.

Pages are still slow

Smaller images help, but they are only part of page speed. Make sure your theme serves the resized file rather than a stored original, and that images further down the page load lazily instead of all at once.

WebP vs JPG vs HEIC on the web

WebPJPGHEIC
Displays in Chrome, Edge and FirefoxYesYesNo
Displays in SafariYes, since version 14YesDepends on version
Size compared with JPGTypically 25 to 35 percent smallerBaselineSmaller, but unusable on most sites
Accepted by CMS uploadsYes on current platformsEverywhereRarely
Transparency and animationBoth supportedNeitherPossible, unused by camera photos
Email clientsPatchyUniversalPoor
Can be created in Safari hereMay failYesNot an output
Best forPhotos on web pagesEmail, print and sharingStorage on Apple devices

Rate this tool

4.9/5·1257 ratings

Tap a star to add your rating.

Frequently asked questions

What quality should I use for WebP images on a blog?

Start at 80. Move toward 85 for detailed photos and toward 75 for thumbnails or simple scenes; much lower than that and artifacts start to show.

Why do I get an error converting HEIC to WebP on my iPhone?

Creating WebP depends on the browser's built-in encoder, and Safari and other WebKit-based browsers may not have one. Convert on a computer with Chrome, Edge or Firefox, or choose JPG.

Can I upload WebP images to WordPress?

Yes. WordPress has supported WebP in the media library since version 5.8. Some older themes and plugins handle it poorly, so test a single image first.

Should I convert to WebP if my site already optimizes images?

Probably not. If your platform or CDN creates WebP automatically, upload a high-quality JPG and let it do the work, so the photo is not compressed twice.

What pixel size should a WebP hero image be?

1920 px on the longest edge suits most full-width banners. Images inside an article column rarely need more than 1280 px.

Will publishing a converted WebP reveal where my photo was taken?

No. Converted files carry no EXIF data, so GPS coordinates, the date taken and camera details are not published with the image.

Should I use WebP or AVIF for website photos?

WebP is the safer default: it encodes quickly and displays in every current browser. AVIF usually makes smaller files but takes longer to create, so it suits sites chasing every last kilobyte.