Developer
Vibe coding a WinUI page with Claude Code
Presses the hotkey on a misaligned dialog, draws one arrow and pastes. The file lands in the repo's screens folder and Claude Code reads it by path.
Coming SoonFree editionDesktop & dev workflow
Capture Studio
Screen capture built for the loop: see it, capture it, paste it into Claude Code in VS Code, with the file path and the image both on the clipboard.
The problem
When you are coding with Claude Code inside VS Code you take a dozen screenshots an hour: an error dialog, a layout bug, a VM console. Snipping Tool puts an image on the clipboard but not a path, names files randomly in Pictures, and has no annotation or redaction flow. ShareX can do it, after an afternoon of configuration.
Features
- One hotkey: region, window, monitor or scrolling capture, DPI-correct on mixed-DPI setups
- Saved as PNG into a project-aware folder (the open repo's .claude/screens or one you choose) with sequential names, and the file path plus the image placed on the clipboard together, so Ctrl+V works in VS Code, in a terminal and in a chat
- Annotation in two seconds: arrows, numbered steps, boxes, blur; secrets redacted automatically where OCR spots tokens, e-mails and keys
- OCR to text with the Windows engine, for error messages you want as text, not pixels
- Short MP4 or GIF recordings for bug reproduction, trimmed and small
- Capture history strip to drag earlier shots into a chat; VM console windows captured sharp
Who it is for
QA engineer
Reporting a bug seen in a VM console
Records 12 seconds of the console as an MP4, trims it, and attaches it to the issue with the OCR'd error text.
Technical writer
Writing a user guide
Numbered-step annotations across twenty captures named 01 to 20 in the docs folder, with the test tenant's e-mail redacted in each.
Benefits
- A screenshot is in VS Code or Claude Code in two keystrokes, with the path ready to reference
- No secrets leak into a chat: tokens and e-mails are blurred before the file exists
- Error text arrives as text, so the assistant reads it instead of squinting at pixels
Built to be trusted
- Every capture is written to disk before it is placed on the clipboard, so nothing is lost when the clipboard is overwritten
- Redaction is applied to the saved file, not only the preview
- Recordings are written in chunks, so a crash keeps everything up to the last second
Good to know
ShareX will always have more destinations and automations. We do not compete on uploads; we win the local loop between the screen and an AI coding session.
Under the hood
For technical readers
- Windows.Graphics.Capture; DwmGetWindowAttribute; PrintWindow fallback
- Windows.Media.Ocr
- Win2D annotation layer; RegisterHotKey
- CF_DIB plus CF_HDROP plus text on the clipboard; Media Foundation H.264
Related products
Works well with
ReadyFree edition
Copy Engine
Files & transfer
Unbuffered, journaled, verified copying that survives disconnects and tells the truth about progress.
Coming SoonFree edition
Recovery Proof Lab
Raspberry Pi & hardware
How the device would earn the words 'world class'.
ReadyFree edition
Job Engine
Platform
The shared runtime: pause, resume, cancel, crash-safe journal, honest ETA, sealed reports.
Coming Soon
Notify me when Capture Studio is ready
Capture Studio is planned for a later release. Leave your e-mail address and we will write once when it becomes available. We ask you to confirm your address first, and you can unsubscribe at any time.
Questions now? Contact our team.