If the annotation is for you, your computer already does it: Edge's Web capture (Ctrl + Shift + S) draws on a full-page screenshot, and on a Mac, Safari's File > Print > PDF opens in Preview's Markup. Chrome has no built-in annotation at all and Firefox's screenshot tool captures without drawing. But every built-in method produces a static file, so the moment someone else has to reply, all four of them stop working and you need a tool that annotates the live page.
| Method | Needs an install? | Annotates | Can someone reply? |
|---|---|---|---|
| Built-in markup | No, already there | A static capture | No |
| Browser extension | Yes, for you | The live page | Yes, once shared |
| Web annotator link | No, either side | The live page, in a tab | Yes |
| Developer tools | No | Nothing; it copies element data | No |
Pick on the last column. Everything else is detail.
Free, immediate, and the right answer whenever the annotation is for you or for someone who only has to look.
Microsoft Edge has the best built-in version on any desktop browser. Press Ctrl + Shift + S, or open the … menu in the top right and choose Web capture. Pick Capture full page to get the whole scrolling page rather than the visible part. Microsoft's own guide describes what you get next: Web capture "lets you draw on, highlight, share, or copy your capture before saving it".
macOS, in Safari, takes two steps because Safari has no markup of its own. Choose File > Print, click the PDF button at the bottom of the print dialog, and save the file. Open it in Preview and use the Markup toolbar, which gives you pen, shapes, text, highlighting and a signature tool.
iPhone and iPad have the best mobile route by a distance. Take a screenshot, tap the preview thumbnail before it disappears, then switch from Screen to Full Page. That captures the entire scrolling page as a PDF, the Markup tools work across all of it, and you save it out. If you are annotating from a phone, stop reading here: this is the method, because nearly every dedicated tool in this category is desktop only.
Windows Snipping Tool marks up well, with pen, highlighter, shapes and an eraser, and it will pull text out of an image. It has no full-page web capture, so it only ever sees what is on screen.
Two browsers do less than people expect.
Chrome ships no annotation feature at all. Print > Save as PDF produces a PDF with nothing to draw with. The DevTools command "Capture full size screenshot" produces a PNG with nothing to draw with. An article titled "how to annotate a website in Chrome" is therefore always an article about installing something, whether or not the title admits it.
Firefox Screenshots captures and does not annotate. Mozilla's own documentation is clear that the tool takes the picture; the drawing is your problem.
An extension injects the drawing tools into the page you are already looking at, in your own browser, already signed in. That last part is the whole reason the method exists.
Use it when the page is not publicly reachable: an admin panel, a client's WordPress dashboard, a staging site behind basic auth, a localhost dev server. No tool that loads the page in its own tab can reach any of those, because it arrives as an anonymous visitor and gets the login screen.
The cost is that the install is on you, and on anyone else who wants to draw rather than just read. Most tools in this category, MarkLayer included, split the difference: the person creating the annotation installs an extension, and the people receiving it need nothing.
A web annotator loads the page inside its own tab and puts the drawing surface on top. Nothing is installed anywhere. You paste a URL, mark it up, and send a link; the other person opens it in whatever browser they have and can usually reply in place.
This is the method to use when the reviewer is someone whose goodwill you are spending: a client, a stakeholder, anyone who will quietly not bother if the first step is an install or a signup. The staging-site walkthrough covers that specific handover in detail.
It has one hard limit, and it is worth knowing before you rely on it. The page has to be publicly reachable and willing to load inside another page. Checked on 29 August 2026, YouTube, Instagram, X, Facebook and TikTok all refuse. Anything behind a login is excluded by definition, which is what pushes you back to Method 2.
Right-click, Inspect, and you have the element: its selector, its computed styles, its position. Nothing is annotated and nothing is shareable, so this is not a review workflow.
It is worth knowing anyway, because the reason to identify an element precisely has changed. Handing a CSS selector and a description to a coding agent is now a normal way to get a UI change made, and a screenshot is useless for it: the agent cannot tell which of forty divs you meant. Some annotation tools now capture the selector for you and pass it along, which is the same job with the manual step removed. The localhost and AI agents walkthrough covers that path.
Every method in Section 1 ends in a file. A PNG or a PDF, sitting in a Downloads folder, attached to an email.
Files do not answer back. The person you sent it to reads your arrow pointing at the header, agrees, fixes it, and then has to tell you so in prose, because there is nowhere on the file to say "done". You reply asking which of the six things they fixed. This is the email thread the annotation was supposed to replace, and it grew back because the artefact was dead on arrival.
Files also go stale instantly. A screenshot records how the page looked at 14:32 on a Tuesday. By Thursday the page has changed, and nobody can tell whether the comment still applies without opening both and comparing. An annotation bound to an element rather than to a coordinate survives that, which is why the tools worth paying for anchor to the element and not to a pixel position.
So the decision rule is short. Annotating for yourself, or for someone who only has to look: use the built-in method, it is free and already installed. Annotating for someone who has to respond: none of the built-in methods will do, and the choice becomes which tool, which is a separate and longer question.
Pages behind a login defeat every method except the extension.
Sites that refuse to be embedded defeat the share-link method specifically. The big social platforms are the ones you will hit.
Phones defeat almost everything except Apple's built-in Full Page capture. The dedicated tools in this category are overwhelmingly desktop only, MarkLayer included, and marklayer.app will say so if you open it on a phone.
Very long pages defeat the naive screenshot. If the page scrolls, you need a full-page capture, and only Edge and iOS have one built in that you can then draw on.
Retention defeats you later rather than now. A link that expires takes the review round with it. Whatever tool you pick, find out how long it keeps the work before you put a client on it; most vendors do not publish an answer.
For a full price and feature comparison of the tools behind Methods 2 and 3, including what each one keeps and for how long, see twenty-one website feedback tools compared. For how MarkLayer specifically handles links, drafts and deletion, see how MarkLayer works.
MarkLayer is free, requires no sign-up, and works on any webpage. Recipients of your share links don't need to install anything.
Add to Chrome