HEADER CHAIN · LOCAL DOCX STRUCTURE CHECK
Word header on every page?
Trace its DOCX references.
Trace header and footer references through your DOCX sections. Separate an explicit reference, inheritance, an inactive selector and an unresolved chain.
Inspect a DOCX locally
Choose a DOCX file, then analyze it locally.
No upload, analytics, document-content preview or repair. Processing runs in a dedicated worker. Cancel and a page-side 5-second timeout terminate it; browser scheduling can delay a timeout.
Section relationships
| Section | Kind | Type | Selector | Provenance | Structural result | Relationship ID | Part path | Inherited from section |
|---|
Unknown stays unknown. Unsupported XML or package conventions, ambiguous references and unsealed inheritance branches are not guessed.
What this does — and does not — establish
A part shown as present means only that its referenced package entry exists. Its content is not read or validated. This is not proof of readable text, a visible header, page numbering, Word's visual rendering, or what Word will recover from a damaged file.
Supported conventional packages yield section/type relationship metadata. Other conventions can return unknown. The document is not changed, and no text from the body, headers or footers is displayed.
Find the section reference behind a repeating header
- Choose one DOCX from your device. Selection alone does not run the analysis.
- Choose Analyze locally. Review each section’s default, first-page and even-page header/footer rows.
- Compare the relationship ID, referenced part path and inheritance source. An inherited reference can explain a shared structural source, but cannot prove which pages Word displays it on.
Use Cancel to terminate an in-progress worker or Clear to discard the displayed result and selection. Your original document is not changed. If a result is unknown, do not treat it as an absent or valid header.
Why can a header reference be unused?
A first-page or even-page reference can exist while its corresponding selector is off. This tool keeps that declaration separate from an active reference. It does not enable the selector or change Word’s settings.
Does “referenced part present” mean the header is readable?
No. It means only that the named package entry exists. The tool does not read header/footer text, resolve fields, paginate the document or compare visual pages.
Why can a valid-looking DOCX return unknown?
Only a bounded conventional WordprocessingML package is supported. Alternate package conventions, ambiguous references, unsafe targets, unsupported XML or unresolved inheritance branches can be unknown. A stopped or unsupported analysis is not a diagnosis that Word cannot open the file.
Supported method and limits · Primary sources · Privacy and search measurement · Dependency notices