{# Per-pair FAQ accordion — rendered from `pair_faqs`
(list of 12 dicts from webp.page_faqs.get_pair_faqs).
Replaces the old 5-card hardcoded block keyed on
`{tool}_faq_question_` which served identical Q/A
across every /-webp/ URL (SpamBrain shape). #}
How do I turn a WebM video into a WebP animation?
+
Upload the WebM file and our converter samples frames (default 15 fps for WebP = GIF, 24 fps for animated WebP / AVIF / APNG), encodes them into the animated WebP container, and applies palette quantization where the WebP format requires it.
How short / long should my WebM clip be for a good WebP?
+
Animated WebP is best for clips under 10 seconds. Longer than that and the file balloons for GIF (which is uncompressed per frame). For longer animations target animated WebP, AVIF, or APNG — all three compress similarly to a real video codec.
What is the file size of a 5-second WebP animation from a WebM clip?
+
GIF: 2-8 MB at 480p depending on motion complexity. Animated WebP: 200 KB to 1 MB at the same resolution. Animated AVIF: even smaller, often 100-500 KB. WebP / AVIF are 5-10x more efficient than GIF — use them whenever the platform you ship to supports them.
Will the WebP animation have the same frame rate as the WebM?
+
By default we downsample to 15 fps for GIF (the format works poorly above 25 fps) and 24 fps for WebP / AVIF / APNG (which handle higher rates fine). Override via the frame-rate option to keep the source rate if your target viewer supports it.
Will the WebP animation have audio?
+
No — animated WebP formats (GIF, WebP, AVIF, APNG) do not store an audio track. If you need sound, target a video format (MP4, WebM) instead of WebP.
Can I make the WebP animation loop forever?
+
Yes — the loop-count option controls whether WebP loops infinitely (default), plays N times, or plays once. Loop info is stored in the WebP container header and respected by all common viewers and browsers.
Why does my WebP look choppy compared to the WebM?
+
Two common causes: frame-rate downsampling (15 fps GIF vs 30 fps source — fix with the frame-rate option) and palette quantization on GIF (only 256 colors per frame — switch to animated WebP or AVIF for full 24-bit color and smooth gradients).
Can I crop or resize WebM before making the WebP?
+
Yes — the resize option scales the input down before frame extraction, which dramatically shrinks the final WebP. A 480p WebP from a 4K WebM is 16x smaller than a 4K WebP. Crop is handled separately via /video-cutter/.
Is my WebM private during WebP conversion?
+
Yes — same privacy model as every conversion. Source and output are isolated and deleted within minutes of completion.
How long does the WebM to WebP encode take?
+
Animated WebP encoding is CPU-bound and slower than typical video re-encode — expect about 1x source duration for animated WebP / AVIF, slightly faster for GIF. A 10-second clip finishes in around 10 seconds.
Does the WebP preserve transparency from the WebM?
+
Animated GIF supports single-color transparency only (binary mask). Animated WebP, AVIF, and APNG support full alpha channels. WebM sources without an alpha channel (most camera footage) produce fully-opaque WebP regardless of format.
Can I share the WebP on Discord / Slack / Twitter / iMessage?
+
Animated GIF plays everywhere. Animated WebP plays on Twitter, Discord, and every modern browser but not on iMessage or older Slack clients. AVIF support is growing but still patchy on chat apps. For maximum compatibility ship GIF; for size ship WebP.