Support
Getting started, the things that most often go wrong, and how to reach a human when this page does not cover it.
Getting started
- Install the extension from the Chrome Web Store.
- Open any page you want to capture.
- Click the OmniSnap icon, or press Alt + Shift + S, and choose a capture mode.
- The Studio opens when the capture finishes. Annotate it, read its panels, then export or copy.
If you plan to record console output, switch it on in the popup before loading the page you want to record. See below for why.
Which capture mode to use
| Mode | Use it when |
|---|---|
| Full page | You want the whole document, stitched edge to edge. |
| Visible | You only need what is on screen right now. This is the fastest option. |
| Breakpoint | You need the page as it lays out at 375, 768, 1440 or 1920 px. |
| Responsive Matrix | You want mobile, tablet and desktop in one pass for a comparison. |
| Inspect & Redline | You want measurements drawn onto the capture for handoff. |
Troubleshooting
The capture is cut off, or parts are blank
The page is probably still rendering as it is photographed. Open the popup and raise the capture pace from Balanced to Patient. That gives animations, lazy images and fonts more time to settle between tiles. Pages with heavy entrance animations usually need Patient.
An embedded widget appears empty
Cross-origin iframes, such as embedded videos, maps, payment widgets and third-party chat, cannot be read by any browser extension. This is a browser security boundary, not a bug we can fix. Those regions will render blank or show their placeholder.
“This page cannot be captured”
Chrome blocks extensions from running on its own internal pages
(chrome:// URLs, the New Tab page, the Web Store) and on other extensions'
pages. Open an ordinary website and try again.
Chrome says OmniSnap is debugging this browser
That banner is Chrome's own, and it appears whenever an extension uses the debugger API. OmniSnap uses it for Turbo capture, the Responsive Matrix and breakpoint rendering, and detaches the moment the capture finishes, and the banner disappears with it. If you would rather it never appeared, turn Turbo off in the popup; ordinary scroll-stitched captures do not use it.
Console messages are missing from my report
Console messages and uncaught errors are events. Nothing in the browser retains them, so they cannot be recovered after the fact. The recorder has to be listening before the page runs its first line. Switch Record console & errors on in the popup, then reload the page, reproduce the problem, and capture.
Only console.error and console.warn are recorded, since those
are the only levels the defect report uses.
The Handoff panel is missing or says the model is unavailable
The on-device AI needs Chrome 138 or newer and a device with enough free storage and memory to hold the model. The first draft downloads the model, which takes a few minutes on a normal connection and shows progress while it runs. Where it cannot run, the panel explains that and hides its controls. Every other feature is unaffected.
The ticket the AI wrote is wrong or oddly worded
The built-in model is small and runs locally, which is the trade-off for never sending your capture anywhere. It is grounded strictly in the evidence the capture collected and is told never to invent findings, but it can still phrase things awkwardly. Treat the draft as a first pass, and use Copy ticket with evidence so the measured numbers travel with the prose.
A capture disappeared
Only the most recent capture is kept, so taking a new one replaces the last. Export or copy anything you want to keep before capturing again.
Requirements
- Chrome 116 or newer for capture, Figma export, redlines, brand kit and diagnostics.
- Chrome 138 or newer for the on-device AI Handoff writer.
- Desktop Chrome. Chromium-based browsers such as Edge, Brave and Arc generally work, but are not formally tested.
Reporting a bug
OmniSnap is rather good at producing bug reports, so please use it on itself. The most useful report includes:
- What you expected, and what happened instead.
- The URL you were capturing, if it is public.
- Your Chrome version and operating system.
- The capture mode and pace you used.
- Anything in the Studio's QA panel, if diagnostics were on.
Please redact first. Use the Studio's blur tool on anything confidential before attaching a screenshot, and remember that URLs and console messages can contain identifiers. Never send us credentials or tokens.
Contact
For bugs, feature requests, privacy questions or anything this page does not answer:
We aim to reply within a few working days. There is no account system, so please include enough detail in your first message for us to reproduce the problem.
Supporting the project
OmniSnap is free and has no paid tier. It also has no running costs to recover: there is no server, no API bill and no subscription behind it. Support is genuinely optional rather than a trial in disguise. Every feature stays available either way.
If it saved you time, or if an answer on this page got you unstuck, you are very welcome to buy the developer a coffee.