GIF does not store one global frame-rate value in the same way as a typical video. Each frame can have its own delay, usually represented in hundredths of a second. “FPS” is therefore a convenient approximation, not always a complete description of GIF timing.
Convert delay to approximate FPS
A 10-centisecond delay is 0.10 seconds per frame, or roughly 10 FPS. A 5-centisecond delay is roughly 20 FPS. The formula is FPS ≈ 100 ÷ delay in centiseconds. If delays vary between frames, the animation has no single exact FPS.
Why very short delays behave differently
Browsers and image viewers may clamp extremely short frame delays to avoid excessive CPU use. As a result, a GIF requesting an unusually high frame rate may play differently across apps. For predictable sharing, moderate timing is usually safer than trying to reproduce 30 or 60 FPS video.
Frame rate versus file size
More frames usually mean more data, but the relationship is not perfectly linear because GIF can store differences between frames. Dropping redundant frames and increasing their delays can reduce size while preserving the same overall duration. Use the GIF Speed Changer for timing and the compressor for file-size optimization.
Choose timing for the content
- Slides and instructions: use longer pauses so text can be read.
- Reaction GIFs: moderate timing usually communicates the action clearly.
- Screen demonstrations: preserve pauses around clicks or state changes.
- Loading animation: prioritize a consistent rhythm over many frames.
Diagnose uneven playback
Extract frames with Split GIF Frames to inspect the sequence, then check whether one frame has a much longer delay. If the source came from video, reconvert a shorter clip with a sensible FPS using Video to GIF.