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:UEFI capsule

From ReverseEngineering.wiki
Format
Extensions .cap, .fd, .bin
Endianness little
License BSD-2-Clause-Patent (edk2 headers)
On this wiki Facts · Code · Notes · Topics

The firmware update package of UEFI (EFI_CAPSULE_HEADER, 28 bytes: capsule GUID, header size, flags, image size), often wrapping a firmware volume or an FMP payload.

Header (EFI_CAPSULE_HEADER)

Offset Size Field
0 16 CapsuleGuid: identifies the payload kind (no magic number; recognise by GUID)
16 4 HeaderSize (offset of the payload)
20 4 Flags
24 4 CapsuleImageSize (total size including the header)

Flags: 0x00010000 PERSIST_ACROSS_RESET, 0x00020000 POPULATE_SYSTEM_TABLE, 0x00040000 INITIATE_RESET (the low 16 bits are GUID-specific).

UEFITool's copy of the flags (common/ffs.h line 43-45) also defines 0x00000001 as SETUP; the generic standard-capsule GUID it recognizes is 3B6686BD-0D76-4030-B70E-B5519E2FC5A0. For the flash layout that often follows a capsule see Format:Intel flash descriptor.

Analyst notes

  • Vendor BIOS update files are frequently a capsule (or an Intel/AMI/Insyde wrapper) around a Format:UEFI firmware volume (PI) or a whole flash image: skip HeaderSize bytes, or just scan for _FVH.
  • The firmware-management (FMP) capsule GUID is 6DCBD5ED-E82D-4C44-BDA1-7194199AD92A (checked: EFI_FIRMWARE_MANAGEMENT_CAPSULE_ID_GUID in edk2 MdePkg/Include/Guid/FmpCapsule.h @ c1415771ac, line 20: 0x6dcbd5ed, 0xe82d, 0x4c44, {0xbd,0xa1,0x71,0x94,0x19,0x9a,0xd9,0x2a}); its payload begins with an EFI_FIRMWARE_MANAGEMENT_CAPSULE_HEADER (u32 Version, u16 EmbeddedDriverCount, u16 PayloadItemCount, then a u64 ItemOffsetList[EmbeddedDriverCount + PayloadItemCount], per the same header).
  • Vendor capsules use their own capsule GUIDs: UEFITool (common/ffs.h, lines 31-86) lists Intel, Lenovo, Toshiba and AMI Aptio signed/unsigned GUIDs, and its APTIO_CAPSULE_HEADER adds RomImageOffset u16 and RomLayoutOffset u16 after the 28-byte capsule header; RomImageOffset counts from the capsule start to the volume. See the identification fact on capsule GUIDs. Unverified: that a given vendor file always has the volume exactly at RomImageOffset; test by scanning for _FVH past HeaderSize.

Source: edk2 MdePkg/Include/Uefi/UefiSpec.h.

Code & repositories

  • https://github.com/tianocore/edk2 @ c1415771ac592ad8509351c46cd3cda4f38d7d52 · license: BSD-2-Clause (read from License-History.txt; GitHub's detector did not classify it)
    EDK2 reference headers for PI firmware volumes, FFS, sections, TE and capsules (MdePkg/Include/Pi, Uefi, IndustryStandard/PeImage.h)
    Tested on: source read, not run: source read · checked 2026-10-18; last activity 2026-10-16
  • https://github.com/LongSoft/UEFITool @ dac91b26733ca21cb204e41614c1b8c81cc50860 · license: BSD-2-Clause
    UEFITool/UEFIExtract; common/ffs.h and common/descriptor.h read for capsule, volume, FFS and flash descriptor structures
    Tested on: source read, not run · checked 2026-10-19; last activity 2026-07-29; Note: the latest release ships binaries; the wiki links only the source, never the binaries