What is the OBD file format?
An .obd file is a Microsoft Office Binder Document - a container that bundles multiple Office documents (a Word file, an Excel spreadsheet, a PowerPoint presentation, or a Project file) into a single package for unified storage and printing. Microsoft introduced the Binder feature with Office 95 and included it through Office 2000.
Internally, an .obd file is an OLE2 Compound File Binary (CFBF) container - the same format underlying legacy .doc, .xls, and .ppt files. It opens with the standard OLE2 magic bytes D0 CF 11 E0 A1 B1 1A E1. Inside, a Binder root storage holds numbered section storages (1, 2, 3, …), each embedding a complete Office object alongside SummaryInformation and DocumentSummaryInformation metadata streams. The companion .obt extension was used for Office Binder Templates.
Microsoft removed Binder from Office XP (2001), citing low adoption. No version of Office since 2003 can open .obd files natively. An "Unbind" add-in was released for Office 2003 to extract the individual embedded documents, but that add-in is itself no longer supported. Users encountering an .obd file today should ideally open it using Office 2000, or use the Office 2003 Unbind add-in if available - there is no modern migration tool.
The .obd format was never ported to the Open XML era; Microsoft chose not to create an OOXML-based Binder equivalent when transitioning to DOCX, XLSX, and PPTX formats.
Security & safety
RISK: MEDIUMOBD files are OLE2 containers and can theoretically contain malformed OLE2 structures or exploit old parser bugs in legacy Office versions. Viewing them requires very old, unpatched software (Office 2000/2003) that itself has unpatched security vulnerabilities. Treat with caution in any production environment; open only in an isolated/sandboxed legacy system.
Format details
in a nutshell- OBD On-Board Diagnostics (automotive) - Unrelated: some automotive diagnostic software uses .obd for vehicle scan data; completely different format.
Programs that open OBD files
Technical details
deep spec| Encoding | Binary |
| Byte order | Little-endian (OLE2/CFBF) |
| Container format | OLE2 Compound File Binary Format (CFBF) - the same container used by legacy `.doc`, `.xls`, and `.ppt` |
| Magic bytes | `D0 CF 11 E0 A1 B1 1A E1` at offset 0 (standard OLE2/CFBF signature) |
| Internal structure | OLE2 root storage → `Binder` storage → numbered section storages (`1`, `2`, `3`…) each holding an embedded OLE2 Office object |
| Metadata streams | `SummaryInformation`, `DocumentSummaryInformation`, and `HdrFtr` (header/footer data) streams |
| Embeddable object types | Word documents, Excel spreadsheets, PowerPoint presentations, Microsoft Project files |
| Typical file size | 50 KB - 50 MB (scales with number and size of embedded documents) |
| Companion extension | `.obt` - Office Binder Template (same CFBF structure, used as a reusable Binder layout) |
| Supported Office versions | Office 95, 97, 2000 (native Binder); Office 2003 (Unbind add-in only); no support in Office XP or any later version |
| MIME type | application/msword (shared with legacy `.doc`) |
| Migration path | Office 2003 Unbind add-in extracts embedded documents to individual files; no modern equivalent extraction tool exists |
| Released | 1995 (Microsoft Office 95) |
| Latest version | Final version included in Office 2000 (v9); Unbind add-in for Office 2003 only |
| Specification | learn.microsoft.com |
OBD conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about OBD files.