Product

Editor & annotations

A raw capture is usually good enough to send. When it is not, the editor lets you rewrite, reorder, and draw on it without losing the original screenshot.

Editing guide

Make it exactly right

โžก๏ธ
AnnotateArrows, boxes, highlights, numbers, text, and blur, drawn directly on any screenshot.
โ†•๏ธ
Reorder in placeDrag steps to reorder and the numbering follows. Edit instructions inline.
๐Ÿ’ก
Tips & alertsAttach a callout to any step so readers catch the gotcha that is invisible to them.

What the editor gives you

Seven annotation types, stored as regions

Annotations are saved as regions rather than baked into the pixels, so you can move or delete one later and the original screenshot is still underneath.

  • click-target: the highlight Knovvy places automatically on what you clicked.
  • arrow and box: point at something, or frame it.
  • highlight: a translucent wash over a region.
  • blur: obscure anything auto-blur could not detect.
  • text and number: labels and sequence markers on the image.
The blur you still have to do yourself

Auto-blur catches form fields, because that is what the DOM describes as sensitive. A secret rendered as page text, an API key shown after you generate it, a customer name in a table, is not detected. Drop a blur region on it here.

Editing steps
  • Rewrite any instruction inline. The text and its screenshot stay tied together.
  • Delete a stray click on the way to the real action.
  • Attach a tip or a warning callout to a step.
  • Rename the guide if the auto-generated title is close but not right.
When to re-record instead

If the underlying tool changed enough that half the screenshots are wrong, capturing again is faster than repairing. A fresh capture costs about two minutes and is correct by construction. That economics is the whole argument in why SOPs go stale.

Ready to capture the know-how?