Where is PHP Error Log in WordPress? A Beginner’s Guide

When your WordPress site encounters a problem, it can feel overwhelming. You might face the infamous “white screen of death,” a broken feature, or a cryptic error message. These issues often stem from problems within the site’s underlying PHP code. To fix them, you first need to find the cause. This is where your WordPress PHP error log becomes your most valuable tool for troubleshooting.

This guide will walk you through everything you need to know. We’ll cover what a PHP error log is, why it’s so important, and provide step-by-step instructions on how to find it. Learning where the PHP error log in WordPress is located is a fundamental skill for managing your site effectively.

What Are PHP Error Logs?

WordPress is built using the PHP programming language. When your site’s code—whether from the core files, a plugin, or a theme—runs into a problem it can’t resolve, it generates an error. A PHP error log is a file that records these events as they happen.

Think of it as a black box for your website. It contains a chronological list of warnings, errors, and notices generated by your site’s code. Each entry typically includes:

• A timestamp of when the error occurred.
• The type of error (e.g., Fatal Error, Warning, Notice).
• A description of the problem.
• The specific file and line number where the error was triggered.

This information is invaluable for pinpointing exactly what went wrong and where.

Why Finding the Error Log is Crucial

Ignoring PHP errors is like ignoring the check engine light in your car. While some minor notices won’t break your site immediately, they can point to underlying issues that could cause significant problems later.

Here are the main reasons why you need to know how to access your error logs:

• Fast Troubleshooting: Instead of deactivating plugins one by one, the error log can point you directly to the faulty theme or plugin causing the issue. This saves you an immense amount of time and guesswork.
• Solving the White Screen of Death: A fatal PHP error is the most common cause of the “white screen of death.” The error log is often the only place you’ll find information about what caused the complete site failure.
• Improving Site Performance: Constant PHP warnings and notices can consume server resources, slowing down your website. Resolving these issues can lead to a faster, more stable site.
• Better Security: Some errors can expose potential vulnerabilities in your code. By identifying and fixing them, you help secure your website against potential attacks.

How to Find and Enable the WordPress PHP Error Log

The location of your PHP error log isn’t always obvious. By default, WordPress often has error logging turned off to save server space and hide potentially sensitive information. Therefore, the first step is usually to enable debugging mode.

Here are the primary methods to find where your PHP error log in WordPress is.

Step 1: Enable WordPress Debug Mode

The wp-config.php file is one of the most important files in your WordPress installation. It contains your site’s base configuration details, and it’s also where you can enable the built-in debugging mode.

You will need to access this file using an FTP client (like FileZilla) or the File Manager in your hosting provider’s control panel (like cPanel). The wp-config.php file is located in the root directory of your WordPress installation.

1. Connect to your server using FTP or navigate to your site’s root folder in File Manager.
2. Locate the wp-config.php file. Before editing, it is always a good idea to download a backup copy to your computer.
3. Open the file to edit it.
4. Find the line that says /* That's all, stop editing! Happy publishing. */.
5. Just before this line, add the following code:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Let’s break down what each line does:

• define( 'WP_DEBUG', true );: This turns on the debug mode in WordPress.
• define( 'WP_DEBUG_LOG', true );: This tells WordPress to save all errors to a log file. This is the key command for our purpose.
• define( 'WP_DEBUG_DISPLAY', false );: This prevents errors from being displayed directly on your website’s pages. Displaying errors publicly can be a security risk, so it’s best to keep them in a private log file.

Step 2: Locate the Debug Log File

Once you have saved the wp-config.php file with the new code, WordPress will start logging errors.

To trigger an error, you can simply visit your website, especially any pages that were showing issues. WordPress will then generate a new file named debug.log.

You can find this debug.log file inside the /wp-content/ folder of your WordPress installation.

Simply download this file and open it with a plain text editor to view the logged errors.

Alternative Method: Checking Server Error Logs

Sometimes, you may need to look for logs at the server level. This is especially true if WordPress fails to load completely, preventing the wp-config.php file from even being processed. The location of server-side logs varies depending on your hosting provider.

Here are some common places to look:

• cPanel: Most hosts using cPanel have an “Errors” or “Error Log” icon on the main dashboard. This will show you the latest server errors, which often include PHP errors.
• Hosting Provider Dashboard: Many managed WordPress hosts (like Kinsta, WP Engine, or SiteGround) provide their own custom tools for error logging. Look for a section named “Site Tools,” “Logs,” or “Error Logs” in your hosting account panel.
• Direct Server Access: If you have SSH access to your server, PHP error logs are often found in specific directories. Common locations include /var/log/, /var/log/httpd/, or within your user’s logs directory. You may need to consult your hosting provider’s documentation to find the exact path.

How to Read and Use Your Error Log

Opening the debug.log file might look intimidating at first. It will be a wall of text, but the structure is consistent. Each error is typically on a new line and contains the key pieces of information we discussed earlier.

Here is an example of what a typical PHP error might look like:

[20-Nov-2025 10:30:15 UTC] PHP Fatal error: Cannot redeclare my_custom_function() (previously declared in /home/user/public_html/wp-content/themes/my-theme/functions.php:25) in /home/user/public_html/wp-content/plugins/my-plugin/my-plugin.php on line 50

Let’s dissect this:

• Timestamp: [20-Nov-2025 10:30:15 UTC] tells you when it happened.
• Error Type: PHP Fatal error indicates a serious issue that likely stopped the page from loading.
• Error Description: Cannot redeclare my_custom_function() tells you the problem. In this case, a function with the same name was defined twice.
• File Path and Line Number: The message points to /plugins/my-plugin/my-plugin.php on line 50 as the source of the conflict. It also helpfully notes where the function was first declared.

With this information, you know the problem is a conflict between your theme and “my-plugin.” You can then either contact the plugin developer or attempt to rename the function in your theme’s code to resolve the conflict.

Final Tips for Effective Debugging

• Start with a Clean Slate: Before debugging, it’s sometimes helpful to clear the existing debug.log file. This ensures you are only looking at the most recent errors generated after you start testing.
• Focus on Fatal Errors First: Fatal errors are what break your site. Warnings and notices are important to fix, but they are a lower priority. Filter through the log to find fatal errors and address them first.
• Use the Timestamps: If an issue started happening at a specific time, use the timestamps to narrow down which errors are relevant.
• Remember to Turn Debugging Off: Once you have resolved the issues, it’s crucial to go back into your wp-config.php file and set WP_DEBUG to false. Leaving debug mode on in a live environment can expose sensitive information and fill up your server storage with unnecessary logs.

Knowing where the PHP error log in WordPress is and how to use it transforms you from a panicked site owner to an empowered troubleshooter. It takes the mystery out of website errors and gives you a clear path toward a solution.