Deadlock settings and FOV

Enable the dev command console in settings, press F7, and the field-of-view variable is citadel_camera_hero_fov. The current community convar table lists a default of 90. Variable existence does not establish that changing it is permitted or functional in matchmaking.

By the deadlock.run editorial desk · Last checked 2026-10-29. Source and corrections policy.

I am not publishing a graphics preset. Nobody measured frames on a named PC for this guide. City Never Sleeps did add a default-value mark on sliders, which is the settings change I can actually cite.

Deadlock lane fight from a Valve store screenshot

Deadlock combat from a Valve store screenshot

Documented settings, not a benchmark

The console is restricted in normal matchmaking, so try a variable change in a custom or practice match first. Community threads share aim-down FOV binds; treat them as unofficial scripts, not Valve features.

Deadlock runs an autoexec.cfg file on its own. That is why Deadlock Mod Manager removed its autoexec launch option in version 2.2.0 and stopped writing custom crosshairs into that file.

Questions

How do I change FOV?

With citadel_camera_hero_fov in the console, after you enable the dev console. F7 opens it.

What is the default?

The community raw convar reference lists 90. Recheck the reference after patches; it is not a promise about your current mode.

Is lowering FOV allowed?

Valve has not published a rule on FOV binds. Stick to the documented console variable, and do not treat a community bind as Valve approval for matchmaking.

Sources

Checked 2026-10-29. Volatile numbers are labelled as estimates when they come from a tracker rather than Valve.