About XHTML Files
XHTML Document
XHTML is XML-compliant HTML for strict document processing.
Family
Documents & Text
Extension
.xhtml
MIME Type
application/xhtml+xml
Can Use As
HOW XHTML
CAME TO BE.
XHTML 1.0 was published by the W3C in January 2000 as a reformulation of HTML 4.01 in strict XML. The idea: HTML’s permissive syntax let browsers render sloppy markup, which caused subtle rendering inconsistencies; if every document had to parse as valid XML (closed tags, quoted attributes, lowercase everything), the web would become more rigorous and tooling could process pages with off-the-shelf XML parsers.
XHTML 2.0 ambitions (2001-2009) went further, breaking backward compatibility in the name of purity. The web rejected it. When Mozilla, Apple, and Opera split from the W3C in 2004 and formed WHATWG, they drafted what became HTML5 — an error-tolerant spec that codified how browsers actually worked. W3C eventually abandoned XHTML 2.0 in 2009 and embraced HTML5. XHTML is still used in EPUB ebooks (which require strict XHTML), some government publishing systems, and academic tooling — but the web moved on.
CURIOSITIES &
TRIVIA.
The W3C's refusal to kill XHTML led four major browser vendors (Mozilla, Apple, Opera, later Microsoft) to split and form WHATWG in 2004.
EPUB ebooks must contain XHTML 1.1 or HTML5 chapters — the spec is stricter than web HTML.
XHTML requires lowercase tags, quoted attributes, and every tag explicitly closed — no `<br>`, only `<br/>`.
The 2009 abandonment of XHTML 2.0 is considered a pivotal moment where the web chose pragmatism over purity.
Sending XHTML with application/xhtml+xml MIME makes browsers refuse to render pages with XML errors — useful for debugging.
STRENGTHS &
LIMITATIONS.
Strengths
- Rigorous XML syntax — can be parsed with any XML tool.
- Native EPUB and DocBook support.
- Enforces clean markup — no sloppy error recovery.
- Namespaces allow mixing SVG, MathML, and XHTML in one document.
Limitations
- Browsers reject XHTML with strict MIME on any markup error — harsh failure mode.
- Authoring is more tedious than HTML5.
- Not served by ~99% of the web.
- Largely superseded by HTML5.
Typical Sizes & Weights
EPUB chapter
5-50 KB
DocBook reference page
10-100 KB
Technical Specifications
- MIME types
- application/xhtml+xml, text/html
- Extensions
- .xhtml, .xht, .xml
- Standards
- XHTML 1.0 (2000), XHTML 1.1 (2001)
- Encoding
- UTF-8 (required with XML prolog)
- Used in
- EPUB, DocBook, some government sites
CONVERT FROM
XHTML
Common Use Cases
Strict web documents, XML pipelines
Related Formats
Popular comparisons
XHTML vs PDF
Differences, file size, and when to choose each format.
XHTML vs DOCX
Differences, file size, and when to choose each format.
XHTML vs ODT
Differences, file size, and when to choose each format.
XHTML vs TXT
Differences, file size, and when to choose each format.
XHTML vs MD
Differences, file size, and when to choose each format.
XHTML vs HTML
Differences, file size, and when to choose each format.
Popular XHTML conversions
The most-requested destinations when starting from XHTML.
Frequently Asked Questions about XHTML
Frequently Asked Questions
XHTML (XHTML Document) is a document format used to store paginated text, with optional formatting, tables, images, hyperlinks, headers and footers. It sits in the documents & text family and is typically associated with a specific office suite or publishing pipeline that defined the format and ships the canonical reader.
Modern office suites — Microsoft Word, Google Docs, LibreOffice Writer, Apple Pages — open most XHTML files with reasonable fidelity. If your installed software does not support XHTML, convert to DOCX or PDF first using KaijuConverter; both open in virtually every reader, including free online viewers.
Upload the XHTML to KaijuConverter and pick DOCX, PDF, ODT, RTF, HTML, Markdown, or plain text. Our pipeline runs LibreOffice headlessly plus pandoc for text formats — the same engines behind professional document pipelines. Styles, tables, images, and hyperlinks survive the conversion intact.
Yes, to a high degree. Standard fonts, headings, lists, tables, images, hyperlinks and page structure transfer cleanly. Custom fonts substitute to the closest match if not embedded; obscure layout features unique to XHTML (frames, legacy macros) may flatten to static content in the target format.