Customer recordings with console logs and network requests
When a customer records an issue on your web app, Screendesk attaches the console logs, network requests, and system details from their browser. Engineers see what failed without asking the customer to open developer tools.
Trusted by support teams from startups to enterprises
How console logs and network requests get attached to a recording
Install the snippet once. After that, recordings your customers make on your site carry their technical context.
Add the snippet to your web app
Copy the Screendesk snippet from Settings → Logs & blur, add it to your site, and run the built-in test to confirm it loads.
Send a recording request
Your agent sends a recording link from the helpdesk. The customer opens it in their desktop browser, reproduces the issue, and submits the recording, with nothing to install.
Open Insights on the recording
Console messages, errors, and the customer’s clicks follow the video’s timeline, and the Network tab lists each request. Filter by log level or show errors only.
Console and network capture works on websites where the Screendesk snippet is installed; a recording of another site or app does not include that app’s logs. Logs from scripts that run before the snippet are not captured. System details are collected by the recorder and need no snippet. Mobile customers record with their camera, so those videos carry no browser logs. In Safari, logs are captured only on tabs of the subdomain where the recording started.
Logs & blur documentation · Install the snippet · Request a customer recording · Capture your own bug reports · Plans
See what the browser saw. The console and the network, next to the video.
The console, in order
Messages with their level, uncaught errors with stack traces, failed requests, and the customer’s clicks, along the video’s timeline.
Every request, with its response
Fetch and XHR calls, documents, scripts, and WebSocket connections, with status, timing, headers, and response body.
Context engineers can act on. Collected in the customer’s browser, ready for your team and your tools.
Readable by AI agents. Claude, ChatGPT, Cursor, and coding agents read a recording’s console logs and network requests through the Screendesk MCP or CLI.
Secrets redacted in the browser. Passwords, tokens, cookies, authorization headers, API keys, and card numbers are redacted before anything is sent.
Sensitive fields blurred. With auto blur on Pro and Enterprise, card, email, and phone fields on your pages are blurred while the customer records.
Send it to engineering. Create a Linear, Jira, or GitHub issue from the recording, with an AI-drafted description and the technical context attached.
System details included. OS, browser, device, screen size, locale, timezone, and connection speed come with each customer recording, with no snippet needed.
Your app’s context. Attach the user ID, plan, or feature flags from your app, so engineers know who hit the issue.
Context
See exactly what happened. Every recording includes the context behind the issue.
Works better together. Console & network logs is one part of the Screendesk platform.
Questions about console & network logs
Does Screendesk capture console logs and network requests with a customer recording?
Yes. With the Screendesk snippet on your web app, a recording your customer makes there includes console messages, uncaught errors with stack traces, and network requests with their status, timing, headers, and response body.
Which plans include console and network logs?
Every plan. Console and network logs are included on Free, Plus, Pro, and Enterprise.
Does the customer have to install anything or open developer tools?
No. The customer opens a recording link and records in their desktop browser. The snippet on your site collects the logs, so nobody has to copy anything from the browser console.
What is redacted from the logs?
The snippet redacts data in the browser before anything is sent: passwords, tokens, cookies, authorization headers, and API keys, and personal data such as email addresses, phone numbers, and card numbers.
Do mobile recordings include logs?
No. Mobile browsers can’t record the screen, so mobile customers record a video with their camera. Those videos don’t include browser logs.
Do bug reports from the Chrome extension include logs?
Yes. The Screendesk Chrome extension attaches console logs, network requests, clicks, and page navigation to the recordings, screenshots, and instant replays your team captures.
Screendesk has significantly improved our troubleshooting resolution times. Our support specialists also actively request recordings for complex issues.