Files
indd-utils/docs/format/container.md
T
aiongg ac957b0eb2 feat: read master pages and contiguous objects
Select the active master page by sequence number, read the database page
count, iterate the contiguous objects after the database pages, and
extract the XMP packet. `indd info` now prints these fields.

The layout comes from Adobe's BSD-licensed XMP Toolkit SDK and is checked
against all 352 corpus files and the fixtures. Add Adobe's BlueSquare.indd
sample (BSD) as a fixture and record the XMP Toolkit as a permitted
reference.
2026-10-06 15:34:39 +00:00

2.6 KiB
Raw Blame History

INDD container layout

Source: Adobe XMP Toolkit SDK, XMPFiles/source/FileHandlers/InDesign_Handler.cpp (BSD 3-Clause, commit 7093513bd3ca; licence in third_party/xmp-toolkit-sdk/LICENSE). Every fact below was also checked against the local corpus (352 files, InDesign 3.0–21.6) and the fixtures.

Overall layout

Part Location
Master page 0 0x0000–0x0FFF
Master page 1 0x1000–0x1FFF
Database pages from 0x2000, up to db_pages × 4096
Contiguous objects from db_pages × 4096, back to back
Padding to the next 4096-byte boundary

The file size is always a multiple of 4096.

Master pages

Both master pages start with the header described in header.md. The one with the higher sequence number is active.

Offset Size Field Notes
0x108 8 Sequence number, u64 little-endian Little-endian even in big-endian files (checked on 2 big-endian files). The two master pages always differ by 1 in the corpus.
0x118 4 Database page count, u32 little-endian Includes the two master pages

The XMP Toolkit names the byte at 0x18 the "object stream endian" flag. The version at 0x1D follows that byte order (header.md), but the fields above do not.

Contiguous objects

Each contiguous object is a copy of one database object, stored as a continuous byte stream:

Part Size
Header marker 32
Data length bytes
Trailer marker 32

Marker layout, all integers little-endian:

Offset Size Field
0 16 GUID: header DE 39 39 79 51 88 4B 6C 8E 63 EE F8 AE E0 DD 38, trailer FD CE DB 70 F7 86 4B 4F A4 D3 C7 28 B3 41 71 06
16 4 Object UID
20 4 Object class ID
24 4 Data length
28 4 Checksum (the XMP Toolkit writes FFFFFFFF)

The list ends at the first position that does not start with the header GUID.

Observed in the corpus

  • Every file has exactly one contiguous object: the XMP metadata packet.
  • Its class ID field is 0xC0000000 (327 files) or 0xE0000000 (25 files).
  • The XMP object's data is a u32 packet length (in the file's byte order), equal to the data length minus 4, followed by the packet starting with <?xpacket begin=.
  • In 13 files, non-zero bytes follow the last object before the end of the file. In the one examined, they are space characters, which matches the padding at the end of an XMP packet from an earlier, longer save.

Not yet known

  • How database pages are organised and how objects are found in them.
  • What the object UID and class ID values identify.