Inspect and debug the pages you build without leaving VS Code. Open a folder, start Browser DevTools, and your
site appears in a live preview beside your code, with every inspection tool you know from the browser docked in
the panel next to the terminal. Save a file and the page updates; pick an element and its styles are right
there; break on a line and step through it in the editor's own debugger.
No browser window to juggle, no add-on to install in a browser, nothing to configure before the first run.
What it does for you
|
|
| Live preview |
Serves the folder you are working on and shows it in an editor tab. It finds a free port by itself and offers a starter page when the folder is empty. |
| Instant updates |
Saving a page reloads it; in built-in mode, saving a stylesheet restyles the page in place, without losing where you were. |
| Responsive design |
Device presets, a custom width and height, rotation and touch input, straight from the preview's toolbar. |
| Elements |
The page as a tree, a visual outline or a 3D view. Hover to highlight, click to select, edit attributes and content, delete nodes, and jump from an element to the line of source that made it. |
| Styles |
The rules that apply to the selected element, editable in place, its box model and its computed values, filterable. |
| Console |
Messages, uncaught errors and rejected promises, with objects you can expand like in the browser, and suggestions as you type. |
| Network |
Every request with its status, type and timing; open one to see headers, payload, response and a timing breakdown. |
| Performance |
Page load and resource timings, frame rate, and a CPU profile that shows where the time goes, function by function. |
| Memory |
Memory use over time and snapshots broken down by object type. |
| Storage |
Local and session storage, cookies with every field, and the page's databases, browsed and queried side by side. |
| Accessibility |
Roles, accessible names, whether it can take focus, and colour contrast for the selected element, plus the full accessibility tree. |
| Debugging |
Breakpoints in your own files, variables, watches, the chain of calls and stepping, all in VS Code's debugger, attached to the page in the preview. |
| Element picker |
Click anything in the page to select it in the inspector. |
Text in the panels is never smaller than your editor font, and the panels take on your VS Code theme.
Getting started
- Open the folder of your site in VS Code.
- Run Browser DevTools: Start Live Server & Inspector from the Command Palette, or press the play button in
the Browser DevTools panel.
- The preview opens in an editor tab and the inspector in the bottom panel, next to the terminal.
- Edit and save: the page follows.
To debug, run Browser DevTools: Debug Page (or Browser DevTools: Start & Debug). Debugging runs on the
browser mode described below; Browser DevTools offers to switch when needed. Browser DevTools: Add Debug
Configuration sets your workspace up so you can also attach from the Run and Debug view.
Two ways to run
- Built-in mode (the default) runs entirely inside VS Code. Nothing else to install.
- Browser mode runs your page in a Chromium-based browser already on your computer (Chrome, Edge or
Chromium, found automatically), shown live in the preview. It adds the interactive preview, the CPU profiler,
memory snapshots, full request and response bodies, errors traced back to your original source files, the full
accessibility tree and debugging.
Choose the mode with the Browser DevTools › Backend setting. Every panel works in both.
Settings
| Setting |
What it does |
| Public Directory |
The folder the preview serves (public by default): relative to the workspace, absolute, or using ${workspaceFolder}. |
| Port / Host |
Where the preview is served. A busy port is skipped for the next free one. |
| Auto Open Preview |
Open the preview as soon as Browser DevTools starts. |
| Spa Fallback |
Serve index.html for unknown addresses, for single-page apps with their own routing. |
| Backend |
Built-in mode or browser mode. |
| Chrome Path |
The browser to use in browser mode, when you want a specific one. |
| Remote Debugging Port |
The port the debugger attaches to in browser mode. |
| License: Status Bar |
Show the subscription in the status bar. |
Free and Pro
|
Free |
Pro |
| Live preview, instant updates, responsive design |
✓ |
✓ |
| Elements, Styles, Console, Network, Performance, Memory, Storage, Accessibility |
✓ |
✓ |
| Editing the page, element picker |
✓ |
✓ |
| Browser mode: interactive preview, CPU profiler, memory snapshots, full request bodies, errors traced to your source, full accessibility tree |
|
✓ |
| Debugging the page in VS Code's debugger |
|
✓ |
| Inspecting several pages at once |
|
✓ |
The trial: 60 minutes of Pro, once per install, with no account and no key. It starts when you ask for it,
never by itself: choose Start trial in the subscription menu or where a Pro feature asks. When it ends, Browser
DevTools keeps working on the Free plan and Pro features ask before they open.
Your plan in the status bar: the item reads Browser DevTools: Free, Pro, Team or Pro trial with
the time left. Click it, or run Browser DevTools: Subscription…, for the one menu that does everything: sign
in, start the trial, see the plans, manage your subscription, enter a license key.
Going Pro: choose Sign in. Your browser opens, you allow this computer with your Soft Forge account,
choosing a plan first if you have none, and Pro turns on. There is no key to copy, renewals arrive by themselves,
and Pro keeps working while you are offline for a while. Manage subscription opens your plans, bills and
devices; Sign out frees this computer's seat.
A license key, for a computer that cannot sign in: Enter license key takes the key from your client portal
and keeps it stored securely on the computer. It keeps working for 14 days without reaching Soft Forge.
Plans and subscriptions: https://soft-forge.dev/payments/browser-devtools/client/
| |