Interpretation and ownership guidance for standard SMBIOS types.

Function signatures, structure members, macros, and return contracts are generated directly from the public header under SMBIOS Structure APIs. These guides focus on selection rules, version-dependent fields, and raw-value interpretation. For vendor-specific records, see OEM SMBIOS Type Guides.

Find a type by topic

If you know what you are looking for but not its structure number, start here. Types marked (obsolete) are defined by earlier revisions of the specification and are parsed for completeness.

Topic	Types
Identity and firmware	0 BIOS · 1 System · 2 Baseboard · 3 Chassis · 13 Language · 45 Firmware Inventory
Processors and cache	4 Processor · 7 Cache · 44 Processor Additional
Memory	16 Memory Array · 17 Memory Device · 19 Array Mapped Address · 20 Device Mapped Address · 37 Memory Channel · 5 Memory Controller (obsolete) · 6 Memory Module (obsolete)
Memory errors	18 32-Bit Error · 33 64-Bit Error
Slots, ports and devices	8 Port Connector · 9 System Slots · 21 Pointing Device · 40 Additional Information · 41 Onboard Devices Extended · 10 On Board Devices (obsolete)
Power and battery	22 Portable Battery · 25 Power Controls · 39 Power Supply
Sensors and cooling	26 Voltage Probe · 27 Cooling Device · 28 Temperature Probe · 29 Current Probe
Management and remote access	30 Out-of-Band Remote Access · 34 Management Device · 35 Device Component · 36 Threshold Data · 38 IPMI Device · 42 Controller Host Interface
Security, boot and reset	23 System Reset · 24 Hardware Security · 31 Boot Integrity Services · 32 System Boot · 43 TPM Device
Logs, groups and vendor data	11 OEM Strings · 12 Configuration Options · 14 Group Associations · 15 System Event Log · 46 String Property

How to read a type guide

Every guide follows the same shape, so once you have read one you can skim the rest:

Result set and ownership — how to iterate what the getter returned, and which free function or context member owns it.
Fields — what each parsed member means, and which raw encodings the parser preserves rather than normalizing.
Decoded values — which encoded fields have a ready-made string or computed value waiting in decoded. Decoding happens during parsing; there is nothing for a caller to invoke.

Before consuming any optional value, check its availability with LAZYBIOS_FIELD_STATUS. The rules behind that metadata are described in Core Concepts and Ownership.