Guide
Press the hotkey after the bug. Everything else takes about five seconds.
Install
Download the installer and run it. CapturePack lives in the tray and starts with Windows. It is unsigned for now, so Windows may warn on first run — More info → Run anyway.
Captures, telemetry and crash reports are never uploaded. The only outbound app request is the optional GitHub update check, which you can disable.
Capture
When Live recording is on (the default), CapturePack keeps a rolling replay — 30 seconds by default and configurable from 1–60. That is why you press the hotkey after the thing you want to show. Turn recording off and nothing is recorded.
Ctrl + Alt + C
The replay freezes and its source media and captured object context are preserved before editor rendering. The editor then opens at the moment you pressed the hotkey; History can reopen the capture even if you close the editor.
Capture an image
Ctrl + Alt + S
Region selection is the default and can cross monitor boundaries without a seam. The Full screen capture button explicitly captures every monitor as one virtual-desktop image. Images that fit open at native 100%; oversized captures open fitted so the whole image is visible.
An image pack has no replay or timeline. A region pack stores only the selected pixels and crop placement — never a hidden full-screen or second-monitor image.
Three gestures, no toolbar
- Left click On a still, select the captured control or window under the pointer. A replay has nothing to pick — you draw its boxes.
- Right drag Draw a box anywhere. A description field opens as you release.
- Wheel Travel back through the replay to the moment the bug happened.
On a still, Windows UI Automation supplies accessible controls; the optional Chrome extension supplies selector, role, text and URL for an explicitly picked element; a real HWND window is the fallback. Every observation names its display, so reopened multi-monitor packs keep the same timing and coordinates. Press Enter to save, ? for every shortcut.
What you get
A local folder, not an archive — so you can open it, read it, and drop it anywhere. A video pack has replay and timeline data; an image pack does not. Zip it only when you send it.
CapturePack_2026-07-29_114804/
README.mdwhat this is, for a personreport.mdthe annotations, in order, as sentencessnapshot.pngthe frame you pressed on, per screenreplay.mp4 / .webmthe original seconds before it, per screenreplay_annotated.webmoptional derived replay, only when the final manifest declares itannotations.jsonthe machine-readable source of truthskills/how to read all of the above, for an LLMplugins/the objects on screen: windows, controls, DOM elements
CapturePack_2026-07-29_114804/
snapshot.pngthe explicit region or full virtual desktopannotations.jsonthe machine-readable source of truthreport.md · README.md · skills/image-specific context, with no timelineplugins/the objects on screen: windows, controls, DOM elements
Blur is non-destructive. It protects annotated views, but snapshot.png and the original replay in a full pack remain unredacted. Review the original before sharing the full pack.
Give it to an AI
Drag the folder into ChatGPT, Claude, Cursor or Gemini and ask your question. The pack explains itself — skills/ tells the model what every file is and how the pieces relate.
Or use the optional MCP server, which is local-only, read-only, enabled and auto-started by default, and switchable in Settings → MCP. It reads saved packs only and cannot start a capture. Point your client at it and say:
“Analyze the latest CapturePack.”
Browser context
With the preview extension connected, a click in the browser is stored as what you clicked — selector, role, text, URL — instead of only the pixels it was drawn with. Settings → Plugins walks you through it in three steps:
- Press Open and copy the path. Your browser opens on its extensions page and the folder path is already on the clipboard.
- Turn on Developer mode, click Load unpacked, and paste with Ctrl+V.
- Press I did that — find it. CapturePack finds the ID your browser assigned and registers itself.
The extension reads a page only when you pick an element from it. It never streams the DOM, and it talks to nothing but CapturePack on your own machine.
Worth knowing
- Both hotkeys are yours. Settings → Capture independently rebinds video and image shortcuts if Ctrl+Alt+C or Ctrl+Alt+S is taken.
- 30 seconds is a default, not a limit. Longer buffers cost memory; the setting says how much.
- Every screen is captured by default, each at its own resolution and replay clock. You can choose a fixed display instead.
- Nothing is lost by closing the editor. History reopens any past capture to re-annotate or re-render.
- Diagnostics are under Information. Open About / Information → Open logs folder. Logs stay local and are never uploaded automatically.
If something is wrong
- The hotkey does nothing. Another app has claimed it. Rebind it in Settings → Capture.
- A screen reports a low frame rate. A screen capture only makes a frame when the screen changes, so an untouched monitor delivers almost nothing and has lost nothing. The pack records both numbers so a reader can tell which happened.
- Something else. Open an issue — and attach the pack. It was built for exactly this.