Change the ANIM loop count without decoding frames or recompressing the animated WebP payload. Only the little-endian two-byte loop field in the existing ANIM chunk is patched, so frame payloads, durations, metadata, and RIFF order remain byte-identical. The workflow identifies actual animation structure rather than trusting a filename, runs locally, and returns a clearly named derivative or report while leaving the selected source unchanged.
How to use Loop Editor
- Choose a genuine animated WebP and review the available loop count editing controls.
- Run the browser-only operation and inspect the reported frame count, duration, dimensions, and loop details.
- Download the result, preview it in the intended destination, and retain the original until the edited animation is approved.
What this tool is good at
When to use Loop Editor
Prepare a controlled animation loop for publication
Set finite repetition for instructional motion or infinite repetition for a deliberately ambient asset without recompressing frames. Work from the actual animated container and keep the original as the authoritative master until the derivative has been previewed in its destination.
Investigate motion locally
The before-and-after loop value comes from the actual ANIM field rather than filename or player state. This supports evidence-based timing and geometry decisions for client, product, research, or internal assets without transferring image bytes to a conversion endpoint.
Create a repeatable handoff
Save the named output and its reported frames, dimensions, duration, and loop facts beside the publishing task. Zero means infinite repetition, while destination applications and reduced-motion policies can still prevent or alter autoplay.
How to choose the right settings
Preview the complete sequence
Set finite repetition for instructional motion or infinite repetition for a deliberately ambient asset without recompressing frames. Check the first-to-last transition as well as individual frames because a technically valid output can still contain a visible jump or distracting loop.
Budget decoded memory
Compressed size does not predict working memory. The browser may hold complete RGBA canvases for every frame, so the workflow enforces frame-count and pixel-frame limits before creating large derivatives.
Test the real destination
Zero means infinite repetition, while destination applications and reduced-motion policies can still prevent or alter autoplay. Autoplay policy, reduced-motion preferences, rendering load, and viewer-specific delay clamping can affect presentation after download.
Practical workflow and output details
A bounds-aware RIFF parser locates ANIM and patches only its two-byte little-endian loop field. Static application code and the local WebAssembly codec may be loaded, but the selected image itself remains in the current browser tab.
The before-and-after loop value comes from the actual ANIM field rather than filename or player state. Zero means infinite repetition, while destination applications and reduced-motion policies can still prevent or alter autoplay. The tool limits its claims to the named operation and never treats successful container creation as proof of visual quality, accessibility, or universal playback behavior.
Format behavior and limitations
Only the little-endian two-byte loop field in the existing ANIM chunk is patched, so frame payloads, durations, metadata, and RIFF order remain byte-identical. A zero loop value means infinite repetition; applications can still impose their own autoplay, reduced-motion, or playback policies.
Complete displayed frames are decoded to canvas and remuxed as full-canvas keyframes. This preserves visible motion but does not copy EXIF, XMP, or ICC chunks and can change compression size.
Government and research sources
These references support the format facts, metadata terminology, and privacy context explained on this page. They do not endorse PicConverters.
Container-level context for the RIFF chunk structure used by WebP.
Graduate research context for the VP8-derived compression technology used in lossy WebP frame payloads.
Frequently asked questions
Does the Loop Editor upload my animation?
No. The file is inspected and processed in the current browser tab; PicConverters does not receive its image bytes.
Will the result remain animated?
Yes. The operation requires at least two frames and writes or preserves a genuine animated WebP container.
What should I verify before publishing?
Preview motion, frame timing, dimensions, transparency, and loop behavior in the destination browser. A zero loop value means infinite repetition; applications can still impose their own autoplay, reduced-motion, or playback policies.
Related WebP tools
Duration Calculator
Calculate frame delays, one-play duration, loop behavior, and finite total playback time from WebP container bytes.
WebP Animation Checker
Check whether WebP files are animated and report frame count, loop count, total duration, frame rectangles, delays, blending, and disposal.
Animation Player
Play an unchanged animated WebP and export a contact-sheet overview of its decoded frames.