How to Disable VAC on a CS2 Server

Disabling VAC (Valve Anti-Cheat) on your own Counter-Strike 2 server lets you run mods, test custom gameplay, or host private matches without the anti-cheat interfering. This guide walks you through the exact commands and configuration changes needed, assuming you have basic server access (either through a hosting panel or direct file access).

What You’ll Need

• Access to your CS2 server’s command line or configuration files (e.g., via SSH, FTP, or a game panel like Pterodactyl).
• Administrator privileges on the server (you need to be able to edit files or run console commands).
• Basic familiarity with text editing and restarting your server.

Step-by-Step

1. Locate your server’s startup parameters. This is usually in a file called server.cfg, autoexec.cfg, or in the launch options set by your hosting provider. If you use a control panel, look for a “Startup” or “Command Line” section.
2. Add the -insecure launch option. This is the primary way to disable VAC. In your launch parameters (the line that starts the server executable, e.g., srcds.exe or cs2), append -insecure at the end. For example:
   ./cs2 -dedicated -game csgo -insecure
   If you’re using a config file, you can also add sv_cheats 1 to allow cheats, but -insecure is what actually turns off VAC.
3. Set sv_cheats 1 in your server.cfg. While not strictly required to disable VAC, this allows you to use cheat commands (like sv_infinite_ammo) for testing. Add this line to your server.cfg file:
   sv_cheats 1
4. Restart your server. After making changes, restart the server process. This ensures the new launch options take effect.
5. Verify VAC is off. Once the server is back up, open the server console (or check your panel’s console output). Look for a line that says something like “VAC secure mode is disabled” or “[VAC] VAC is disabled.” If you don’t see it, try connecting to the server and typing status in the console; it should show secure as no.

Common Mistakes

• Only setting sv_cheats 1 without -insecure. This is the most common error. sv_cheats 1 allows cheat commands, but VAC remains active and can still ban players for using them. You must use -insecure to disable VAC entirely.
• Putting -insecure in the wrong place. The launch option must be in the server’s startup command line, not inside a config file. Config files are read after the server starts, and launch options are processed before.
• Forgetting to restart the server. Changes to launch parameters only take effect after a full restart. A map change or a soft reload won’t apply them.
• Using a hosting provider that doesn’t allow custom launch options. Some managed hosts lock startup parameters. If you can’t edit them, you may need to switch to a VPS or dedicated server.

Tips

• Use a separate server for testing. Disabling VAC means players won’t be protected from cheaters. Only do this on a private server for friends or for development, never on a public competitive server.
• Keep a backup of your original config. Before making changes, copy your server.cfg and note your original launch options so you can easily revert.
• If you’re using a game panel, look for a checkbox. Many panels (like Pterodactyl) have a dedicated “Insecure” or “Disable VAC” toggle in the startup settings. This is easier and less error-prone than manual editing.
• Combine with sv_lan 1 if you only want LAN play. This further isolates the server from the internet, reducing the risk of unwanted connections.

Troubleshooting

• VAC still shows as secure after restart. Double-check that -insecure is actually in the command line. If you’re using a panel, confirm the toggle is on. Also, make sure you’re looking at the correct server process (if you have multiple instances).
• Server won’t start after adding -insecure. This can happen if the option is misspelled or if your server build doesn’t support it. Verify the exact syntax for your version. Also, check that you didn’t accidentally remove other required parameters.
• Players can’t connect. If you set sv_cheats 1, some clients may show a warning, but they can still join. If they can’t, ensure your server is not password-protected or that the password is correct. Also, check your firewall settings.
• Console doesn’t show the VAC status line. Not all server builds print this clearly. Instead, connect to the server and type status in the client console. Look for the “secure” field; it should say “no”.

Frequently Asked Questions

Will disabling VAC get me banned from Steam?

No. Running a private server with VAC disabled is allowed by Valve. However, you must not use it to host public matches where players expect a fair environment, and you cannot use it to cheat on official Valve servers.

Can I re-enable VAC without reinstalling the server?

Yes. Simply remove the -insecure launch option and restart the server. VAC will be re-enabled automatically.

Does -insecure affect the game’s performance?

No. It only disables the anti-cheat module. Performance is generally unaffected, though some cheat commands may increase server load if used excessively.

Why can’t I use sv_cheats 1 on a VAC-secure server?

Because Valve’s anti-cheat flags any server that allows cheats. Setting sv_cheats 1 on a secure server will cause players to be kicked or banned. Disabling VAC first is the only safe way to use cheat commands.

Is there a way to disable VAC only for specific players?

No. VAC is a server-wide setting. You cannot selectively disable it for individual players. You would need to run a separate insecure server for those players.

Do I need to own CS2 to host a server?

Yes, you need a valid CS2 license to run a dedicated server. However, the server itself does not require a separate purchase; it uses the same game files.

Related

• Word Show or Hide Formatting Marks
• Phantom Blade Zero: Is It a Soulslike?
• 1Password vs LastPass: Which Password Manager Is Better?