This page is a reference of keyboard shortcuts in Chrome DevTools.
- Chrome Browser Developer Tools
- Chrome Developer Tools Download
- Ie Developer Tool Download
- Chrome Apps & Extensions Developer Tool
- Chrome Apps & Extensions Developer Tool For Mac
React Developer Tools is a Chrome DevTools extension for the open-source React JavaScript library. It allows you to inspect the React component hierarchies in the Chrome Developer Tools (formerly WebKit Web I. The original concept of this Chrome extension for developers came from the PNH Developer Toolbar. The chrome extension web developers has a lot of handy tools a developer can use in their day-to-day work – for designers as well as programmers. Discover and download great Developer Tools apps for Chrome.
You can also find shortcuts in tooltips. Hover over a UI element of DevToolsto display its tooltip. If the element has a shortcut, the tooltip includes it.
Keyboard shortcuts for opening DevTools
To open DevTools, press the following keyboard shortcuts while your cursor is focusedon the browser viewport:
Action | Mac | Windows / Linux |
---|---|---|
Open whatever panel you used last | Command+Option+I | F12 or Control+Shift+I |
Open the Console panel | Command+Option+J | Control+Shift+J |
Open the Elements panel | Command+Shift+C or Command+Option+C | Control+Shift+C |
Global keyboard shortcuts
The following keyboard shortcuts are available in most, if not all, DevTools panels.
Action | Mac | Windows / Linux |
---|---|---|
Show Settings | ? or Function+F1 | ? or F1 |
Focus the next panel | Command+] | Control+] |
Focus the previous panel | Command+[ | Control+[ |
Switch back to whatever docking position you last used. If DevTools has been in its default position for the entire session, then this shortcut undocks DevTools into a separate window | Command+Shift+D | Control+Shift+D |
Toggle Device Mode | Command+Shift+M | Control+Shift+M |
Toggle Inspect Element Mode | Command+Shift+C | Control+Shift+C |
Open the Command Menu | Command+Shift+P | Control+Shift+P |
Toggle the Drawer | Escape | Escape |
Normal reload | Command+R | F5 or Control+R |
Hard reload | Command+Shift+R | Control+F5 or Control+Shift+R |
Search for text within the current panel. Not supported in the Audits, Application, and Security panels | Command+F | Control+F |
Opens the Search tab in the Drawer, which lets you search for text across all loaded resources | Command+Option+F | Control+Shift+F |
Open a file in the Sources panel | Command+O or Command+P | Control+O or Control+P |
Zoom in | Command+Shift++ | Control+Shift++ |
Zoom out | Command+- | Control+- |
Restore default zoom level | Command+0 | Control+0 |
Run snippet | Press Command+O to open the Command Menu, type ! followed by the name of the script, then press Enter | Press Control+O to open the Command Menu, type ! followed by the name of the script, then press Enter |
Elements panel keyboard shortcuts
Action | Mac | Windows / Linux |
---|---|---|
Undo change | Command+Z | Control+Z |
Redo change | Command+Shift+Z | Control+Y |
Select the element above / below the currently-selected element | Up Arrow / Down Arrow | Up Arrow / Down Arrow |
Expand the currently-selected node. If the node is already expanded, this shortcut selects the element below it | Right Arrow | Right Arrow |
Collapse the currently-selected node. If the node is already collapsed, this shortcut selects the element above it | Left Arrow | Left Arrow |
Expand or collapse the currently-selected node and all of its children | Hold Option then click the arrow icon next to the element's name | Hold Control+Alt then click the arrow icon next to the element's name |
Toggle Edit Attributes mode on the currently-selected element | Enter | Enter |
Select the next / previous attribute after entering Edit Attributes mode | Tab / Shift+Tab | Tab / Shift+Tab |
Hide the currently-selected element | H | H |
Toggle Edit as HTML mode on the currently-selected element | Function+F2 | F2 |
Styles pane keyboard shortcuts
Action | Mac | Windows / Linux |
---|---|---|
Go to the line where a property value is declared | Hold Command then click the property value | Hold Control then click the property value |
Cycle through the RBGA, HSLA, and Hex representations of a color value | Hold Shift then click the Color Preview box next to the value | Hold Shift then click the Color Preview box next to the value |
Select the next / previous property or value | Click a property name or value then press Tab / Shift+Tab | Click a property name or value then press Tab / Shift+Tab |
Increment / decrement a property value by 0.1 | Click a value then press Option+Up Arrow / Option+Down Arrow | Click a value then press Alt+Up Arrow / Alt+Down Arrow |
Increment / decrement a property value by 1 | Click a value then press Up Arrow / Down Arrow | Click a value then press Up Arrow / Down Arrow |
Increment / decrement a property value by 10 | Click a value then press Shift+Up Arrow / Shift+Down Arrow | Click a value then press Shift+Up Arrow / Shift+Down Arrow |
Increment / decrement a property value by 100 | Click a value then press Command+Up Arrow / Command+Down Arrow | Click a value then press Control+Up Arrow / Control+Down Arrow |
Sources panel keyboard shortcuts
Action | Mac | Windows / Linux |
---|---|---|
Pause script execution (if currently running) or resume (if currently paused) | F8 or Command+ | F8 or Control+ |
Step over next function call | F10 or Command+' | F10 or Control+' |
Step into next function call | F11 or Command+; | F11 or Control+; |
Step out of current function | Shift+F11 or Command+Shift+; | Shift+F11 or Control+Shift+; |
Continue to a certain line of code while paused | Hold Command and then click the line of code | Hold Control and then click the line of code |
Select the call frame below / above the currently-selected frame | Control+. / Control+, | Control+. / Control+, |
Save changes to local modifications | Command+S | Control+S |
Save all changes | Command+Option+S | Control+Alt+S |
Go to line | Control+G | Control+G |
Jump to a line number of the currently-open file | Press Command+O to open the Command Menu, type : followed by the line number, then press Enter | Press Control+O to open the Command Menu, type : followed the line number, then press Enter |
Jump to a column of the currently-open file (for example line 5, column 9) | Press Command+O to open the Command Menu, type :, then the line number, then another :, then the column number, then press Enter | Press Control+O to open the Command Menu, type :, then the line number, then another :, then the column number, then press Enter |
Go to a function declaration (if currently-open file is HTML or a script), or a rule set (if currently-open file is a stylesheet) | Press Command+Shift+O, then type in the name of the declaration / rule set, or select it from the list of options | Press Control+Shift+O, then type in the name of the declaration / rule set, or select it from the list of options |
Close the active tab | Option+W | Alt+W |
Code Editor keyboard shortcuts
Action | Mac | Windows / Linux |
---|---|---|
Delete all characters in the last word, up to the cursor | Option+Delete | Control+Delete |
Add or remove a line-of-code breakpoint | Focus your cursor on the line and then press Command+B | Focus your cursor on the line and then press Control+B |
Go to matching bracket | Control+M | Control+M |
Toggle single-line comment. If multiple lines are selected, DevTools adds a comment to the start of each line | Command+/ | Control+/ |
Select / de-select the next occurrence of whatever word the cursor is on. Each occurrence is highlighted simultaneously | Command+D / Command+U | Control+D / Control+U |
Performance panel keyboard shortcuts
Action | Mac | Windows / Linux |
---|---|---|
Start / stop recording | Command+E | Control+E |
Save recording | Command+S | Control+S |
Load recording | Command+O | Control+O |
Memory panel keyboard shortcuts
Action | Mac | Windows / Linux |
---|---|---|
Start / stop recording | Command+E | Control+E |
Console panel keyboard shortcuts
Action | Mac | Windows / Linux |
---|---|---|
Accept autocomplete suggestion | Right Arrow or Tab | Right Arrow or Tab |
Reject autocomplete suggestion | Escape | Escape |
Get previous statement | Up Arrow | Up Arrow |
Get next statement | Down Arrow | Down Arrow |
Focus the Console | Control+` | Control+` |
Clear the Console | Command+K or Option+L | Control+L |
Force a multi-line entry. Note that DevTools should detect multi-line scenarios by default, so this shortcut is now usually unnecessary | Command+Return | Shift+Enter |
Execute | Return | Enter |
Expand all sub-properties of an object that's been logged to the Console | Hold Alt then click Expand | Hold Alt then click Expand |
Feedback
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
Google today announced plans to kill off Chrome apps for Windows, Mac, and Linux in early 2018. Chrome extensions and themes will not be affected, while Chrome apps will continue to live on in Chrome OS.
Chrome apps are web applications that run on Google’s browser. There are two types: Hosted apps (first available in December 2010) contain a single manifest file and are limited by webpage security restrictions, while packaged apps (first available in September 2013) have features similar to native desktop apps and can interact with local storage.
![Extensions Extensions](https://images.filehippo.net/img/ex/1177__chrome1.png)
In December 2015, Google removed the notification center from Chrome and in July 2016, the company removed the Chrome app launcher from its browser on Windows, Mac, and Linux. After making Chrome apps harder to access, the company is now turning its attention to the apps themselves.
Here’s the deprecation timeline:
- Late 2016: Newly published Chrome apps will not be available to Windows, Mac, and Linux users (when developers submit apps to the Chrome Web Store, they will only show up for Chrome OS). Existing Chrome apps will remain available as they are today and developers can continue to update them.
- Second half of 2017: The Chrome Web Store will no longer show Chrome apps on Windows, Mac, and Linux.
- Early 2018: Chrome apps will not load on Windows, Mac, and Linux.
Over the next few months, the Chrome Web Store “will undergo a series of UI changes to emphasize extensions and themes,” a Google spokesperson told VentureBeat. Given that it won’t be surfacing Chrome apps on Windows, Mac, nor Linux, it makes sense that to give the store a new look and feel.
So why is Google killing Chrome apps off now? There appear to be two main reasons.
First, web apps have gotten more powerful over the years, as Google explains:
For a while there were certain experiences the web couldn’t provide, such as working offline, sending notifications, and connecting to hardware. We launched Chrome apps three years ago to bridge this gap. Since then, we’ve worked with the web standards community to enable an increasing number of these use cases on the web. Developers can use powerful new APIs such as service worker and web push to build robust Progressive Web Apps that work across multiple browsers.
I asked Google why it is choosing to start deprecating Chrome apps now and not sooner.
Chrome Browser Developer Tools
“We wanted to wait until a lot of the Chrome Apps functionality was brought to the web,” a Google spokesperson told VentureBeat. “We know there are still gaps on the web platform and that all of Apps functionality hasn’t been replicated, but we’re working on it and want to collaborate with developers and other browsers to identify what are the most important APIs we could be adding.”
And secondly, Chrome apps aren’t very popular:
Today, approximately 1 percent of users on Windows, Mac and Linux actively use Chrome packaged apps, and most hosted apps are already implemented as regular web apps. Chrome on Windows, Mac, and Linux will therefore be removing support for packaged and hosted apps over the next two years.
It’s great to see Google giving developers more than 1.5 years to migrate their apps, but that’s really the only good news here if you invested in the platform. Not all Chrome apps can be easily ported to the web, so Google is asking these developers to help the company prioritize new APIs, consider building a Chrome extension, or move to platforms such as Electron or NW.js.
Chrome Developer Tools Download
Chrome apps are all but dead
Chrome OS appears to have come out unscathed in the removal of Chrome apps, the Chrome app launcher, and app notifications. This makes sense given that these were all built for Chrome OS in the first place.
And Google promises that “additional enhancements to the Chrome apps platform” are on the way. At the same time, the company states, “Developers can continue to build Chrome apps (or Android apps) for Chrome OS” but that “On Windows, Mac, and Linux, we encourage developers to migrate their Chrome apps to the web.”
The trouble is that most developers who build Chrome apps aren’t targeting just Chrome OS or just Windows, Mac, and Linux. The appeal was that building a Chrome app would ensure it worked on Chrome OS as well as Chrome for Windows, Mac, and Linux.
This naturally raises the question: Why build or maintain Chrome apps anymore? They were already not very popular, even when available across Windows, Mac, Linux, and Chrome OS. But now, with Windows, Mac, and Linux out of the picture, as well as with Google Play coming to Chrome OS next month, it’s an incredibly hard sell to developers.
Ie Developer Tool Download
Want to build an Android app or a Chrome extension? Go for it. The former will work on Android and Chrome OS while the latter will work on Windows, Mac, Linux, and Chrome OS.
Chrome apps, however, will soon be a Chrome OS-only affair.
Chrome Apps & Extensions Developer Tool
My last question to Google: Why would a developer build a Chrome OS app when they can just build an Android app that works on Chrome OS?
Chrome Apps & Extensions Developer Tool For Mac
“We want to leave it to developers to build what makes sense for them based on their user base and their development stack,” a Google spokesperson told VentureBeat.