By default, the window appears docked to the bottom side of the Firefox window, but you can detach it if you like. This is what it looks like when it's docked:
The window itself is split into two parts: a toolbar along the top, and a main pane underneath:
The toolbar contains controls to activate a particular tool, to dock/float the window, and to close the window.
On the far left there's a button to activate the node picker. This lets you select a page element for inspection. See "Selecting elements".
Then there is an array of labeled buttons which enables you to switch between the different tools hosted by the Toolbox. The array may include the following tools:
Note that not all the hosted tools are always listed here: only the tools actually available in this context are shown (for example, not all tools support remote debugging yet, so if the debugging target is not the Firefox instance that launched the window, not all the hosted tools will be shown).
Next there's an array of buttons that can be added or removed in the developer tool settings. By default this array includes:
The following tools are not included in the toolbar by default, but you can add them in the settings:
- Highlight painted area
- 3D view
- Grab a color from the page
- Take a full-page screenshot: this is new in Firefox 32. It takes a screenshot of the complete web page and saves it in your Downloads directory
- Select a frame as the currently targeted document: this is new in Firefox 34.
Finally there's a row of buttons to:
- close the window
- toggle the window between attached to the bottom of the browser window, and attached to the side of the browser window
- toggle the window between standalone and attached to the browser window
- access developer tool settings
Clicking the "Settings" button () gives you access to settings for the Toolbox itself and for the tools it hosts:
Default Firefox Developer Tools
This group of checkboxes determines which tools are enabled in the toolbox. New tools are often included in Firefox but not enabled by default.
Available Toolbox Buttons
This group of checkboxes determines which "standalone tools" get buttons in the toolbar. This defaults to the node picker, the split console, and responsive design mode.
Firefox 32 adds a button to take a screenshot of the complete web page, which is unchecked by default.
Choose DevTools theme
This enables you to switch between a light and a dark theme:
Settings that apply to more than one tool. There's just one of these:
- Enable persistent logs: a setting to control whether or not the Web Console and Network Monitor clear their output when you navigate to a new page.
- Show browser styles: a setting to control whether styles applied by the browser (user-agent styles) should be displayed in the Inspector's Rules view. This setting is new in Firefox 32. Note that this setting is independent of the "Browser styles" checkbox in the Inspector's Computed view.
- Default color unit: a setting to control how colors are represented in the inspector:
- Enable timestamps: controls whether the Web Console displays timestamps. From Firefox 28 the Web Console defaults to hiding timestamps.
- Show original sources: when a CSS preprocessor supporting source maps is used, this enables the Style Editor to display the original, preprocessor, sources rather than the generated CSS. Learn more about Style Editor support for CSS source maps. With this setting checked, the Page Inspector Rules view will also provide links to the original sources.
- Autocomplete CSS: enable the Style Editor to offer autocomplete suggestions.
- Show Gecko platform data: a setting to control whether or not profiles should include Gecko platform symbols.
- Detect indentation: auto-indent new lines based on the current indentation
- Autoclose brackets
- Indent using spaces
- Tab size
- Keybindings: choose the default CodeMirror keybindings, or keybindings from one of several popular editors:
- Sublime Text
- Disable cache: disable the browser cache to simulate first-load performance. From Firefox 33 onwards this setting persists, meaning that if it is set, caching will be disabled whenever you reopen the devtools. Caching is re-enabled when the devtools are closed.
- Enable chrome debugging: enable you to use developer tools in the context of the browser itself, and not only web content
- Enable remote debugging: enable the developer tools to debug remote Firefox instances
The content of the main pane in the window is entirely controlled by, and specific to, the hosted tool currently selected.