search

Found

info Overview

Convert between GIF frame delay in milliseconds and FPS, then read total playback duration and loops per minute from your frame count.

📘 How to Use

  1. Choose a conversion direction (delay to FPS or FPS to delay)
  2. Enter the frame delay or FPS value
  3. Add a frame count to read the total duration

GIF Frame Delay Calculator

ms
frames
Frame delay
100
ms
FPS
10.00
fps
Total duration
3.00 s
Loops per minute
20.0
Delay FPS Feel

※ GIF stores each frame's on-screen time in centiseconds (1/100 s, 10 ms steps), so the delay is a multiple of 10 ms. fps = 1000 / delay(ms)

grid_view Related

Article

GIF Frame Delay Calculator | Convert Frame Delay and FPS

Convert a GIF's per-frame delay in milliseconds to its effective frame rate (FPS) and back. Add a frame count and the tool returns total playback duration plus loops per minute, so you can size up an animation before you export it.

💡 About this tool

GIFs store the display time of each frame as a "delay" value, but most editors let you think in either milliseconds or FPS, which forces a bit of mental math whenever you switch tools. This calculator lines up the delay-to-FPS mapping and then turns your frame count into a real duration, so you stop doing that math by hand.

  • Two-way conversion: Flip between "what FPS is 100 ms" and "what delay is 12 FPS" with a single toggle.
  • Total duration at a glance: Enter a frame count and the tool multiplies delay by frames to show the full length in seconds or minutes.
  • Reference table: Scan delays from 20 ms to 1000 ms with their matching FPS and a smoothness label.

🧐 Frequently Asked Questions

Q. Can a GIF really use millisecond-precise delays?

A. The GIF spec stores delay in hundredths of a second (10 ms steps), so a value like 33 ms is usually rounded by the encoder to 30 ms (3 centiseconds) or 40 ms. This tool derives FPS from the exact number you type, so the theoretical figure can differ from what the encoded file actually plays.

Q. Why do so many GIFs land around 10 FPS?

A. Very short delays such as 10 ms (a theoretical 100 FPS) get clamped to a browser minimum, so they never play as fast as the number suggests. A delay of 50 ms (roughly 20 FPS) has long been treated as a safe floor, and balancing motion against file size pushed 100 ms (10 FPS) into the default zone.

Q. Why enter a frame count?

A. The same 10 FPS lasts 3 seconds at 30 frames but 12 seconds at 120 frames. When you need to fit a sticker or a social clip under a length cap, you can juggle frame count and delay and read the resulting duration each time.

📚 Fun Facts

When GIF arrived in 1987 it had no animation at all; multi-frame looping was only standardized in the 1989 GIF89a revision. The per-frame delay that lives in each frame's Graphic Control Extension block, measured in hundredths of a second, is a direct leftover from that era.

Strictly speaking a GIF has no "FPS" field — the frame rate we casually quote is just a value back-calculated from the delay. A 40 ms delay maps to 25 FPS on paper, but the real cadence shifts with the encoder and the viewer. Animators on r/gifs and indie sticker shops often find that adding frames buys smoother motion more reliably than shaving the delay, because the duration, file size, and smoothness all pull against each other.