liveBook · Manning

Browser developer tools

Also called DevTools, Dev Tools

Browser developer tools are browser-integrated utilities for inspecting, debugging, testing, profiling, and analyzing web pages, applications, and browser-executed code.

How 5 Manning books explain it

Fast by Default

Chrome DevTools is Google's integrated browser development toolkit for inspecting, debugging, and profiling web pages and applications.

How it is used
Diagnoses web loading, runtime, and memory problems before code review by comparing observed performance with budgets.
How deep it goes
Explains panel selection, trace recording, CPU throttling, flame-chart interpretation, and common diagnostic patterns rather than browser internals.
Examples
Uses a scrolling social widget with a 180 ms task and forced reflows, plus short page-load and button-click recordings.
What you can do after
Diagnose/debug with browser panels by recording focused traces, locating costly work, and rechecking fixes against a budget.

Read how Fast by Default explains browser developer tools →

WordPress Power Toolkit: Harness AI to build next-level websites

A browser inspector is a browser-integrated developer tool for examining and modifying a web page's HTML, CSS, layout, and runtime presentation.

How it is used
Helps investigate and test how CSS affects the appearance of HTML elements on a web page.
How deep it goes
Walks through opening the Inspector, selecting elements, reading overridden styles, and live-editing CSS; only lists its broader debugging tools.
Examples
Uses a selected HTML element, a crossed-out box-sizing value, an h1 CSS rule, and a search for a site theme.
What you can do after
Diagnose/debug with it by identifying applied or overridden CSS and previewing style changes immediately.

Read how WordPress Power Toolkit: Harness AI to build next-level websites explains browser developer tools →

CSS in Depth, Second Edition

Browser developer tools are built-in utilities for inspecting and debugging a webpage's structure, styles, and runtime behavior.

How it is used
Diagnoses CSS results by exposing applied, overridden, and inherited declarations for individual elements.
How deep it goes
Shows rule ordering, inheritance, overrides, source locations, filtering, and interactive clip-path editing.
Examples
Uses inherited fonts, crossed-out declarations, filtered properties, and draggable clip-path vertices as inspection examples.
What you can do after
Diagnose/debug with browser DevTools by locating the rule, inheritance path, or clip-path value behind a rendered result.

Read how CSS in Depth, Second Edition explains browser developer tools →

JavaScript in Depth

A set of browser developer tools for inspecting, debugging, profiling, and analyzing JavaScript applications.

How it is used
Diagnoses JavaScript applications interactively or from captured performance and memory artifacts.
How deep it goes
Connects runtimes and names profiling artifacts, but does not detail diagnostic interpretation or panel procedures.
Examples
Uses F12, node --inspect, node --inspect-brk, chrome://inspect, .cpuprofile files, and .heapsnapshot files.
What you can do after
Diagnose JavaScript behavior with browser tools, remote runtime inspection, profiles, heap snapshots, and memory graphs.

Read how JavaScript in Depth explains browser developer tools →

Vanilla Web

Browser developer tools are utilities for inspecting, debugging, testing, and profiling web pages and applications.

How it is used
Support browser-based editing and debugging during local web development, and inspect persisted application data when storage bugs arise.
How deep it goes
Shows source editing and names storage areas to inspect, but leaves freshness, migration, backup, and recovery strategy to application design.
Examples
Uses Chromium DevTools Workspaces to edit source and the Application tab to inspect storage usage and API data.
What you can do after
Operate browser tools to edit source in a workspace and diagnose stored data by inspecting browser storage areas.

Read how Vanilla Web explains browser developer tools →

Also covered in

What to know first

Related concepts

Questions about browser developer tools

What is browser developer tools?

Browser developer tools are browser-integrated utilities for inspecting, debugging, testing, profiling, and analyzing web pages, applications, and browser-executed code.

Which Manning books explain browser developer tools?

Fast by Default, WordPress Power Toolkit: Harness AI to build next-level websites, CSS in Depth, Second Edition, JavaScript in Depth and Vanilla Web.

What should I know before learning browser developer tools?

Manning books that teach browser developer tools usually introduce CSS, HTML and viewport first.

What is browser developer tools part of?

Browser developer tools is part of browser. A web browser is software that retrieves, interprets, and renders web resources, executes supported web content, and enables interaction with web applications.

What are the parts of browser developer tools?

Browser developer tools includes performance panel.

What is browser developer tools also called?

Browser developer tools is also called DevTools or Dev Tools.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.