Understanding 120 FPS & The 8.33-Millisecond Frame Budget
Achieving a true 120 Frames Per Second (FPS) output requires the graphics processing unit (GPU) and the browser's compositor thread to execute all scene layout calculations, DOM updates, and raster operations within a strict 8.33-millisecond frame budget:
Δt_(budget) = (1000 ms)(120 FPS) = 8.333 msIf any single JavaScript calculation, layout reflow, or garbage collection pause takes longer than 8.33 milliseconds, the frame misses the hardware VSync deadline and causes an immediate dropped frame, inducing perceptible stutter.
Comparison Table: 60 FPS vs. 120 FPS Performance Specifications
The table below highlights performance metrics between standard 60 FPS and high-speed 120 FPS rendering:
| Performance Dimension | 60 FPS Rendering | 120 FPS Rendering | High-Speed Advantage |
|---|---|---|---|
| Frame Delivery Interval | 16.67 ms | 8.33 ms | 50% Lower Display Latency |
| Motion Blur Persistence | 16.67 ms sample-and-hold | 8.33 ms sample-and-hold | 2x Motion Clarity & Sharpness |
| Touch / Cursor Tracking Delay | ~30 – 50 ms | ~15 – 25 ms | Fluid, instantaneous responsiveness |
| Hardware Requirements | Standard HDMI 1.4+ | HDMI 2.0 / DP 1.2+ / HDMI 2.1 | Supports 1080p, 1440p, and 4K 120Hz |
Troubleshooting 120Hz on Apple ProMotion & Windows 11
- Apple ProMotion (macOS): Ensure ProMotion is selected under System Settings → Displays → Refresh Rate. In Safari, verify that Low Power Mode is disabled in Battery settings, as battery saver restricts Safari animations to 60Hz.
- Google Chrome Flags: If Chrome is locked at 60 FPS on a 120Hz monitor, open
chrome://flags, search for Choose ANGLE graphics backend, and switch from Default to D3D11on12 or OpenGL.