Valve’s third-person hero shooter MOBA, Deadlock, runs on the latest iteration of the Source 2 engine. While Source 2 is famously efficient at handling clean geometry and precise hit registration, Deadlock presents a unique hardware challenge. Unlike traditional tactical shooters like Counter-Strike 2, Deadlock combines a massive vertical map, six distinct lanes, thousands of active lane creeps, and twelve players spamming high-impact particle abilities simultaneously.
Understanding where your hardware bottlenecks occur is key to finding the best Deadlock settings for FPS. In the early laning phase, performance is usually smooth and bound by your graphics card. However, as matches progress into 30-minute late-game teamfights—where team wipes, Patron pushes, and endless particle effects collide—the game becomes heavily CPU-bound. Frame drops during these crucial moments are rarely caused by GPU shading limitations; they stem from CPU draw calls, tick-rate processing, and physics calculations across Source 2’s entity system. As Valve continues to optimize the game engine in 2026, dialing in your graphics parameters ensures high framerates and clean competitive visibility when chaotic teamfights erupt.
Quick answer: For most people in 2026, the best deadlock settings for fps is the Rendering API — our #1 rated choice. See the full ranked comparison, alternatives and buying advice below.
Quick Preset Summary
If you want to apply optimized configurations immediately without digging into individual sub-menus, use the tailored presets below. These target three primary user profiles: competitive players seeking maximum frame consistency, mid-range system owners wanting a balance of visuals and speed, and budget or handheld users pushing for playable framerates.
| Setting | Competitive (Max FPS/Clarity) | Balanced (Mid-Range) | Low-End PC / Handheld |
|---|---|---|---|
| Rendering API | DirectX 11 (or Vulkan) | DirectX 11 | DirectX 11 |
| Upscaling Technology | Off (Native) or DLSS Quality | DLSS / FSR Quality | FSR Performance / Balanced |
| Render Scale | 100% | 100% | 80% – 90% |
| Shadow Quality | Low | Medium | Low |
| Model Detail | Medium | High | Low |
| Texture Detail | High (VRAM permitting) | High | Medium / Low |
| Visual Effects Detail | Low | Medium | Low |
| Distance Field Ambient Occlusion | Off | Off | Off |
| Screen Space Reflections | Off | Low | Off |
| Post-Processing Quality | Low | Medium | Low |
| Motion Blur | Off | Off | Off |
| Anti-Aliasing | FXAA / Low TAA | TAA | FXAA / Off |
| NVIDIA Reflex Low Latency | On + Boost | On | On |
Settings That Matter Most for FPS
Not all graphic toggles in Deadlock are created equal. Some drastically lower your framerate while providing minimal visual gains, whereas others are crucial for spotting enemy heroes through abilities. Here is a breakdown of the settings with the largest performance impact.
Distance Field Ambient Occlusion (DFAO)
Performance Impact: Very High (~12% to 18% FPS hit)
DFAO generates soft contact shadows in open areas by calculating ray-marched distance fields across static and dynamic geometry. In Deadlock‘s complex urban map, DFAO taxes shader execution units severely. Turning this off provides an instant frame boost, particularly on mid-range and older GPUs. Disabling it also brightens dark alleys, making it easier to spot enemy heroes hiding near juke spots or neutral monster camps.
Shadow Quality
Performance Impact: High (~10% to 15% FPS hit)
Shadow Quality dictates the resolution of shadow maps, dynamic character shadow casting, and shadow draw distance. High dynamic shadows strain both the GPU and the CPU, as the main thread must process dynamic shadow casting matrices for every creep and hero on screen. Dropping Shadow Quality to Low drastically cuts CPU draw overhead during late-game base pushes without sacrificing your ability to see basic player silhouettes.
Visual Effects & Particle Detail
Performance Impact: High in Teamfights (~15% to 25% 1% Low FPS drop)
This setting controls the resolution, density, and rendering pass limits of magic effects, weapon tracer particles, and ultimate abilities. While your baseline FPS in an empty lane might not change dramatically, keeping this on High causes massive frame drops during 6v6 clashes when heroes combine ultimates. Lowering Visual Effects Detail to Low keeps frametimes consistent during heavy combat, ensuring smooth tracking and aiming.
Screen Space Reflections (SSR)
Performance Impact: Moderate to High (~8% to 12% FPS hit)
SSR adds real-time reflections to wet streets, rooftops, and metallic surfaces across the map. While it makes the environment look polished, it creates distracting visual noise during firefights and consumes valuable GPU bandwidth. Turning SSR Off yields a solid bump in average framerates and clarifies the ground terrain, making area-of-effect abilities easier to identify.
Model Detail
Performance Impact: Moderate (~5% to 8% FPS hit)
Model Detail alters geometric complexity and Level of Detail (LOD) transitions for buildings, props, lane creeps, and player characters. Setting this too low can cause aggressive object pop-in at long ranges, which impedes long-distance snipers. Setting it to Medium provides the ideal compromise: clean hitboxes and high-distance visibility without overloading your CPU’s geometry pipeline.
Upscaling, Anti-Aliasing, and Frame Generation
Because Deadlock is an aim-heavy third-person shooter requiring rapid 180-degree camera flicks, how you handle frame reconstruction and image smoothing drastically impacts your input latency.
NVIDIA DLSS vs. AMD FSR vs. Native Resolution: If you are running at 1440p or 4K with an NVIDIA RTX card, enabling DLSS in Quality mode provides a substantial performance boost with virtually no loss in image clarity. AMD FSR 2/3 is available for non-RTX cards, but FSR can introduce temporal shimmer on fine details like overhead power lines and ziplines. If your GPU handles native resolution comfortably, running native with FXAA or light TAA yields the cleanest visual response.
Why Frame Generation Should Be Avoided: Frame Generation technologies (such as DLSS 3 Frame Gen or FSR 3 Motion Vector Generation) insert synthesized frames between real rendered frames. While this inflates your counter’s FPS value, it increases input lag and introduces latency instability. In a fast-paced game like Deadlock, low input latency is far more valuable than perceived visual smoothness. Leave Frame Generation turned Off.
Anti-Aliasing Choices: TAA (Temporal Anti-Aliasing) removes jagged edges effectively, but introduces visual blur during fast mouse movements. For maximum competitive performance, use FXAA or low-level TAA. FXAA processes quickly on the GPU with zero temporal trailing, keeping enemy models sharp even while fast-ziplining across lanes.
Outside the Game: Launch Options and Driver Optimization
You can unlock extra performance and improve frametime stability in Source 2 through system-level adjustments outside of Deadlock‘s in-game options menu.
Steam Launch Options
Right-click Deadlock in your Steam Library, select Properties, and paste the following commands into the Launch Options field:
-novid -high -threads [X] -exec autoexec.cfg
-novid: Bypasses startup logos to load into the main menu faster.-high: Gives the Deadlock executable high CPU priority in Windows.-threads [X]: Replace [X] with your CPU’s physical core count (e.g., 6 or 8) to optimize Source 2 engine thread allocation.
API Selection: DirectX 11 vs. Vulkan
Source 2 supports both DirectX 11 and Vulkan renderers. For most Windows users with modern NVIDIA or AMD graphics cards, DirectX 11 delivers superior frametime consistency and fewer hitching issues. However, if you are playing on Linux, Steam Deck, or older AMD graphics cards, Vulkan may offer better frame pacing. Test both APIs on your specific rig to see which yields a smoother frametime graph.
NVIDIA Control Panel & AMD Software Tweaks
- Power Management Mode: Set to Prefer Maximum Performance.
- Low Latency Mode / AMD Anti-Lag: Set to On or Ultra. This reduces the render queue size, decreasing input lag when your GPU reaches high utilization.
- Shader Cache Size: Set to 10GB or Unlimited. Source 2 compiles shaders dynamically; expanding your shader cache prevents stuttering when new abilities are cast for the first time in a match.
Settings You Should Leave Alone
When tuning for maximum FPS, it is easy to over-optimize and disable settings that provide important visual information without offering meaningful performance gains.
- Texture Detail: As long as your GPU has sufficient VRAM (6GB or higher), keeping Textures at High causes zero frame loss. Dropping textures down to Low makes hero skins and ability markers look muddy without raising your FPS limit.
- Anisotropic Texture Filtering: Leaving this set to 16x costs less than 1% of your overall GPU bandwidth on modern hardware, but keeps ground markings and lane distances crisp when viewed at sharp angles.
- Camera Field of View (FOV): While reducing FOV technically decreases the rendered geometry on screen, doing so destroys your peripheral vision. Always max out your FOV slider for competitive awareness.
- Audio Occlusion / Spatial Sound: Unless you are running an outdated dual-core processor, disabling audio processing provides no measurable CPU gain and makes tracking enemy footsteps through walls nearly impossible.
Frequently Asked Questions
Is Deadlock CPU or GPU bound?
Deadlock is hybrid-bound, shifting dynamically throughout a match. During early laning, performance is largely GPU-bound. However, during mid-to-late game teamfights, the game becomes heavily CPU-bound. The Source 2 engine must calculate hundreds of pathfinding entities, dynamic hitboxes, ability interactions, and network updates simultaneously, placing heavy reliance on single-core CPU speeds and cache size.
Should I use Vulkan or DirectX 11 for Deadlock?
For the vast majority of Windows systems, DirectX 11 offers higher average framerates and lower frame latency variance. Vulkan is recommended primarily for Linux users via Proton, handheld devices like the Steam Deck, or older AMD GPUs where DirectX 11 drivers are less optimized.
Why does my FPS drop drastically during late-game teamfights?
Late-game frame drops occur because the CPU render queue becomes saturated with draw calls. When twelve players cast particle-heavy ultimates simultaneously alongside dozens of active lane creeps and neutrals, your processor struggles to keep up with the frame instructions sent to the GPU. Lowering Visual Effects, Shadow Quality, and Ragdoll physics reduces this CPU bottleneck.
Does using upscaling like DLSS or FSR create input lag in Deadlock?
Standard spatial or temporal upscaling (DLSS Super Resolution or FSR 2/3 in Quality modes) adds minimal to no input lag, and can actually decrease input latency if it shifts your system out of a GPU bottleneck. However, Frame Generation technologies (DLSS 3 Frame Gen or FSR 3 Frame Gen) do add latency and should remain disabled for competitive play.
Ready to decide? Our #1 pick for 2026 is the Rendering API.
Live price & availability on Amazon.