Ladik’s MPQ Editor

About Ladik’s MPQ Editor

Classic Diablo II and Lord of Destruction keep their data in MPQ archives, the format Blizzard introduced with the first Diablo and named MoPaQ after its designer, Mike O’Brien. Ladik’s MPQ Editor, written by Ladislav Zezula, is the tool most modders use to work with those archives. As a free Diablo 2 MPQ editor it can browse an archive like a folder, extract its contents, add or replace files and build new archives, which covers nearly everything a classic mod needs.

What the tool is used for in classic modding

The game’s art, sounds, maps, strings and data tables are spread across several archives in the installation folder, with a patch archive that overrides the others. Mods change the game by supplying altered versions of those files. To make one, a modder first extracts the original tables or graphics, edits them with other tools and then either packs the results into a patch archive or loads them as loose files. The program handles the first and last steps of that cycle and is equally useful for simply looking at how the game is put together.

How to open MPQ files and extract data

To open MPQ files, start the program and pick an archive from the Diablo II folder. Older archives, including those of Diablo II, do not store the names of their own files, so the program needs a listfile to show a readable folder tree; the official site offers a listfile package for this purpose, and without it many entries appear as numbered unknown files. Once the tree is visible, select files or whole folders and extract them with their paths preserved. For table editing, the usual target is the excel folder inside the global data directory, which holds the tab-separated text tables that define items, monsters, skills and levels.

Editing and building archives

Files can be added, replaced, renamed and deleted inside an existing archive, and a new archive can be created from scratch or from a folder on disk. A merged mode opens several archives together in the same priority order the game uses, so you see the final version of each file after patches are applied, which is the easiest way to be sure you are editing the copy the game actually loads. A built-in console accepts script commands for repeatable builds, which is handy when a mod is repacked many times during development. After heavy editing, an archive can be compacted to remove unused space.

Supported games and systems

According to the official page, the program supports archives from Diablo I through Diablo III, so it also serves Warcraft III, StarCraft and other Blizzard titles of that era. Builds are offered in English, Chinese, Russian and Polish, each containing 32-bit and 64-bit versions, and the program runs on Windows NT 4.0 or newer as well as under ReactOS and Wine. The changes for each release are recorded in a history file included with the program. It is built on StormLib, the author’s open-source library under the MIT licence, which was still receiving commits in September 2026.

Working safely

Always copy an archive before changing it, and never edit the originals in a game folder you also use for Battle.net; modified archives belong in a separate installation or inside a mod manager such as D2SE. Many modders avoid repacking during development altogether by running the game with loose files and only building the final archive for release. Close the game before saving changes, because it keeps its archives open while running. If a rebuilt archive makes the game crash at start, restoring the backup is faster than hunting for the damaged entry.

Companion tools

The program moves files in and out of archives but does not edit their contents. Tables are easier to change in AFJ Sheet Editor, string tables in AFJ tbl Editor and map files in Win_DS1Edit. Mods that add features through code often rely on PlugY as well. Diablo II: Resurrected no longer uses this format; its data sits in a CASC storage, which is read with CascView from the same author.

Limitations

There is no preview or editing for the game’s own graphic and table formats, so it is only one part of a modding toolkit. A listfile is needed for comfortable work with Diablo II archives. The interface is functional rather than friendly, and the official documentation is brief. It is a Windows program, although it is reported to run under Wine.

Who should use it

It is meant for classic Diablo II and LoD modders, for players who want to inspect or extract original game files and for anyone repairing or customising an old mod. Players who only install finished mods usually never need to open an archive themselves, and Resurrected modders need a CASC tool instead.

D2 Horadric editorial view

This is the reference tool for the archive format of classic Diablo II: free, small, dependable and written by the author of the library that much of the Blizzard modding scene relies on. Its plain interface, the need for a separate listfile and the lack of built-in editors for game formats keep it in the middle of our scale, but no classic modding setup is complete without it.