Main parts of the CS2 Workshop Tools workflow
| Component or stage | Purpose | Typical use |
|---|---|---|
| Counter-Strike 2 Authoring Tools | Installs the CS2-specific authoring environment through the game’s tools options | Start from current CS2 assets, examples and utilities |
| Hammer | Edits and assembles playable map environments | Build layout, geometry, lighting and map entities |
| Compile utilities | Process authored map files into game-loadable content | Build a testable map version |
| Face Poser and Prefabs | Provide supporting authoring features and reusable examples | Create or inspect supported scene content and learn from samples |
| Workshop Map Publisher | Packages and submits a map for Workshop distribution | Publish revisions so players can subscribe and test |
| Workshop Item Editor / Item Publisher | Previews and submits supported cosmetic items using the CS2 tools | Inspect finishes and prepare supported item submissions |
What the Workshop Tools are for
The CS2 Workshop Tools are the creator-facing tools for making Counter-Strike 2 community content. Their most visible role is map production: a creator builds a map, compiles it into a form CS2 can load, tests it in the game and publishes it through the Workshop workflow. Other supported tools let creators preview and prepare cosmetic submissions such as weapon finishes or stickers.
This toolset is separate from the player-facing Steam Workshop browser. The Workshop browser helps players discover and subscribe to published content; Workshop Tools are used by creators to author and prepare that content. Installing the tools does not automatically subscribe to a map, publish a project or add custom content to official matchmaking.
Valve’s CS2 Workshop FAQ describes the authoring package as including an updated Source level editor, Hammer, command-line compiling utilities, an updated Face Poser, the Workshop Map Publisher, and tutorial maps and Prefabs. Valve also distributes Counter-Strike Authoring Tools and resources through its Workshop Resources page. Exact names and UI locations may change as the tools are updated, so use the current CS2 tools installation interface.
Installing and launching the tools
The CS2 Authoring Tools are provided through the game’s tools options. After installation, launch the Workshop Tools environment from the available CS2 tool entry rather than attempting to use an editor or compiler package for another Source game. The project assets, material systems and file formats should match the current Counter-Strike 2 tool version.
A creator should keep the game and authoring tools aligned and review current documentation when an update changes the editor or publishing flow. A map can fail to compile or load when it depends on stale assets, invalid configuration or files intended for another game. Tool troubleshooting should begin with the exact CS2 tool version, build output and the affected project files. Community discussions and Valve’s Workshop resources provide a place to compare errors and find current guidance.
Workshop Tools are a sizeable development environment rather than a single menu command. A creator should expect to work with project folders, source files, assets and compiled output. Preserve the editable source project so maps can be revised; a compiled map or Workshop item alone may not contain everything needed to continue development.
Building a map with Hammer
Hammer is the level editor used to lay out and assemble a CS2 map. The author defines playable spaces, geometry, routes, collision, lighting and the entities needed for the intended game mode. A map should be designed around how players move, see and interact, not only how the environment looks in the editor. Spawn positions, objectives, cover, readable silhouettes and navigation all affect whether a layout plays well.
Tutorial maps and Prefabs provide examples and reusable starting points. They can help a new author understand CS2 conventions and avoid rebuilding common structures from scratch. A Prefab is a resource for the authoring process; using one does not guarantee that the finished layout is balanced, technically valid or suitable for an official mode. Authors remain responsible for testing how all components work together.
After editing, compiling utilities process the project into map content the game can load. The author then launches the map and checks geometry, lighting, visibility, collisions and gameplay behavior. If a player can become stuck, see through an unintended gap, exploit a route or encounter severe performance problems, revise and compile again. Iteration between editor and in-game test is a normal part of the workflow.
A map intended for a particular custom game mode may also need its own configuration. Valve’s Workshop FAQ describes custom settings packaged with maps to support variants such as aim maps. The map’s configuration determines which mode behavior is expected; publishing a map does not make its custom rules work in every queue or community server.
Testing and publishing a Workshop map
Test a map in CS2 before publishing it. Inspect the complete playable route, team starts, objectives, round flow and all visible or reachable surfaces. Test with multiple players when team interaction matters; a layout that seems clear in solo inspection may create unfair sightlines, spawn pressure or inaccessible areas during a match. Test the compiled version that will actually be published, not only the editor view.
When ready, use the Workshop Map Publisher in the CS2 toolset to prepare the map listing and submit the item. The Workshop listing gives the community a way to subscribe, play, rate and provide feedback. The author can revise the item as fixes are made. Subscription makes the published map available to players through the CS2 Workshop map browser, but it does not itself place the map in Premier, Competitive or a tournament.
Valve’s Counter-Strike Workshop invites community creations and may consider popular or suitable submissions for inclusion in CS2. Selection remains Valve’s decision and requires separate integration and testing. A creator should describe a submission as Workshop content until an official dated CS2 announcement confirms adoption. See Workshop Maps for the player-side subscription and play process.
Cosmetic item tools
The CS2 Workshop tool environment also supports authoring and previewing cosmetic content. Valve provides the Workshop Item Editor for viewing and editing weapon finishes in the game client, accessed through the Counter-Strike 2 Workshop Tools. The item workflow allows a creator to inspect how a finish looks on an existing weapon before submitting it. The supported item categories and technical requirements are defined by Valve’s current submission guidance.
The Workshop Item Publisher handles supported cosmetic submissions. Creating a finished texture, compiling its source and previewing it in the editor are separate steps; a pattern image by itself is not necessarily ready to submit. The finish guide explains the supported styles and asset requirements. Stickers have their own creation guidance and preview workflow. These cosmetic tools do not provide a path to add new weapons, animations or arbitrary character models unless Valve explicitly expands its supported submission types.
Submitting to the Workshop is not the same as adding an item to the game. Community publication makes an item available for feedback and review. Valve may select and integrate content through a later CS2 update, but creators should not claim official in-game availability until that occurs. Cosmetic submission also remains separate from a playable Workshop Map.
Source 2 and CS2 compatibility
Counter-Strike 2 uses Source 2, and its Workshop Tools are built for CS2’s assets and authoring pipeline. The game’s official overview describes Source 2 tools and rendering features as available to community map makers and artists. This supports iteration on CS2 content, but does not mean that every tool, asset or tutorial for a different Source game can be used unchanged.
Older Hammer releases, legacy branches and asset packages can target another engine generation or game. Opening the wrong version can yield missing resources, incompatible materials or output that CS2 cannot use. Use the Counter-Strike 2 Authoring Tools and current CS2-specific documentation when preparing a CS2 submission. The Source 2 engine and Workshop Tool environment should be understood as part of this game’s specific content pipeline.
This article covers Counter-Strike 2 Workshop Tools only. It does not document tool packages for other Valve games or reproduce legacy Source 1 instructions. When Valve updates the tool package, record the CS2 change and revise installation or publishing steps against the current interface.
September 27, 2023 Counter-Strike 2 launch update
The CS2 launch help system added contextual guides, including grayscale value ranges for alpha-channel masking and paint-by-number mask-color assignments for the current finish type. These guides help cosmetic creators prepare supported materials and understand how a mask is interpreted. Workshop Tools clients running in tool mode were also barred from connecting to VAC-secure game servers, separating authoring sessions from protected matchmaking.
Paint Kit authoring options
The August 31, 2023 Limited Test update added Item Editor enhancements for Paint Kit finishes: custom normal maps and ambient occlusion for all styles, an optional pearlescent mask, an optional standard PBR roughness texture, and custom Paint-By-Numbers masks. The latter enabled Paint-By-Number masks for the Spray-Paint style. These are material-authoring capabilities, not gameplay weapon modifiers.
Multiple team-introduction variants
The August 15, 2023 Limited Test update added Workshop Tools support for multiple team-introduction variants. This lets an authored map provide more than one team-introduction variant in the supported tool workflow. The patch note does not specify selection rules, randomization behavior or the complete authoring format. The later August 31 update added more Paint Kit material options to the CS2 Item Editor; these are separate creator-tool features.
Limited Test editing controls (July 17, 2023)
The July 17, 2023 Limited Test update enabled Undo and Redo buttons in Workshop Tools and listed additional bug fixes. The buttons let a map creator reverse or reapply recent editing actions during authoring. The notes do not enumerate the accompanying fixes, so no specific tool behavior beyond the named controls is inferred.
Hammer and item-submission fixes (June 15, 2023)
The June 15, 2023 Limited Test update fixed a freeze or hang in Hammer and improved the descriptions on the CS2 Workshop Tools convar helper page. It also corrected the aspect ratio used for Workshop submission screenshots and added the Zeus x27 to the weapon list available during Workshop submissions. These are authoring and submission workflow changes; the update does not say that Zeus finishes were newly enabled or that a particular tool command changed.
Workshop Tools introduced to the Limited Test (June 6, 2023)
Counter-Strike 2 Workshop Tools became available to Limited Test players on June 6, 2023; they could be enabled and downloaded through the in-game settings menu. The announced toolset let community contributors create weapon finishes, stickers and maps, with Hammer providing the CS2 map-editing and lighting workflow. At that time, the Steam Community Workshop did not yet support uploading CS2 maps, so tool availability and map publication were separate steps. This date marks the initial Limited Test tooling release, not the later return of public Workshop map uploads.
Weapon-finish preview model fix (June 7, 2023)
The June 7, 2023 Counter-Strike 2 Workshop Tools update fixed legacy models appearing while previewing new weapon paint finishes. The note concerns the model shown in the preview workflow, not the item model used in a live match or the appearance of a particular finish.
Asset-compiler paths with spaces (June 9, 2023)
The June 9, 2023 Workshop Tools update fixed an asset-compiler bug that created stray files when the compiler ran in directories whose paths contained spaces. The note names this path condition but does not describe the extra files or a broader compiler change.
Map compilation crash with instances (April 16, 2024)
The update fixed Workshop Tools crashing when compiling maps that contain instances. The note identifies the affected workflow—map compilation with instances—but does not specify an instance type, project setup or workaround. It is a tooling stability fix, not a change to how instances function in the game or a guarantee that every compilation failure was resolved.
Arms Race added to Workshop map submissions (May 1, 2024)
On May 1, 2024, Arms Race was added as a game mode for Workshop map submissions. This expands the mode choices available to creators submitting a community map for Counter-Strike 2. It is a Workshop authoring and submission change, not an announcement of a new official map or a change to Arms Race's match progression. The patch provides no further detail about the submission interface or approval process.
Ancient material blending example (August 14, 2025)
The August 14, 2025 CS2 update added ancient_zoo.vmap, a file containing Ancient assets and examples of the map’s material-blending options. The update also introduced blending options for ancient materials such as wetness and moss. This is a mapmaking reference and example resource, not a new playable map or a change to Ancient’s round objective. The page does not claim that the file is a tutorial for every map or material type.