How to improve FPS in Team Fortress 2 (PC)
Team Fortress 2 runs on Source Engine, a 2007 engine that prioritizes physics simulation and netcode over the graphics department, so its hardware demand is minimal even for entry-level GPUs. Its real ceiling isn't the raw FPS any modern card can deliver, but frametime stability during massive 24-player fights with particles, blood, and class effects (Pyro's flames, Spy's teleports, Soldier's rockets) saturating the screen. TF2's competitive community has spent over a decade optimizing the game far beyond the options menu, using console commands and dedicated configs to squeeze every millisecond of input lag. This guide covers both the standard graphics settings and the console configs that actually make a difference on this engine, plus a clarification of what you CANNOT do in a game with no modern upscaling support.
This is what you'd gain with a NVIDIA RTX 3050
Calculations based on our FPS model combined with the % gain of each setting (measured in public benchmarks).
1. Quick wins (no visual loss)
Start here. Each one adds a little, but together they give +38% free FPS.
Multicore Rendering
Enables splitting rendering work across several CPU cores. On 4+ core systems it's the single biggest gain in TF2 and has no visual effect.
Shadow Detail
Completely disables the calculation of dynamic shadows from players and projectiles. In 6v6 fights with many characters on screen, shadows are among the engine's most expensive variables.
Model/Texture Detail
Reduces texture resolution for weapons and nearby characters. The visual impact is low because TF2 uses a cartoon art style with few high-frequency textures.
Water Detail
Forces simple water reflections instead of reflecting full geometry. Several competitive maps (Process, Snakewater) have water areas that, if left unrestricted, generate localized frametime drops.
Motion Blur
Source's motion blur adds post-processing cost without contributing anything in a precision shooter; it also reduces the readability of fast projectiles like rockets or arrows.
2. Medium impact settings
Here's where most of the FPS is. Minor visual impact, major performance impact.
Ragdoll/Corpse Fade Time
Reduces how long physical corpses stay on the map after death. In long matches with many deaths, accumulating ragdolls with active physics noticeably penalizes the CPU.
Particle Detail/Effects
Reduces the density of smoke, fire, blood, and explosion particles. It's the setting with the biggest visual impact on this list, but also one of the ones that frees up the most FPS in massive Pyro/Demoman fights.
Antialiasing
Source's MSAA is costly relative to the visual benefit given the game's stylized art. Disabling it or leaving it at 2x is the sweet spot for most GPUs.
HDR
Source's HDR adds an extra rendering pass. On limited hardware, disabling it frees up FPS; on modern GPUs the cost is marginal and it improves contrast on dark maps.
Texture Filtering (Anisotropic)
Dropping anisotropic filtering to bilinear slightly reduces texture sharpness at an angle, but frees up some memory bandwidth that helps on integrated or very old GPUs.
3. Upscaling (DLSS / FSR / XeSS)
The biggest gain in the game. Compatible with almost any modern GPU.
Sin soporte de upscaling
+0% FPSTeam Fortress 2 runs on Source Engine (2007) and does NOT and will NOT have native support for DLSS, FSR, or XeSS: these are modern-engine technologies with deferred rendering pipelines that Source doesn't implement. Any mention of "enabling FSR in TF2" is a myth; ignore tutorials that promise it.
Resolución custom + mat_queue_mode como sustituto
+15% FPSThe real alternative in TF2 is manually lowering the internal render resolution (mat_setvideomode or a desktop resolution below native) and letting the monitor or OS scaling stretch the image. It's not smart upscaling, but on 1440p/4K screens with low-end GPUs it lets you recover FPS similarly to a manual "Performance mode."
4. Tips by GPU
NVIDIA
- •Enable Low Latency Mode on Reflex/Ultra inside the NVIDIA panel to reduce input lag in close combat, something critical in a skill-based shooter like TF2.
- •Force Power Management Mode to "Prefer Maximum Performance" to avoid downclocks on GPUs that TF2 doesn't saturate enough to maintain stable boost clocks.
- •Cap FPS with V-Sync disabled and an fps_max slightly below your monitor's maximum to avoid tearing without the input lag of traditional V-Sync.
AMD
- •Enable Radeon Anti-Lag to reduce input latency, especially useful on mid-range GPUs where TF2 runs far above the monitor's framerate and generates unnecessary frame queuing.
- •Disable Radeon Chill or any dynamic FPS limiter: TF2 has load spikes so variable (fights vs. empty hallways) that these systems generate perceptible microstutter.
- •Use Radeon Image Sharpening at a low value (10-20%) if you manually lower render resolution, to compensate for sharpness loss with no relevant performance cost.
Sistema
- •TF2 is still single-thread heavy in much of its game logic (physics, netcode), so CPU per-core frequency matters more than core count: prioritize high IPC/GHz over very multicore CPUs.
- •Install the game on an SSD; texture and sound streaming spikes when loading a new map or respawning on servers with many plugins can cause noticeable microstutter on HDD.
- •If you play on community servers with many plugins (SourceMod), expect some tickrate fluctuation that doesn't depend on your hardware: it's the server's responsibility, not your local configuration.
5. Known game issues
Bot crisis on Valve's casual servers
Since late 2020, waves of aimbot bots and spam scripts invaded Valve's official Casual servers. It doesn't directly affect framerate, but it degrades the experience enough that a large part of the competitive and serious casual community migrated to third-party community servers (UGC, ETF2L, comp.tf), where perceived net performance is much better due to less network saturation and better tickrate.
Memory leak in long sessions
Sessions of several hours in a row, especially switching maps many times without restarting the game, can accumulate RAM usage until it generates progressive stutter. Restarting the game every few hours of a long session avoids the problem entirely.
Stutter spikes when loading new particles
The first time a specific particle effect appears in a session (a crit, an explosion from a rarely used weapon), Source Engine compiles/caches it on the fly, causing a one-off microstutter. It's inherent to the engine and isn't solved by more powerful hardware, only mitigated by preloading with warm-up maps.
6. Frequently asked questions
Why doesn't TF2 use all of my CPU even with 8 or 16 cores?▾
Which FPS config should I use, comfig or chris' config?▾
Is it worth pushing FPS above 300 if my monitor is 144Hz?▾
Why doesn't my new GPU push much more FPS than my old one in TF2?▾
Want to know exactly how many FPS YOUR PC will get?
Enter your GPU and CPU in our calculator and measure the real impact of each setting.
Calculations based on consensus of technical sources and our own FPS model. More about our methodology →