HEIF is the container HEIC lives in, read here and not written. WebP is lossy or lossless depending on the encoder, with alpha and animation. ImageMagick sits between the two, and this page says exactly what happens to a HEIF file on the way to becoming a WEBP one.
What runs when a HEIF file becomes WEBP
ImageMagick 6.9.12, on a machine we rent and watch. Your HEIF file is uploaded once, ImageMagick runs once, the WEBP comes back, and neither file is kept. HEIF to WEBP is one of the 3649 pairs that engine was probed on with a real file, which is why it has a page here and why the pairs the probe could not prove do not.
What survives from the HEIF into the WEBP
The pixel dimensions of your HEIF file. The WEBP comes out the size the HEIF went in, because nothing on this path resizes anything.
Transparency. HEIF and WEBP both carry a real alpha channel, so a cut-out sent as HEIF is still a cut-out as WEBP.
What HEIF to WEBP costs you
Nothing measurable, which is rare enough to say plainly. HEIF and WEBP carry the same kind of content with the same fidelity, so this pair changes the container and not the picture. What does change is the size, and often by a lot.
Where HEIF and WEBP files come from
HEIF. The container standard; HEIC is the name it goes by when the picture inside is HEVC. Read here and not written, because the write alias is not wired on the engine and pretending otherwise would hand you a file under the wrong name.
If a model is going to read the WEBP
A WEBP file is pixels, and pixels are expensive for a model to read. Handed this WEBP, an assistant spends its budget looking at the picture rather than reading it, and it will paraphrase what it thinks it saw. If your HEIF is mostly words, the useful move is to pull the text out of it, not to change which picture format holds it.
HEIF to WEBP, measured rather than promised
Running HEIF to WEBP against the real engine with a real file, ImageMagick wrote 416 bytes of WEBP in under a tenth of a second, machine otherwise idle. That is one HEIF file on one day and not an average, which is why the number is given together with the file that produced it.
The HEIF to WEBP verdict was reached by a format signature, meaning at least four bytes unique to the format were found at the right offset. Which check was used matters, because they do not all prove the same thing, and a status code of 200 proves nothing whatsoever about whether the WEBP file has anything inside it.
The same HEIF file, sent somewhere else
Other outputs the probe measured out of a HEIF file, so the cost of choosing WEBP can be read against something. Sizes do not compare across engines, because each family was probed with its own HEIF witness file.
HEIF to PDF: 94,782 bytes in under a tenth of a second, verified by a format signature.
HEIF to JPG: 1,666 bytes in under a tenth of a second, verified by a format signature.
HEIF to PNG: 1,403 bytes in under a tenth of a second, verified by a format signature.
HEIF to GIF: 2,918 bytes in 0.1 seconds, verified by a format signature.
HEIF to TIFF: 90,264 bytes in under a tenth of a second, verified by a format signature.
Other ways into WEBP, and what they measured
Among the published routes into WEBP, HEIF is the fourth largest output of the 8 measured. The witness files differ, so this ranks the probe run and not your document.
ICO to WEBP: 370 bytes in under a tenth of a second.
SVG to WEBP: 608 bytes in under a tenth of a second.
TIFF to WEBP: 370 bytes in under a tenth of a second.
PNG to WEBP: 370 bytes in under a tenth of a second.
JPG to WEBP: 350 bytes in under a tenth of a second.
What we will not pretend about HEIF to WEBP
A HEIF file over 25 MB is refused before the upload finishes rather than after it, so you do not wait for a rejection.
A HEIF to WEBP run that passes 30 seconds is killed, and the ImageMagick process is killed with it. A run left behind would sit on one of the machine's two cores until somebody noticed.
No text is read out of the HEIF anywhere on this path. Converting a picture to WEBP never turns it into words, whatever the picture happens to contain.
ImageMagick was not saturated at sixteen simultaneous conversions: it held 47.5 a second while latency moved from 0.22 s to 0.34 s, and the service memory did not move off 51 MB. That is the measured headroom behind HEIF to WEBP, not a marketing number.
One HEIF file at a time, chosen in the browser. There is nothing else to set up and nothing else on offer.
HEIF to WEBP: what people ask
What actually converts my HEIF file to WEBP?
ImageMagick does it, 6.9.12, on a machine we rent and watch. Not a browser trick and not somebody else service: the HEIF file is uploaded once, ImageMagick runs once, the WEBP comes back, and neither file is kept afterwards.
How long does HEIF to WEBP take?
On the file the probe used, ImageMagick took under a tenth of a second and wrote 416 bytes of WEBP. That is one real measurement on one real HEIF file, not an average and not a promise about yours: a larger HEIF takes longer, and past 30 seconds the run is stopped.
What do I lose going from HEIF to WEBP?
The one to know about first: Nothing measurable, which is rare enough to say plainly. HEIF and WEBP carry the same kind of content with the same fidelity, so this pair changes the container and not the picture. What does change is the size, and often by a lot.
Does the WEBP come out the same size as the HEIF?
The same pixel size, yes: nothing on this path resizes anything, so the WEBP is as wide and as tall as the HEIF was. The number of bytes is a different question and usually moves a long way, which is normally the reason for doing this at all.
Is HEIF to WEBP free?
There is a free allowance every month, and one HEIF to WEBP conversion costs half a credit against it. When the allowance runs out the tool says so and stops, rather than quietly handing you a worse WEBP.