CodeWalker is to GTA map modding what a level editor is to a Source mod scene - the tool that lets you actually see what you are doing. Before CodeWalker existed, working with the RAGE engine's map files meant editing XML by hand and hoping. CodeWalker turned that into a graphical editor and the scene grew accordingly.

We keep this overview short. It exists as a glossary anchor for the dozens of articles on this site that mention CodeWalker in passing - if you're reading one of those and wondering what the tool is, this is the answer.

What CodeWalker is

CodeWalker is an open-source graphical editor for the asset files used by GTA V's RAGE engine. It can render the GTA V map directly, navigate it like a flycam, inspect individual map files, edit them, and export them back into a format the game can load.

The map data inside GTA V is stored in YMAP files - an XML-derived format that defines what objects sit at what positions, with what rotations, with what variants. YMAP, YMT and YDR are the file types that matter most for map modding. CodeWalker handles all of them, plus the tooling around them.

What CodeWalker actually lets you do

View the map. Place new objects from the existing GTA V prop library. Move and rotate existing objects. Add or replace MLO interiors. Inspect the collision and lighting data attached to each piece of map. Export edits back into a YMAP file that drops into the modded game.

What CodeWalker doesn't do, on its own, is build new 3D content. Custom buildings, interiors and assets are still authored in 3ds Max, Blender or Maya, then exported via plugins, then wired into the game with CodeWalker. The split is similar to other 3D modding workflows - authoring tool plus level editor plus packaging.

Where CodeWalker came from

CodeWalker is a community project. It is not a Rockstar tool. It started as a smaller asset viewer and grew over years into a fully-featured editor. The current version is open-source and continues to be developed.

Without naming individuals, the small group of people who maintain CodeWalker has done extraordinary work. The reverse-engineering effort behind reading and writing the RAGE engine's map formats is significant, and most of what the modern GTA 5 modding scene takes for granted depends on CodeWalker remaining maintained.

How CodeWalker fits into the wider toolchain

OpenIV handles the archive layer - opening the .rpf files Rockstar packs assets into. CodeWalker handles the map layer - reading and writing the actual world data. 3ds Max or Blender plugins handle 3D content authoring. ScriptHookV handles runtime script integration. The four pieces together are the GTA 5 modding stack.

If you wanted to learn map modding from scratch in 2024 or 2025, the recommended path was: start with OpenIV, learn the file structure, move into CodeWalker for the map editing itself, then add 3ds Max or Blender for asset authoring. That has been a stable path for several years.

What this means for GTA 6

If GTA 6's map file structure is a recognisable evolution of GTA V's, CodeWalker is well-positioned to be extended. If the format has been substantially redesigned, the editor has to be rebuilt or replaced. We don't know yet which of those is true. The question matters because the gap between 'no tool exists' and 'tool exists' is when serious map modding becomes possible.

Realistically, expect a CodeWalker successor to emerge within the first year of the GTA 6 PC release - sooner if the format is similar, later if it isn't. We cover the broader expectation question in the modding tools expectations piece.