Skip to main content

Chrome DevTools Keyboard Shortcuts Cheat Sheet

ยท 7 min read
Daniel Caldas
Co-founder

DevTools has hundreds of shortcuts, and you need about twenty. This cheat sheet keeps the ones that save time every day, grouped by what you are doing, with the keys for Windows and Linux and for Mac side by side.

Most of these only work while DevTools has focus: click inside it first. They work the same in Edge and every other Chromium browser.

Open DevToolsโ€‹

ActionWindows / LinuxMac
Open or close DevToolsF12 or Ctrl + Shift + IโŒ˜ + Option + I
Open DevTools on the ConsoleCtrl + Shift + JโŒ˜ + Option + J
Inspect an element on the pageCtrl + Shift + CโŒ˜ + Shift + C
Open the Command MenuCtrl + Shift + PโŒ˜ + Shift + P
Open a file of the pageCtrl + PโŒ˜ + P
Search across all filesCtrl + Shift + FโŒ˜ + Option + F
Open DevTools SettingsF1 or ?F1 or ?

Learn the Command Menu first. It is the one shortcut that replaces the others: type "screenshot", "dark", "disable JavaScript", "sensors", "coverage" or "blocking" and run the command, without knowing which panel or menu hides it. Delete the > and it becomes the file finder (Ctrl + P).

Move around DevToolsโ€‹

ActionWindows / LinuxMac
Next / previous panelCtrl + ] / Ctrl + [โŒ˜ + ] / โŒ˜ + [
Switch dock position (bottom, side, ...)Ctrl + Shift + DโŒ˜ + Shift + D
Show or hide the drawer (Console, ...)EscEsc
Toggle device modeCtrl + Shift + MโŒ˜ + Shift + M
Zoom DevTools in / out / resetCtrl + + / Ctrl + - / Ctrl + 0โŒ˜ + + / โŒ˜ + - / โŒ˜ + 0

The drawer is underrated: press Esc in the Elements or Network panel and a Console opens underneath, so you can run code against what you are looking at.

Debug JavaScript (Sources panel)โ€‹

ActionWindows / LinuxMac
Pause or resumeF8 or Ctrl + \F8 or โŒ˜ + \
Step over the next callF10 or Ctrl + 'F10 or โŒ˜ + '
Step into the next callF11 or Ctrl + ;F11 or โŒ˜ + ;
Step out of the current functionShift + F11 or Ctrl + Shift + ;Shift + F11 or โŒ˜ + Shift + ;
Toggle a breakpoint on the current lineCtrl + BโŒ˜ + B
Deactivate all breakpointsCtrl + F8โŒ˜ + F8
Go to lineCtrl + GCtrl + G
Go to a function in the fileCtrl + Shift + OโŒ˜ + Shift + O

On a Mac, the function keys may need Fn, which is why the letter versions exist.

Deactivate, don't delete. Ctrl + F8 switches every breakpoint off at once and keeps them where they are, for when you want the page to run normally for a minute.

Elements panelโ€‹

ActionWindows / LinuxMac
Hide the selected elementHH
Edit the element as HTMLF2Fn + F2
Delete the selected elementDeleteDelete
Undo a changeCtrl + ZโŒ˜ + Z
Expand or collapse a nodeโ†’ / โ†โ†’ / โ†
Search the DOM (text, selector, XPath)Ctrl + FโŒ˜ + F

H toggles visibility: hidden on the element, so the layout keeps its space. It is the fastest way to see what is underneath a modal, a banner or a sticky header.

Consoleโ€‹

ActionWindows / LinuxMac
Clear the consoleCtrl + LโŒ˜ + K
New line without runningShift + EnterShift + Enter
Previous / next commandโ†‘ / โ†“โ†‘ / โ†“
Accept an autocompleteTab or โ†’Tab or โ†’

The Console also answers to a few shortcuts in code: $0 is the element selected in the Elements panel, $_ the last result, and copy(value) puts any value on your clipboard.

Network panelโ€‹

ActionWindows / LinuxMac
Start or stop recordingCtrl + EโŒ˜ + E
Reload, recording from the startCtrl + RโŒ˜ + R
Hard reload, ignoring the cacheCtrl + Shift + RโŒ˜ + Shift + R

With DevTools open, right-click (or long-press) the browser's reload button for Empty cache and hard reload, which also clears what the page cached. Our guide to the Network tab covers the panel itself: filters, timing, Copy as cURL, blocking and overrides.

Browser shortcuts developers use all dayโ€‹

ActionWindows / LinuxMac
Jump to the address barCtrl + LโŒ˜ + L
Reopen the last closed tabCtrl + Shift + TโŒ˜ + Shift + T
Next / previous tabCtrl + Tab / Ctrl + Shift + TabโŒ˜ + Option + โ†’ / โŒ˜ + Option + โ†
View the page sourceCtrl + UโŒ˜ + Option + U
Open a new incognito windowCtrl + Shift + NโŒ˜ + Shift + N
Open the history pageCtrl + HโŒ˜ + Y

An incognito window is the quickest clean profile: no cookies, no cache, and no extensions unless you allowed them there.

Shortcuts for what DevTools does not doโ€‹

DevTools inspects what the page sends and receives. Changing it, so you can see how the page copes with a different answer, is where an extension takes over. tweak mocks and modifies responses, rewrites headers, redirects and blocks requests, and it has its own shortcuts:

ActionWindows / LinuxMac
Start or stop tweak on the tabCtrl + Shift + ,โŒ˜ + Shift + ,
Open tweakCtrl + Shift + .โŒ˜ + Shift + .
Open or close the Developer ToolboxCtrl + Shift + YโŒ˜ + Shift + Y
Search your rules (in tweak)Ctrl + KโŒ˜ + K

The full list, and how to change them, is in the shortcuts docs.

Make your ownโ€‹

  • DevTools: Settings (F1) > Shortcuts lists every shortcut, lets you change one, and can switch the whole keymap to Visual Studio Code's.
  • Extensions: chrome://extensions/shortcuts sets or changes the shortcuts of every extension you have installed.

FAQโ€‹

What is the keyboard shortcut to open Chrome DevTools?

F12 or Ctrl + Shift + I on Windows and Linux, Cmd + Option + I on a Mac. Ctrl + Shift + J (Cmd + Option + J) opens it on the Console, and Ctrl + Shift + C (Cmd + Shift + C) opens it in inspect element mode.

What is the most useful DevTools shortcut to learn first?

The Command Menu: Ctrl + Shift + P, or Cmd + Shift + P on a Mac. Type what you want (screenshot, dark mode, disable JavaScript, sensors, blocking) and run it, without knowing which panel or menu it lives in.

How do I see every DevTools shortcut?

Open DevTools Settings with F1 (or ? while DevTools has focus) and pick Shortcuts. It lists every shortcut, and you can switch the keymap to Visual Studio Code's.

Why does a DevTools shortcut not work?

Most of them only work while DevTools has focus. Click inside DevTools first. On a Mac, some function keys need Fn, and the operating system or another extension may take a combination before Chrome sees it.

Summaryโ€‹

Learn three first: open DevTools (F12), inspect an element (Ctrl + Shift + C) and the Command Menu (Ctrl + Shift + P). Add the debugger's step keys when you next set a breakpoint, and Esc for the drawer. The rest you can look up here, or in DevTools Settings > Shortcuts.

If you liked this article, consider sharing (tweeting) it to your followers.



Did you like this article?

Need something else? Request a feature