Overview
You can now capture screenshots that correctly display all images, fonts, and media from authenticated sites. This feature ensures screenshots show exactly what users see, even when resources require login credentials to load.
This guide shows you how to enable authenticated media capture in your Marker.io project settings. The feature helps when working with sites protected by authentication like SSO, Okta, Auth0, or custom login systems.
When to use this feature
Common issues this feature solves
Without this feature, screenshots on authenticated sites often show:
Broken image placeholders instead of user avatars
Missing custom fonts (fallback to system fonts)
Blank spaces where protected images should appear
Missing CSS background images
Enable when:
Your website is behind SSO (Okta, Auth0, SAML)
Images are served from authenticated APIs
Custom fonts require login
Users report broken images in screenshots
Working with internal tools or dashboards
Skip when:
Working with public-facing websites
All resources are publicly accessible
Performance is critical and milliseconds matter
Images regularly exceed 5MB each
Your team is already using the browser extension
Enabling in your project settings
Turn on authenticated media capture directly in your Marker.io project settings.
Navigate to Project settings > Widget > Screen capture
Find the Authenticated Media Capture section
Toggle Capture behind-login content to ON
The setting saves automatically
That's it. No additional configuration needed.
Verifying it works
After enabling the feature:
Navigate to a page with authenticated images
Create a test screenshot using Marker.io
Check that user avatars and custom fonts appear correctly
Performance considerations
Enabling this feature may increase capture time by 1-3 seconds, as it needs to collect all visible assets on the page before rendering your screenshot remotely. This depends on:
Number of protected resources on the page
Size of images and fonts
Network latency to resource servers
For most teams, this small delay is worth the improved screenshot accuracy.
Frequently asked questions
Does this work with all authentication systems?
Does this work with all authentication systems?
Yes, it works with any system that uses cookies for authentication, including Okta, Auth0, and custom implementations.
Will this expose sensitive data?
Will this expose sensitive data?
No, it only uses the current user's existing authentication. No credentials are stored or transmitted.
Can I enable it for specific pages only?
Can I enable it for specific pages only?
Currently, it's a project-wide setting.
Does it work with browser extensions?
Does it work with browser extensions?
Browser extensions already have access to authenticated content, so this feature primarily benefits the JavaScript widget and SDK implementations.
Need help?
Contact our support team if you experience issues with authenticated media capture. We're here to help ensure your screenshots capture everything correctly.