How to Export Word Comments to Excel

Word comments are easiest to review when they leave the margin and become a table. One row per comment gives reviewers, editors, and project managers a shared checklist: who raised it, when it was raised, whether it is resolved, what was said, and which document passage it refers to.

This guide compares three common approaches - a Word/VBA macro, a Word add-in, and the PDFAnnotations browser tool - then explains how to prepare a useful comment spreadsheet without inventing data.

What Word Stores in a DOCX Comment

A modern .docx file is an Open XML package. Comments are usually stored in word/comments.xml, while additional review metadata may live in parts such as word/commentsExtended.xml. Depending on the Word version, export path, and document producer, a comment can provide:

• Comment ID
• Author
• Date
• Resolved or open status
• Comment text
• Anchor text, meaning the selected or surrounding document text linked to the comment

Not every field is guaranteed. Some documents omit authors or dates, and resolved-status information is not always stored in a reliably matchable form. A useful exporter should show only fields it can determine from the document rather than filling a spreadsheet with invented unknown values.

Approach 1: Export Word Comments with VBA

VBA works well when your organization permits macros and you want a customizable, no-extra-installation route from inside Word.

Basic VBA workflow

1. Open the DOCX in Word.
2. Press Alt+F11 to open the VBA editor.
3. Insert a module and write a macro that loops through ActiveDocument.Comments.
4. Write selected properties to a new worksheet.
5. Save the workbook manually or from the macro.

A minimal macro can collect Author, Date, and Range.Text. More complete scripts can also capture the commented text through Comment.Scope.

Advantages

• No third-party service receives the document.
• Fields and formatting can be adapted to an internal template.
• Convenient for repeated, organization-specific workflows.

Limitations

• The macro must be enabled and maintained.
• Word object-model behavior can differ across Word versions and platforms.
• A macro that writes directly to Excel needs the right Office automation environment.
• If a field is not reliably exposed for a particular document, the script must decide whether to omit it or fabricate a placeholder.

VBA is a strong option for controlled internal workflows, but it is not always the shortest path for a one-off review document.

Approach 2: Use a Word Add-in

Word add-ins and review-workflow products can provide comment export, dashboards, and team reporting. They are useful when your team already works inside that product and needs its broader workflow.

Before choosing one, check three things:

• Data handling: Does the document leave your device, and if so, what is retained?
• Fields: Does it expose author, date, status, comment text, and anchor text, or only a subset?
• Cost and setup: Are licenses, admin consent, or a centralized workspace required?

Add-ins are most valuable when their collaboration features match your process. For a single confidential DOCX, their setup and data-handling requirements may be more than the job needs.

Approach 3: Export DOCX Comments in the Browser

The Word comments tool reads a standard .docx directly in your browser. There is no account requirement for the basic flow, and the document is not uploaded to a processing server.

The workflow is:

1. Open Export Word Comments.
2. Drag one DOCX into the tool, or start with the demo document.
3. Search comments, filter by author, and use status filters when reliable status data exists.
4. Export the visible comments to CSV, Markdown, TXT, Excel, JSON, or a custom template.

CSV, Markdown, and TXT are free. Excel, JSON, and custom templates use the existing PDFAnnotations Pro features. The tool does not create a second Word-specific permission system.

Why local processing matters

Review comments often identify unpublished claims, legal concerns, personnel issues, or unfinished conclusions. Local browser processing keeps the source document on the device while still turning the comments into structured rows.

Local processing does not make an unreadable document readable: a damaged package, a legacy .doc file, or an unusual producer can still be rejected. Standard .docx files are the supported input for V1.

Recommended Spreadsheet Columns

For most reviews, start with these columns:

Column	Use
Comment ID	Stable reference back to the Word comment
Author	Reviewer who wrote the comment
Date	When the comment was written, when stored
Status	Open or resolved, only when reliably readable
Comment	The reviewer's note
Anchor Text	Document passage linked to the comment

Avoid merging author and date into one cell if you plan to sort or group later. Keep the comment text unwrapped in a long text cell rather than splitting one comment across multiple rows.

If you import a CSV into Excel, Google Sheets, or Numbers, check that quoted commas and multiline comments survive the transfer. A direct Excel export can also preserve these values without an intermediate CSV conversion.

Why Page Numbers Are Not Inferred

Many printed-page workflows expect a page column. V1 deliberately does not infer one for Word comments.

A .docx stores logical document content, not one fixed printed layout. Pagination depends on the Word version, fonts available on the machine, paper size, margins, headers and footers, compatibility settings, and printer driver. Two people can repaginate the same document differently without changing its comments.

Guessing a page from character or paragraph position can therefore point a reviewer to the wrong page. Rather than export a possibly misleading or mostly empty column, V1 omits Word page numbers completely. If reliable DOCX pagination is added as a separate capability in the future, the export schema can be extended deliberately.

Prepare the DOCX Before Export

If you control the source document:

1. Save legacy .doc files as .docx.
2. Let Word finish saving comment metadata before closing the file.
3. Keep the original document available for follow-up review.
4. Remove sensitive comments only after you have exported the review log you need.

If you receive a document from another organization, avoid editing it solely to inspect comments. Open a copy, export the comments, then decide how to respond.

Workflows After Export

• Editorial review: Filter by author, sort by comment ID, then mark each item as handled in your project tracker.
• Legal or contract review: Preserve anchor text with the comment so the referenced clause is clear without reopening the full margin view.
• Compliance audit: Export before cleanup, retain the original package, and use comment IDs to connect the log with the source document.
• Team summary: Group a CSV or Excel export by author to see review workload, while keeping individual comments linked to anchor text.

Frequently Asked Questions

Can I export Word comments without macros?

Yes. The browser-based tool reads a .docx locally and exports comments without a Word macro. CSV, Markdown, and TXT are free formats.

Does the Word export include page numbers?

No. V1 does not infer Word page numbers because DOCX pagination depends on the rendering environment. The export omits the column instead of providing unreliable estimates.

Is Word resolved status always available?

No. Status is shown or exported only when the DOCX stores status data that can be read reliably. If it cannot be matched to comments, the status UI and column remain hidden.

Can I export comments from a legacy .doc file?

Not directly in V1. Open the file in Word and save it as .docx first. This preserves the modern Open XML package structure used by the parser.

Does the browser tool upload my Word document?

No. DOCX parsing and export run in the browser. The document is not sent to PDFAnnotations or a third-party processing service.

Does this extract Word Track Changes?

No. Comments and tracked revisions are different data. V1 extracts comments in the current DOCX; it does not extract Track Changes, OCR content, Microsoft 365 version history, or Word Compare results.

Which export format should I choose?

CSV is the simplest free option for spreadsheets. Markdown works well in notes and documentation, TXT is useful for plain-text logs, and Excel, JSON, and custom templates are available with Pro.

Can I export only selected Word comments?

Use search and filters first, then export. The browser tool exports the comments currently visible after search, author, and reliable status filters are applied.