How to Merge PDF Comments from Multiple Reviewers

Three reviewers return three copies of the same brochure. One corrects the product name, another rewrites the introduction, and a third asks you to keep the original wording. Before you can update the InDesign file, you need to work out which changes belong in the next version.

To merge PDF comments, collect annotations from copies of the same proof into one master PDF. Then review the combined feedback and agree on the instructions the production team should apply. Bringing comments together makes them easier to compare; it does not decide which reviewer is right.

This guide covers that process for teams preparing an InDesign revision round.

Start with copies of the same proof

Choose the exact PDF that everyone reviewed. Check the version identifier, page count, page order, and layout against each returned copy. A filename alone is not enough: someone may have renamed an older proof.

For example, if one reviewer commented on a 12-page brochure and another used an earlier 10-page version, do not import both sets into the latest PDF and assume the annotations will land correctly. Compare the older feedback separately and confirm whether each instruction still applies.

Keep the returned PDFs unchanged in an archive folder. Create a working copy of the original proof for consolidation, with a clear name such as Brochure_v03_feedback_master.pdf. This gives you somewhere to assemble feedback while preserving what each reviewer actually sent.

Import the comments into a master PDF

Adobe Acrobat can import comments from another PDF, or from FDF and XFDF comment data files. For separate annotated copies of the same proof, use this desktop workflow:

1. Open your working master PDF in Acrobat.

2. Open the comments list through All tools > Add comments.

3. In the comments list Options menu, choose Import Data File.

4. In the file picker, choose All Files if necessary, then select a reviewer's annotated PDF and open it.

5. Check the imported annotations, repeat for the remaining reviewers, and save the master PDF.

Adobe documents this process in its guide to importing and exporting comments: https://helpx.adobe.com/acrobat/using/importing-exporting-comments.html. Menu labels can vary by interface version.

This imports annotations into the document you have open. Combining PDF pages is a different operation and will not give you one proof with all feedback aligned to it. Imported comment positions depend on the source and destination documents matching.

After each import, check several annotations against that reviewer's original file, including comments near the beginning and end. Confirm that the text, author information, and position are usable. If a comment points to the wrong passage, stop and check the proof versions before continuing.

Separate repeated feedback from conflicting instructions

Read the consolidated feedback page by page. Look for repeated requests on the same passage, instructions that contradict each other, and comments that depend on an unanswered question.

Two reviewers might both ask you to change “2025” to “2026.” That is one edit with two supporting comments. Keep enough context to show both requests were considered, but do not apply the correction twice.

A conflict needs a decision. If marketing asks for “Start your free trial” and legal asks for “Request a consultation” on the same button, combining the comments has only made the disagreement visible. Ask the person responsible for the final wording to choose, then record the approved text.

Do not treat the latest timestamp as automatic approval. Reviewers may have different responsibilities, and a later comment may have been written without seeing an earlier one.

Turn vague notes into usable instructions

A production team needs to know what to change and where. Comments such as “too long,” “make this stronger,” or “same as before” leave the designer to interpret an editorial decision.

Before handing over the proof, clarify the target passage and the expected result. Instead of “shorten the intro,” provide the final replacement paragraph. Instead of “wrong image,” identify the approved asset and say whether the crop should change.

Where useful, ask reviewers to use text replacement, insertion, or deletion annotations for precise copy corrections. Keep broader layout instructions descriptive and specific. A note about spacing may require a design judgment even when the requested text change is straightforward.

One person should own the consolidated handoff. Their role is to resolve questions with the relevant reviewers and make sure the final instructions are consistent, rather than quietly rewriting feedback to fit their own preference.

Prepare the InDesign revision round

Once the decisions are settled, identify which comments are approved, superseded, or still awaiting an answer. Keep unresolved questions visible and tell the production team whether they block the next proof.

For a native InDesign workflow, Adobe documents File > Import PDF Comments. Its PDF Comments panel can apply supported replacement, insertion, and strikethrough text edits through Accept. Other feedback still needs interpretation and manual work. Adobe also advises keeping the InDesign document unchanged after creating the review PDF for accurate comment placement.

See Adobe's import guide: https://helpx.adobe.com/indesign/desktop/collaborate-and-review/share-and-collaborate/import-pdf-comments.html.

If the source has changed since the proof went out, inspect the mapping carefully before applying corrections. Even a clear instruction can be applied to the wrong place when the review copy and source have drifted apart.

For the broader handoff, read our guide to turning PDF comments into InDesign changes: https://blog.formatstack.com/pdf-comments-to-indesign-changes.

Check the revised proof before sending it back

After applying the agreed changes, export a fresh PDF and compare it against the consolidated instructions. Check replacement text in context, then inspect the surrounding layout for new line breaks, text overflow, shifted captions, and pagination changes.

A resolved comment is a workflow status; it is not proof that the exported document looks right. Our practical InDesign revision checklist covers this final checking stage: https://blog.formatstack.com/indesign-revision-checklist.

Before releasing the next proof, confirm that:

• Every returned review file has been accounted for.

• The comments came from the correct proof version.

• Repeated requests were handled once and conflicts have an explicit decision.

• Approved wording and asset references are clear.

• Remaining questions have an owner.

• The new PDF has been checked against both the instructions and the layout.

From consolidated feedback to source file edits

Consolidation gives your team a coherent set of corrections to apply. The next step is carrying those decisions into the editable source file.

FormatStack's upcoming fully automated workflow is being built to turn annotated PDF feedback into source-file edits, starting with InDesign. Clear, agreed feedback remains essential: reviewers should settle conflicting instructions before the revision handoff.

Visit https://formatstack.com to contact us about launch availability and discuss your team's PDF-to-InDesign revision workflow.