Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 36 ยท Getting Started

Opening DevTools, Docking and Layout

Open Chrome DevTools with menus and shortcuts, dock it to the side or bottom, undock it, use the drawer and the Inspect tool, with runnable shortcut stand-ins.

Before you can debug anything you need to open DevTools quickly and arrange it so you can still see the page. Chrome gives you several ways to open the tools, four docking positions, and a split view with a drawer that holds a second tool at the bottom. Knowing these small things makes every later lesson faster.

Ways to open DevTools

There are four common ways, and each has a use:

  1. F12, or Ctrl+Shift+I (Windows and Linux) / Cmd+Option+I (macOS). Opens DevTools on the last panel you used.
  2. Right-click an element and choose Inspect. Opens the Elements panel with that node selected. This is the fastest way to answer "what is this thing?".
  3. Ctrl+Shift+J (Windows/Linux) / Cmd+Option+J (macOS). Opens straight on the Console.
  4. Chrome menu, then More tools, then Developer tools. Slower, but good to know if shortcuts are blocked on a kiosk or managed browser.

Press the same shortcut again, or F12, to close the tools.

You can also use Ctrl+Shift+C (Cmd+Shift+C on macOS) to start the Inspect tool: hover any element on the page, click it, and DevTools jumps to that node in the Elements panel.

Docking: where DevTools lives

By default DevTools is docked to the right or bottom of the browser window and shares the space with the page. Open the three-dots menu at the top right of the DevTools window to change the Dock side:

  • Dock to right keeps the page on the left. Good on wide screens.
  • Dock to bottom keeps a wide, short panel under the page. Good for the Console and Network.
  • Dock to left is the mirror image of right.
  • Undock into a separate window gives DevTools its own window, ideal on a second monitor.

A keyboard shortcut cycles through dock positions: Ctrl+Shift+D (Cmd+Shift+D on macOS) in current Chrome versions.

When docked, the page becomes narrower. That changes layout and can trigger responsive breakpoints, so a layout that "breaks when DevTools opens" is usually a viewport-width effect, not a bug. Undocking or using Device mode (a later lesson) removes that confusion.

flowchart TB
  A["Open DevTools"] --> B{"Where is the room?"}
  B -->|"Wide monitor"| C["Dock right"]
  B -->|"Need wide tables"| D["Dock bottom"]
  B -->|"Two monitors"| E["Undock"]

Choose the dock position from your screen, not from habit.

Switching panels and the drawer

Panels sit in a tab bar at the top. Use Ctrl+[ and Ctrl+] (or Cmd+[ and Cmd+]) to move to the previous and next panel. Panels that do not fit hide behind the >> overflow button.

Press Esc to toggle the drawer, a second area at the bottom with its own tabs: Console, Search, Rendering, Network conditions, Issues, Animations, and more. The drawer is one of the best habits to adopt: keep Elements on top and the Console in the drawer, so you can inspect markup and run JavaScript at the same time.

The drawer's three-dots menu has an entry for each drawer tool. Many tools you may never see otherwise (Rendering, Sensors, Coverage) live here or in the Command Menu, which a later lesson covers.

Resizing, zooming and themes

  • Drag the divider between the page and DevTools to resize it.
  • Ctrl + and Ctrl - zoom the DevTools UI itself when focus is inside it (Cmd + / Cmd - on macOS). This is useful on high-resolution screens where text is tiny.
  • The theme follows your system by default (light, dark). You can force it in Settings, Preferences, Appearance.

A stand-in for shortcut lookup

Remembering shortcuts across systems is half the battle. The stand-in below is a small lookup table that prints the right keys for a platform. It is plain JavaScript that mirrors the table above, not part of DevTools.

JS Stand-in: shortcut lookup by platform

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Practice: a decision helper for docking

This second stand-in suggests a dock position from screen width and number of monitors. The thresholds are opinions, not Chrome rules, so change them to suit your taste.

JS Stand-in: pick a dock position

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Inspecting pages that block shortcuts

A few pages try to block right-click or F12. Chrome's own menu (More tools, Developer tools) still works. Some enterprise policies disable DevTools entirely; in that case the menu entry is missing, and you cannot enable it from the page.

Pages inside other contexts open DevTools differently:

  • Browser extensions' popups open with a right-click on the popup, then Inspect.
  • iframes are reached by right-clicking inside the frame, then Inspect.
  • Other tabs or devices can be inspected remotely at the chrome://inspect page, which lists debuggable targets.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which action opens DevTools directly on the Elements panel with a node selected?

    Inspect opens Elements with the clicked node selected. Ctrl+Shift+J opens the Console.
  2. 2. What does the Esc key do inside DevTools?

    Esc shows or hides the drawer, which holds secondary tools such as the Console.
  3. 3. Your layout breaks only while DevTools is docked to the right. What is the likely reason?

    Docking shrinks the page's viewport width, which can trigger media queries.
  4. 4. Which dock option is best for a second monitor?

    An undocked window can be moved to another screen so the page keeps its full width.

Summary

  • Open with F12, Ctrl+Shift+I, Inspect, or Ctrl+Shift+J for the Console.
  • Dock right, bottom, left, or undock; the page shrinks when docked, which can change the layout.
  • Esc toggles the drawer, a great place for the Console beside Elements.
  • Ctrl+Shift+C starts the Inspect tool; chrome://inspect reaches other targets.

Next: The Command Menu and Keyboard Shortcuts