
A Cloudinary video delivered with a WebP extension is not automatically the animated WebP you intended. The documented video-to-animated-WebP route uses both fl_awebp and fl_animated. Decide whether the destination needs one poster frame or a moving image, then verify the actual output and its loop behavior.
Key Takeaways
- A still poster and a video-derived animation are different deliverables.
- Animated WebP uses the documented animation flags as well as the format.
- Video-resource animations run once by default; looping is another choice.
Identify the output role before changing extensions
Keep the source film and write the intended behavior. A gallery card may need a stable poster, while an email or product illustration may need a short moving excerpt. A frozen frame can be correct for the first role and wrong for the second.
The Cloudinary animated-image guide documents the WebP flags and the different GIF route. Its GIF conversion normally produces animation from a video when the extension is changed to GIF. Do not use a GIF extension as a guessed way to request one static poster.
For a still, use the separately documented video-thumbnail workflow, which describes image output and frame selection. The website poster guide explains where that still belongs in a gallery.
Request motion through the supported route
For animated WebP from an uploaded video, keep the documented fl_awebp and fl_animated requirements with the chosen extension. Do not infer that an image named after the original video still contains its timeline.
For automatic animated-image format selection, the official guide describes either fl_animated with f_auto or f_auto:animated. That requests a browser-suitable animated image; it should not be confused with a video format negotiation request.
Do not apply ImageKit's still-thumbnail syntax to this Cloudinary conversion. The providers' parameter contracts are different even when the visible symptom is one frame.
Check motion and repetition separately
Play the downloaded result in a viewer that supports the requested animation format. Observe whether frames change, whether the intended beginning and ending survive and whether another cycle begins.
Cloudinary documents a single run by default for these animations with the video resource type. The loop effect changes repetition; lack of an automatic second run is therefore not by itself proof that only one frame was delivered.
For a hypothetical five-second product turn, check the whole rotation before deciding whether its last frame makes the asset appear frozen. A deliberate still selection serves another purpose and should have its own filename.
Accept the actual destination behavior
Test the intended browser, email client or placement rather than relying only on an asset-library thumbnail. The email animation guide helps choose motion versus a linked film for that channel.
Accept when the output's format, frame behavior and repetition match the stated role. No conversion, browser-support survey, size saving or playback result is claimed here.
Related tasks
- Why Does a Video Card Show a Black Image Before Playback?
- Why Does My Animated GIF or WebP Upload as Just One Photo?
- Should My Email Announcement Use an Animated GIF or a Link to an MP4?
Sources and scope
- Cloudinary: Converting videos to animated images: Video-to-GIF delivery uses the GIF extension; animated WebP requires fl_awebp and fl_animated. Automatic animated output uses fl_animated with f_auto or f_auto:animated. Video-resource animations run once by default and e_loop changes looping.
- Cloudinary: Video previews and posters: e_preview analyzes the whole video; eager or explicit generation and notification are recommended for production, while direct experimentation can initially return 423. Requested duration affects selected content. It is not supported as an incoming transformation.
Documentation-based guidance from the cited official pages captured on October 25, 2026. Scenarios and acceptance procedures are proposed, not executed tests. No account operation, measured demand, AI-citation frequency, processing benchmark or search-indexing outcome is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.