321Kit Tools ready in 3, 2, 1.

Office files

DOCX Metadata Inspector

Read Word core properties such as title, creator, subject and dates.

● Processed only in your browser
ResultChoose a file or enter content to begin.

Files are never uploaded, stored or sent to a third party. Temporary download URLs are released when this page closes.

Method, example & boundaries

DOCX Metadata Inspector: from input to a reviewable result

Inspect the core properties stored inside a local DOCX package, including title, creator, subject, keywords, description, and created or modified timestamps when present. The result is a readable inventory of the document metadata, not a copy of the document body, and the Word file never leaves the browser.

Worked example: audit a project brief before sharing

Example input
launch-brief.docx with Title “Autumn launch”, Creator “M. Chen”, Subject “Partner review”, and Modified “2026-08-18T09:30:00Z”.
Example output
A labelled text list containing the four stored properties; absent core properties are omitted rather than invented.

How to interpret it

The inspector reads docProps/core.xml from the DOCX ZIP package and decodes the actual XML values, so the result can be reviewed before the file is sent outside the team.

Read Word core properties from the package

A DOCX file is opened locally as a ZIP archive. The parser looks specifically for docProps/core.xml, extracts the recognized Dublin Core and Word timestamp fields, decodes XML entities, and renders the values as text. It does not upload the archive or infer properties from the visible paragraphs.

Metadata boundaries

  • Missing properties are reported as absent; the tool cannot reconstruct deleted metadata.
  • Core properties are not a complete revision history, comment audit, or forensic chain of custody.
  • Stored author names and timestamps can be edited by document software and should not be treated as proof of identity.

← Back to office workstation