CS2 Autoexec Generator

By Josh Lingenfelter

Build a custom autoexec.cfg tailored to your priorities. Choose a preset or tweak individual settings, then download the ready-to-use config file.

// ═══════════════════════════════════════════════════
// CS2 Autoexec — Generated by CSDB.gg
// ═══════════════════════════════════════════════════

// ── Performance ──────────────────────────────────
fps_max 0
cl_showfps 1
r_drawtracers_firstperson 1

// ── Telemetry HUD (CS2 replacement for net_graph) ─
// 0 = never, 1 = show when conditions are poor, 2 = always show
cl_hud_telemetry_ping_show 2
cl_hud_telemetry_net_misdelivery_show 1

// ── Audio ────────────────────────────────────────
volume 0.5

// ── Viewmodel ───────────────────────────────────
viewmodel_presetpos 1

// ── HUD ─────────────────────────────────────────
hud_scaling 0.85
cl_hud_color 0

// ── Save settings ───────────────────────────────
host_writeconfig

// Generated at csdb.gg/autoexec-generator

What Each Setting Does

fps_max caps your frame rate. Setting it to 0 (unlimited) is generally recommended if your PC can maintain high framerates. Some players cap it slightly above their monitor refresh rate (e.g., fps_max 300 on a 240Hz monitor) to reduce power consumption and heat.

Telemetry HUD(the cl_hud_telemetry_* commands) is CS2's replacement for CS:GO's net_graph, which no longer exists. cl_hud_telemetry_ping_show controls the on-screen ping readout and cl_hud_telemetry_net_misdelivery_show surfaces packet problems — each takes 0 (never), 1 (only when conditions are poor), or 2 (always show). Note that CS:GO's manual network tuning commands (rate, cl_interp_ratio, cl_updaterate, cl_cmdrate) were removed in CS2; the sub-tick engine manages this itself.

viewmodel_presetpos switches between the three built-in weapon positions (1 Desktop, 2 Couch, 3 Classic), and hud_scaling resizes the HUD — most competitive players shrink it slightly to free up screen space.

Frequently Asked Questions

What is an autoexec.cfg in CS2?

An autoexec.cfg is a configuration file that automatically executes console commands every time CS2 launches. It ensures your preferred settings are always applied, even if the game resets them. Place it in your CS2 cfg folder.

Where do I put my autoexec.cfg?

Place autoexec.cfg in: Steam/steamapps/common/Counter-Strike Global Offensive/game/csgo/cfg/. Create the file if it doesn't exist. The file must be named exactly "autoexec.cfg" and end with the command "host_writeconfig".

Will an autoexec improve my FPS?

Only slightly. An autoexec is mainly about consistency, not raw frames — commands like r_drawtracers_firstperson 0 remove minor visual work, and fps_max controls your frame cap. The big FPS levers in CS2 are your video settings (resolution, shadows, MSAA) and hardware, not console commands.

Is using an autoexec allowed in competitive?

Absolutely. Autoexec files only adjust client-side settings that you could change manually through the console or settings menu. They do not provide any unfair advantage and are used by virtually every professional player.

What commands should every autoexec have?

Essential commands include: your sensitivity and crosshair settings, fps_max, viewmodel_presetpos, cl_hud_telemetry_ping_show 2 (the CS2 replacement for net_graph info), any binds you rely on, and host_writeconfig at the end to save changes. CS:GO staples like rate, cl_interp_ratio, and cl_updaterate were removed in CS2.