WordPress PHP Fatal Error Decoder
Paste the error. See which plugin it points to.
Runs in your browser. Nothing is uploaded.
Paste an error and the culprit appears here.
The culprit
—
—
What the error means
—
What to do
About the WordPress PHP Fatal Error Decoder
Paste a WordPress PHP fatal error to see which plugin or theme its stack trace points to, what the error means and what to try next. It runs in your browser.
Paste a PHP fatal error from debug.log, your host's error log or the white screen. The decoder finds the file the error points to and says whether that file belongs to a plugin, a theme, a must-use plugin, a drop-in, wp-config.php or WordPress core. It then explains the error type and lists what to try. The text is read in your browser and not sent anywhere.
Worked example: a plugin calls a function that does not exist
Input: an entry that WordPress 7.1.4 wrote to wp-content/debug.log on a WordPress Playground test site (PHP 8.3, 1 November 2026). The test plugin, some-addon, calls a function that is not defined anywhere.
[01-Nov-2026 16:57:07 UTC] PHP Fatal error: Uncaught Error: Call to undefined function some_addon_missing_helper() in /wordpress/wp-content/plugins/some-addon/some-addon.php:6
Stack trace:
#0 /wordpress/wp-includes/class-wp-hook.php(353): {closure}('')
#1 /wordpress/wp-includes/class-wp-hook.php(377): WP_Hook->apply_filters(NULL, Array)
#2 /wordpress/wp-includes/plugin.php(523): WP_Hook->do_action(Array)
#3 /wordpress/wp-includes/template-loader.php(23): do_action('template_redire...')
#4 /wordpress/wp-blog-header.php(19): require_once('/wordpress/wp-i...')
#5 /wordpress/index.php(17): require('/wordpress/wp-b...')
#6 {main}
thrown in /wordpress/wp-content/plugins/some-addon/some-addon.php on line 6 Output, from running the decoder's own script in Node.js with that input on 16 November 2026. The three result boxes are shown as plain text.
The culprit
Plugin: some-addon
/wordpress/wp-content/plugins/some-addon/some-addon.php:6
What the error means
Something called the function some_addon_missing_helper(), which did not exist at the moment it ran. Usually a plugin depends on another plugin, or on a PHP extension, that is not active. It can also mean the function was called too early, before WordPress had loaded the file that defines it.
What to do
1. If the function name looks like it belongs to another plugin (acf_*, wc_*, elementor_*), that plugin is deactivated, deleted, or loading after this one. Reactivate it.
2. If the plugin was just updated, the update may have dropped a dependency. Roll it back.
3. If the function is part of PHP itself (for example mb_strlen, curl_init or imagecreatefromjpeg), your server is missing a PHP extension. Ask your host to enable it. How it got there:
- It started at the "PHP Fatal error" line. A debug.log usually holds many entries, so the decoder takes the last fatal error in what you paste and reads down to the next timestamp. Warnings and notices above it are ignored.
- "Call to undefined function" is one of the nine error types it knows. The function name in the meaning comes from the message.
- The file comes from "in /wordpress/wp-content/plugins/some-addon/some-addon.php:6", and the folder after wp-content/plugins/ gives "Plugin: some-addon". That is the plugin's folder name, which is not always the name on the Plugins screen.
- Frames #0 to #6 show WordPress running the template_redirect hook, which called the plugin's code. The error was raised in the plugin file itself, so the decoder did not need them here.
- The steps are fixed text for this error type. Step 3 does not apply in this case: some_addon_missing_helper is not a PHP function.
The fix here is to deactivate some-addon. If wp-admin is down too, rename the plugin's folder in wp-content/plugins over FTP or your host's file manager, and its code stops loading.
When the error surfaces in core
Many fatal errors are raised inside wp-includes, because that is where WordPress runs a plugin's callback or uses the value a plugin passed in. When the file in the message belongs to core, the decoder walks the stack trace and names the first plugin or theme frame it finds.
For example, take a made-up entry whose message points at wp-includes/class-wp-hook.php line 324, with frame #2 in /srv/wp-content/plugins/fancy-forms/inc/setup.php line 88. The decoder names "Plugin: fancy-forms", shows that frame's file and line, and puts this note first in the steps: "The error surfaced in another file, but the stack trace shows this code made the call that led there. Start with it."
If the paste has no frames at all, it can only say that the file is core, and it asks for more of the trace. Copy the whole entry from debug.log; the WP_DEBUG code generator writes the lines that turn the log on.
What it recognises
Nine kinds of PHP fatal error: call to undefined function, call to undefined method, cannot redeclare, class not found, missing required file, memory exhausted, maximum execution time exceeded, syntax (parse) error, and any other uncaught error or exception. A missing file that belongs to WordPress itself (in wp-includes or wp-admin) is reported as incomplete WordPress files, with the steps to put them back. The exception is a file that WordPress 7.1.4's updater deletes because newer WordPress no longer includes it (the list in wp-admin/includes/update-core.php): when a plugin or theme still loads one of those, the decoder names that plugin or theme and says it needs an update. Any other PHP fatal error still gets its file, its plugin or theme and PHP's own message.
A paste with only warnings, notices or deprecations gets a short answer: where the line came from, and that PHP kept running after it. Four warnings get their own answer, because each one does break something: "Cannot modify header information - headers already sent" names the file after "output started at" (and says so when PHP left that part out), the mysqli_real_connect() warning that comes before "Error establishing a database connection" explains the common reason codes (1045, 2002, 1040, 1203 and 1226), "POST Content-Length … exceeds the limit" shows the request size against post_max_size, and PHP's own "Input variables exceeded …" warning ("in Unknown on line 0") says that PHP dropped the form fields beyond max_input_vars, so part of what you saved never reached WordPress. (The same words from parse_str() in a plugin's file are read like any other warning.) When "headers already sent" names a file outside WordPress core after "output started at", that answer wins over the others in the same paste. Otherwise the database warning comes first, then the two size limits, then "headers already sent". Any other warning PHP writes while it starts up ("PHP Startup:" or "PHP Request Startup:", "in Unknown on line 0") is reported as a PHP setting, not a plugin problem, unless the paste also has a warning from a plugin, a theme or another file outside WordPress core and wp-config.php: then the paste is read like any other warning, and the first file with a warning in it is named.
It reads the error format of debug.log, of Apache's error_log (which writes the stack trace on one line, with \n for each line break, and doubles every backslash) and of nginx's "PHP message:" lines. When PHP-FPM joins a warning and the fatal error from the same request into one entry, it reads the fatal error's part. It also reads the HTML version PHP prints on a white screen, the same text copied from the browser (where the whole stack trace ends up on one line), and the "An error of type E_ERROR was caused in line … of the file …" text from the email WordPress sends when it pauses a plugin or theme (that wording is read from the WordPress 7.1.4 source). File paths can be Unix or Windows style, with or without spaces (LocalWP puts sites in a "Local Sites" folder). The plugin or theme is taken from the first plugins, mu-plugins or themes folder below wp-content, so code that a theme bundles in its own plugins subfolder still counts as the theme's. Code that a plugin ran through PHP's eval(), the way snippet plugins such as Code Snippets run snippets, is named as that plugin's, with a note that the line counts lines in the snippet. For a chained exception ("Next …"), the meaning and the file both come from the first one, where the problem started.
For the problems behind these errors, see the guides to the "There has been a critical error" message and the white screen of death. A memory exhausted error has its own guide, because raising the limit is not always the fix.
Limits
- It decodes PHP fatal errors. Apart from the warnings above, a paste of PHP warnings or notices gets a short note, not a diagnosis. The "Error establishing a database connection" page on its own, a 500 error with no message, or a JavaScript error from the browser console does not match any pattern, and the decoder says so.
- It names the code the error points to, which is usually but not always the code at fault. For a type error or an argument-count error, it starts from the function that refused the value; when that function is part of WordPress, the stack trace decides, as above. A plugin can crash because another plugin passed it bad data, or because it needs a newer PHP version than your server runs.
- The steps are general advice for the error type. They do not know your plugins, your host or what you changed last.
- Memory and timeout errors have no stack trace, so the file they name is just where PHP happened to be when the limit ran out.
Sources
- WordPress Advanced Administration Handbook: Debugging in WordPress
- WordPress Code Reference: wp_get_extension_error_description() (the "An error of type … was caused in line …" text in the recovery email)
- PHP Manual: Error Handling, Predefined Constants (E_ERROR, E_PARSE and the other error types)
Guides for this tool
The decoder reads PHP errors: the text you find in debug.log, in your host's error log or on the white screen. It cannot read the "Error establishing a database connection" page itself or a JavaScript error from the browser console, so the guides for those problems use other checks.
- Error Establishing a Database Connection in WordPress
Fix the WordPress error establishing a database connection: check the four wp-config.php credentials, confirm the database server is up, then repair tables.
- There Has Been a Critical Error on This Website: The Fix
Get past the screen saying there has been a critical error on this website by reading the real PHP message in debug.log and disabling the plugin behind it.
- WordPress HTTP Error on Image Upload: Find the Real Cause
Find the cause of a WordPress HTTP error on image upload: read the status code, then check firewall, memory, post_max_size, Imagick, permissions and filename.
- Fix the WordPress Block Editor Not Loading
Fix a blank or broken WordPress block editor by reading the browser console, checking the REST API, and enabling WP_DEBUG to find the plugin that broke it.
- The WordPress White Screen of Death, Explained
Get your site back from the WordPress white screen of death: turn on the debug log, read the last fatal line, and rename the plugin folder it names.
Related
Other tools you might need
FAQ
Questions
What does 'Call to undefined function' mean in WordPress?
Something called a function that did not exist at the moment it ran. Usually a plugin depended on another plugin that is deactivated or deleted — or it ran too early, before WordPress had loaded the file defining the function. If the function is a PHP built-in like mb_ or curl_, your host is missing a PHP extension.
The error only mentions wp-includes files. Is WordPress core broken?
Usually not. Core is often just where a plugin's callback or bad value ended up, so core files sit at the top of the stack trace and the plugin that made the call sits further down. The decoder reads the frames and names the first plugin or theme it finds. If your paste has no frames, copy the whole entry from debug.log instead. The exception is a “Failed opening required” error for a file inside wp-includes or wp-admin: then WordPress's own files are missing, and the decoder says so. If that file is one WordPress deleted in an update and a plugin or theme still loads it, the decoder names that plugin or theme instead.
Is it safe to paste my error log here?
The parsing happens entirely in your browser, and the text you paste is never transmitted. Your network tab will show this site's own analytics requests, but none of them carries what you pasted. That is worth caring about: stack traces routinely contain absolute server paths, and sometimes worse.