DOCX Style Auditor
Compare Word style definitions with body paragraphs to inspect inheritance, heading hierarchy and direct formatting by paragraph number.
Key features
- Map styles.xml names, types, basedOn relationships and paragraph usage
- Locate missing parents, type mismatches, inheritance cycles and undefined paragraph styles
- Trace heading sequence and skipped levels from outlineLvl evidence
- Show direct paragraph and run properties with paragraph numbers and excerpts
- Count TOC field clues and locate undefined numbering IDs
- Download a local JSON review report with bounded evidence
How to use
- Choose a local DOCX or run the sample document.
- Inspect heading levels and their inherited sources.
- Locate affected paragraphs in the style and direct-format tables.
- Save JSON if needed, then verify rendered formatting and TOC in Word.
Use cases
- Find a Heading 3 paragraph directly after Heading 1
- Inspect a cycle in basedOn style references
- Collect paragraphs with direct bold or spacing overrides
- Find TOC field clues before updating a table of contents in Word
Frequently asked questions
Does this render Word pages?
No. It reads a selected subset of WordprocessingML inside DOCX. Confirm page layout and font substitution in Word.
Is all direct formatting an error?
No. Direct bold can be intentional emphasis. This table identifies places to review for style consistency.
Does it verify that the table of contents is current?
No. It finds TOC field clues and heading levels only. Update fields and compare the displayed TOC in Word.
Is this an accessibility or full OOXML conformance test?
No. It checks selected style, heading and numbering rules. It does not certify accessibility or ISO/IEC 29500 conformance.
Does the file leave my browser?
No. The source is processed in browser memory. A downloaded JSON report can include short text excerpts, so review it before sharing.
Privacy
DOCX data stays in browser memory and is not uploaded. The JSON report may contain the filename and short text excerpts; review it before sharing.
Comments & questions