Pular para o conteúdo principal
Conversor de imagens Conversor de vídeo Conversor de áudio Conversor de documentos
Ferramentas Guias Formatos Preços API
Entrar
🇬🇧 English 🇪🇸 Español 🇩🇪 Deutsch
XHTML file
xhtml
Formato de arquivo

Sobre os arquivos XHTML

Documento XHTML

Lançado em 2000 Por W3C

Variante de HTML conformada com XML strict (2000). Mais rigorosa que HTML5 moderno. Usada em algumas aplicações que exigem parsing XML estrito.

Família

Documents & Text

Extensão

.xhtml

Tipo MIME

application/xhtml+xml

Pode ser usado como

Entrada Saída
A história

COMO NASCEU O
FORMATO XHTML.

2000
2001
2004
2009

XHTML 1.0 was published by the W3C in January 2000 as a reformulation of HTML 4.01 in strict XML. The idea: HTML\u2019s 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.

CURIOSIDADES E
FATOS INTERESSANTES.

01

The W3C's refusal to kill XHTML led four major browser vendors (Mozilla, Apple, Opera, later Microsoft) to split and form WHATWG in 2004.

02

EPUB ebooks must contain XHTML 1.1 or HTML5 chapters — the spec is stricter than web HTML.

03

XHTML requires lowercase tags, quoted attributes, and every tag explicitly closed — no `<br>`, only `<br/>`.

04

The 2009 abandonment of XHTML 2.0 is considered a pivotal moment where the web chose pragmatism over purity.

05

Sending XHTML with application/xhtml+xml MIME makes browsers refuse to render pages with XML errors — useful for debugging.

VANTAGENS E
LIMITAÇÕES.

Vantagens

  • 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.

Limitações

  • 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.

Tamanhos típicos de arquivo

EPUB chapter

5-50 KB

DocBook reference page

10-100 KB

Especificações técnicas

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

CONVERTER A PARTIR DE
XHTML

Casos de uso comuns

Strict web documents, XML pipelines

Formatos relacionados

Comparativos populares

Conversões populares de XHTML

Os destinos mais procurados ao converter arquivos XHTML.

Perguntas frequentes sobre XHTML

Perguntas frequentes

XHTML (XHTML Document) is a document formato used to store paginated text, com optional formatoting, tables, images, hyperlinks, headers e footers. It sits no documents & text family e is tipicamente associated com a specific office suite ou publishing pipeline that defined the formato e ships the canonical reader.

Modern office suites — Microsoft Word, Google Docs, LibreOffice Writer, Apple Pages — abrir most XHTML arquivos com reasonable fidelity. If your installed software does not support XHTML, converter to DOCX ou PDF first usando KaijuConverter; both abrir in virtually every reader, including grátis online viewers.

Upload the XHTML to KaijuConverter e pick DOCX, PDF, ODT, RTF, HTML, Markdown, ou plain text. Our pipeline runs LibreOffice headlessly plus pandoc para text formatoos — the same engines behind profissional document pipelines. Styles, tables, images, e hyperlinks survive the conversion intact.

Sim, para um alta degree. padrão fonts, headings, lists, tables, images, hyperlinks e page structure transfer cleanly. Custom fonts substitute para o closest match if not embedded; obscure layout features unique to XHTML (frames, legacy macros) may flatten to static content no target formato.