View OpenDocument Text (.odt) files in your browser without LibreOffice.
An .odt file is not a document file in the usual sense; it is a ZIP archive whose main entry, content.xml, holds the text and structure as XML. This viewer unpacks the archive in your browser, parses that XML, and rebuilds the document as a web page: headings, paragraphs, tables, lists, and embedded images. Nothing is converted, exported, or uploaded. The thing people most often get wrong: the page you see is a fresh re-layout, not a copy of what LibreOffice displays, so exact fonts, spacing, and pagination can differ.
A concrete input and expected output from the current implementation.
Input
A one-page .odt whose content.xml body contains a text:h element with text:outline-level="1" and the text 'Meeting Notes', followed by a text:p element containing 'Call at 3 PM.'
Expected output
A rendered page showing 'Meeting Notes' as a heading (bold and larger than body text) and 'Call at 3 PM.' directly beneath it as a body paragraph, with both strings copyable in that order.
In the ODF content model, text:h is a heading whose level is set by the text:outline-level attribute, and text:p is a paragraph. The viewer renders them as distinct blocks in the order they appear in the XML, so this minimal document yields exactly two lines of content.
The tool treats the file's bytes as a ZIP archive, decompressing entries with the DEFLATE algorithm. It locates content.xml, which holds the document body; styles.xml, which defines the named styles; and META-INF/manifest.xml, which lists every entry. Images stored under Pictures/ are decoded in place. This is why an .odt opens faster than you might expect: everything needed is a small set of XML files.
content.xml is a tree: office:text wraps text:h headings, text:p paragraphs, text:table tables, text:list lists, and text:image anchors. The viewer walks that tree in document order, maps each element to the corresponding HTML block, applies the styles it can resolve from styles.xml, and renders embedded images where they occur. The entire pipeline runs inside the browser tab; the file never leaves the machine.
No. LibreOffice and this viewer both derive their display from the same content.xml, but fonts, metrics, wrapping, and pagination are applied by each renderer independently. Use this tool to read and verify what a document contains; use an office application to proof its final layout.
No. The archive is unpacked and parsed entirely in the browser, and the tool makes no network request carrying the document. For confidential files that is the point: you can view them without sending their contents anywhere.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Convert between bytes, KB, MB, GB, and TB with precise binary and decimal calculations.
Open, view, and edit CSV files in a spreadsheet-style table with sorting and filtering.
Visualize JSON data as a collapsible tree with syntax highlighting and search.
Generate Code 128, EAN, UPC, and other barcode formats with customizable size and labels.
Convert images to Base64 data URLs and decode Base64 strings back to images.
Generate Apache .htaccess redirect rules for 301, 302, and rewrite configurations.