Core How-Tos
Find a page's console errors
When a page looks broken or a button does nothing, its console usually says why. Console errors records what it says and tells you whether the site, another site or one of your extensions caused it.
Record the errors
- Open the page with the problem.
- Click the Browser Quick Fix Kit icon, then Console errors under Support.
- Leave Reload the page first on to catch errors while the page loads, or switch it off to record what happens next.
- Press Reload and record. It records for a few seconds; Chrome shows its "debugging this browser" bar while it does.
The errors and warnings come back grouped by where they came from: an extension (named), this site, other sites, or Chrome itself. Copy for support puts them on your clipboard, ready for a ticket.
When an extension is named
If the errors come from one of your extensions, open Extensions in the panel and switch it off, then reload the page. To rule out every extension at once, switch off All extensions; switching it back on restores just the ones that were on.
Open the Console yourself
Chrome doesn't let an extension open DevTools, so the view shows the shortcut instead. On the page, press Ctrl+Shift+J (⌘⌥J on a Mac).
Related guides
Pair the errors with a HAR file when a request fails. If you turned on Ask AI, it sees the summary too.