Static versus animated WebP
A static WebP holds one frame, the same idea as a JPEG. An animated WebP stores a sequence of frames with timings, so a viewer plays them in a loop much like a GIF.
The difference shows up in the data. Animated files carry multiple images and frame metadata, and tools that only understand a single frame cannot process them correctly.
How to tell them apart
Most photo apps and browsers identify the file type from its header rather than the extension, and some players show an animation control for moving files.
A quick practical test is whether the image moves when opened. If it plays, it is animated, and any tool that promises still-image handling will need a frame exported first.
- Static: one frame, behaves like a JPEG or PNG
- Animated: many frames played in sequence
- Animated files are usually larger
- Export a single frame to treat one as static
Static WebP in Filekind
Filekind converts static WebP to JPEG and PNG, and converts JPEG and PNG to static WebP, entirely within the browser. Animated WebP files are rejected rather than flattened without warning.
Inputs follow the shared limits of 25 MB, 16,000 pixels per side, and 48 megapixels, and no file leaves the device during the conversion. Outputs open in any viewer that supports WebP stills, which covers current browsers, image editors, and most upload forms.