CS2 Hammer workflow at a glance
| Stage | What the creator does | How it relates to the next step |
|---|---|---|
| Set up tools | Enable and download Counter-Strike 2 Workshop Tools through the game’s supported tool flow. | Opens the CS2/Source 2 authoring environment. |
| Build the level | Create playable spaces, routes, surfaces, lighting and gameplay entities in Hammer. | Geometry and entities establish how the map looks and functions. |
| Compile and inspect | Use the CS2 authoring tools to build the map and review errors or visual results. | A compiled version can be tested in the game environment. |
| Playtest and revise | Check movement, visibility, collision, spawns, objectives and performance. | Find issues that the editor view alone cannot reveal. |
| Publish | Prepare the supported Workshop submission and metadata. | Publishing makes a community map available; it does not make it an official matchmaking map. |
What Hammer does in Counter-Strike 2
Hammer is the level editor included with Counter-Strike 2 Workshop Tools. A map creator uses it to design the playable environment and arrange the objects and game logic that make a level work. A CS2 map is more than a visual scene: routes, collision, spawn locations, objective areas, lighting, materials and readable silhouettes all affect whether players can understand and use the space.
Hammer belongs to the Source 2 authoring toolchain. It is not the in-match Buy Menu, a console command or a separate game mode. The Workshop Tools package supplies related utilities for authoring and publishing, while Hammer concentrates on constructing and inspecting map content. For a broader overview of the tool package see Workshop Tools; for playing and distributing a finished map see Workshop Maps.
The CS2 version should be treated as its own editor workflow. Older Hammer tools and map files made for other Counter-Strike games can use different formats, assets and engine behavior. This article describes CS2 map creation and does not use an unrelated same-name legacy Hammer weapon entry as its source.
Designing routes and objectives
A creator begins by shaping spaces players can move through and understand. Map geometry defines corridors, rooms, elevations, entrances, cover and sightlines. The layout needs to support the chosen CS2 scenario: Bomb Defusal maps require functional bombsites and routes for both teams, while Hostage Rescue uses hostage locations and rescue paths. Other supported modes can require their own spawn logic, boundaries or objective elements.
Player collision and grenade collision both need to match what the map appears to show. A railing that looks solid but allows a grenade through, a visible gap that players cannot traverse, or a corner that catches movement can make a map feel inconsistent. Test movement and utility from both teams’ likely routes. Dated CS2 map updates frequently adjust clipping and grenade interactions, showing why map geometry should be inspected in play rather than judged only from a top-down editor view.
Spawn points and objective entities are part of gameplay setup, not decorative props. Their positions determine where players enter, what areas they can reach first and whether the map’s intended mode can start correctly. A creator should check that both sides can move through the level, that objectives are placed and named as intended, and that the map has no unintended shortcuts, trapped locations or unusable areas.
Map readability is as important as physical layout. Surface materials, lighting, contrast, signs and landmarks help players identify routes and communicate positions. A visually detailed room can still be hard to play if important edges blend into the background or if the player models disappear against the environment. Use repeated playtests to find confusing silhouettes and sightlines, then adjust lighting, material treatment or prop placement.
Lighting, materials and the Source 2 workflow
Hammer lets creators inspect the map while they work with materials and lighting. The June 6, 2023 CS2 Workshop Tools notes highlighted GPU-accelerated ray tracing in Hammer for previewing and baking lighting. Valve stated that it could significantly speed up compilation and initially listed a ray-tracing-capable GPU as a requirement for full functionality. That is a dated launch-era tool note; current hardware requirements should be checked against the installed Workshop Tools package.
Lighting affects both atmosphere and competitive readability. The creator needs to see how surfaces, shadows and player silhouettes appear from common approaches, not only from an editor camera. A light source can make a landmark easy to recognize while also creating glare or a dark patch that hides an opponent. Review multiple viewing angles and graphics conditions when practical, and adjust the map until important routes remain legible.
Materials and props provide surface appearance and environmental detail. Their visual treatment should support navigation rather than obscure the edge of a doorway, a usable ledge or a player model. The Source 2 authoring environment also includes assets and prefabs that can help creators work with common map elements. Reusing a suitable prefab can establish a known setup, but creators still need to confirm its configuration matches the intended map and mode.
The full workflow includes more than pressing a build button. A creator saves source work, compiles or builds the map using the supplied tools, reads diagnostics, launches the result for inspection and iterates. The Workshop Tools package has received updates to editor controls and tools over time, so button names, requirements and workflow details should be verified in the installed CS2 version rather than copied from a guide for another Source game.
Testing a Hammer map
A successful editor build does not prove that the map is ready for play. Load the map in an appropriate CS2 testing session and check both teams’ routes, spawn behavior, collisions, visibility, objective entities and grenade trajectories. Try common jumps and movement paths, inspect places where players can become stuck, and look for locations where a grenade bounces or passes through geometry unexpectedly.
Playtesting should include the intended game mode. A Bomb Defusal map needs a functional plant-and-defuse flow and enough routes for attackers and defenders to make meaningful decisions. A Wingman layout has a smaller team and a different scale; a Hostage Rescue map uses distinct objectives. Map entities and their configuration need to match the scenario that the creator plans to publish.
Iterate on what testers can describe. Ask where they became lost, which sightline felt unfair, whether a route was unreadable and whether the objective was clear. Then change one part of the design and retest the effect. A workshop map can be updated after feedback, and community-server or local testing may reveal issues that are not apparent in an editor viewport.
Performance and visual quality also need review. Dense props, expensive lighting or complicated visibility can affect how smoothly the level runs. Hammer’s preview is useful, but the finished map should be tested in the game client on realistic settings. Keep an eye on frame pacing, load time, sound occlusion and visibility in addition to whether the map compiles.
Publishing and official map status
Hammer is used to create and prepare map content; the Workshop publishing workflow makes a finished community map available for players to discover. Valve announced on November 2, 2023 that the CS2 Maps Workshop was open for map uploads and that community servers could host Workshop maps. Workshop submission and playability are separate from being selected for official matchmaking.
An uploaded map remains community content unless Valve later adopts or integrates it into official CS2 modes. A map’s appearance in a Workshop listing does not establish that it is in Premier, Competitive, Casual or another queue. The Map Rotations entry records dated pool changes, while each map page describes its scenario, layout and Counter-Strike 2 history.
Creators should prepare a clear map name, mode, screenshots and description, then use the supported Workshop publisher and submission flow. The tools can help package and upload the work, but do not guarantee that it will be selected for official play. If Valve later updates an official map, the changes belong in that map’s dated history as well as the relevant CS2 patch record.
CS2 version and compatibility boundaries
This article covers the Hammer editor supplied for Counter-Strike 2 Workshop Tools. The June 6, 2023 Limited Test update introduced the tools and described ray-traced lighting preview and baking. The November 2, 2023 update enabled map uploads to the Steam Workshop and community-server hosting. These dates describe the CS2 toolchain’s launch and distribution milestones, not every later interface revision.
Hammer versions are tied to an engine and game toolchain. Instructions, assets, entity lists, lighting workflows and map files from Global Offensive or earlier Counter-Strike titles may not work as written in CS2. Do not assume that a legacy map file is directly compatible or that an old editor screenshot shows the current Source 2 interface.
The authoring process, available Workshop features and hardware requirements can change with CS2 updates. Use the Workshop Tools included for the current game version and consult the dated Patch Archive for documented changes. Hammer helps build maps; it does not itself determine official map-pool membership or matchmaking availability.
GPU-accelerated lighting workflow (June 6, 2023)
The June 6, 2023 Counter-Strike 2 Workshop Tools update made Hammer use GPU-accelerated ray tracing to preview and bake lighting for CS2 maps. Valve said this substantially accelerated compile times, while requiring a ray-tracing-capable GPU for Hammer to be fully functional. The announcement listed an Nvidia 2060 Ti with 6 GB or AMD 6600 XT as minimum examples, and Nvidia 2080 Ti or AMD 6800 XT and higher as recommended. These are hardware requirements stated for that dated Limited Test tools release, not a fresh assessment of current hardware support.
Asset-compiler paths with spaces (June 9, 2023)
A June 9, 2023 Counter-Strike 2 Limited Test fix addressed Hammer’s asset-compiler behavior in directories with spaces in their paths, where stray files could be created. The release note does not identify the files or imply that every compile in such a directory failed.