Capturing browser console errors
When something isn't working as expected such as a page won't load, a button doesn't respond, or you see a blank screen where content should appear, there's often an error recorded silently in the background that can tell us exactly what went wrong.
This guide shows you how to find and share that information. It takes around 2 minutes.
What is the browser console?
Every web browser has a built-in diagnostic tool that records what's happening behind the scenes as you use a website. When something goes wrong, it often leaves an error message here, even if nothing obvious appears on screen.
You don't need to understand what the errors mean. We sometimes just need you to capture them and send them to us.
Reproduce the issue first
Before opening the console, get yourself to the point where the problem occurs or as close to it as possible.
For example:
If a page won't load, navigate to that page
If a button doesn't work, go to the screen where the button is
If something looks wrong, open the area where it appears
We want to capture the error at the moment it happens. If you open the console after the fact, the relevant error may have already been cleared.
Open the browser console
Press F12 on your keyboard (or Fn + F12 on some laptops)
Alternatively, right-click anywhere on the page and select Inspect
A panel will open on the side or bottom of your screen
Click the Console tab along the top of that panel
You'll likely see a mix of white, yellow, and red text. Don't worry about what it says — we're looking for errors, which appear in red.
If you opened the console after the issue occurred, you may need to trigger the problem again. For example, by refreshing the page or clicking the button that isn't working, so the error appears fresh.
Clear the console and trigger the issue again
To make sure we're only seeing errors relevant to your issue:
Right-click anywhere in the console panel
Select Clear console — the panel should now be empty
Now perform the action that causes the problem (refresh the page, click the button, etc.)
Watch for any red error messages to appear
Take a screenshot
Once you can see the error (or errors) in the console:
Make sure both the platform and the console panel are visible on screen at the same time
Take a screenshot:
Windows: Press Windows key + Shift + S, then drag to select the relevant area
Mac: Press Cmd + Shift + 4, then drag to select the relevant area
Save the screenshot somewhere easy to find
Try to capture as much of the red error text as possible. If there are multiple errors, scroll to the top of the console first— the earliest error is often the most important one.
Copy the error text
A screenshot is helpful, but the raw error text is even better as it lets us search for the exact issue. Here's how to copy it:
Right-click on any red error message in the console
Select Copy message (or Copy error)
Paste it into your support ticket message
If there are several errors, copy the first one — or all of them if they're short.
Send it to us
Reply to your support ticket (or raise a new one) and include:
✅ A screenshot showing the console errors
✅ The copied error text pasted into the message
✅ A brief description of what you were doing when it happened
Don't worry if you're not sure whether what you're seeing is relevant. Send us the screenshot anyway — even a console with no red errors is useful, as it helps us rule things out and points us in a different 26
Last updated
Was this helpful?