Console logs
Capture browser console output during recordings to debug client-side errors faster.
Console logs capture what your app wrote to the browser console during the session. This is the fastest way to debug client-side failures without asking customers to open DevTools.
Availability
Console logs are captured for widget-based recordings when enabled by an admin.
You typically need:
The Screendesk widget installed on your site
Console logging enabled in workspace settings
Console logs start capturing after you enable the feature. Older recordings won’t be backfilled.
Enable console logs (admin)
Install the widget (if needed)
Console capture relies on the Screendesk script on your site.
Turn on console capture
Go to Settings → Console Logs.
Enable Enable Console Logs.
Verify on a test recording
Create a new test recording. Then confirm you see a Console tab on the recording.
Where to find console logs
Open a recording.
Click the Console tab.
Use search and level filters to narrow down noise.
How to use console logs (fast workflow)
Find the first real error
Start with Error entries. Ignore repeated follow-on errors at first.
Correlate with the video
Jump to the timestamp. Watch what the user did right before the error.
Escalate with the right payload
Include:
Error message
Stack trace
Timestamp
Recording link
Common patterns (with examples)
Uncaught TypeError
Usually a frontend bug or missing data. Escalate with the stack trace.
CORS blocked
Usually a server header or environment mismatch. Pair this with the failing request in network logs.
Failed resource / 404
Usually a bad URL, missing asset, or wrong environment.
Deprecation warnings
These are rarely the direct cause. Track as tech debt unless they block the flow.
Console logs vs. network logs
Use console logs when:
UI breaks and you suspect frontend code
You need stack traces and error context
Use network logs when:
Data doesn’t load
You need status codes, payloads, and responses
See Network Logs.
Privacy and security
Console logs can include sensitive data (tokens, IDs, and internal state). Limit access.
Recommended practices:
Restrict access to technical roles.
Redact secrets before sharing outside your org.
Avoid copying full logs into public tickets.
Troubleshooting
I don’t see a Console tab
Check these in order:
Console logging is enabled in Settings → Console Logs.
The Screendesk widget is installed on the page being recorded.
You’re testing with a new recording (no backfill).
Browser extensions aren’t blocking the widget.
Console logs are empty
This can be normal. Some apps don’t log anything unless there’s an error.
Try reproducing again, or add targeted logging in your app for the failing flow.
There are too many logs
Filter to Error first. Then search for the API endpoint or feature keyword.
If this is persistent, reduce verbose debug logs in production builds.
Related pages
Last updated
Was this helpful?