12 DevTools capabilities that most developers never discover.
Everyone knows how to right-click and "Inspect Element." But DevTools has a massive feature set buried under those familiar panels. Here are the ones that genuinely matter for daily development work.
Select an element in the Elements panel, then switch to Console. Type $0 and you get a direct reference to that element. You can call methods on it, check properties, modify styles - all without writing a querySelector. $1 gives you the previously selected element, and so on up to $4.
Type document.designMode = 'on' in the Console. Now you can click anywhere on the page and just start typing. Every text element becomes editable. It's perfect for testing copy changes, checking how longer text affects layout, or quickly mocking up content changes. Type document.designMode = 'off' when you're done.
The Console has a copy() function that works on any value. copy($0) copies the selected element's HTML. copy(JSON.stringify(data, null, 2)) copies formatted JSON. Way faster than selecting and Ctrl+C.
Your site loads fast on your MacBook Pro with gigabit fiber. Your users in rural areas? Not so much. The Network panel has a throttle dropdown that simulates slow connections - "Slow 3G" and "Fast 3G" are the presets, but you can create custom profiles. Test your loading states properly.
You can intercept network responses and replace them with local files. Open Sources panel, enable "Local Overrides," pick a folder. Now edit any fetched resource and your changes persist across page reloads. It's like having a local proxy without setting one up. Great for testing API response changes without modifying the backend.
Right-click any element in the Elements panel and choose "Capture node screenshot." It exports a perfectly cropped PNG of just that element, with proper dimensions and transparent background if applicable. No more cropping full-page screenshots.
Click any color value in the Styles panel to open the color picker. Then click the eyedropper icon. Now you can click anywhere on the page to sample that pixel's exact color. Works across the entire viewport, not just the inspected element.
Open the Changes tab (More tools in the three-dot menu). It shows a diff of every CSS change you've made in the Elements panel during this session. When you're happy with your tweaks, you can see exactly what changed and copy it back to your source code. No more trying to remember which property you modified.
Open it from the three-dot menu (More tools, then Coverage). Click the reload button. It shows you exactly how much of each CSS and JS file is actually being used on the current page. Red means unused. If 70% of your CSS is red, you've got dead code to clean up.
More tools, Performance monitor. It shows real-time CPU usage, JS heap size, DOM nodes, layout recalculations, and style recalculations as a live dashboard. Leave it open while interacting with your site to spot performance issues as they happen.
The Computed tab in the Elements panel shows the final calculated values for every CSS property on the selected element. When you can't figure out why something is 17px instead of 16px, the computed panel shows you the actual value and you can click through to see which rule won the cascade.
The best way to learn DevTools is to use one new feature per debugging session. Next time you're hunting a bug, try using $0 or the Coverage tab instead of your usual approach. The features become second nature fast once you've used them in real situations.
Need the full keyboard shortcut reference? Check out the Chrome DevTools shortcuts cheat sheet.