Screenshots: quality, protected sites and localhost

Get sharper captures, handle sites behind a login and use PinMarks on localhost.

Updated October 2026

How screenshots are taken

PinMarks tries these in order and uses the first that works:

1. 1The browser extension, if installed (most accurate, supports Entire page).
2. 2The browser's own screen capture, if Browser screenshots is on for the project.
3. 3A server-side render of the page (the default for most visitors).
4. 4An in-browser reconstruction of the page as a last resort.

Tips for better quality

• Install the extension for pixel-perfect and full-page captures. Reporters install it themselves.
• If a page has video, maps or other embeds that render oddly, turn on Browser screenshots in Widget → Screen capture, or capture Desktop (D).
• Use Area (A) to capture just the part that matters.
• Reconstruction can miss cross-origin iframes and some CSS effects.

Protected sites

If images or styles are missing on a site behind a login, in Widget → Screen capture turn on:

• Basic Auth and enter the username and password if your site shows an HTTP login popup.
• Capture login-only images so images that need a login still appear.

The extension and browser screenshots capture exactly what the reporter's browser shows, so they are the simplest option for content behind a login.

Localhost and private sites

• The widget works wherever the snippet is installed, including localhost. If Widget access is set to your listed domains, add localhost to Website domains or allow any website while you test.
• Server-side rendering cannot reach localhost or private network addresses, so use the browser extension or Browser screenshots there.