SnapGleamby RANURANU
Support

Practical help for browser capture problems.

Start with the checks below. If the same problem repeats, send a support message with the capture mode and enough non-sensitive context to reproduce it.

Full Page looks different

Wait for the page to settle, pause changing content where possible, try 100% zoom, and retry after sticky or lazy-loaded elements finish.

Scroll Area stops early

Confirm the page can scroll normally, avoid resizing the browser, and try a slightly smaller selection on pages with nested scroll containers.

Local HTML will not capture

Open Chrome extension settings for SnapGleam, enable Allow access to file URLs, reload the file, and try again.

Element selection feels wrong

Move slowly over the target, choose a stable parent container, close overlays, and retry after the layout stops changing.

FAQ

Common questions

Does SnapGleam require an account?
No. The current free version does not require a SnapGleam or RANURANU account.
Where is screenshot processing performed?
The current workflow is designed around browser-local processing. Captured screenshots are not sent to a SnapGleam-operated screenshot server by the extension.
Why do some browser pages not work?
Chrome restricts extension access to protected browser-controlled pages. SnapGleam does not bypass those restrictions.
Can I capture local HTML?
Yes, when Chrome’s file URL access option is enabled for SnapGleam and you explicitly open the local page.
What can I export?
Depending on the capture, SnapGleam supports copy, PNG save, and PDF export for supported long-page results.

Still need help?

Email RANURANU with your SnapGleam version, Chrome version, capture mode, what you expected, and what happened instead. Do not send passwords, private documents, or sensitive screenshots unless absolutely necessary.

Contact support ↗