What is the W3X file format?
A .w3x file is a custom map for Warcraft III: The Frozen Throne, the 2003 expansion by Blizzard Entertainment. The format is a compound binary container: a 512-byte map header beginning with the HM3W signature (hex 48 4D 33 57) is prepended to a standard MPQ archive, the same packaging format used throughout Blizzard's game catalog.
Inside the embedded MPQ, the map stores all its component subfiles:
war3map.w3i- map metadata (name, author, description, player slots)war3map.j- JASS game logic scriptwar3map.wts- string translation table- Terrain, unit placement, trigger data, and an optional preview image
The header byte at offset 4 distinguishes classic (0x12) from Frozen Throne / Reforged (0x1A) format versions. .w3x differs from the older .w3m format (Reign of Chaos) only in that it enables Frozen Throne-specific flags such as extra tilesets and two additional towns. Both share identical MPQ internals.
Individual files inside the MPQ may be compressed with DEFLATE, zlib, BZip2, or PKWARE Implode, and optionally encrypted per-block. Official Blizzard maps append a 260-byte strong digital signature after the MPQ end. Map sizes range from 8×8 to 480×480 playable tiles.
With Warcraft III: Reforged in 2020, Blizzard updated the extended object and trigger data formats. Despite changes to how maps are hosted on Battle.net, .w3x files continue to circulate and be played directly by the community.
Security & safety
RISK: MEDIUMW3X maps can contain JASS scripts that execute arbitrary Warcraft III Lua/JASS code within the game sandbox. Malicious maps could theoretically exploit in-game scripting vulnerabilities. Only download maps from reputable community sites (Hive Workshop, epicwar.com). A map cannot execute code outside the Warcraft III process.
Format details
in a nutshellPrograms that open W3X files
Technical details
deep spec| Container structure | Custom 512-byte W3X header + embedded MPQ (MoPaQ) archive |
| Header magic | HM3W (hex 48 4D 33 57) at offset 0; MPQ magic 4D 50 51 1A at offset 512 |
| Byte order | Little-endian |
| Compression | DEFLATE, zlib, BZip2, PKWARE Implode (per MPQ block, per-sector) |
| Encryption | Optional per-block MPQ encryption for individual subfiles |
| Map format version byte | Offset 4: 0x12 = classic Reign of Chaos; 0x1A = Frozen Throne / Reforged |
| Playable map size range | 8×8 to 480×480 playable tiles |
| JASS script subfile | war3map.j - game logic written in the JASS scripting language |
| Map info subfile | war3map.w3i - stores name, author, player slots, and description |
| Typical file size | 1 MB - 100 MB; official campaign maps may exceed 100 MB |
| Digital signature | Optional 260-byte strong digital signature appended after MPQ archive end |
| MPQ hash table capacity | Up to 65,535 (2^16 − 1) file entries per embedded archive |
| Distinction from .w3m | Enables Frozen Throne-specific flags; .w3m is Reign of Chaos only |
| Associated OS | Windows; macOS (Warcraft III: Reforged) |
| Released | 2003 (Warcraft III: The Frozen Throne expansion) |
| Latest version | Reforged map format (2020, with extended trigger/object data) |
| Specification | 867380699.github.io |
W3X conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about W3X files.