Next-Gen App & Browser Testing Cloud
Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

To open the Console in Chrome, press Ctrl+Shift+J on Windows or Linux, or Cmd+Option+J on macOS, and Chrome DevTools opens with the Console tab focused. You can also press F12, right-click the page and choose Inspect, or open the three-dot menu and go to More tools > Developer tools.
The Console is one panel inside Chrome DevTools, the browser's built-in suite for inspecting and debugging web pages. It serves two roles: it prints messages logged by the page, including JavaScript errors, warnings, and network problems, and it acts as an interactive REPL where you can run JavaScript against the current page. For developers and testers, the Console is usually the first place to look when a page misbehaves, because runtime errors and failed requests surface here immediately. Every method below opens the same DevTools window; they differ only in whether the Console tab is focused right away.
Chrome offers several routes to the Console, and they all work regardless of your Chrome version:
Shortcuts are the quickest way to reach the Console, especially the J variants, which jump straight to it:
Once the Console is open, you can run JavaScript against the live page. A few commands cover most debugging needs:
// Print a value or message
console.log("Page loaded", document.title);
// Highlight problems
console.warn("Deprecated API used");
console.error("Something broke");
// Inspect the DOM: grab the first heading
document.querySelector("h1");
// Group and count repeated logs
console.table([{ name: "row1" }, { name: "row2" }]);
// Clear everything
clear();For a fuller walkthrough of interactive debugging, the TestMu AI guide on debugging JavaScript using the developer console is a good next step.
Opening the Console in Chrome takes seconds: press Ctrl+Shift+J or Cmd+Option+J to jump straight to it, or use F12, right-click Inspect, or the three-dot menu. Once it is open, use console.log, error filtering, and Preserve log to debug efficiently, and test across real browsers and devices to make sure the fixes hold everywhere your users are. For the broader, browser-agnostic version of this task, see how to open the browser console.
Press Ctrl+Shift+J on Windows and Linux, or Cmd+Option+J on macOS, to open Chrome DevTools with the Console tab already focused. F12 or Ctrl+Shift+I also opens DevTools, but it lands on whichever panel you used last rather than jumping straight to the Console.
Click the three-dot menu in the top-right corner, choose More tools, then Developer tools, and select the Console tab. You can also right-click anywhere on the page and choose Inspect, which opens DevTools where the Console tab sits at the top of the panel.
The console filter may be hiding them. Check the filter dropdown and log-level toggles at the top of the Console tab and make sure Errors and Warnings are enabled. Also confirm you have the correct frame selected, since messages from an iframe appear only when that context is chosen.
Chrome on Android does not expose DevTools directly, but you can inspect a mobile page by connecting the device to a desktop and using remote debugging via chrome://inspect. Cloud platforms also provide DevTools access on real mobile browsers without any local setup.
The Console is where JavaScript logs, errors, and interactive commands appear, while the Elements panel (opened by Inspect) shows the live HTML and CSS of the page. Both live inside Chrome DevTools, and you can switch between them using the tabs at the top of the panel.
Type clear() and press Enter in the Console, press Ctrl+L, or click the circular clear icon at the top-left of the Console tab. To keep logs across page reloads instead, enable the Preserve log checkbox in the Console settings.
KaneAI - Testing Assistant
World’s first AI-Native E2E testing agent.

TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance