Initializing... drag & drop files here
Supports: HEIC
A HEIC file is a single still photograph — the format Apple devices have written by default since iOS 11 — and WebM is a video container. So this conversion does not "animate" anything: it wraps your photo in a real video file that holds that one frame on screen for a duration you choose. That is exactly what an HTML5 <video> background, a CMS that only accepts video uploads, or a video-editing timeline needs when all you have is a .heic. This page walks through the settings that actually change the result, then covers the errors people hit.
.webm. Files are uploaded over an encrypted connection, converted on our servers, and deleted automatically after a few hours — no sign-up, no watermark.Most of the Advanced Options inherit sensible defaults. Three of them genuinely change what you get:
Bitrate and target-file-size modes are deliberately hidden for image sources — for a static frame they have nothing meaningful to work against, so quality-based encoding is the only mode offered.
| Property | HEIC (input) | WebM (output) |
|---|---|---|
| Kind of file | Still image | Video container |
| Standard | HEIF, ISO/IEC 23008-12 (finalised March 2015) | WebM, maintained by the WebM Project |
| Payload | HEVC (H.265) intra-coded image | VP9 by default; VP8 and AV1 selectable |
| Audio | None | None — a photo carries no audio to encode |
| Frames | Exactly one | One frame repeated for the duration you set |
| Native browser rendering | Safari 17+ only, about 15% of browsers | About 96% — Chrome 25+, Firefox 28+, Edge 79+, Opera 16+, Safari 16+, iOS Safari 17.4+ |
| Typical source | iPhone/iPad camera roll | Web delivery, HTML5 video elements |
| Codec | When to choose it | Trade-off |
|---|---|---|
| VP9 (default) | Almost everyone. Every WebM-capable browser decodes it and encoding is quick. | Balanced; no reason to change unless you have a specific target |
| VP8 | Feeding an old player or an embedded device that predates VP9 | Larger files at the same visual quality |
| AV1 | Smallest possible file, or matching a pipeline that is already AV1 | Noticeably slower to encode; needs a newer decoder |
No. A HEIC holds one still frame, so the output is a static-image video — the same picture held on screen for the duration you set. There is no pan, zoom, or Ken Burns effect; that needs a video editor, not a format converter. What this tool gives you is a genuinely playable .webm where you previously had an image file that most software cannot open.
VP9 by default. The Video Codec control on this page offers exactly three choices — VP9, VP8, and AV1 — and VP9 is the right pick for nearly every use, because any browser that plays WebM at all can decode it. VP8 exists for very old players and produces bigger files; AV1 compresses harder but takes considerably longer to encode. There is no Theora option for a WebM target.
Because there is only one distinct frame to show. The encoder loops the still image for the requested duration at a 1 fps output rate with B-frames disabled, which keeps the file tiny and avoids the start-time offset that B-frames introduce on identical frames. We probed the output of a five-second conversion and counted exactly five encoded frames across a 5.000-second duration. Every player treats this as a normal video; if a downstream tool insists on 24 or 30 fps, re-encode it there or set a framerate in your editor.
The clip length equals the Image Duration you choose, and the dropdown tops out at 10 seconds per frame. To go longer, upload the same photo several times with "Merge images" selected — each copy contributes another segment, so three copies at 10 seconds gives 30 seconds.
Yes on current versions. Desktop Safari plays WebM from version 16, and Safari on iOS and iPadOS added it in 17.4. Combined with Chrome 25+, Firefox 28+, Edge 79+ and Opera 16+, that is roughly 96% of browsers by global usage. If your audience might be on older Apple hardware, convert HEIC to MP4 instead — H.264 in MP4 remains the most universally playable combination.
Not quite. Before encoding, every image is normalised to a clean PNG and clamped so that neither side exceeds 4096 pixels, because the frame-import stage is unreliable above that. A 48-megapixel capture is therefore scaled down to fit 4096 on its long edge before the video encode. That is still well above 4K, so for any playback use the difference is invisible — but if you need the original pixel count, keep it as an image and use HEIC to PNG.
Because a tall photo cannot fill a wide video frame, so the empty area is painted with the Background Color, which defaults to White. You have three fixes: change the Background Color (Black is the classic choice), pick a Fixed Resolution with the same shape as the photo — 1080 x 1920 for a vertical phone shot — or accept the bars as intentional framing.
Yes. Upload them all and leave Merge strategy on "Merge images". Each photo is encoded as its own segment at the Image Duration you set, and the segments are joined in upload order into a single WebM. Choose "Video per image" instead if you want one separate file per photo. Note that all photos share the same duration setting — there is no per-image timing control here.
Three real reasons come up repeatedly. HTML5 <video> backgrounds and many CMS upload fields accept video files only, and will reject a .heic outright. Video editors frequently refuse to import HEIC but accept WebM as a held shot on the timeline. And HEIC itself renders natively only in Safari 17 and later — about 15% of browsers — so a WebM is far more likely to display than the source file. If you only need a viewable picture, HEIC to JPG is the simpler answer.
It is uploaded over an encrypted connection, converted on our servers, and deleted automatically a few hours later. There is no sign-up, no watermark on the output, and nothing is shared or made public. The practical limit on a very large batch is upload size and time rather than anything on the conversion side.