Convert HEIC to WebP in your browser

The iPhone photo, in the format the web actually wants. Slightly smaller than the JPEG you would otherwise upload, and readable by every current browser, which HEIC is not.

HEIC

No HEIC selected

Drop a file to start

Drop HEIC files here

or browse your device. Everything is processed on this device

No HEIC to hand?

HEIC to WebP options

Quality 80%

Quality numbers are not comparable between codecs, so do not read 80 here as 80 on the JPG page. Your HEIC is lossy already, which is why this does not default lower.

Max width Original

Worth setting for the web. A modern iPhone photo is over 4000px wide and no page needs that; 1920 or 1280 is usually the real requirement.

Compress to a target size Off

We search for the highest quality that still fits under your figure, then tell you where we landed.

Speed Fast

Fast uses the browser encoder, which is the weak one for WebP. Smallest hands the pixels to libwebp and searches hardest, worth about 11% on the sample photograph; Balanced sits between them and on a photo often lands no better than Fast. For anything going on a site, use Smallest.

Metadata is always removed

The image is decoded to pixels and encoded again from those pixels alone, so EXIF and GPS, the XMP packet, embedded colour profiles, and any Content Credentials or AI-generation tags the file arrived with do not survive. There is no switch for this, because there is no way to keep them.

How to convert HEIC to WebP

01

Drop the HEIC files

Straight from an iPhone, AirDrop or the Files app. One photo or the whole shoot, and nothing is uploaded at any point.

02

Set a width and quality

Cap the width at what the page will actually display, then leave quality near 80. Drag the divider to check it against the original.

03

Save the WebP

A .webp ready to go straight into a site, a little smaller than the JPEG would have been, with the EXIF and GPS gone.

Why WebP rather than JPG, from a HEIC?

Because the destination is a web page. HEIC and WebP are both modern formats that beat JPEG on size at matching quality, but only one of them is read by browsers: Safari added HEIC support for its own platform and nothing else followed, whereas WebP has been supported by every current browser since 2020. So a photo destined for a site is a photo that has to leave HEIC, and JPEG is not the only place it can go.

Be careful with the size claim, because the usual one is misleading here. "WebP is 25 to 35% smaller than JPEG" is Google's figure and it is measured against baseline libjpeg, the encoder most software shipped in 2010. Measured against mozjpeg, which is what this site writes a JPEG with on its Smallest setting, the same photograph at quality 80 came out 528KB as WebP against 544KB as JPEG. That is about 3%, not a third. Against the browser's own JPEG encoder it is nearer 8%.

One thing to get right while you are here. The photo off the phone is over 4000 pixels wide, and no web page displays it at that size. The browser downloads every one of those pixels and then throws most of them away. Setting the width cap to what the layout actually uses will save you more bytes than any quality setting on this page, so do that first and treat the quality slider as a refinement.

HEIC to WebP FAQ

Why not just convert to JPG?

You can, and for emailing a photo or sending it to a print shop you should. WebP is the better answer when the destination is a web page: it is a little smaller at matching quality, it carries transparency if you ever need it, and it is what performance audits ask for. For anything that has to open in arbitrary desktop software, JPG remains the safer file.

Which browsers can read a WebP?

All the current ones. Chrome, Edge, Firefox, Safari and every mobile browser have supported it since 2020. The remaining gaps are in older desktop applications rather than browsers, which is why this is a page about publishing rather than about sharing.

Does the location data survive?

No, and that matters more here than usual. A HEIC off a phone carries GPS coordinates, the camera model and the timestamp. This page decodes the image to pixels and writes a new file from them, so none of it reaches the WebP. A photo published to a website should not be carrying the address it was taken at.

What quality should I use?

80 is the default and is right for most photographs. Below about 65 you will start to see it on skin tones and gradients. Note that quality numbers are not comparable between codecs: 80 here and 80 on the JPG page are different encoders making different trade-offs, so compare the files rather than the settings.

Will it be smaller than the HEIC?

Usually not, and that is not the comparison that matters. HEIC is an extremely efficient format and WebP is merely a very good one. The useful comparison is against the JPEG you would otherwise have published, which the WebP beats comfortably.

Can I convert a whole camera roll at once?

Yes. Drop the folder and every file queues with the same width and quality applied. Because nothing is uploaded, a few hundred photos is a question for your laptop rather than for anyone's server.

Are my HEIC files uploaded to convert them?

No. The HEIC is decoded and the WebP is written by your own browser, in this tab. There is no upload endpoint in the site for a file to go to, which you can check in your network tools: convert something and watch that no request carries it. Disconnect from the network after the page loads and it still works.

Does this remove EXIF, GPS and AI metadata?

Yes, every time, and there is no way to turn it off. The image is decoded to pixels and encoded again from those pixels alone, so EXIF and GPS, the XMP packet, embedded colour profiles, and any Content Credentials or AI-generation tags the file arrived with do not survive. There is no switch for this, because there is no way to keep them. What no compressor can remove is a watermark written into the pixels themselves, such as the invisible marks some image generators add: those survive re-encoding here and everywhere else.