Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Format:CASC (Content Addressable Storage Container)

From ReverseEngineering.wiki
Format
Developer Blizzard Entertainment
Uses Library:CascLib
Magic BLTE (data frames), 'EN' encoding, 'DL' download, 'IN' install manifests
Extensions .idx, data.NNN, .index
Endianness mixed: sizes and counts in manifests and idx entries big endian
On this wiki Facts · Code · Notes · Topics

Blizzard's local game storage (Heroes of the Storm, Diablo III, Overwatch, StarCraft II/Remastered, WoW since Warlords/Legion, Warcraft III Reforged): a Data folder with bucketed .idx index files, data.NNN archives holding BLTE-encoded blobs, and ENCODING/ROOT/INSTALL/DOWNLOAD manifests that map names to content keys.

Overview

CASC replaced Format:MPQ (MoPaQ) in Blizzard games. Files are not found by path but by hashes: a name (or file id) goes through the game-specific ROOT manifest to a 16-byte content key (CKey, MD5 of the file), the ENCODING manifest maps the CKey to one or more encoded keys (EKey, a trimmed MD5 of the BLTE header), and the local .idx files map the first 9 bytes of the EKey to a (data file, offset, size) triple. The same scheme (TACT) is used on Blizzard's CDN, where archives are listed by .index files. Structures below are from CascLib src/CascStructs.h (commit 38a3466), which cites wowdev.wiki (TACT, CASC pages) as its source.

Local layout

  • Data/data/ holds data.000, data.001 ... (CascLib allows up to 0x1000 data files) and 16 bucket index files named <bucket 2 hex digits><version 8 hex digits>.idx (printf %02x%08x.idx). The bucket index is also stored inside each file.
  • .build.info and Data/config/ hold the build and CDN configs (text, naming the root, encoding, install and download keys). Unverified: exact file names, not read here.

Index files (.idx)

Header version 1 (revision 0x05) and version 2 (revision 0x07, original name tact::KeyMappingTable::DiskFileHeader) carry: bucket index, SpanSizeBytes (length of the size field), SpanOffsetBytes (length of the offset field), KeyBytes (9) and SegmentBits (how many bits of the offset field are the offset inside a data file; the rest is the data file number), MaxFileOffset (size of one data segment). Entries are 18 bytes: 9-byte EKey, 5-byte big-endian combined data-file number and offset, 4-byte big-endian encoded size. Header and entry blocks are guarded by a size and a Jenkins hash.

BLTE and data files

Each blob in a data file begins with a local header (EKey in reverse byte order, encoded size as little endian, Jenkins hash, checksum; the BLTE signature follows 0x1E bytes after the start), then BLTE (0x45544C42), a big-endian header size, and if that is non-zero 0x0F, a 24-bit frame count and one 24-byte record per frame (encoded size, content size, MD5 of the encoded frame). Each frame starts with an encoding letter; CascLib's reader handles N (stored), Z (zlib) and E (encrypted), and does not support F (recursive frames). Other TACT documentation lists LZ4 frames as well (unverified here).

Manifests

ENCODING ('EN', version 1): header with CKey/EKey lengths (usually 16), page sizes in KB and page counts (big endian), an ESpec string block, then pages of CKey entries (EKey count, 4-byte content size, CKey, EKey). DOWNLOAD ('DL') lists EKeys with a 5-byte size and priority; INSTALL ('IN') lists tags and files. ROOT differs per game: CascLib has one reader per variant (WoW, Diablo III, Overwatch, MNDX for StarCraft II / Heroes, TVFS for newer titles, plain text, install).

Tools

Library:CascLib reads local storages.

Code & repositories

  • https://github.com/ladislav-zezula/CascLib @ 38a34665624b8775bb875274b36191b21c38d97b · license: MIT
    CASC storage reader (MIT); src/CascStructs.h holds idx, ENCODING, DOWNLOAD, INSTALL and BLTE structures
    Tested on: source read, not run: source reading only · checked 2026-10-18; last activity 2026-09-25

Pitfalls

  • Mixed endianness: manifests and idx entries are big endian, some local headers little endian.
  • Names are usually not stored; many titles need a community listfile to map file ids to paths.
  • Encrypted frames need a key by name that the game ships or downloads separately.