Frame Time Budget Calculator
Convert a target FPS into a per-frame millisecond budget and check whether your subsystem timings fit.
60 FPS means 16.67ms per frame; 120 FPS just 8.33ms; 30 FPS a roomy 33.3ms. Everything — input, logic, physics, render submission, GPU work, present — must fit. Subsystems run partly in parallel (CPU/GPU pipelined), so summing is a conservative worst case; the real bottleneck is the longest stage.
Formula
Disclaimer: This tool is for general informational and estimation purposes only and is not professional financial, tax, accounting or legal advice. All figures are estimates — verify with a qualified professional before making decisions. Read the full disclaimer.
About Frame Time Budget Calculator
Every frame rate is really a time budget: 60 FPS gives you 16.67 milliseconds to do everything — input, game logic, physics, animation, render submission, GPU work and present — before the frame is late. This calculator converts your target FPS into that per-frame budget and checks whether your measured subsystem timings fit, flagging the overage and the actual FPS you'd hit. It's the mental model behind all real-time optimization: you're not chasing 'speed', you're fitting work into a fixed, unforgiving millisecond window that shrinks as the target rises.
How to use Frame Time Budget Calculator
- 1Enter your values into Frame Time Budget Calculator — sensible, domain-typical defaults are pre-filled so you see a real result immediately.
- 2The result recomputes live using the formula shown on the page; there is no button to press.
- 3Adjust any input to compare scenarios, then read the worked example to see the substituted numbers.
Why use Frame Time Budget Calculator?
- ✓Computes Frame Time Budget instantly in your browser — no sign-up, no upload, no server round-trip.
- ✓100% free and unlimited, with the exact formula shown: frame budget = 1000 / target FPS (ms).
- ✓Runs entirely client-side, so every value you enter stays private on your device.
- ✓Live recompute as you type, with a worked example and authoritative references for trust.
Frequently asked questions
How many milliseconds is 60 FPS?+
16.67 ms per frame (1000/60). 30 FPS gives a roomy 33.33 ms, 120 FPS a tight 8.33 ms, and 144 FPS just 6.94 ms. Each doubling of frame rate halves your budget, which is why high-refresh targets demand dramatically more optimization — there's simply less time to do the same work.
Can I just add up subsystem times like this tool does?+
Summing is a conservative worst case. In reality CPU and GPU work is pipelined — the CPU prepares frame N+1 while the GPU renders frame N — so your frame time is governed by the LONGEST stage, not the sum, once the pipeline is full. Use the sum as a safe upper bound, then profile to find which single stage is the true bottleneck.
What happens when I exceed the frame budget?+
The frame is late, causing a stutter (with V-sync, the frame rate drops to the next divisor — 60 to 30 to 20 FPS, a harsh cliff) or a torn frame (without V-sync). Consistent frame times matter more than average FPS: 60 FPS with occasional 40ms spikes feels worse than a steady 50 FPS, because the spikes are visible hitches.
How do I find headroom on a missing frame?+
Profile to attribute milliseconds to each subsystem (this tool's inputs), then attack the largest. Common wins: reduce draw calls and overdraw (GPU), cut per-frame allocations and physics substeps (CPU), move work off the critical path (async loading, multithreading), and apply LODs and culling. Re-measure after each change against the budget here.
Related Game Dev tools
DPS (Damage Per Second) Calculator
Effective DPS from hit damage, attack speed, crit chance and crit multiplier — the core combat-balance number.
● LiveEffective HP (EHP) Calculator
True survivability from raw HP plus damage reduction (armor/resist) — why 50% reduction doubles your effective health.
● LiveDrop Rate / Expected Tries Calculator
Probability of at least one drop in N tries, expected tries to get one, and the 'pity' attempt count.
● Live