Tiny Online Tools logoTiny Online ToolssearchSearch tools…grid_viewAll Tools
Homechevron_rightDocument Toolschevron_rightOpenDocument InspectorOpenDocument Inspector

OpenDocument Inspector

Look inside ODT, ODS and ODP packages: mimetype, manifest, metadata and every XML part, checked against the OpenDocument packaging rules.

upload_file

Click to browse or drag & drop files here

ODT, ODS, ODP, ODG, OTT, OTS or OTP

Accepted: .odt,.ods,.odp,.odg,.ott,.ots,.otp,.odf,.odm

Similar Tools

Universal Office File Inspector

Universal Office File Inspector

Open DOCX, XLSX, PPTX, ODT, XPS, MHTML, CHM and Publisher files and inspect their parts, relationships and metadata in your browser.

DOCX Internal Inspector

DOCX Internal Inspector

Browse document.xml, the style table, every relationship, the media and the embedded objects inside a Word file.

3MF Package Inspector

3MF Package Inspector

Open a .3mf archive and see everything inside it: the OPC part graph, objects, build transforms, materials, declared extensions, thumbnails and the slicer settings hidden in it.

ICS Calendar Inspector

ICS Calendar Inspector

Open an .ics file and inspect its events, recurrence rules, time zones, alarms and attendees.

Browser 3D Slicer

Browser 3D Slicer

Slice STL, 3MF and OBJ models into printer-ready G-code in your browser. Nothing is uploaded.

JPG to PDF

JPG to PDF

Combine JPG images into a single PDF document.

XML to JSON

XML to JSON

Convert XML documents into JSON.

apps

More Tools

Browse our full collection of free online tools.

OpenDocument is a ZIP with rules

An ODT, ODS, ODP or ODG file is a ZIP archive, but not just any ZIP. The format specifies a small set of parts and two packaging rules, and this tool shows all of it.

content.xml holds the document body. styles.xml holds the named and automatic styles, page layouts, headers and footers. meta.xml holds the title, author, dates, editing cycles and the document statistics that OpenDocument records and Office Open XML mostly does not. settings.xml holds application state — the cursor position, the zoom level, print ranges — and is not part of the document at all. META-INF/manifest.xml lists every part with its media type; ODF has no content-types table, so the manifest is the index.

The two rules that get broken

ODF requires the mimetype entry to be first in the archive and stored, not deflated, so that a reader can identify the file by reading its first few dozen bytes without unpacking anything.

Both of those facts are destroyed by any ZIP library that hands you decompressed bytes, so this tool reads the archive's first local file header directly: the compression method is a 16-bit value at offset 8 and the filename starts at offset 30. Method 0 means stored, 8 means deflate. The result you see is a measurement, not an assumption.

What else you get

  • The manifest as a table: path, declared media type, size, and whether the entry is encrypted.
  • Metadata: every meta.xml field, the document-statistic counts (pages, words, characters, tables, images) and any user-defined properties.
  • Sheet names for a spreadsheet and slide names for a presentation.
  • A content summary — paragraphs, headings, tables, frames, images, lists, links and annotations.
  • Every picture in the package, previewed and downloadable.
  • The document's plain text, extracted from content.xml.
  • A part viewer that re-indents and highlights the XML, which ships minified onto one line.

If the package is encrypted, that is stated plainly: content.xml will read as noise and no tool can do anything about it without the password.

Privacy

Everything happens in your browser. The file is never uploaded.