0.5ms vs 1ms Timer Resolution: Which Value Should You Use?
Published
On this page
If you’ve decided to use timer resolution for gaming, the next question is which value to actually set: 0.5ms or 1.0ms? This guide explains what each one does, why lower isn’t automatically better, and how to pick the value your hardware and your frame pacing actually prefer.
0.5ms and 1.0ms are both good targets — the right one is whichever gives you steadier frame times, and that varies by system.
What the number actually means
Timer resolution is how often Windows’ system timer “ticks” — the smallest interval on which the OS schedules work and wakes threads. The default is 15.625ms, which is coarse. Requesting 1.0ms or 0.5ms makes that interval much finer, so Windows can service game threads and deliver frames on a tighter schedule.
Both 1.0ms and 0.5ms are enormous improvements over the 15.625ms default. The gap between them is far smaller than the gap between either of them and default — so don’t expect 0.5ms to feel dramatically different from 1.0ms. It’s a refinement, not another leap.
0.5ms vs 1ms — the honest comparison
| 1.0ms | 0.5ms | |
|---|---|---|
| Frame pacing | Very good | Often marginally tighter |
| Input-lag jitter | Reduced vs default | Slightly more reduced on many systems |
| Hardware support | Almost universal | Most modern platforms, not all |
| Idle power cost | Low | Slightly higher |
| Risk of worse 1% lows | Very rare | Rare, but possible on some CPUs |
The pattern for most modern desktops: 0.5ms is a touch smoother, and it’s the lowest value most current hardware exposes, so it’s a sensible default to try first. But “lower is always better” is a myth — on some CPUs an aggressively low timer generates more scheduler wakeups than it’s worth and can slightly worsen your 1% lows. That’s why you test rather than assume.
Check what your hardware supports first
Before you argue 0.5 vs 1, confirm your system even offers 0.5ms:
- Open an elevated command prompt.
- Run Microsoft’s Sysinternals ClockRes.
- Read the output:
- Maximum timer interval — the coarse default (~15.625ms).
- Minimum timer interval — the lowest your system supports. If this is ~0.5ms, you can use 0.5ms. If it’s ~1.0ms, that’s your floor.
- Current timer interval — what’s active right now.
If your minimum is 1.0ms, requesting 0.5ms just clamps to 1.0ms — you gain nothing by “setting” a value the hardware won’t deliver.
How to pick — test both, trust your frame times
Don’t choose by reputation; choose by your own frame-time graph:
- Pick a game and a repeatable scenario (a range, a fixed replay, a busy area).
- Set the timer to 1.0ms, play a few minutes, and watch your 1% lows and frame-time consistency with an overlay like RivaTuner Statistics Server or your FPS overlay.
- Switch to 0.5ms and repeat the exact same scenario.
- Keep the value with the flatter frame-time line and steadier 1% lows — not the higher average FPS, which barely moves.
If you genuinely can’t feel or measure a difference, use 0.5ms on a desktop (it’s the lowest floor) or 1.0ms on a laptop (marginally kinder to battery). Either is a good answer.
A resident timer tool makes this test painless: Tier1Timer applies your chosen value and holds it, and its Auto Mode only raises the timer while a game is focused — so you can flip between 0.5ms and 1.0ms and compare cleanly without the timer silently resetting mid-test. (If yours is resetting between runs, that skews the comparison — see Timer Resolution Not Working?.)
Bottom line
- 0.5ms — try it first on a modern desktop; usually the smoothest, and the lowest value most hardware exposes.
- 1.0ms — the classic value, near-universally supported, still excellent, and slightly gentler on laptop battery.
- Both crush the 15.625ms default; the gap between them is small.
- Test both and keep the steadier one. Lower is not automatically better — your 1% lows have the final say.
Related guides
Frequently asked questions
Is 0.5ms timer resolution better than 1ms?
On many modern systems 0.5ms gives slightly tighter frame pacing than 1ms, but it is not automatically better on every CPU. The difference is small, and some systems are more consistent at 1.0ms. Test both, watch your 1% lows and frame-time graph, and keep whichever is steadier for you.
What timer resolution should I use for gaming?
Start at 0.5ms if your hardware supports it, since it is the lowest most modern platforms expose. If 0.5ms feels no smoother or your frame pacing looks worse, drop to 1.0ms — the classic value that is still perfectly good. There is no benefit to requesting a value your hardware cannot actually deliver.
How do I know if my PC supports 0.5ms timer resolution?
Run Microsoft's Sysinternals ClockRes from an elevated command prompt. It prints the maximum, minimum and current timer resolution. If the minimum reads about 0.5ms you can use it; if the lowest your system reports is 1.0ms, that is your floor and requesting 0.5ms will just clamp to 1.0ms.
Does a lower timer resolution mean lower input lag?
Indirectly. A finer timer lets Windows schedule and wake threads on a tighter interval, which can smooth frame delivery and shave a little latency jitter. It does not slash input lag on its own, and going from 1.0ms to 0.5ms is a small refinement, not a large drop. Treat it as frame-pacing polish, not a magic latency fix.
Can setting 0.5ms timer resolution hurt performance?
Rarely, but it can. On a few CPUs an aggressively low timer causes more scheduler wakeups than it helps, showing up as slightly worse 1% lows. That is exactly why you test both values instead of assuming lower is always better. On laptops on battery, a lower timer also raises idle power draw slightly.