For pure visual sign-off, Pastel and Markup.io are the most direct. If you want the comment to hit the exact element, capture its selector and turn into a tracked task in a board, pick Couac.
Search intent
The reader wants to drop comments directly on a web page, usually during acceptance testing or a design review with a client or team.
Selection criteria
Annotating without making the client install anything
Your client will not create an account or add a Chrome extension just to tell you the button overflows. Look at how the other side annotates: is a plain link enough, or is there onboarding first? The more invisible it is, the more feedback you actually collect.
What the pin actually attaches to
A dot dropped somewhere on the page is a treasure hunt for your dev. A good tool targets the exact DOM element, not a rough zone. Some go further and keep the CSS selector, so the dev opens the inspector and lands right on the node. Ask yourself: does the feedback point at a coordinate, or at an identifiable element?
What the pin becomes when the layout shifts
An annotation dropped on desktop should still read when someone reopens the page on mobile, or after a deploy. If the pin is frozen to pixels, it drifts and the comment floats in empty space. Check how the tool re-anchors feedback in responsive: to a stable element, or to a screen point that no longer means anything.
The path from comment to task
This is where tools split. Some stop at a discussion thread under the red dot. Others open a status, a priority, an assignee, a due date. Follow the route of the feedback: does it stay an isolated bubble, or become a card that a specific person has to handle and close?
Tools to compare
Couac
Best for: Web teams and agencies whose annotations end up as bug fixes, not just design notes.
The client clicks the page through a JS widget and points at the spot; Couac targets the exact DOM element, keeps its selector, then attaches the URL, device, console and network. The annotation does not stay a bubble: it becomes a ticket in an internal Kanban board, with status and assignee. REST API, signed webhooks and a native MCP server to wire in the rest, magic-link shared boards so the client comments with no account.
It is not a creative approval tool. If you want to annotate PDFs, videos or static mockups alongside the web, look elsewhere.
Pastel
Best for: Agencies getting sites and mockups signed off by a non-technical client.
Paste a URL, share a link, and the client clicks and comments right on the rendered page. No account needed on their side, it is fast and readable. Feedback stays mostly a comment thread on the page, built for creative review and client go-ahead.
Targeting stays at the level of the clicked zone, with no element selector. For a dev to attack the right node, they will often have to find it by hand.
Markup.io
Best for: Multi-format reviews where the web is just one asset among many (images, PDFs, videos).
Very versatile: you annotate a live site but also files, PDFs and videos in one place, with a task-management layer to track feedback. Handy when a project mixes web and print deliverables.
That breadth has a cost: for pure targeting of a single web-page element it is less precise than a dedicated tool. Check what the pin actually attaches to.
BugHerd
Best for: Fix-oriented website QA with a built-in board.
Probably the closest to Couac on intent: on-page annotation that points at the targeted element, then a ticket organised in an internal kanban with an assignee. Mature and well-worn for turning feedback into a tracked QA task.
Annotation often goes through a browser extension, real friction for an occasional client who just wants to click and comment.
zipBoard
Best for: QA on large web and e-learning projects with many reviewers.
Built to handle volume: web annotation that turns into a tracked bug, a ticket board, and a soft spot for e-learning content (SCORM) and PDFs. Good when several teams comment on the same deliverable and you need to know who handles what.
The interface can feel busy for a simple client back-and-forth. Fine targeting of a precise element is still more of a dedicated-QA-tool job.
Ziflow
Best for: Creative studios that need formal approvals with sign-off stages.
It is proofing first: annotation on web, images and videos, approval workflows, versions and sign-offs. The annotation becomes a tracked approval step more than a fix task.
Focused on creative sign-off, not bug fixing. The comment points at a zone to approve, not a DOM element a dev has to go fix.
Pointing at a zone, or pointing at an element
Two tools can show the same red dot and capture two radically different things. The first remembers a coordinate: "click 412 pixels from the top". Pretty on the screenshot, useless the moment the page changes. The second targets the DOM element under the cursor: this button, this field, this block, with its selector. The difference shows up the day your dev gets the feedback. With a coordinate, they reopen the page, scroll, guess. With a selector, they open the inspector and land right on the node. When you test a tool, do not look at whether the pin is pretty; look at what it actually stores behind it. That is what decides whether the comment is still usable a week later, on another screen, after a deploy.
The life of a comment after the click
Drop a piece of feedback and follow it with your eyes. In some tools it stops dead: a bubble stuck to the page, a reply thread, and that is it. As long as everyone lives in the tool it holds; the moment the work happens elsewhere, the feedback gets lost. In others, the comment changes nature: it takes a status (new, in progress, fixed), a priority, an assignee, and lands in a board column. That is exactly the route feedback takes in Couac: the client points at the element, and the annotation becomes a Kanban card you assign, comment on and close. So before comparing features, look at one thing: does the comment stay a note glued to a page, or become a task someone owns?
Testing precision in one afternoon
Do not trust feature pages, test on a real case. Take a recent, well-located bug, say a form field that misbehaves. Annotate it with the tool, exactly the way your client would, from a device you do not control. Then copy the feedback link, open it on another screen, and check whether the pin still points at the right element. Ask three questions. Could the client comment without an account or an install? Does the feedback hit the exact element, or just a page zone? And did the comment become an assignable task, or stay an isolated thread? If all three answers suit you, you have your tool.
Frequently asked questions
Pastel or Couac to get a site approved by a client?
If the client just needs to say "ok" or "nudge that heading", Pastel is simpler: one link, no account, comment on the rendered page. If their remarks point at a precise bug your dev has to fix, Couac targets the exact element, keeps its selector, and turns the comment into an assigned task in a board.
How does the tool know which element I clicked on?
It all depends on what it records. Basic tools keep a coordinate on the page image. The more precise ones walk up the DOM and identify the clicked element, sometimes down to the CSS selector. Couac does that targeting on the widget side: the red dot is not a screen position, it is the element itself, which keeps it findable even after a layout change.
Once the comment is dropped, who picks it up?
That is the difference that matters. In a thread-based tool, the feedback waits to be read. In a task-oriented tool, it gets a status and an owner. Couac files each annotation as a card in an internal Kanban board, with assignment and tracking, and exposes it through a REST API, signed webhooks and a native MCP server to push it into your other systems if needed.