This translation is incomplete. Please help translate this article from English.
For the latest developer tools and features, try Firefox Developer Edition.
The Core Tools
View and edit page content and layout. Visualise many aspects of the page including the box model, animations, and grid layouts.
These developer tools are also built into Firefox. Unlike the "Core Tools" above, you might not use them every day.
- Figure out which objects are keeping memory in use.
- Storage Inspector
- Inspect cookies, local storage, indexedDB, and session storage present in a page.
- DOM Property Viewer
- Inspect the page's DOM properties, functions, etc.
- Developer Toolbar
- A command-line interface for the developer tools.
- Select a color from the page.
- Style Editor
- View and edit CSS styles for the current page.
- Shader Editor
- View and edit the vertex and fragment shaders used by WebGL.
- Web Audio Editor
- Examine the graph of audio nodes in an audio context, and modify their parameters.
- Taking screenshots
- Take a screenshot of the entire page or of a single element.
See what your users see in their browsers. Test your sites in up to 800 browser and OS combinations with our cross-browser testing tutorial.
Made just for you by Mozilla and Sauce labs.
Connecting the Developer Tools
If you open the developer tools using keyboard shortcuts or the equivalent menu items, they'll target the document hosted by the currently active tab. But you can attach the tools to a variety of other targets, too, both within the current browser and in different browsers or even different devices.
- Debug add-ons, content tabs, and workers running in the browser.
- Connecting to Firefox for Android
- Connect the developer tools to an instance of Firefox running on an Android device.
- Connecting to iframes
- Connect the developer tools to a specific iframe in the current page.
- Connecting to other browsers
- Connect the developer tools to Chrome on Android and Safari on iOS.
Debugging the browser
By default, the developer tools are attached to a web page or web app. But you can also connect them to the browser as a whole. This is useful for browser and add-on development.
Extending the devtools
The developer tools are designed to be extensible. Firefox add-ons can access the developer tools and the components they use to extend existing tools and add new tools. With the remote debugging protocol, you can implement your own debugging clients and servers, enabling you to debug websites using your own tools or to debug different targets using the Firefox tools.
- Example devtools add-ons
- Use these examples to understand how to implement a devtools add-on.
- Add a new panel to the devtools
- Write an add-on that adds a new panel to the Toolbox.
- Remote Debugging Protocol
- The protocol used to connect the Firefox Developer Tools to a debugging target like an instance of Firefox or a Firefox OS device.
- Source Editor
- A code editor built into Firefox that can be embedded in your add-on.
- Web Console custom output
- How to extend and customize the output of the Web Console and the Browser Console.
Migrating from Firebug
Firebug is coming to the end of its lifespan (see Firebug lives on in Firefox DevTools for details of why), and we appreciate that some people will find migrating to another less familiar set of DevTools to be challenging. To ease a transition from Firebug to the Firefox developer tools, we have written a handy guide — Migrating from Firebug.
If you want to help to improve the developer tools, these resources will get you started.