6

How can I get Chrome to launch and close "developer tools" on Mac (like Firebug with F12 & Ctrl+Shift+C)? It was so convenient in Firefox/Firebug to just hit F12 followed by "toggle inspect mode" (Ctrl+Shift+C) and then hover my mouse over the different elements. I would love it if anyone else used to have this workflow.

phuclv
  • 26,555
  • 15
  • 113
  • 235
Elijah Lynn
  • 1,444
  • 3
  • 17
  • 26

3 Answers3

11

For those that are still looking for ways to access Chrome's Developer Tools:

To access the developer tools, open a web page or web app in Google Chrome. Then take one of the following actions:

  • Select the Wrench menu at the top-right of your browser window, then select Tools -> Developer tools.
  • Right-click on any page element and select Inspect element.
  • On Windows and Linux, press
    • Ctrl+Shift+I to open Developer Tools
    • Ctrl+Shift+J to open Developer Tools and bring focus to the Console.
    • Ctrl+Shift+C to toggle Inspect Element mode.
  • On OS X, press
    • ++I (Option+Command+I) to open Developer Tools
    • ++J (Option+Command+J) to open Developer Tools and bring focus to the Console.
    • ^++C (Control+Command+C) to toggle Inspect Element mode.

Source: http://code.google.com/intl/nl/chrome/devtools/docs/overview.html

appel
  • 226
  • 2
  • 6
  • 1
    You have the key symbols mixed up... **⌘ = Command, ⌥ = Option**. See [Dan Rodney's List of Mac OS X Keyboard Shortcuts & Keystrokes](http://www.danrodney.com/mac/). – Nathan Aug 13 '12 at 17:59
  • 1
    In newer versions of Google Chrome, you can now use F12 to open developer tools. – Petr Hudeček Sep 08 '14 at 05:20
0

On my Mac, I use:

"Cmd" + "Option" + "I" - To open/close Developer Tools

"Cmd" + "Shift" + "C" - Opens Inspect

Stuti Verma
  • 101
  • 1
0

Ctrl + Shift + I

Opens developer tools. I don't think you can toggle "inspect mode" (I found this looking for that)

Sathyajith Bhat
  • 61,504
  • 38
  • 179
  • 264
edfuh
  • 101
  • 1
  • Thanks for confirming that, one thing I really loved about Firebug, hopefully it comes to Chrome (or I switch back to FF). – Elijah Lynn Sep 28 '10 at 23:57