application/msword Word Document (Legacy .doc) Common
Identifies legacy, pre-2007 Microsoft Word documents (.doc) — an older binary format, distinct from modern DOCX.
What it's for
application/msword identifies legacy Microsoft Word documents (.doc) — the binary format used by Word versions before Office 2007, when Microsoft switched to the XML/ZIP-based Office Open XML format (DOCX). Unlike DOCX's inspectable ZIP-of-XML-files structure, .doc is a proprietary binary format (based on Microsoft's Compound File Binary format) that isn't human-readable or easily parsed without a dedicated library that understands its internal structure.
You'll encounter this MIME type today almost entirely through legacy content — old documents, archives, and systems that predate the DOCX transition — rather than anything actively chosen for new document creation.
Format & syntax
Content-Type: application/msword
No parameters. The internal format is a binary Compound File structure with its own internal "streams" and "storages," a fundamentally different architecture from DOCX's ZIP-of-XML approach — meaning tools built to parse one format generally can't read the other without explicit separate support for both.
How it's used in practice
- Legacy document archives and migrations — organizations with older document repositories, especially government, legal, or enterprise archives predating 2007, commonly still hold significant volumes of
.docfiles that need occasional access, conversion, or migration. - Backward-compatible export options — some document-generation tools offer a legacy
.docexport option specifically for compatibility with very old Word versions or systems that haven't been updated to handle DOCX. - File upload validation for older content — document management and content migration systems accepting historical uploads need to recognize and handle this MIME type distinctly from modern DOCX, since the two require entirely different parsing logic.
- Conversion pipelines — tools that convert
.docto.docx(or to PDF, plain text, etc.) for modernizing document archives rely on correctly identifying this MIME type before selecting the appropriate legacy-binary parser.
Common mistakes & gotchas
- Assuming .doc and .docx are interchangeable formats — they are completely different internal structures (binary Compound File vs. ZIP-of-XML) despite both being "Word documents." Code, libraries, or validation logic built for one will not correctly read the other without explicit separate support.
- Trying to parse .doc with a DOCX/XML-based library — a common integration mistake: passing a legacy
.docfile to a library or parser that only understands the modern OOXML structure will fail, sometimes with a confusing or generic error rather than a clear "wrong format" message. - Renaming a .doc file to .docx (or vice versa) expecting it to work — unlike some formats where extension mismatches can be forgiving, these are structurally incompatible internal formats; renaming the extension doesn't change or fix the underlying binary structure.
- Underestimating the complexity of writing a .doc parser from scratch — the legacy binary format is considerably more complex and less documented than DOCX's relatively approachable XML structure, which is why most tooling relies on established libraries (or converts through Word/LibreOffice automation) rather than implementing
.docparsing directly.
Comparison & FAQ
| Type | Purpose | Key difference from application/msword |
|---|---|---|
| DOCX (OOXML) | Modern Word document format | XML/ZIP-based, human-inspectable structure, introduced with Office 2007 — not interchangeable with legacy .doc |
| application/rtf | Cross-platform formatted text | Much simpler internal format with broader cross-application compatibility, though far more limited formatting support than either Word format |
What's the difference between .doc and .docx?
They're fundamentally different formats: .doc uses an older, proprietary binary structure (pre-Office 2007), while .docx uses a modern, XML-based structure inside a ZIP archive (Office 2007 onward). They require different parsing logic entirely and aren't directly interchangeable by renaming.
Can I open a .doc file with a DOCX-only library?
No — libraries built specifically for the modern OOXML/DOCX structure generally can't parse the legacy binary .doc format at all; you need a library or tool with explicit legacy binary format support, or a conversion step through Word or a compatible tool first.
Should I still support .doc uploads in a new application?
It depends on your audience — if you expect users might have older archived documents, supporting .doc alongside .docx broadens compatibility, though it does mean maintaining or depending on a library capable of handling the more complex legacy binary format.
How do I convert a .doc file to modern DOCX?
Most word processors (Word itself, LibreOffice) can open and re-save .doc files as .docx directly, and this is the most reliable path for one-off or small-batch conversions; for bulk/automated conversion pipelines, headless document-conversion tools or libraries with dual-format support handle this at scale.