THE FILE FIELD GUIDE
.wad

WAD Game Data

Games & Saves

DOOM WAD files bundle maps, graphics, audio and other resources. Base IWAD and add-on PWAD serve different roles; an add-on may require a compatible base game. Other products also use WAD, so identify the origin before selecting an engine.

What it is used for
Game maps, graphics, audio and related resources
What the file contains
Producer-dependent
All sections, questions and sources

Content reviewed: · Editor:Kai

Opening steps

Choose your environment or purpose to see its steps.

Identify use and game

Not every WAD uses DOOM’s format.

  1. Identify provider, game/device and version.
  2. For DOOM, distinguish base and add-on data.
  3. Check supported engine and required base data.
Use a DOOM-format add-on

Use authorized base assets and a compatible engine.

  1. Identify the required base WAD.
  2. Select a copy through the engine’s add-on workflow.
  3. Inspect maps, assets and load order.
Inspect the contents

Edit only a backup copy.

  1. Inspect lump entries with a compatible tool.
  2. Inspect map names, media and dependencies.
  3. Save separately and verify with the intended engine.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Add-on fails: inspect required IWAD and engine compatibility.
  • Wrong graphics/text: inspect game target, resource-name conflicts and load order.
  • Cannot parse: inspect unrelated WAD formats, corruption or incomplete downloads.
  • Save incompatible: compare base/add-on data and engine version.
  • Map absent: inspect map naming and engine support.
  • Entries lost after editing: compare archive listing/output format.

Inspect/export resources with a matching WAD tool

  1. Identify IWAD/PWAD and target game; preserve a copy.
  2. Export intended resources using matching tools and verify maps/graphics/audio in the target engine.
  3. Verify maps/assets with the required base data.

Renaming to ROM/ZIP is not conversion; engine-source and game-data permissions are separate.

Lumps and map structure

Edit named entries through the intended engine’s format requirements.

Example: match a documented base IWAD and compatible engine for an add-on.

Source for these steps:id Software · DOOM — WAD loader

Engine and asset permissions differ

Use authorized base data and inspect add-on licensing independently of engine source availability.

Source for these steps:id Software · DOOM — WAD loader

Related-format differences

Related-format differences
Format / methodRoleWhat to verify
IWADDOOM base dataAuthorized original
PWADAdd-on dataBase/load order
Other WAD usesDifferent formatProducer

Handling and security

Verify provenance/base-game rights and avoid installing unknown device WAD files.

Questions and answers

Can an add-on WAD run alone?

Check required base-game data and engine support.

Does WAD always mean DOOM?

No; identify its producer.

Does an open engine make game assets free?

No; their permissions are separate.

What does IWAD versus PWAD identify?

In DOOM context they distinguish base/add-on data; still inspect engine and base requirements.

Can load order change the result?

Overlapping entries can matter; follow documented load order/version.

Format facts: name, steward and MIME type
Formal name
DOOM WAD resources / other producer-specific WAD
Steward / specification
id Software (DOOM family) / other producers
MIME type
Depends on the producer or server; an extension alone does not establish a MIME type.

Primary and official sources

  • Official documentationDOOM — WAD loader

    Original implementation recognizing IWAD/PWAD game resources.

    id Software · Link checked: