Video Frames Calculator
Convert frames, FPS, and duration for AI video
This video frames calculator converts between frame count, frame rate, and clip duration for AI video and animation workflows. Enter any two values and the third computes instantly, using the (frames - 1) / fps convention that Wan, AnimateDiff, ComfyUI video nodes, and Stable Video Diffusion all follow.
Open video models think in frames, not seconds. Wan 2.x generates 81 frames at 16 fps, AnimateDiff works in 16-frame contexts, and ComfyUI batch counts are raw frame numbers. Filmmakers think in seconds and timeline frame rates. This calculator translates between the two, and the interpolation panel below shows what RIFE or FILM does to your frame count and fps on the way to a 24 fps timeline.
Everything runs in your browser. Nothing you enter is sent to any server.
Your conversion
5 seconds
Frames: 81
Frame rate: 16 fps
Duration: 5 s
Naive frames / fps would give 5.063 s. The playable length spans frames - 1 intervals, which is why generated clips run one frame interval shorter than the simple division suggests.
Frame interpolation
RIFE, FILM, and similar interpolators multiply your frame rate without changing duration: each frame interval gains new in-between frames.
Output fps: 32
Output frames: 161
Duration: 5 s (unchanged)
duration = (frames - 1) / fps | out_fps = fps x factor | out_frames = (frames - 1) x factor + 1
Target: 24 fps timeline
From 16 fps the exact interpolation factor is 1.5x, giving 121 frames at 24 fps with the same 5 s duration. Integer-only interpolators get there with 3x to 48 fps, then a 2:1 frame drop or an NLE conform down to 24.
Retiming the original frames at 24 fps instead shortens the clip to 3.333 s, a 33.3 percent duration loss. That shift is why AI clips dropped straight onto a 24 fps timeline feel sped up.
Frame count reference table
Frame counts for common clip lengths, using frames = duration x fps + 1.
| Clip length | 8 fps | 12 fps | 16 fps | 24 fps | 25 fps | 30 fps | 60 fps |
|---|---|---|---|---|---|---|---|
| 2 s | 17 | 25 | 33 | 49 | 51 | 61 | 121 |
| 4 s | 33 | 49 | 65 | 97 | 101 | 121 | 241 |
| 5 s | 41 | 61 | 81 | 121 | 126 | 151 | 301 |
| 8 s | 65 | 97 | 129 | 193 | 201 | 241 | 481 |
| 10 s | 81 | 121 | 161 | 241 | 251 | 301 | 601 |
How it works
Pick which value to solve for, enter the other two, and the calculator applies duration = (frames - 1) / fps. The minus one matters: a clip's playable length is the time between its first and last frame timestamps, so N frames span N - 1 intervals. That is why Wan ships 81 frames for a 5 second clip at 16 fps, and why AnimateDiff renders come out slightly shorter than frame count divided by fps. The interpolation panel applies out_fps = fps x factor and out_frames = (frames - 1) x factor + 1, the arithmetic RIFE and FILM nodes use in ComfyUI.
How many frames is 5 seconds of video?
It depends entirely on frame rate. Five seconds is 81 frames at 16 fps, 121 frames at 24 fps, and 151 frames at 30 fps, each counted with the plus-one endpoint frame. A frames to seconds calculator only gives useful answers once you know which fps your model generates at: Wan defaults to 16 fps, AnimateDiff workflows commonly run 8 to 16 fps, and Stable Video Diffusion ships short bursts at 6 to 14 fps depending on settings.
The fps to frame count relationship also runs the budget math for AI video. ComfyUI video length is set in frames, and every extra frame costs VRAM and generation time, so knowing that a 5 second clip at 16 fps needs 81 frames (the classic 81 frames at 16 fps duration question) tells you exactly what to type into the length field and what it will cost before you queue the job.
Getting AI output onto an editorial timeline is the other half. Editors cut at 24, 25, or 30 fps, and a 16 fps generation dropped onto a 24 fps timeline either plays a third short or judders through frame blending. Frame interpolation is the cheap fix: a 1.5x pass takes 16 fps to exactly 24, and a 3x pass to 48 fps gives you clean 24 fps after a 2:1 drop plus a 2x slow motion option for free.
Who this is for
- AI filmmakers: convert a shot list measured in seconds into the frame counts Wan, AnimateDiff, or ComfyUI actually ask for, before spending GPU time.
- Editors: figure out the interpolation factor that lands generated footage on a 24 or 30 fps timeline without stutter or unwanted retiming.
- Animators: plan animation on 8 or 12 fps (shooting on twos) and know the exact frame budget for each clip length.
Video Frames Calculator: the complete guide
It solves any one of frame count, fps, or duration from the other two using the (frames - 1) / fps convention, and models frame interpolation so you know the output fps and frame count before running RIFE or FILM.
For this workflow, the central problem is clear: open video models measure clips in frames while filmmakers plan in seconds, and the (frames - 1) / fps convention makes naive conversions come out wrong. Left unresolved, this creates downstream friction and slower decisions. The practical target is exact frame counts, frame rates, and durations that match what the model generates and what the timeline expects.
Limitation to keep in mind: It cannot know model-specific frame count constraints (like Wan's 4n+1 steps) beyond documenting them, and it does not predict encoder behavior after export; verify final timing in your NLE.
Advanced workflow: Advanced teams standardize one generation fps per project, log frame counts per shot in the shot list, and batch all interpolation at a single factor so every clip conforms to the timeline identically.
Step-by-Step Workflow
- Pick the value to solve for, then enter the two you know: model output is usually frames plus fps, a storyboard is usually seconds.
- Use the fps chips to match your model's native rate (16 for Wan, 8 to 16 for AnimateDiff) instead of guessing.
- Run the interpolation panel to plan the path from generation fps to timeline fps before generating anything.
- Copy the result into your shot list so frame budgets survive into the edit and the cost estimate.
Use Cases By Profile
- AI filmmaker: convert a 6 second shot into the exact frame count to type into a ComfyUI length field before queuing.
- Editor: pick the interpolation factor that lands 16 fps generations on a 24 fps timeline without retiming artifacts.
- Animator: budget frames for 12 fps animation passes and know the runtime cost of every added second.
Common Mistakes To Avoid
- Dividing frames by fps and wondering why every clip is one interval shorter than expected.
- Dropping 16 fps generations straight onto a 24 fps timeline and shipping the resulting judder or speed-up.
- Ignoring model frame-step constraints and requesting counts the model silently rounds.
Professional Best Practices
- Memorize the anchors: 81 frames at 16 fps is 5 seconds, 121 frames at 24 fps is 5 seconds.
- Interpolate before color and grain passes; interpolators behave better on clean frames.
- When a model constrains counts (4n+1 for Wan), pick the nearest valid count and recompute the true duration here.
Treat this tool output as a decision support layer, not a replacement for authorship. Great scripts are remembered for specific choices, emotional precision, and clarity of dramatic movement. Tools help by removing noise so your energy can go where it matters: character, conflict, escalation, and payoff. If you review outcomes after each pass and keep an explicit log of accepted changes, your workflow becomes faster and more predictable from draft to draft. That consistency is exactly what professional collaborators value: fewer surprises, clearer rationale, and a script that evolves with intent.
Extended FAQ
What formula does a video frames calculator use?
duration = (frames - 1) / fps. The minus one exists because N frames span N - 1 playable intervals. Frames from duration is the inverse: duration x fps + 1.
Why does Wan generate 81 frames?
Wan 2.x natively outputs 16 fps and targets 5 second clips: 5 x 16 + 1 = 81. The model also prefers 4n+1 frame counts, and 81 satisfies both.
What fps does AnimateDiff use?
AnimateDiff's motion modules were trained around 8 to 16 fps context windows, and most workflows render at 8, 12, or 16 fps, then interpolate up for delivery.
Is it better to generate at 24 fps or interpolate up to it?
Generating at 24 fps costs 50 percent more frames than 16 fps for the same duration. Most workflows generate at the model's native rate and interpolate, reserving native 24 fps for shots with fast motion where interpolation artifacts show.
How does frame count affect VRAM and generation time?
Roughly linearly for time and significantly for VRAM, since video models attend across frames. Halving fps at the same duration halves the frame budget, which is the main reason 16 fps generation plus interpolation is the default economy move.
What frame rate should the final export use?
Match your delivery target: 24 fps for cinematic work, 25 for PAL broadcast, 30 or 60 for social and screen capture. Decide the target first, then plan generation fps and interpolation factor backward from it.
Frequently asked questions
Because duration is (frames - 1) / fps, not frames / fps. A clip's playable length spans the intervals between frames, and N frames only have N - 1 intervals. An 81-frame clip at 16 fps lasts exactly 5.0 seconds, not 5.06.
81 frames: 5 x 16 = 80 intervals, plus the endpoint frame. This is exactly why Wan's default output is 81 frames, which decodes to a 5 second clip at its native 16 fps.
Interpolate by 1.5x if your tool supports fractional factors, which keeps duration identical. With integer-only interpolators, run 3x to 48 fps and drop every other frame, or export at 48 fps and let your NLE conform. Avoid simply retiming: playing 16 fps frames at 24 fps cuts a third off the duration.
Multiply the target seconds by your output fps and add 1. A 4 second clip at 16 fps is 65 frames; at 24 fps it is 97. Some nodes also constrain counts to model-specific steps (Wan uses 4n+1 values like 81), so round to the nearest valid count.
No. Interpolation fills each existing frame interval with new in-between frames, so a 2x pass on 81 frames at 16 fps yields 161 frames at 32 fps and the duration stays 5 seconds. Duration only changes if you retime, speed ramp, or drop frames afterward.
Plan the whole AI film, not just one clip
ScreenWeaver takes your script from scene breakdowns to storyboards and shot lists, so every clip you generate has a place in the cut before you spend GPU time. Free to start.
Plan your film free
