You spent years on Greenshot muscle memory: tap a hotkey, grab a region, scribble an arrow, save to a folder you named yourself. Then IT reimaged your laptop and the install is gone, with no admin rights to put it back. A browser capture tool fills the gap, but some of your old habits carry over and some quietly work against you. Here is where the line falls.
Reaching for a global hotkey that no longer exists
In Greenshot, Print Screen triggered the capture from anywhere. The reflex is to hit a key and expect a region selector. A browser tool cannot bind a system hotkey, because it is a web page, not a background process with OS permissions. Tapping Print Screen out of habit just copies a full-screen image to your clipboard and leaves it there.
The correction is to lean into that. Hit your normal OS screenshot key, then paste straight into the review. In a no-install Greenshot alternative, you open a tab, paste the image, and it becomes an item you can mark up. Or click Capture screen and let the browser prompt you to share a window. Either path lands in the same place. Drop the expectation of a global hotkey; keep the instinct to capture fast.
Saving every shot to a local folder
The Greenshot habit was a tidy folder of PNGs with timestamps, your personal archive. On a managed laptop that folder is often the thing getting wiped, synced to a drive you do not control, or blocked by policy. Worse, a local file does nobody else any good. Whoever needs to act on the bug still has to receive it, and a PNG buried in Downloads is not a handoff.
Replace the folder with a link. When you Publish, the review gets a short /r/<slug> address anyone can open, plus a read-only /s/<slug> page for people who just need to read it. The image, your pins, and your comment travel together. If you want the old archive feeling, exports to PDF and Word are there, and so is a clean markdown version at /r/<slug>/markdown. You stop managing files and start sending something the receiver can act on.
Annotating in isolation, then explaining in a separate message
Greenshot gave you arrows, boxes, and text on the image, which is great, but the explanation always lived somewhere else: a Slack message, an email, a ticket you pasted the PNG into. The annotation said where, the message said what, and the two drifted apart. The reader had to stitch them back together.
Keep the annotation habit. Arrows, boxes, circles, numbered pins, and short single-line labels in bright colors all survive the move, and pins and drawings are baked into the exported image so the receiver sees exactly what you marked. What changes is where the words go. Attach your comment to the same item, by typing or by dictating with the browser's built-in speech recognition in Chrome or Edge. One item carries the mark and the explanation. For pointing cleanly, a numbered pin on the exact spot beats a vague arrow and a paragraph of "the button near the top right."
Treating the screenshot as the final deliverable
In the old flow, the annotated PNG was the end product. You handed it over and hoped. But a flat image gives the reader nowhere to respond. They cannot ask a question on item two or tell you item three is already fixed without starting a new thread.
The correction is to let the shot be a living item, not a dead file. People with the review link can comment on any individual item, and you can mark each comment resolved as it gets handled. That turns a one-way drop into a short loop without pulling in a bug tracker. If you want to see how a review reads from the other side, what your client sees on a review link walks through it.
Expecting the same capture flow on your phone
Greenshot was a desktop tool, so the phone question never came up. Now your reviewer might be a founder checking a staging link on an iPhone. Phone browsers cannot capture the screen directly, and a Greenshot-era assumption that capture always means "grab the window" leaves phone users stuck.
On a phone, take a normal screenshot with the OS, then add it: paste, drag and drop, or use Add image. The rest of the flow is identical. Pins, a comment, Publish, share. If your team splits across devices, a designer on desktop and a client on a phone can work from the same review without either learning a new app.
Forgetting that the cost model changed
Greenshot was a free download you installed once. A browser tool has its own shape, and pretending it is just "free" would be dishonest. Trying it costs nothing: unlimited reviews and screenshots, no password, no credit card. Cobalt asks for an email when a review is ready so it can send you the link. After 7 days a review goes read-only for you, meaning editing, exports, and agent access stop, though the shared link keeps working for everyone you sent it to and nothing is deleted. Pro is $5 a month or $50 a year to keep every review editable with no cutoff, and you can cancel any time. The full pricing details are worth a two-minute read before you commit to the workflow.
Next time you hit a bug on the locked-down laptop, skip the reinstall request. Open a tab and start a review, paste your screenshot, pin the spot, and send the link.