Repro notes and defect reports
Mark the exact control, failing state, and step order so engineers do not have to infer what went wrong from a raw screenshot.
The system of record for how work actually happens.
Twelve annotation types, layered editing, separate undo for markup and styling. Built for QA reports, design review, knowledge bases, and customer support — without exporting into a second app.
“Step 2 looks ambiguous — let’s circle the disabled state.”
Arrows, steps, highlights, magnify, blur, and review markup.
Every annotation type lives on the same canvas — pick the one that actually communicates the feedback. Hover any card to play the tool.
Curved or straight arrows for direction and intent.
Plain rule with endpoint handles for connecting regions.
Auto-numbered markers for walkthroughs and repros.
Crop-style frames for areas of focus.
Soft attention rings for buttons or fields.
Marker-style sweep over text or rows.
Inline labels with full type controls.
Pixel-faithful zoom lens for detail callouts.
Measurement overlay with px / unit ticks.
Selective blur over chosen regions.
Darkened vignette that frames attention.
Pen-style scribbles for rough markup.
Annotations stay as structured layers while you work — selectable, hidable, duplicable, nudgeable. Annotation history is its own undo stack so the markup never gets trashed by a styling change.
Three short moves take a raw screenshot from inbox to inbox. No tab swaps, no “hold on, opening Figma,” no second tool just to flatten the markup.
Paste from the clipboard, drag in a file, or swap the current source while keeping the editor context intact.
Use the right overlay mix for the job: arrows for direction, steps for sequence, magnify for detail, or spotlight to frame attention.
Copy the result, export it, frame it, or turn the same marked-up canvas into a shareable style or downstream store-marketing asset.
Each persona below shows the exact annotation pattern that team actually sends — pulled straight from the toolset above.
Mark the exact control, failing state, and step order so engineers do not have to infer what went wrong from a raw screenshot.
Use text, highlights, and shape callouts to point at spacing, hierarchy, or interaction issues during design review.
Turn screenshots into process steps by layering numbered markers, notes, and emphasis rather than exporting plain captures.
Highlight exactly what a customer needs to click while redacting or blurring any information that should not travel further.
The four questions teams ask most about how the markup layer behaves — pinned to the wall and answered straight, the way you’d drop a note to a teammate.
The implementation currently includes arrow, line, rectangle, circle, text, highlight, blur, step, freehand, spotlight, magnify, and ruler annotations.
Yes. Layers remain editable while you work, so you can adjust placement, styling, visibility, and content before export.
Yes. Annotation does not sit in a separate dead-end tool. You can continue into frames, layouts, store-size presets, and exports from the same workspace.
Yes. Fyboard Shot tracks annotation undo and beautify undo separately, which is useful when you are iterating on both the markup and the final presentation.
Every track on this page has its own dedicated workspace — from quick markup to redaction, device mockups, and store listing sets — and they all share the same brand kit, canvas, and export pipeline.