TF2 Lowest Input Lag Settings: Fullscreen, FPS Cap, Vulkan
Published
On this page
The lowest input lag in Team Fortress 2 comes from exclusive Fullscreen, V-Sync and MSAA off, Multicore Rendering on, a frame cap at or above your refresh rate (or an external RivaTuner cap), raw mouse input, and Ultra Low Latency / Anti-Lag in your GPU driver — TF2 has no NVIDIA Reflex, so the driver is where you stop frames queuing. TF2 is a light Source game that runs at hundreds of FPS on modern PCs, so the gains come from removing latency the defaults add, not from raw FPS. Everything here works on the current 64-bit build.
The short version
| Setting | Where | Value |
|---|---|---|
| Display mode | Options → Video | Fullscreen |
| Wait for vertical sync | Video → Advanced | Disabled |
| Antialiasing mode | Video → Advanced | None |
| Multicore Rendering | Video → Advanced | Enabled |
Frame cap (fps_max) | Console | ≥ refresh rate, or 0 with a RivaTuner cap |
| Raw mouse input | Console | On (m_rawinput 1) |
| Low Latency Mode / Anti-Lag | GPU driver | Ultra / On |
| Renderer | Launch options | DirectX 9 default; test -vulkan |
Display mode: exclusive Fullscreen
Set Options → Video → Display mode → Fullscreen. In Windowed or Windowed (no border), Team Fortress 2’s frames pass through the Windows desktop compositor, which can add latency; exclusive Fullscreen gives the game direct control of the display. Fullscreen is also what lets your GPU stretch a 4:3 resolution — see the TF2 stretched resolution guide. More on the difference: Fullscreen vs Borderless vs Windowed.
Advanced video settings that add latency
Open Options → Video → Advanced:
- Wait for vertical sync: Disabled. V-Sync holds finished frames until the next refresh, adding delay; mastercomfig recommends keeping it off. If tearing bothers you, NVIDIA Fast Sync or AMD Enhanced Sync tear less with far lower latency than traditional V-Sync (V-Sync on or off?).
- Antialiasing mode: None. Mastercomfig notes that on DirectX, enabling MSAA may increase input latency — and TF2’s art style reads clearly without it.
- Multicore Rendering: Enabled. It splits TF2’s rendering across CPU threads, which keeps frame times lower and steadier on any modern multi-core CPU.
Frame cap: high, or external
Team Fortress 2’s cap is the fps_max console variable. A higher cap lowers input delay, so set it at or above your monitor’s refresh rate — never below it.
The catch: mastercomfig documents that TF2’s built-in limiter has precision problems on many CPUs (Intel Skylake and newer) and accuracy problems on Windows, because it uses millisecond timers. If you want an exact cap — for example refresh minus 3 to stay inside a G-Sync/FreeSync range — cap with RivaTuner Statistics Server and set fps_max 0 so the two limiters don’t fight. Don’t push the cap past about 1000 FPS, which mastercomfig treats as the maximum safe value. More on choosing a cap: how to cap your FPS correctly.
Launch options: -vulkan and DirectX level
On Windows, Team Fortress 2 renders with DirectX 9 by default. Since the 2024 64-bit update it also offers a -vulkan launch option, which runs the game through DXVK (DirectX 9 translated to Vulkan). The mastercomfig documentation says -vulkan improves input latency and fixes some graphics bugs, with a trade-off depending on your system and drivers — so test it rather than assuming.
- In Steam, right-click Team Fortress 2 → Properties → Launch Options.
- Launch once with
-dxlevel 95, then remove it. - Add
-vulkanand compare against DirectX 9 on the same map with a frame-time overlay. Keep whichever gives flatter frame times on your PC.
A useful base line is mastercomfig’s recommended set: -novid -nojoy -nosteamcontroller -nohltv -particles 1. Don’t leave -dxlevel in permanently — mastercomfig warns it can stop graphics settings applying, slow loading and cause freezes. Avoid DirectX 8 (-dxlevel 81): it’s an old path that can add input lag and has been reported to crash since the 64-bit update.
Mouse: raw input on
Enable raw mouse input by entering m_rawinput 1 in the developer console (put it in your autoexec.cfg so it sticks). Raw input reads the mouse directly instead of through Windows pointer settings, so Windows acceleration and pointer speed don’t touch your aim. Pair it with a 1000 Hz polling rate — the practical sweet spot for most mice (polling rate explained).
GPU driver settings
TF2 has no NVIDIA Reflex, so the driver is where you stop the GPU queuing frames ahead of the CPU:
- NVIDIA: NVIDIA Control Panel → Manage 3D settings → Program Settings → Team Fortress 2 → Low Latency Mode: Ultra, Power management mode: Prefer maximum performance. See NVIDIA Low Latency Mode explained.
- AMD: AMD Software → Gaming → Team Fortress 2 → Radeon Anti-Lag: On.
Low Latency Mode matters most when your GPU is the bottleneck; in TF2 the CPU usually is, so expect a small gain rather than a dramatic one.
Windows settings
- Power plan: High Performance or Ultimate Performance, so the CPU doesn’t downclock between frames.
- Game Bar recording / Game DVR: off.
- Timer resolution: Windows’ default 15.6 ms system timer adds scheduling jitter; a 0.5 ms timer tightens frame pacing. Tier1Suite applies it in one click — see the timer resolution guide.
Input lag vs network lag in TF2
None of the settings above change your ping. If shots feel late only on some servers, that’s network latency and server tick, not input lag: pick servers close to you, use a wired connection, and leave TF2’s network rates at defaults unless you know why you’re changing them.
Related guides
Frequently asked questions
How do I reduce input lag in Team Fortress 2?
Run Team Fortress 2 in exclusive Fullscreen, turn off Wait for vertical sync and MSAA, keep Multicore Rendering on, and set the frame cap at or above your monitor's refresh rate — or cap with RivaTuner instead of the built-in limiter. TF2 has no NVIDIA Reflex, so enable Ultra Low Latency Mode (NVIDIA) or Anti-Lag (AMD) in your driver to keep the GPU from queuing frames.
Does the -vulkan launch option reduce input lag in TF2?
It can. The -vulkan launch option runs Team Fortress 2 through DXVK, which translates its DirectX 9 rendering to Vulkan, and the mastercomfig documentation says it improves input latency and fixes some graphics bugs, with a trade-off that depends on your system and drivers. Launch once with -dxlevel 95 first, then use -vulkan, and compare frame times on your own PC before keeping it.
What should fps_max be in TF2?
Set fps_max at or above your monitor's refresh rate; a higher cap lowers input delay as long as your PC holds it. TF2's built-in limiter is imprecise on many modern Intel CPUs and on Windows, so for an exact cap such as refresh minus 3 with G-Sync, use RivaTuner Statistics Server and set fps_max 0 to remove the in-game cap. Avoid going above about 1000 FPS, which mastercomfig treats as the maximum safe value.
Is TF2 Fullscreen or Windowed better for input lag?
Exclusive Fullscreen is better. Windowed and Windowed (no border) modes send TF2's frames through the Windows desktop compositor, which can add latency, while Fullscreen gives the game direct control of the display. Fullscreen is also required for GPU-scaled stretched resolution.
Should I use a -dxlevel launch option permanently in TF2?
No. Use -dxlevel 95 or -dxlevel 100 for one launch to set the DirectX level, then remove it. Mastercomfig warns that leaving -dxlevel in your launch options can stop graphics settings applying properly, slow loading, cause freezes and keep TF2 from using your hardware properly.