When someone captures a screenshot via the widget, our servers will read the content of your page and render it back to the reporter.

This is the most user-friendly solution - nothing to install or set up.

In most cases, the result should be perfect.

When the screenshot output is not ideal, there are a few workarounds you can implement to improve the quality of your screenshots.

  1. Enable basic auth

  2. Install browser extension

  3. Native browser API

Enable basic auth

If your website requires basic authentication (e.g. using .htaccess), our servers may be unable to access your site URL, including static resources such as images and stylesheets.

By providing credentials to our servers, we can access protected assets without requiring additional work for your reporters. If that matches your setup, read the following guide:

Install browser extension

While it does require reporters to take an extra step, this is probably the best workaround across the board!

Reporters will only need to install our browser extension once, then they can forget about it.

Once installed, our widget will always use the browser extension capture engine to generate pixel-perfect screenshots. Since screenshots will be generated locally, this will give the best results compared to server-side rendering.

If you can get your clients and team to install the extension, this will give you the best results.

We have browser extensions for:

Native browser API

Like the browser extension, the screenshot will be captured locally when using the Native browser API. This means that it won't go through our servers, and the results will almost always be perfect.

This could be useful to capture on-page elements like Videos & <canvas> containing cross-domain content that cannot be rendered.

Here are the downsides to using this method:

  1. Not supported on mobile: we fall back to the regular server-side rendering in that case.

  2. It requires an extra step for the reporter to choose what screen/window they want to capture.

  3. Screenshots are not retina-ready on Chrome & Edge Chromium: screenshots aren’t pixel perfect on retina screens, but on Safari & Firefox, they’re perfect.

For more info, read the following guide.

None of these options work for you?

We're always trying to improve our service-side renderer within the technical constraints. Feel free to use the chat to send us the URL of the page you're trying to capture, and our team will investigate if we can improve it.

Did this answer your question?