TF2 sv_pure Whitelist Builder

sv_pure controls which client-side files (HUDs, sounds, models) are allowed — separate from the weapon whitelist. Use sv_pure 1 with a custom whitelist to allow community HUDs and hit sounds while blocking unauthorized model edits.

sv_pure Level

Whitelist Path Rules

any — allow any client file at this path (custom HUDs, sounds).
trusted_source — only allow files from Valve's signed paks (blocks custom models at this path).

sound\ui\...

resource\ui\...

materials\vgui\logos\...

materials\temp\...

models\player\...

models\weapons\...

Quick-add common paths:

Generated Config

// ─── sv_pure Setting (add to server.cfg) ───────────────────
sv_pure 1

// ============================================================
// pure_server_whitelist.txt
// Save as: tf/cfg/pure_server_whitelist.txt
// ============================================================

"whitelist"
{
    "sound\ui\..."    "any"
    "resource\ui\..."    "any"
    "materials\vgui\logos\..."    "any"
    "materials\temp\..."    "any"
    "models\player\..."    "trusted_source"
    "models\weapons\..."    "trusted_source"
}

Save as tf/cfg/pure_server_whitelist.txt. Changing sv_pure requires a map restart to take effect.

sv_pure Level Reference

Level	Behavior	Custom HUDs?
-1	No file restrictions at all	Yes
0	Mild default restrictions	Yes (mostly)
1	Whitelist rules apply (pure_server_whitelist.txt)	Configurable
2	Full lockdown — ignore all client custom files	No

Private Team Fortress 2 hosting

Run your own Team Fortress 2 server.

Rent a private Team Fortress 2 server on real hardware — full control-panel access, your mods, your configs, your rules. It's your server; run it your way.

Rent a Team Fortress 2 server Real hardware · Full control panel · 98% SLA

Don't want to run it yourself? Our managed services & consulting team will set it up and keep it running for you — game servers, Windows, Linux, and cloud, from 10+ years of MSP work.