An unmarked screenshot says “look here” only if the recipient already knows where to look. Annotation is what turns a capture into communication: an arrow at the error, a box around the region, a blur over the sensitive field. On macOS you have three realistic tools for it, each with a different speed profile.

Tool 1: The capture thumbnail (fastest, shortest window)

After any ⌘⇧3 or ⌘⇧4 capture, a thumbnail appears in the bottom-right corner for about five seconds. Click it and macOS opens its quick markup editor:

  • Pen, text, shapes (rectangle, ellipse, line, arrow)
  • Highlighter
  • Signatures
  • Save to file or share via the share sheet

The catch: the window is short. If you’re still positioning your cursor when the thumbnail fades, the annotation opportunity is gone and you fall back to Preview. For deliberate captures this works; for a fast daily loop it’s fragile.

If you keep missing it, ⌘⇧5 → Options → Show floating thumbnail turns the thumbnail off entirely, and the file saves straight to disk. That trades the annotation window for no second chance at all, so it’s a setting worth trying before you give up on the built-in flow.

Tool 2: Preview (most capable, slowest)

Open the saved PNG in Preview and use the markup toolbar (the icon in the top-right of the window, or Tools → Annotate). You get the full markup set plus rotation, cropping, and PDF support.

  • Good for: careful edits, multiple rounds of marking, anything you’ll reuse.
  • Bad for: speed. Opening Preview, finding the file, loading the image adds several seconds per screenshot, which compounds quickly when you’re taking ten in an afternoon.

Tool 3: A menu bar capture app with an instant editor

This is where the workflow difference shows up. In Shotivo, the annotation editor opens the instant you release the region drag. There is no thumbnail to catch and no app to launch. The toolset:

Tool Use for
Pen Freehand marks, circling something by hand
Arrow “This specific thing”, the workhorse of bug reports
Rectangle Bounding a region or UI element
Ellipse Softer emphasis than a rectangle
Text Labels: step numbers, field names, expected vs actual
Blur Hiding sensitive data before the image leaves your machine
Line Connecting two points with a straight stroke
Highlight A wide marker stroke in the current colour, to draw the eye to a row or label
Pixelate Hiding exact values such as tokens, keys and numbers behind coarse blocks
Crop Tightening the shot after capture
Undo / Redo Recovery from fat-finger strokes

The editor is deliberately lightweight. It’s not a photo editor. No filters, no layers, no color management. The goal is to go from “captured” to “communicates clearly” in one or two seconds.

Annotation patterns that actually help

Bug reports

Writing Better Bug Reports has the full template; the annotation side of it:

  1. Arrow at the exact element that misbehaves. One arrow beats three paragraphs.
  2. Text label with the repro step number if the report has multiple steps: ① click here, ② this appears.
  3. Blur anything sensitive, like tokens, customer names, and internal URLs, before sharing. Blur before upload, never after; once an unblurred version is online it’s gone.
  4. Crop to the relevant region. A full-screen shot with a tiny arrow is harder to read on mobile than a tight crop.

Design and product feedback

  • Rectangle + short text (“spacing feels tight”, “this wraps awkwardly”) beats vague “make it pop”.
  • Numbered annotations let you reference them in comments: “see 2”.
  • Keep strokes thin and high-contrast (red or blue on light UI) so they read at thumbnail size.

Support requests

  • Show the state before and after if it’s a transition bug; two annotated shots beat one.
  • Include the error message unblurred but blur everything around it.
  • The share page’s metadata (dimensions, file size) helps support confirm they’re looking at the same build/resolution.

Speed comparison (typical, per screenshot)

Path Approximate time to annotated image
⌘⇧4 → catch thumbnail → mark up 5 to 10 s (if you catch it)
⌘⇧4 → open Preview → mark up 10 to 20 s
Menu bar app: global shortcut → drag → tools → done 3 to 6 s

The last row is why a dedicated utility earns its place in the menu bar: the annotation step stops being a separate task and becomes part of the capture motion itself.

Practical tips

  • Build muscle memory for two tools only. Arrow and blur cover 90% of real-world annotation.
  • Set a default stroke color that contrasts with most UIs (red on light, yellow on dark).
  • Blur first, share second. Make it a hard rule; exceptions are how sensitive data leaks.
  • Crop generously after annotating. Remove empty margins so the annotation carries more of the frame.