HEVC to WebP Converter

HEVC to WebP Converter

HEVC (H.265) is a video codec and WebP is a still-image format, so this conversion decodes your video and writes one frame out as a WebP picture. It exists because a .hevc file has no thumbnail to copy: there is no embedded poster image, no cover art, nothing an image viewer can read directly. A decoder has to render an actual frame first, and this page lets you choose which one.

A .hevc file is a raw H.265 elementary bitstream — picture-only, with no audio track and no container holding timing or camera metadata. That is exactly what frame extraction needs: the decoder reads the H.265 parameter sets (VPS/SPS/PPS) straight from the stream and renders the picture at the timestamp you ask for. If your footage is an iPhone .mov instead (HEVC wrapped in a QuickTime container), use MOV to WebP — this page takes the raw .hevc stream specifically.

HEVC Format at a Glance

WebP Format at a Glance

How to Convert HEVC to WebP

1. Upload Your HEVC File: Drag and drop your .hevc file onto the page or click "+ Add Files" to browse. You can queue several clips and convert them with the same settings.
2. Set the Frame Selection: Choose "Specific Frame" and type a timestamp into "Time (seconds)" — 2.100 means 2 seconds and 100 milliseconds in. Choose "Multiple Screenshots" instead to export a series of stills, with "Capture Rate" controlling the interval from one frame every 0.1 seconds up to one every 10 seconds.
3. Pick Quality Preset and Lossless (Optional): Leave "Quality Preset" on "Very High (Recommended)" for a photographic frame, or set "Lossless?" to "Yes" when the shot is a screen recording, chart, or anything with sharp text. "Specific file size" and "Preset Resolutions" are there when you need a hard size or pixel target.
4. Convert and Download: Click "Convert" to get your WebP. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark.

Frequently Asked Questions

Does this produce a still WebP or an animated WebP?

Still images only. The WebP container does define animation chunks (ANIM and ANMF), but this converter treats WebP as a single-picture target: "Specific Frame" writes one still at the timestamp you enter, and "Multiple Screenshots" writes a series of separate .webp files at the interval you set — not one looping file. If you want an actual animation out of the clip, use HEVC to GIF, which exposes the frame rate and resolution controls an animation actually needs.

I have a .heic photo from my iPhone, not a .hevc video — am I on the right page?

Probably not, and the names are genuinely confusing because HEIC images are HEVC-encoded pictures wrapped in a HEIF container. If your file is a photo ending in .heic, go to HEIC to WebP instead. If it is an iPhone video ending in .mov, use MOV to WebP. This page accepts the bare .hevc elementary stream — the kind you get from an encoder, a capture card, or an ffmpeg raw-bitstream dump.

Will the WebP keep the 10-bit HDR color from my Main 10 HEVC clip?

No — WebP is an 8-bit format in both of its modes, so a 10-bit source is reduced to 8 bits per channel on the way out. Lossy WebP uses VP8, which per RFC 6386 "works exclusively with an 8-bit YUV 4:2:0 image format," so it also halves chroma resolution in both directions. Lossless WebP uses VP8L, which stores 8-bit ARGB pixels exactly with no chroma subsampling — still 8-bit, but no color-detail loss on top of it. For a still that has to carry HDR or wide-gamut data, extract to a format built for it rather than WebP.

When should I switch "Lossless?" to Yes?

When the frame is synthetic rather than photographic: a screen recording, a game HUD, a spreadsheet, a chart, a slide, or anything with hard edges and flat color blocks. Lossy WebP's 4:2:0 subsampling is what smears colored text and thin lines, and lossless VP8L skips that step entirely while still landing about 26% smaller than the same picture saved as PNG. For camera footage, leave it on "No (Recommended)" — lossy at a high quality preset is dramatically smaller and visually very close.

Why is my captured frame black when I leave the time at 0?

HEVC encodes long groups of pictures: one IDR keyframe followed by many P- and B-frames that reference it. Ask for the picture at exactly 0 seconds and some raw streams have not yet presented a complete keyframe, so the grab comes back black or blocky. Nudge "Time (seconds)" forward by 0.1 to 0.5 — landing on or just after the first keyframe returns a clean still. The same trick fixes a frame that lands mid fade-in.

Should I extract to WebP or JPG?

WebP if the frame is headed for a web page: it is roughly 25-34% smaller than a JPEG of equivalent quality by Google's own SSIM measurements, and it decodes natively in about 96% of tracked browsers (Chrome 32+, Firefox 65+, Edge 18+, Safari 16+ on desktop, Safari 14+ on iOS). JPG if the frame is going somewhere older or less predictable — an email client, a legacy CMS upload field, a print workflow, or an embedded device. HEVC to JPG is the safer pick there, and it is one of the few image formats that essentially nothing refuses.

Does the WebP keep any EXIF, GPS, or camera metadata?

There is none to keep. A raw .hevc bitstream carries video coding parameters, not camera metadata — no EXIF block, no GPS coordinates, no capture timestamp, because those live in the container (MP4, MOV) that a .hevc file does not have. The WebP container itself supports optional EXIF, XMP , and ICCP chunks, so the output can hold metadata in principle; it just has nothing to inherit from this particular source. Frames pulled from a .mov or .mp4 are the same story once the frame leaves the container.

How large is a typical extracted WebP frame?

In our testing, a 1080p frame pulled from a phone-shot HEVC clip at the "Very High (Recommended)" preset landed around 120-180 KB — comfortably under the 180-260 KB the same frame took as a visually matched JPEG, which tracks with Google's 25-34% figure. Flipping "Lossless?" to Yes on that same photographic frame pushes it past 1 MB, which is why lossless is worth reserving for graphics and screen captures. Sharpness is bounded by the source: HEVC is itself lossy, so a motion-blurred frame stays blurry no matter which still format you write it to.