Frame Time Calculator

Frame time is how long (in milliseconds) your GPU takes to render each individual frame. It is the inverse of the frame rate, or FPS (frames per second):

Frame Time (ms) = 1000 ÷ FPS

While FPS gives an average, frame time reveals consistency. A game averaging 60 FPS could still feel stuttery if individual frames take wildly different amounts of time to render: a phenomenon called frame pacing.

Why frame time matters:

• A perfectly smooth 60 FPS means every frame takes exactly 16.67 ms
• If most frames take 10 ms but one frame takes 100 ms, your average FPS looks fine but you feel a jarring stutter
• Frame time analysis (1% and 0.1% lows) is how reviewers detect poor frame pacing

Frame budgets by target FPS and refresh rate:

Monitor sync technologies:

• G-Sync / FreeSync: these sync the monitor’s refresh rate to whatever the GPU produces, so tearing disappears and frame time consistency matters more than raw FPS.
• VRR (variable refresh rate) window: a panel only syncs inside a range, commonly around 48 Hz up to its maximum. Fall below the floor and Low Framerate Compensation kicks in, doubling frames to stay in the window. It works, but staying above the floor is cleaner.

CPU vs GPU frame time

The two limits look identical on an FPS counter and completely different on a frame time graph. When the GPU is the limit, it runs flat out and frames arrive at a steady spacing, which feels smooth. When the CPU is the limit, the GPU finishes early and then waits for the CPU to hand it the next frame. Draw calls, physics, pathfinding and world streaming all live on the CPU, and their cost swings from frame to frame far more than rendering does.

That is why a CPU-limited game can post a perfectly respectable 90 FPS average with 1% lows down at 45, while a GPU-limited game at the same average feels fine. If your frame time graph looks like a saw blade rather than a flat line, look at the CPU first.