SnipPage support

Let's get your capture back on track.

Start with the guidance below. If the issue remains, email SmartGuy with the page type, capture mode, and what you expected to happen.

Email supportReport an issue
01

A browser page cannot be captured

Chrome blocks extensions on protected pages such as chrome:// settings, the Chrome Web Store, and some extension pages. Open a regular website tab and try again.

02

A page changes while capturing

SnipPage stops at the page height measured when capture began. It waits for visible images and adds a capture note when content grows, times out, or cannot be verified.

03

A long page is split into files

Very large captures are stored as ordered, full-resolution PNG segments when one browser canvas would be unsafe. This prevents silent downscaling or missing content.

04

Local storage is full

Keep the Studio tab open, export important work, then open Saved Captures and delete unreferenced captures you no longer need. SnipPage keeps the current in-memory edit when an autosave fails.

05

Clipboard copy is unavailable

Clipboard access depends on Chrome and the operating system. Your capture remains intact; use Download image as the reliable fallback.

06

Redaction needs to be permanent

Use Redact, which replaces exported pixels with an opaque cover. Do not rely on Pixelate for sensitive information, and inspect the final export before sharing.

Still need help?

Send a useful problem report.

Include your Chrome version, capture mode, page type, the exact message shown, and steps that reproduce the problem. Do not send passwords, personal data, or an unredacted confidential screenshot.