What Is Frame Time?
Frame time is the amount of time it takes to render a single frame, usually measured in milliseconds (ms). While frames per second (FPS) tells you how many frames are drawn each second, frame time tells you the gap between consecutive frames. The two are simply reciprocals of each other: a higher FPS means a lower frame time. This calculator converts any frame rate into its corresponding frame time.
How to Use This Calculator
Enter your frame rate in FPS and the calculator returns the time per frame in milliseconds. For example, 60 FPS produces a frame time of about 16.67 ms, while 144 FPS gives roughly 6.94 ms. Lower frame times generally mean smoother, more responsive motion in games and video.
The Formula Explained
The conversion uses a single equation:
$$\text{Frame Time (ms)} = \frac{1000}{\text{FPS}}$$
There are 1000 milliseconds in one second. Dividing 1000 by the number of frames in that second yields the duration of each frame. Because the relationship is inverse, doubling the FPS halves the frame time.
Worked Example
Suppose a game runs at 30 FPS. Plugging into the formula: $$\frac{1000}{30} = 33.333 \text{ ms}.$$ This means each frame stays on screen for about 33.3 ms. Compared to 60 FPS (16.67 ms), the 30 FPS experience feels noticeably less responsive.
FPS to Frame Time Reference Table
Frame time is simply the reciprocal of frame rate expressed in milliseconds:
$$\text{Frame Time (ms)} = \frac{1000}{\text{FPS}}$$All values below are \(1000 / \text{FPS}\) rounded to three decimals, so they are approximations of exact fractions (for example 60 FPS is exactly 16.6\(\overline{6}\) ms). The "typical use" column lists common conventions in film, broadcast and PC/console gaming; these are industry habits, not universal requirements.
| Frame rate (FPS) | Frame time (ms) | Typical use |
|---|---|---|
| 24 | 41.667 | Standard cinema / theatrical film |
| 25 | 40.000 | PAL-region broadcast and video (Europe, Australia, much of Asia/Africa) |
| 30 | 33.333 | Web video and a common console performance target (NTSC-region broadcast is actually 29.97 FPS ≈ 33.367 ms) |
| 48 | 20.833 | High frame rate cinema; also 2 × 24 for judder-free film playback |
| 50 | 20.000 | PAL-region 50 Hz video and sports broadcast |
| 60 | 16.667 | Mainstream gaming target; 60 Hz displays (NTSC-region 59.94 FPS ≈ 16.683 ms) |
| 75 | 13.333 | Entry-level high-refresh monitors; older LCD/VR panels |
| 90 | 11.111 | VR comfort target on several PC headsets |
| 100 | 10.000 | Round-number benchmarking reference; 100 Hz displays |
| 120 | 8.333 | PC gaming, 120 Hz TVs, current-generation console high-frame-rate modes, many VR headsets |
| 144 | 6.944 | Very common PC gaming monitor refresh rate |
| 165 | 6.061 | Overclocked/high-end PC gaming monitors |
| 240 | 4.167 | Competitive esports monitors |
| 360 | 2.778 | Top-tier esports panels |
| 480 | 2.083 | Cutting-edge esports and OLED high-refresh panels |
Worked example for 144 FPS, showing the full substitution:
$$\text{Frame Time} = \frac{1000}{144} = 6.944\ \text{ms}$$Frame Time Across Real-World Scenarios
Because frame time is a reciprocal, equal-looking jumps in FPS are not equal jumps in milliseconds. The table below steps through common upgrade targets and shows how much time per frame each step actually saves.
| Scenario / refresh target | FPS | Frame time (ms) | ms saved vs. previous step |
|---|---|---|---|
| Console / cinematic 30 FPS baseline | 30 | 33.33 | — |
| Standard 60 Hz gaming target | 60 | 16.67 | 16.67 |
| 120 Hz display / console performance mode | 120 | 8.33 | 8.33 |
| 144 Hz PC gaming monitor | 144 | 6.94 | 1.39 |
| 240 Hz esports monitor | 240 | 4.17 | 2.78 |
| 360 Hz esports monitor | 360 | 2.78 | 1.39 |
Sample step calculation (60 → 120 FPS):
$$\frac{1000}{60} - \frac{1000}{120} = 16.667 - 8.333 = 8.333\ \text{ms saved per frame}$$Gains shrink rapidly as FPS rises. Doubling 30 → 60 FPS removes 16.67 ms per frame, while doubling 120 → 240 FPS removes only 4.17 ms — roughly a quarter as much. Above about 144 FPS, each additional frame per second buys a fraction of a millisecond, which is why further upgrades are usually judged on display refresh rate, frame pacing consistency and total input latency rather than on raw FPS alone. Perceived benefit also depends on the person, the content and the display, so treat these numbers as timing facts rather than a promise of how much smoother something will feel.
Key Terms and Definitions
- Frame rate (FPS) — how many complete images are delivered per second. It is a rate, so it averages over a time window (commonly one second).
- Frame time (ms) — how long a single frame takes, in milliseconds: \(1000 / \text{FPS}\). It is an instantaneous, per-frame measure and is the unit engine profilers and optimization work are usually done in.
- Average vs. instantaneous frame time — average frame time is the mean over many frames (and corresponds to average FPS); instantaneous frame time is the duration of one specific frame. A scene can average 16.7 ms while individual frames range from 10 ms to 40 ms.
- Frame time variance / frame pacing (stutter) — the spread and unevenness of consecutive frame times. Alternating 8 ms and 25 ms frames averages to a decent FPS but is visible as hitching. Good frame pacing means frame times are both low and consistent.
- 1% and 0.1% low FPS — benchmark statistics derived from the worst frames. The 1% low reflects roughly the 99th-percentile (slowest 1%) frame times and the 0.1% low the 99.9th percentile, converted back into FPS. They describe the stutters you actually notice, which averages hide. Exact definitions vary between benchmarking tools, so compare numbers only within the same tool.
- Refresh rate (Hz) — how many times per second the display physically redraws, a property of the monitor, not the game. FPS is how fast frames are produced; Hz is how fast they can be shown. Rendering 200 FPS on a 60 Hz panel still shows at most 60 new images per second.
- VSync — synchronizes frame presentation to the display's refresh cycle to eliminate tearing. It effectively caps FPS at the refresh rate and can add latency, because a finished frame may wait for the next refresh.
- Variable refresh rate (VRR) — display technologies (NVIDIA G-SYNC, AMD FreeSync, the VESA Adaptive-Sync standard, HDMI VRR) that let the monitor adjust its refresh interval to match the rendered frame time, reducing tearing and stutter without a fixed VSync cap. Each panel supports VRR only within a stated range.
- Input latency — total delay from a physical input to the corresponding pixels changing on screen. Frame time is one contributor; input polling, engine pipeline depth, present queues, display processing and response time add more. Lower frame time helps latency but does not equal it.
- Frame time budget — the milliseconds a renderer has per frame to hit a target frame rate, i.e. \(1000 / \text{target FPS}\). At a 60 FPS target the budget is 16.667 ms for everything (CPU simulation, draw submission and GPU work); at 144 FPS it is 6.944 ms. Optimization is usually framed as fitting each subsystem into a share of that budget.
These definitions describe general rendering and display concepts; specific product behaviour (VRR ranges, sync modes, benchmark metric definitions) depends on your hardware, drivers and software.
FAQ
Why is lower frame time better? A shorter frame time means frames update more frequently, producing smoother motion and lower input latency.
What frame time is "good"? Many gamers target 16.67 ms (60 FPS) or below; competitive players often aim for 6.94 ms (144 FPS) or less.
Can I convert frame time back to FPS? Yes—just invert the formula: \( \text{FPS} = \frac{1000}{\text{frame time (ms)}} \).