Pinned Comments vs Threaded Comments: Which Works Better for Creative Review?

The debate usually surfaces when a team switches tools. Someone asks: "Should comments be pinned to the design or just listed in a thread?" Then the room splits — designers prefer pins, account managers prefer threads — and the decision gets made by whoever talks loudest rather than what actually fits the work.

This is not a preference question. It is a workflow question. The right format depends on the type of creative being reviewed and the stage of the review cycle. Use the wrong one and you get comments that do not communicate, or a visual layer so dense with pins that the ad underneath is invisible.

What Pinned Comments Actually Do

A pinned comment is attached to a specific coordinate on the creative. The reviewer clicks on the element they are referencing — the CTA button, the headline, the logo position — and the comment appears anchored to that spot. Anyone reading the comment sees exactly what prompted it, without the reviewer having to describe the location in words.

This solves the spatial ambiguity problem that makes creative feedback so exhausting. "The copy in the lower-right quadrant" and "the green button near the bottom" both become unnecessary when the comment is pinned to the exact element. The pin is the description.

Pinned comments are most powerful for:

• HTML5 banner feedback where specific elements need precise revision instructions
• Static display ads where layout, typography, and visual hierarchy are the primary concerns
• First and second revision rounds where the feedback is still granular and element-specific
• Multi-format campaigns where different comments apply to different ad sizes

Where Pinned Comments Break Down

Pins have a density problem. On a 300x250 banner with 15 pieces of feedback, the pin layer becomes its own visual nightmare. Reviewers struggle to distinguish which pin is which, comments overlap, and the process of reading the full set of notes becomes as frustrating as reading them out of context would have been.

Pinned comments also fail when the feedback is not spatial. "The overall tone of this ad is too aggressive for our brand" cannot be pinned to a coordinate. Neither can "I want to reconsider the strategic direction before we go further with this concept." These are conversation-level notes that belong in a thread, not a pin.

A third failure mode: pins are hard to resolve collaboratively. When two stakeholders disagree about a design decision, the back-and-forth discussion does not work well as a series of pins stacked on the same pixel. Threaded replies, where the conversation is clearly sequential, handle disagreement better.

What Threaded Comments Actually Do

A threaded comment exists in a list alongside the creative, not on top of it. The creative is visible in its complete form while the thread runs beside or below it. Replies are clearly sequential — response to response to response — making the discussion easy to follow without spatial confusion.

Threads work well for:

• Strategic or directional feedback that applies to the whole piece, not a specific element
• Late-stage approval rounds where the main creative is settled and notes are holistic
• Multi-stakeholder review where several people are contributing to the same discussion
• Video feedback where the timeline, not spatial coordinates, is the relevant reference point

The Comparison Framework

Scenario	Best Format	Why
Specific element revision (button color, headline font)	Pinned	Location is the context. No description needed.
Overall brand tone or strategic direction	Threaded	No single element to pin. The feedback applies to the whole.
Video ad revision (pacing, music, voiceover)	Time-coded thread	Timestamp replaces spatial pin. Thread handles discussion.
First-round concept feedback (early-stage)	Threaded	Concept-level discussion; spatial precision is premature.
Final pre-approval polish (spacing, alignment)	Pinned	Pixel-level notes need precise coordinates.
Multi-stakeholder consensus discussion	Threaded	Sequential replies make the decision trail legible.

The Hybrid Approach Most Mature Teams Use

The teams with the cleanest review cycles do not pick one format and commit. They establish a convention: pins for element-specific revision instructions, threads for anything that requires discussion or applies to the whole piece.

This distinction is usually communicated in the review link briefing: "Use pins for specific element changes. Leave a comment in the thread for anything about direction or tone." It takes one sentence to frame and saves hours of parsing mixed-context notes.

Some review platforms support both formats in the same interface — the reviewer chooses which type to leave based on what they are commenting on. This is the ideal setup because it puts the decision at the point of feedback rather than requiring an upfront system everyone has to remember.

How This Changes Across Review Stages

Review stage matters as much as creative type. Early-stage concept review should lean heavily threaded — the work is not refined enough for element-specific pins, and the discussion is still directional. Mid-stage revision rounds benefit from a mix: threads for anything structural, pins for the execution details. Final approval rounds should be almost entirely pinned — at that stage, every note should be a specific, actionable, locatable change.

If you are getting threaded notes in a final approval round, that is a signal the creative is not actually ready for approval. The note type reflects the review stage. Vague or holistic feedback in round three means something did not get resolved in rounds one and two.

Where Adhipo Fits

Adhipo supports both pinned and threaded commenting in the same review workspace — on HTML5 banners, static display ads, and video ads. Clients and reviewers can leave a pin directly on a banner element or drop a general comment in the thread without switching tools or views. For agencies managing multi-format campaigns where both feedback modes are needed in a single review session, this removes the friction of routing different types of notes to different places. See how review works in Adhipo.

Stop Arguing About the Tool. Start Arguing About the Convention.

Whether pins or threads are "better" is the wrong question. The question is whether your team has an explicit convention for which to use when — and whether clients understand it before they open the review link. The format is not the problem. Inconsistency is. Pick the framework that matches your creative types and review stages, write it down in your onboarding process, and stop relitigating it every campaign.