Archives

The .meaf archives and IoStore containers a cooked game reads, how a packaged game mounts them, and the MowoIoStore tool.

Last updated Oct 26, 2026Edit this pageVersion 1.0.0

A cooked game reads its content from archives, never from loose files. The cook packs .meaf archives (Mowo Engine Archive Format); packaging can convert them into IoStore containers. Both mount into the same virtual file system, so nothing above it knows which form a pak has.

How the game finds content

Assets are never addressed by absolute disk path. A level stores a project-relative path such as Content/Props/Crate.mesh, and the virtual file system resolves it against a stack of mounts VFS. The highest-priority mount that holds the key wins; equal priorities answer in mount order.

MountPriorityPresent in
DLC paks210A packaged game with DLC installed
Patch paks205A packaged game with patches; a later patch wins a key
Game content paks, at the root200A packaged or cooked game
The project's Content/ folder, at Content150The editor
Engine content, at Content100Always: EngineContent.meaf or the engine pak
Bundled derived data1A packaged game with baked reflection probes
Loose fileslowestA fallback for keys no archive holds

Game content mounts at the root because the cook prefixes every key with Content/ (or Plugins/<Name>/ for plugin content). An archive key reads exactly like the reference a level stores, so a shipped game needs no path rewriting.

Paks in a packaged game

mbt package stages archives in the package's Content/Paks folder. Their file names are opaque hashes; each archive describes itself in a reserved __pak.mdf entry: its kind (engine, shaders, content or patch), its mount point, and its order within the kind, which is a content chunk's id or a patch's sequence. At startup the game scans the folder and mounts each pak by its descriptor.

The .meaf archive

A .meaf is a flat, hash-indexed archive, currently version 8:

  • Compression per entry. zstd (the default) or LZ4. Entries of 256 KiB or more are block-compressed, so a range read decodes only the blocks it touches. An entry that does not shrink, such as an already compressed texture or video, is stored as is. Small text entries of one type can share a trained zstd dictionary.
  • Encryption. XChaCha20 over the table of contents and entry payloads, with the key looked up by the header's key id in FMeafKeyRing. The header stays plaintext.
  • Signing. EdDSA over BLAKE2b covers the header, the table of contents and every payload byte. A signed archive checks each data block the first time a read touches it, so mounting does not hash the whole pak.
  • Open order. Entries can be laid out in the order a play session first read them, from Config/OpenOrder.txt, so startup reads are contiguous. mbt package --promote-open-order copies a recording made with MowoGame --record-open-order over that file.

mbt package encrypts and signs the content paks with the keys in Config/DefaultCrypto.ini; a release package refuses to build without them unless you pass --unprotected. See Shipping for keys and packaging, and Cooking for the cook's --meaf-encrypt-key and --meaf-sign-key.

IoStore containers

An IoStore container splits an archive's content into two files:

  • <name>.mutoc, the table of contents: one row per chunk and per compression block. It is the only file read at mount.
  • <name>.mucas, the container: every chunk cut into fixed-size blocks (64 KiB by default), each compressed on its own and read on demand.
.meaf archiveIoStore container
Partial readsBlock-compressed only for entries of 256 KiB or moreEvery chunk is block-compressed
Identical filesStored twiceShare their blocks
Rebuilds of unchanged contentSame bytesSame bytes, block by block, so a content-addressed patcher such as Steam's depot chunker ships only what changed
PatchesA patch pak of whole changed entriesA patch container of only the chunks whose content changed

A container takes the same encryption and signing as a .meaf. With a signing key registered, an unsigned container or one signed by another key does not mount.

To package with containers, pass --iostore, or set ioStore=true under [packaging] in Config/Packaging.ini:

Shell
./mbt.cmd package -c release --iostore

After the paks are staged, the packager converts each one into a container and deletes the archive. When both forms of one pak sit side by side, the container wins.

MowoIoStore

MowoIoStore creates and inspects containers. Build it with ./mbt.cmd build -t MowoIoStore.

Shell
MowoIoStore create --from Content.meaf --out Paks/Content
MowoIoStore create --from NewContent.meaf --out Paks/Patch1 --patch-base Shipped/Content.mutoc
MowoIoStore list Paks/Content.mutoc
MowoIoStore info Paks/Content.mutoc
MowoIoStore verify Paks/Content.mutoc
MowoIoStore extract Paks/Content.mutoc -o Extracted/
MowoIoStore diff Old/Content.mutoc New/Content.mutoc
Option of createMeaning
--from <archive or folder>, --out <path>Source and output
--block-size <n>Compression block size in bytes (default 65536)
--compression zstd|lz4|noneBlock codec (default zstd); a block that does not shrink is stored
--encrypt-key <file>, --key-id <n>, --sign-key <file>Encrypt and sign
--order-file <file>Paths laid out first, one per line (default: the archive's open order)
--patch-base <file>Write only the chunks whose content differs from this container

diff reports the chunks added, changed, removed and unchanged, and how large a patch container would be.

Engine sources

This page describes behavior implemented in these files of the engine repository, checked against commit 7f8f31f8d.

  • Engine/Source/Runtime/Filesystem/Public/Filesystem/MEAFFormat.h
  • Engine/Source/Runtime/Filesystem/Public/Filesystem/MEAFFileSystem.h
  • Engine/Source/Runtime/Filesystem/Public/Filesystem/MeafKeyRing.h
  • Engine/Source/Runtime/Filesystem/Public/Filesystem/IoStoreFormat.h
  • Engine/Source/Runtime/Filesystem/Public/Filesystem/IoStoreFileSystem.h
  • Engine/Source/Runtime/Filesystem/Public/Filesystem/PackagePaks.h
  • Engine/Source/Runtime/Filesystem/Public/Filesystem/VFS.h

Page feedback

Was this page helpful?