To share an annotated web page, capture the page with its annotations and send that single image to your team — pasted into your chat tool, attached to a ticket, or dropped in a doc. The annotations travel inside the image, so nobody needs the extension, an account, or the same browser to read them.
The review that arrives in twelve pieces
You have gone through the whole homepage. Nine notes, four arrows, two highlights. Now you have to get it to the developer. So you send nine screenshots, or one screenshot with a nine-item list, or you paste the whole thing into a doc and re-describe every mark you already drew. The review took twenty minutes; packaging it takes another twenty.
Why the handoff is where feedback dies
Every extra step between "I saw the problem" and "my teammate saw the problem" is a place where detail leaks out.
- Re-describing annotations in text undoes the reason you drew them.
- A dozen loose images in a thread lose their order and their page context.
- Feedback split across email, chat, and a doc means nobody knows which list is current.
- Tools that require the recipient to sign up guarantee some recipients never look.
Why "just send a link" is not the answer here
The obvious idea is a shareable URL that replays your annotations on the live page. It sounds better than an image, and for some products it is — but it comes with a bill: your annotations, and often a copy of the page, have to live on someone else's server, the recipient needs an account or at least a session, and the link breaks the moment the underlying page ships a change. A flat capture has none of that. It is readable by anyone, forever, in any tool, and it shows the page exactly as it was when you reviewed it. For a review that needs to be acted on this week, that is usually the better trade.
Capture the right thing, not everything
The single biggest quality lever in sharing annotations is what you frame. With Highlite, the export panel (⌘⇧E) asks for the capture region before the destination:
- Viewport — the whole visible page. Right when the feedback is about layout, rhythm, or how sections read together.
- Selection — drag a box around one component. Right when the feedback is about a single element, because cropping is itself a form of pointing.
- Then pick the destination: copy to clipboard to paste anywhere, download the image to attach to a ticket, or send it straight to a Slack channel.
One capture per topic beats one capture for the whole review. A developer can pick up "the pricing card" and close it; they cannot close "the homepage".
Rule of thumb: if your capture needs an ordered list underneath to be understood, split it into one capture per item.
Handing the annotations themselves to a teammate
Sometimes an image is not enough — a teammate needs to continue the review rather than read it. Highlite can export the annotations of a page as a JSON file, which someone else imports to get your notes, arrows, and highlights back on the live page in their own browser. Export is part of the paid Pro plan; importing a file you were sent is free, so a Pro reviewer can always hand off to a free teammate.
Note what this is not: it is a file you send, not a synced workspace. There is no live cursor, no comment thread, no notification. It is deliberately the same shape as sending a document.
A design review on a client staging site: four region captures — hero, pricing table, testimonial block, footer — each with its own notes and arrows, pasted as four separate messages in the project channel under one short heading. The developer works down the channel and ticks them off. Nothing was uploaded to a third-party service, and the client never had to create an account to read the feedback.
Sharing checklist
- One topic per capture, framed tightly around the element it concerns.
- Say what page and what environment in the message — staging and production look identical in an image.
- Keep the annotation legible at Slack preview size: fewer, bigger marks beat many small ones.
- Send to the place the work actually happens — the ticket tracker, not a stray DM.
- Say what you want done. An annotated page shows what is wrong; the message says whether it blocks release.
For the Slack path in detail, see sending an annotated screenshot to Slack. For running the review itself, see giving crystal-clear visual feedback to your developers.
Frequently asked questions
Does the person I share with need the extension?
No. If you share a capture, they are looking at an ordinary image and need nothing installed. The extension is only required if you send them the annotations as a file to reopen on the live page.
Can I share a link to an annotated page?
Highlite does not host your annotations, so there is no public replay link. Annotations stay in your browser and are shared as a capture you send, or as an annotation file a teammate imports. That is the trade-off for nothing leaving your machine until you decide.
Should I capture the full page or just a region?
Capture a region when the feedback is about one component, and the viewport when it is about layout or hierarchy. Region captures get acted on faster because the crop already tells the reader where to look.
Is sharing annotated pages free?
Annotating, capturing, copying to the clipboard, and downloading the image are free and need no account. Sending directly to Slack and exporting annotations as a JSON file are Pro features.
Try the loop on this page: mark up this section, capture just that region, and paste it to a teammate. The whole round trip is under thirty seconds.