Support

Use this page for Screenshot King support, troubleshooting, and privacy-safe issue reporting for the Chrome extension.

Last updated July 4, 2026.

Before reporting an issue

Do not include private screenshots, passwords, access tokens, private keys, customer records, unreleased business material, or confidential page content in a support request. Replace sensitive values with dummy examples such as example.test, user@example.com, or Sample page title.

Helpful details to include

The Screenshot King version shown on the Chrome extension details page.
Your browser and operating system version.
The website where the issue appeared and whether it happened in the drawer, screenshot picker, area selection, full-page capture, clipboard copy, Copy URL, Insert, or Insert all workflow.
The capture mode in use: visible page, selected area, or full page.
A short dummy-safe example, the result you expected, and what happened instead.

Common workflow checks

Confirm the active tab is a normal http or https website. Chrome protected pages and the Chrome Web Store do not allow content scripts.
Use Capture visible page for the most reliable capture of the current viewport.
Use Select area when only part of the rendered page is needed.
Use Refresh if screenshots were captured or stored from another browser tab.
Type /// inside a normal editable field to open the screenshot picker and search by origin, URL, title, or wildcard text.
For heavily virtualized pages, full-page capture may only include content that the page has rendered and exposed to the browser.

Privacy and screenshot data questions

Screenshot King is built around local browser storage for captured screenshots, thumbnails, source URLs, and preferences. It does not run a backend service for screenshot content, does not use telemetry or analytics, and does not sync screenshots to a cloud account.

Read privacy policy

Current support channel

For support, bug reports, privacy questions, or feature requests, use this support page as the reference and keep reports free of sensitive screenshots or secrets.

For concerns or to contact the developer directly, connect with Rolly Falco Villacacan on LinkedIn.