Support & FAQ

No. Zero data leaves your device. All capture, annotation, and export processing runs locally in your browser. The extension has no analytics, no telemetry, and no third-party services. See the Privacy Policy for details.

No. Chrome blocks extensions from capturing chrome://, chrome-extension://, the Chrome Web Store, and about: pages. That block is a Chrome security rule, and no extension can lift it. The extension shows an error if you try.

Chrome limits captureVisibleTab to about 2 calls per second. Every viewport-height tile costs one call, plus a short pause for the page to repaint. A typical 10-tile page takes 5–6 seconds, and a longer page takes proportionally longer. The progress bar in the popup tells you where it is.

Fixed headers do appear — they are captured on the first tile and composited once at the top. A few rare position: sticky setups still slip past that. If you hit one, open a GitHub issue with the page URL.

No. Region selection is viewport-only — it locks scrolling while you drag. To grab an area that extends below the fold, capture the full page and crop it in the editor.

By default the editor opens in a new tab after every capture — you do not need to do anything. Export your annotated screenshot from the editor’s “Export” button in the top bar, or press Ctrl+S / ⌘S.

If the After capture row in the popup is set to Clipboard or Download, no tab opens. Reopen last in the popup footer loads that capture into the editor whenever you want it.

Yes. The After capture row in the popup picks Editor, Clipboard, or Download. The setting applies to every entry point — the popup buttons, the keyboard shortcuts, and the right-click menu. Quick saves are written as PNG, and the toolbar badge is the confirmation since no tab opens.

Set the Delay row in the popup to 3s, 5s, or 10s, then trigger the capture and open the menu. The toolbar badge counts down, and a region capture shows its overlay only after the delay. The right-click menu honors the same setting.

They are saved locally as you work. The next editor tab offers the draft back, and restoring it is always a click — a stale draft never replaces a capture you meant to start fresh. A cropped image gets its own draft, so annotations never restore against the wrong picture.

Yes. Drop an image file onto the editor stage, or paste one with Ctrl+V / ⌘V outside a text field. The import takes the same seat a capture takes, so every tool, the beautify frame, and every export path keep working. It replaces the canvas, so the editor asks first when there are annotations to lose.

Reopen last in the popup footer also loads the most recent capture back into the editor.

No. PDF export runs on a small writer built into the extension (src/editor/pdf-writer.ts). It places each page’s image and compresses it with the browser’s own CompressionStream, so exporting a PDF makes no network request and adds no third-party code. Earlier versions used jsPDF, which pulled in html2canvas and dompurify for a feature the extension never called.

The export dialog carries a Scale control: 25, 50, 100, or 200 %, or an exact pixel width. It is hidden for PDF, which sizes to the page. A size past Chrome’s canvas limit is refused rather than written as an empty file.

The Beautify panel adds padding, rounded corners, a drop shadow, and a gradient, solid, or transparent background. The frame travels into every export, the clipboard, and PDF.

Yes. Open chrome://extensions/shortcuts, or use the Shortcuts link in the popup footer. The defaults are Ctrl+Shift+S for the full page, Alt+Shift+V for the visible area, and Ctrl+Shift+E for a region; on macOS they are ⌘⇧S, ⌘⇧V, and ⌘⇧E. Chrome may leave a command unbound if another extension already claims the combination.

tabCapture is an optional permission, not one the extension asks for at install. Chrome shows the prompt once, the first time you click Record; every recording after that starts in one click, with no further prompt. Declaring it optional means it carries no install-time warning and never appears unless you actually start a recording.

On your device, and nowhere else. Video chunks, the cursor log, and any mic or tab audio are written to IndexedDB as you record, in 1-second pieces, so a crash or a killed background page never loses the take. They stay there until you export or delete the session — nothing is ever uploaded.

The recorder exports through MediaRecorder, which writes WebM natively in every browser that supports tab capture. MP4 export is on the roadmap, via WebCodecs and a muxer, alongside the WebM path this version ships.