Topic
The free tools built into the Demorta extension -- an area screenshot with an annotation editor, and save-page-as-HTML -- and everything around them: how to capture a dropdown or a tooltip, how to blur a name, how to add an arrow, and how each team uses the result.
30 guides
The Snipping Tool is fine until the thing you are capturing is a web page you also need to edit. Then a browser tool is quicker.
Documentation screenshots age badly and look inconsistent. A few rules fix most of it.
An arrow is the most-used and most-misused screenshot mark. Here is how to draw one, and where to point it.
Text on a screenshot fails in one of two ways: too much of it, or unreadable against the background. Both are avoidable.
An arrow, a box and a blur cover almost every screenshot you will ever send. Here is how to use them well.
Blurring is a security step, not a cosmetic one. Here is how to do it so the data is actually gone.
Pages change and disappear. Here is how to keep the one you are looking at, in a format you can still open later.
Most screenshots are pasted, not saved. Here is how to skip the file entirely.
The best crop is the one you never have to do. The second best is the one that does not need another app.
Pixelation is the blur that cannot be undone. Here is how to apply it to part of an image in seconds.
Save As gives you a folder of fragments or a format nothing opens. Here is how to get one file that actually works.
A chart pasted into a slide should look like it belongs there. That is mostly about how it was captured.
Press the screenshot key and the menu disappears. Here is how to get it before it goes.
The tooltip is only there while the pointer is. Capture it without moving the pointer.
Any screenshot of a logged-in page is a screenshot of your account. Treat it that way.
The error is the most important thing on the screen and the easiest to capture badly. A short checklist.
You rarely want the whole tab. Here is how to grab only the bit that matters, on Windows and Mac.
Chrome can screenshot more than people think, including the whole page. It is just hidden in DevTools.
A good bug report screenshot removes the first three questions the developer would ask. Here is what goes in it.
A watermark on a screenshot you are sending to a customer is a small embarrassment every time. Here is how to avoid it.
Both are captures of your product. They answer different questions.
Half of support is pointing at a button. An annotated screenshot does it in one reply.
"The spacing feels off" is not feedback. A box around the spacing is.
A freelancer’s screenshots are seen by paying clients. They should look like it.
PMs produce more screenshots than anyone and rarely think about them. Three habits fix most of it.
A defect report is only as good as its evidence. Here is what QA screenshots need to contain.
A good screenshot cuts a support thread by two replies. A bad one adds three.
A screenshot in a slide is read from six metres away. Most are captured for a screen thirty centimetres away.
A screenshot of the thing they asked about beats a polished graphic of the thing you sell.
Three formats, three jobs. Most people use the wrong one out of habit.