Native screenshot uses the browser's built-in Screen Capture API to capture a tab, window, or entire screen: an exact match for what the user sees. It's the right tool when your site uses rendering that Userback's standard screenshot engine struggles with, like WebGL or a 3D canvas, or when your site isn't publicly reachable.
When native screenshot is used
Complex rendering. Pages using WebGL, 3D canvas, Google Maps, or similar are often captured poorly by the standard engine, since it renders server-side. Native screenshot captures directly from the browser instead.
Sites behind a firewall or otherwise not publicly reachable. The standard engine needs your site to be publicly accessible. If it isn't, screenshots automatically fall back to native screenshot.
Localhost. The widget automatically falls back to native screenshot on localhost. No configuration needed.
How to turn it on
Outside of the automatic cases above, add one of these to your widget code:
Userback.native_screenshot = true;
or, as an init option:
Userback.init('widget_access_token', { native_screenshot: true });
What your users see
When someone submits feedback with native screenshot active, their browser prompts them in two steps: choose what to share (a tab, a window, or the entire screen), then click Allow.
This permission prompt is a browser-level security feature. Userback can't skip or customize it, and it appears every time.
Limitations
Not available on mobile browsers; the standard screenshot engine is used there instead.
Some of the standard engine's screenshot customization options don't apply once native screenshot is active.
Auto Screenshot (capturing automatically when the widget opens) still works with native screenshot enabled. The user just sees the browser permission prompt as soon as the widget opens, before they start typing feedback.
What's next