Query Monitor is the developer tools panel for WordPress.
Query Monitor is the developer tools panel for WordPress. It enables debugging of database queries, PHP errors, hooks and actions, block editor blocks, enqueued scripts and stylesheets, HTTP API calls, and more.
It includes some advanced features such as debugging of Ajax calls, REST API calls, user capability checks, and full support for block themes and full site editing. It includes the ability to narrow down much of its output by plugin or theme, allowing you to quickly determine poorly performing plugins, themes, or functions.
Query Monitor focuses heavily on presenting its information in a useful manner, for example by showing aggregate database queries grouped by the plugins, themes, or functions that are responsible for them. It adds an admin toolbar menu showing an overview of the current page, with complete debugging information shown in panels once you select a menu item.
Query Monitor supports versions of WordPress up to three years old, and PHP version 7.4 or higher.
For complete information, please see the Query Monitor website.
Here’s an overview of what’s shown for each page load:
SELECT
, UPDATE
, DELETE
, etc), responsible component (plugin, theme, WordPress core), and calling function, and provides separate aggregate views for each.is_single()
, is_home()
, etc.switch_to_blog()
and restore_current_blog()
on Multisite installations.In addition:
qm
property of the response.By default, Query Monitor’s output is only shown to Administrators on single-site installations, and Super Admins on Multisite installations.
In addition to this, you can set an authentication cookie which allows you to view Query Monitor output when you’re not logged in (or if you’re logged in as a non-Administrator). See the Settings panel for details.
I maintain several other plugins for developers. Check them out:
Query Monitor is private by default and always will be. It does not persistently store any of the data that it collects. It does not send data to any third party, nor does it include any third party resources. Query Monitor’s full privacy statement can be found here.
Query Monitor aims to be fully accessible to all of its users. Query Monitor’s full accessibility statement can be found here.
Yes, it’s actively tested and working up to PHP 8.2.
By default, Query Monitor’s output is only shown to Administrators on single-site installations, and Super Admins on Multisite installations.
In addition to this, you can set an authentication cookie which allows you to view Query Monitor output when you’re not logged in, or when you’re logged in as a user who cannot usually see Query Monitor’s output. See the Settings panel for details.
Short answer: Yes, but only a little.
Long answer: Query Monitor has a small impact on page generation time because it hooks into a few places in WordPress in the same way that other plugins do. The impact is negligible.
On pages that have an especially high number of database queries (in the hundreds), Query Monitor currently uses more memory than I would like it to. This is due to the amount of data that is captured in the stack trace for each query. I have been and will be working to continually reduce this.
Yes, you can call do_action( 'qm/cease' )
to instruct Query Monitor to cease operating for the remainder of the page generation. It will detach itself from further data collection, discard any data it’s collected so far, and skip the output of its information.
This is useful for long-running operations that perform a very high number of database queries, consume a lot of memory, or otherwise are of no concern to Query Monitor, for example:
A list of add-on plugins for Query Monitor can be found here.
In addition, Query Monitor transparently supports add-ons for the Debug Bar plugin. If you have any Debug Bar add-ons installed, deactivate Debug Bar and the add-ons will show up in Query Monitor’s menu.
Please use the issue tracker on Query Monitor’s GitHub repo as it’s easier to keep track of issues there, rather than on the wordpress.org support forums.
Yes, the Altis Developer Tools are built on top of Query Monitor.
Yes, but a user needs to be granted the view_query_monitor
capability to see Query Monitor even if they’re an administrator. See the WordPress VIP documentation for more details.
This feature was removed in version 3.12 as it was rarely used and considerably increased the maintenance burden of Query Monitor itself. Feel free to continue using version 3.11 if you need to make use of this feature.
Yes. You can enable this on the Settings panel.
You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team helps validate, triage, and handle any security vulnerabilities. Report a security vulnerability here.
I am accepting sponsorships via the GitHub Sponsors program. If you work at an agency that develops with WordPress, ask your company to provide sponsorship in order to invest in its supply chain. The tools that I maintain probably save your company time and money, and GitHub sponsorship can now be done at the organisation level.
In addition, if you like the plugin then I’d love for you to leave a review. Tell all your friends about it too!
qm/assert
actiondb.php
handling when activating and deactivating Query Monitor on a single site within a Multisite network, and when DISALLOW_FILE_MODS
is in use$EZSQL_ERROR
for database query errors as it’s not possible to determine if the error should be ignoredsessionStorage
for the selected table column filters so they don’t persist across tabs or sessionswpdb
(see the FAQ for more information)wp-content/db.php
from another plugin doesn’t get removed when deactivating QMposix_getpwuid()
or posix_getgrgid()
doesn’t return an expected value.For the changelog of earlier versions, please refer to the releases page on GitHub.