Capture it, mark it up, ship it — screenshots that actually explain themselves.
TL;DR: This is the annotation layer Windows should have shipped a decade ago.
Let's be honest — the built-in Snipping Tool is a crayon in a world that needs a fountain pen. screenshot-annotator-editor exists because every developer, support agent, QA tester, and PM I've ever worked with ends up doing the same dumb dance: screenshot → paste into Paint → squint → draw a wobbly red circle → export → apologize for the wobbly red circle. This tool kills that dance dead. It's a purpose-built screenshot annotator and editor for Windows that treats markup as a first-class citizen, not an afterthought bolted onto a capture utility.
Under the hood, this is a desktop editor tuned specifically for the annotate-and-share workflow: arrows that actually point where you meant, blur tools for redacting secrets before they end up in a public Slack channel, numbered step markers for documentation, and text callouts that don't look like they were typed on a flip phone. It's for the technical writer building a knowledge base, the support engineer triaging fifty tickets a day, the developer filing a bug report nobody can misread, and the designer who just needs to leave one (1) comment on a mockup without opening a whole design suite.
The philosophy is simple: screenshots are communication, not just pixels. A raw capture tells you what happened. An annotated one tells you what matters. This project is entirely about that gap — closing it fast, closing it cleanly, and closing it without fifteen menus standing between you and a finished image.
TL;DR: click the button below, run the exe, start annotating. That's the whole onboarding.
Tip
Pin it to your taskbar after the first run. If you're capturing screenshots more than twice a day, a one-click launch pays for itself by Wednesday.
TL;DR: capture, annotate, redact, export — with tools that don't fight you.
-
Region, window, and full-desktop capture — grab exactly the pixels you need, not the entire 4K canvas plus your cluttered desktop icons.
-
Vector-based annotation layer — arrows, boxes, ellipses, freehand pen, and highlighter strokes that stay crisp and re-editable until you flatten the export, not baked-in bitmap scribbles.
-
One-click blur and pixelate redaction — because API keys, emails, and account numbers do not belong in your public GitHub issue screenshots (yes, this happens more than anyone admits).
-
Numbered step markers — auto-incrementing badges for building tutorials and how-to docs without manually typing "1, 2, 3" into text boxes like it's 2009.
-
Smart text callouts — speech-bubble and label tools with auto-sizing backgrounds so your text is always legible, even over a busy background.
-
Multi-layer undo/redo history — a real edit stack, not a single "undo last thing" button that forgets everything after your third click.
-
Instant clipboard round-trip — capture, annotate, copy — paste directly into your ticketing system, chat, or doc without ever touching a "Save As" dialog.
-
Custom color palettes and stroke presets — save your team's brand colors once and stop re-picking the same shade of red every single time.
Note
Every annotation is non-destructive until export. Change your mind about that arrow color three edits later? Go for it. Nothing is locked in until you hit export.
TL;DR: four steps, zero dependencies, no accounts required.
-
Hit the Download button above — it routes to the official landing page.
-
Run the standalone executable. No installer wizard interrogating you about optional toolbars.
-
Trigger a capture with the global hotkey (default:
Ctrl+Shift+S) or launch from the tray icon. -
Annotate using the floating toolbar, then export, copy, or save — your call.
That's it. There is no step 5. If you find yourself hunting for a step 5, something's gone sideways — check Troubleshooting below.
TL;DR: if it runs Windows 10, it runs this.
| Requirement | Spec |
|---|---|
| OS | Windows 10 (64-bit) or Windows 11 |
| RAM | 4 GB minimum, 8 GB comfortable |
| Disk | ~150 MB free space |
| Dependencies | None — fully standalone, no runtime installs |
| Internet | Not required after download |
| GPU | Any — rendering is lightweight and CPU-friendly |
Important
No .NET runtime hunt, no Visual C++ redistributable roulette, no silent background installer. It's an executable. It behaves like one.
TL;DR: capture → layer → annotate → flatten → export, in that exact order, every time.
The architecture is deliberately boring in the best way — boring means predictable, and predictable means you trust it during a live incident at 2 AM.
-
Capture engine grabs the raw pixel buffer from the selected region, window, or screen.
-
Canvas loader drops that buffer into an editable surface with its own coordinate space.
-
Annotation layer stacks vector objects (arrows, shapes, text, blur regions) on top — independently editable, independently deletable.
-
Render pipeline composites everything on export, flattening layers into a final raster image.
-
Output router sends the result to clipboard, disk, or both, depending on what you told it to do.
flowchart LR
Capture --> Canvas
Canvas --> Annotate
Annotate --> Flatten
Flatten --> Export
Tip
Keep annotations un-flattened as long as possible in your workflow. Export is the one step you can't cleanly undo once the file leaves the app.
TL;DR: most "bugs" are actually the hotkey or the DPI scaling. Check those first.
My global hotkey isn't triggering a capture.
Another app (looking at you, certain cloud-sync clients and streaming software) may have claimed that key combo first. Change the hotkey in Settings, or close the conflicting app and relaunch.
Annotations look blurry or misaligned on my 4K/high-DPI monitor.
This is almost always a Windows display-scaling mismatch. Right-click the executable → Properties → Compatibility → Change high DPI settings, and let the app control scaling instead of Windows overriding it.
The blur/pixelate tool isn't fully hiding text underneath.
Increase the blur radius in the tool's side panel — the default strength is tuned for casual redaction, not forensic-grade obfuscation. For sensitive data, bump it up and zoom in to verify before exporting.
Copy-to-clipboard isn't pasting into my target app.
Some apps only accept specific clipboard image formats. Try "Save As" and drag the file in manually as a fallback — this is an app-side limitation, not a bug on our end.
My saved color presets disappeared after an update.
Settings persist in a local config file tied to your user profile — if you moved profiles or ran the app under a different Windows account, presets won't carry over automatically.
Warning
Always double-check redactions by zooming in before sharing a screenshot externally. A light blur is a suggestion, not a vault door — crank the strength up for anything genuinely sensitive.
TL;DR: everything has a hotkey, dark mode is default, and the toolbar gets out of your way.
| Action | Shortcut |
|---|---|
| New capture | Ctrl+Shift+S |
| Region capture | Ctrl+Shift+R |
| Undo / Redo | Ctrl+Z / Ctrl+Y |
| Switch tool: Arrow | A |
| Switch tool: Text | T |
| Switch tool: Blur | B |
| Switch tool: Shape | S |
| Copy to clipboard | Ctrl+C |
| Export | Ctrl+E |
| Toggle toolbar visibility | Tab |
Themes: Dark (default), Light, and High-Contrast — all switchable live from Settings without a restart.
Settings that matter:
- Default save location and filename pattern
- Stroke width and color memory (per-tool, remembers your last used setting)
- Hotkey remapping for every action listed above
- Auto-copy-on-export toggle, for the "I never touch a save dialog" crowd
Note
The toolbar auto-hides during freehand drawing so your pen strokes never get interrupted by an accidental click on a button edge.
TL;DR: issues and pull requests are welcome; be specific, be kind, include screenshots (obviously).
This project grows on real-world friction — if a tool feels clunky, that's a signal, not a complaint to ignore. Bug reports with a reproduction case are gold. Feature requests with a concrete use case beat vague wishlists every time.
- Open an issue describing the behavior you expected vs. what happened
- Attach an annotated screenshot of the problem (yes, made with this tool — it's meta and it's great)
- Keep pull requests focused — one fix or one feature per PR, not a grab bag
Tip
Before filing "it's slow," check whether it's the render pipeline or your antivirus scanning the exe on every launch. Half of all "performance bugs" in tools like this are actually AV overhead.
TL;DR: MIT. Use it, ship it, fork it, just don't sue anyone.
Released under the MIT License, 2026. Do what you want with it — commercial, personal, weird internal tooling nobody outside your team will ever see. Just keep the license notice intact.
TL;DR: it's an editing tool, not a security product — use your own judgment on sensitive content.
`scre