ODT Document Inspector & Extractor
Extract body paragraphs, headings, lists, tabs, explicit spaces and line breaks from content.xml; tables become tab-separated text, including repeated rows and cells. Download the text, each original Pictures/ file, or a ZIP of all pictures. Styles, page layout, comments and tracked-deletion history are not reproduced.
About this odt document inspector & extractor
Extract body paragraphs, headings, lists, tabs, explicit spaces and line breaks from content.xml; tables become tab-separated text, including repeated rows and cells. Download the text, each original Pictures/ file, or a ZIP of all pictures. Styles, page layout, comments and tracked-deletion history are not reproduced Parses and structures office document payloads locally in memory without transmitting private company files to external servers.
Document parsing & data extraction pipeline
Inspects, parses, and converts open publishing and scheduling formats conforming to IDPF EPUB 3.2 / 3.3 specifications, IETF RFC 5545 (iCalendar - .ics), and RFC 6350 (vCard v4.0 - .vcf). EPUB tools unpack the OCF (Open Container Format) ZIP package, parsing META-INF/container.xml and the OPF (Open Packaging Format) package document to extract Dublin Core metadata (dc:title, dc:creator, dc:identifier), spine order, manifest items, and table of contents (NCX / Nav doc), converting chapters to Markdown.
Worked document extraction example
Scenario: Execute ODT Document Inspector & Extractor with sample data to verify transformation accuracy and output formatting.
Sample input:
Processing: After the page loads, processing runs locally in a Worker without uploading the file. Cancel or clear stops the task.
Illustrative output:
File size & structure constraints
Input must be strictly smaller than 50,000,000 bytes. Limits: 100,000 ZIP entries; 16 MiB per XML; 64 MiB per other selected part; 128 MiB selected data; XML depth 128 and 1,000,000 nodes; 64 MiB text output; 30 seconds including file reading. Very complex ODT repetition can reach the output budget earlier. Encrypted selected content, external reading resources, DTDs and non-XHTML spine items are rejected. Only the first rendition is read; this is not a conformance validator or a native reading application. Preview pages contain 16,000 characters. Downloads are complete. JSON keys, package paths and original metadata are technical/source values, not interface translations. Picture ZIPs support at most 65,535 files.
ODT Document Inspector & Extractor parses structured OpenXML and PDF data locally. Review exported tables or sheets against original files.
Zero-upload document security boundary
File buffers and document assets in ODT Document Inspector & Extractor are processed in-memory via local browser APIs with zero file uploads to CZOA servers.
Document schemas & interchange standards
ECMA-376 Office Open XML specifications and ISO 32000 PDF reference standards:
ODT Document Inspector & Extractor verification · Audit standards
How to use it
- Choose a local EPUB / ODT
- Process locally
- Download selected file
Frequently asked questions
What does the ODT Document Inspector & Extractor produce?+
Operational requirements for "What does the ODT Document Inspector & Extractor produce?" are verified in local memory during execution of ODT Document Inspector & Extractor.
What limits and privacy rules apply?+
Inspects OpenDocument Text (ODT) packages, reporting document structure, embedded styles, and XML parts without remote upload.
How do previews and downloads differ?+
Scans content.xml, styles.xml, and meta.xml within the ODT zip archive to report paragraph counts, font declarations, and document properties.
Can I run a local example?+
Choose a local EPUB / ODT → /examples/publication-example.odt → Process locally → Download selected file