Screenshot issues

Native browser screenshots

If our standard rendering mode struggles with your site's layout or protected content, you can switch to native screenshots. This uses the browser's built-in capabilities to capture exactly what the user sees.

• Pros: Pixel-perfect captures; works on localhost and behind firewalls.
• Cons: Requires the user to accept a browser screen-share prompt (one extra click).
• Fallback: If a browser doesn't support native screenshots, Ybug automatically falls back to standard rendering.

To enable: Open your project's Widget configuration → Advanced → Screenshot rendering mode.

HTTP Basic authentication

If your site uses HTTP Basic Authentication, you can pass credentials in the ybug_settings object. We recommend creating credentials used only for Ybug:

window.ybug_settings = {
    id: 'XXXXXXXXX', 
    auth: { 
        type: 'basic',
        username: 'user',
        password: 'pwd',
    }
};

🔒  We store these credentials encrypted and delete them as soon as your screenshot is rendered.

Localhost

Ybug can render screenshots of sites hosted locally, but you might see missing images or fonts if our servers can't reach your local environment.

1. Enable native screenshots — This is the easiest way to get accurate captures on localhost.

2. Use browser extensions — Our browser extensions take screenshots directly in your browser, without relying on server-side rendering.

3. Use a tunnel — Expose your local server with a service such as Ngrok or PageKite so Ybug's servers can load your assets.