A website markup tool lets you draw arrows, boxes and text, and blur sensitive areas, directly on a web page or a page screenshot — turning "this is wrong" into visual feedback that carries positional information. It solves a communication problem: the person looking no longer has to guess which element you mean. It does not collect requirements, assign tasks or track status; that is the job of feedback tools and defect trackers.
Draw the boundary first. If what you need is "collect feedback and follow it through to closure", see website feedback tools compared. If what you need is "mark it on the page so the other side gets it at a glance", this article is enough.
Three categories of tools, kept apart
| Type | How it works | Typical use | Trade-off |
|---|---|---|---|
| Screenshot annotation | Capture an image, draw on it, save it or paste it into chat | One-off communication, pointing a colleague at a spot | The image is static; it goes stale as soon as the page changes |
| Page annotation + share link | Annotate the live page and generate a link for others to view | Design review, client walkthroughs, cross-company feedback | Needs an extension, script or proxy to load the page; dynamic pages can misalign |
| Annotation + dispatch | The annotation becomes a task, ticket or message | Teams that need to follow through to closure | Heavier process, more configuration |
The three are not a ranking; their outputs differ: the first produces an image, the second a link, the third a traceable record.
Six selection criteria
| Criterion | What to look at | Why it matters |
|---|---|---|
| Annotation tools | Arrow, rectangle, text, brush, mosaic | Different issues need different marks; blurring is essential before sharing |
| Capture range | Region, full page, delayed capture | Long pages and dynamic content are the easiest to capture wrong |
| Annotation target | Screenshot or live page | The live page is more accurate, but dynamic content can misalign |
| Sharing | Link, image, login required | Clients refusing to sign up is the biggest drop-off point |
| Environment data | URL, viewport, browser, console, failed requests | Without it, developers ask another round of questions |
| After annotation | Stays in the tool, goes to IM, a spreadsheet or a tracker | Decides whether it actually gets handled |
If you can keep only three: can the client view it without logging in, does the annotation make the position clear, and does anyone act on it afterwards.
Eight tools, grouped by category
Below I only describe publicly verifiable form factors and use cases — no pricing, and no verdict on which is better. Tools change; verify on the spot with the self-test process below before choosing.
Screenshots and lightweight annotation
Awesome Screenshot. A browser extension focused on screenshots, annotation and quick sharing; good for capturing an issue and sending it to a colleague. Its strength is speed, and it is not built for scenarios that need long-term tracking.
Page annotation and sharing
Markup.io. Primarily annotates web pages and files, then generates a share link; good for design review, content proofreading and client communication.
Pastel (Usepastel). Annotation and feedback for web projects, emphasizing annotation on the live page and collecting opinions; good for back-and-forth between agencies and clients.
Ruttl. Annotation on pages and design files, with direct on-page comments; leans toward review workflows and version comparison.
Annotation that needs dispatching
BugHerd. Browser extension plus a task board; annotations land in a to-do list, good for turning client feedback straight into development tasks.
Marker.io. A browser extension that sends annotated feedback with page data into the team's existing tools; good for teams that already have a system of record and only lack an entry point.
Jam.dev. Primarily screen recording with technical details attached; good for bugs with long reproduction steps where the process matters.
BugCapturer. A browser extension: after a screenshot or recording, annotate with five tools — arrow, rectangle, text, brush and mosaic. Reports automatically include the page URL, viewport, browser and OS, console errors and failed requests, generate a share link that opens without installing anything, and can push to Slack, Microsoft Teams, Lark and generic webhooks.
One comparison table
| Tool | Form | Annotation target | Sharing | Best for |
|---|---|---|---|---|
| Awesome Screenshot | Browser extension | Screenshot | Image / link | Fast screenshot-based communication |
| Markup.io | Web app | Page / files | Share link | Design and content review |
| Pastel | Web app | Page | Share link | Client walkthroughs |
| Ruttl | Web app | Page / design files | Share link | Review and version comparison |
| BugHerd | Extension + board | Page | Link + tasks | Turning feedback into tasks |
| Marker.io | Browser extension | Page | Link + push | Teams with a system of record |
| Jam.dev | Browser extension | Recording | Link | Reproducing a process |
| BugCapturer | Browser extension | Screenshot / recording | Link + push | Capture + annotate + dispatch |
This table only settles "which few to look at first"; it does not replace self-testing. Below is a 30-minute validation flow.
When a screenshot tool is enough
This category is only credible if we argue for not switching:
- One-off communication: you just need to tell a colleague "this button is off"; a marked-up screenshot is fastest.
- You want the image, not a workflow: the other side doesn't need to reply, track status or archive anything.
- Extensions are banned at the company: if only the built-in screenshot tool is allowed, put the annotation and the explanation in the message.
- The page holds sensitive data: if you don't want a third-party tool touching page content, capture locally, annotate, then send.
In these four cases, adding a platform only adds overhead.
Four steps after annotating
Annotation is only the beginning. Feedback that actually gets handled usually needs four more steps:
These four steps are the same thing as the report format; see the bug report format, and for the fix-and-verify loop see how to fix bugs.
A 30-minute self-test: five things
Don't just look at screenshots on the vendor site. Run through it on your own pages:
The fifth matters most. A markup tool succeeds not by how pretty the drawing is, but by whether the next person can start work from that record alone.
Frequently asked questions
Is there a difference between markup and annotation? The market uses them interchangeably. Roughly: markup leans toward "marking up the page", annotation toward "adding notes to content". Don't agonize over the words; first confirm whether the output is an image, a link or a traceable record.
Can I annotate someone else's website? Yes, usually through a browser extension or bookmarklet, in your own browser. Two caveats: don't annotate pages containing personal data and share them publicly; dynamic pages can misalign because of load order.
What if the client won't install an extension? Choose a flow where you annotate and the other side opens the link without logging in; or capture, annotate and send. Asking clients to install something is the most common friction point in a review workflow.
Do annotations get lost? It depends on storage and link expiry. Export important annotations as an image at least once, or get them into a task system; annotations that live only in a local browser are gone when you switch devices.
How is this different from Figma comments? Figma comments live on design files and suit the design stage; page annotation happens on the live page and can carry the browser, viewport and runtime errors. They hand off to each other; they don't replace each other.
If what you need is "annotate the live page and have the annotation carry environment data", start with the browser extension; when you're done, it generates a share link and the other side installs nothing. To work out how screenshot tools and feedback tools divide the labor, see how to choose a Chrome screenshot extension. To practice the method first, see how to annotate a website and screenshot annotation best practices. To review a whole site rather than mark one spot, see how to review a website.