Playback Performance
How to Play 120 FPS Video Smoothly on Windows
Smooth 120 FPS video playback needs the whole chain to keep up: the file must really contain 120 frames per second, the decoder must deliver them on time, and the display must refresh fast enough to show them. A 60 Hz screen can play the file at normal speed, but it cannot visibly present all 120 unique frames each second.
Published · By Calvin Sturm
What 120 FPS playback actually needs
- A true high-frame-rate file. Check the frame rate in MediaInfo or the camera's recording details. A file labeled slow motion may be captured at 120 FPS but authored to play back at 30 FPS intentionally.
- A display running at 120 Hz or faster. Frame rate belongs to the video; refresh rate belongs to the monitor. Both must be high enough to see every frame.
- Enough decode throughput. 4K, HEVC, 10-bit, and HDR each add work. A hardware decoder that supports the file's codec and profile usually matters more than raw CPU speed.
- Reliable timing. The player must schedule frames smoothly instead of releasing them in bursts or dropping frames that arrive together.
Check the display refresh rate in Windows
- Open Settings > System > Display.
- Select the monitor where the video will play.
- Open Advanced display.
- Under Choose a refresh rate, select 120 Hz, 144 Hz, 165 Hz, 240 Hz, or the fastest stable option.
Windows can leave a fast monitor at 60 Hz after a driver change, cable swap, or display reset. If the higher option is missing, check the monitor port, cable bandwidth, display mode, and GPU driver. Microsoft's refresh-rate instructions show the current Windows controls.
Separate display limits from playback problems
- Motion is consistent but no smoother than 60 FPS: the display is likely running at 60 Hz, or the source was authored at a lower playback rate.
- Motion hitches at irregular intervals: suspect dropped frames, software decoding, background load, or a timing problem in the player.
- Audio stays smooth while video falls behind: the video decode or presentation path is not keeping pace.
- Every player struggles with the same file: test from a local SSD and check whether the GPU supports the exact codec, bit depth, and profile.
Fix choppy 120 FPS playback
- Set the correct refresh rate and play full-screen on that monitor.
- Close GPU-heavy games, editors, browser video, and background recording tools.
- Copy the file to a local SSD before blaming the decoder or player.
- Try a player with hardware decoding for the file's codec and software fallback.
- Test a lower-resolution 120 FPS sample to separate resolution load from frame-rate load.
- Update the GPU driver if hardware decode fails or produces corruption.
For broader causes—thermal throttling, slow storage, display judder, and codec fallback—use the full Windows video stuttering checklist.
How FastPlay handles 120 FPS
FastPlay uses FFmpeg decoding with a D3D11 hardware path where supported and automatic software fallback. Version 0.4.4 fixed a scheduler problem that structurally discarded about one frame in six at 120 FPS. In the release validation, a synthetic 120 FPS clip improved from 405 dropped frames to 6 out of 2,400 on a 240 Hz display.
Limits and caveats
- A 60 Hz display cannot show 120 unique frames each second, regardless of player.
- Presenting 120 FPS requires a display running faster than 120 Hz in FastPlay's current implementation.
- Unsupported hardware-decode profiles fall back to the CPU and may not sustain heavy 4K120 files.
- Variable-frame-rate footage can report an average near 120 FPS without delivering evenly spaced frames.
Test the file in a 120 FPS-aware player
FastPlay is free and open source for Windows. Open the original file, verify your display refresh rate, and compare motion without converting the video.