About FPS ↔ Frame Time Converter

Convert between FPS and milliseconds per frame with performance budgets. Part of the DevTools Surf developer suite. Browse more tools in the Game Dev collection.

Use Cases

• Game programmers budgeting CPU and GPU time per frame
• Performance engineers diagnosing frame time spikes and hitches
• Technical directors setting frame rate targets for new projects
• VR developers ensuring consistent 90 FPS for motion sickness prevention

Tips

• Remember: 60 FPS means only 16.67ms per frame budget
• Subtract engine overhead to find your actual render budget
• Compare 30, 60, and 120 FPS targets for platform planning

Fun Facts

• The human eye can perceive differences up to approximately 150-240 FPS in controlled studies — the myth that 'the eye can only see 30 FPS' has been thoroughly debunked.
• John Carmack's id Software pioneered 60 FPS gameplay with Quake III Arena in 1999, when most games targeted 30 FPS — this standard persists in competitive gaming today.
• At 120 FPS, each frame has only 8.33ms to render — this is why PS5 and Xbox Series X games that target 120 FPS often reduce resolution or visual fidelity significantly.

FAQ

Why convert FPS to milliseconds?

Frame budget. 60 FPS = 16.67ms per frame. Every game logic + render must fit in that window. Knowing the exact budget helps optimization.

What targets are common?

60 FPS (16.67ms) for smooth gameplay. 30 FPS (33.33ms) for cinematic / mobile. 120/144 FPS for competitive games.

What's vsync?

Synchronization with display refresh rate. 60Hz monitor = 60 FPS maximum vsync'd. Tearing happens without vsync when frame rate and refresh don't match.

Performance budgets shown?

Yes — the tool shows typical budget breakdowns (physics 2ms, render 8ms, logic 4ms, etc.). Useful for profiling and identifying bottlenecks.