Setup & site building · Guide
How to See Logs in WordPress (Step by Step)

Short answer
WordPress has no single log screen. Turn on the debug log in wp-config to record PHP errors in a debug file inside wp-content, open PHP and server logs from your hosting panel, and use plugins for activity, WooCommerce and email logs. Pick the log that matches your problem.
Key takeaways
- WordPress has no built-in log viewer screen.
- WP_DEBUG_LOG writes PHP errors to a debug file.
- Hosts keep PHP and server logs in their panel.
- Activity logs need a plugin and only start on install.
- WooCommerce logs are under Status, then Logs.
- Turn off debug logging and remove old log files.
How do you see logs in WordPress?
WordPress has no single log screen, so you see logs by turning on the debug log, opening your host's PHP and server logs, and using plugins for activity, WooCommerce or email logs.
Which log you need depends on the question. A white screen calls for the PHP error log, a mystery settings change calls for an activity log, and a failed order calls for WooCommerce logs.
This guide shows where each log lives, how to switch it on, and how to read it without exposing private data to visitors.
Before you start, take a backup and, if possible, work on a staging copy. Turning on logging is safe, but editing wp-config.php always carries a small risk of typos.
Which logs can a WordPress site have?
A typical WordPress site can produce six kinds of logs: the WordPress debug log, PHP error logs, web server access and error logs, user activity logs, plugin logs such as WooCommerce, and email logs.
| Log type | What it records | How to see it |
|---|---|---|
| WordPress debug log | PHP errors, warnings and notices from WordPress code | Enable WP_DEBUG_LOG, open wp-content/debug.log |
| PHP error log | PHP errors from the server | Hosting panel or file in your account |
| Server error log | Web server problems such as 500 errors | Hosting panel, often named Errors |
| Server access log | Every request, IP and status code | Hosting panel, often named Raw Access |
| Activity log | Logins, edits, plugin changes by users | Activity log plugin |
| WooCommerce logs | Payment, shipping and API events | WooCommerce > Status > Logs |
| Email log | Messages WordPress tried to send | SMTP or mail logging plugin |
Start with the log that matches your symptom. Reading every log at once wastes time and hides the useful lines in noise.
How do you turn on the WordPress debug log?
Edit wp-config.php and set WP_DEBUG and WP_DEBUG_LOG to true, with WP_DEBUG_DISPLAY set to false, so errors are written to a file instead of shown on screen.
Open wp-config.php in your host's file manager or over SFTP. Above the line that says to stop editing, add or update these lines:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
Save the file, then reproduce the problem by loading the page or repeating the action that fails.
The official debugging in WordPress page explains each constant. Our guide on how to enable debug mode in WordPress walks through the same steps with screenshots of where to find the file.
Where is the WordPress debug log file?
By default the debug log is saved as debug.log inside your wp-content folder, created the first time an error is written.
Open it with your file manager's view or edit option, or download it over SFTP. Newer entries are at the bottom, each with a date and time.
You can also set a custom path by giving WP_DEBUG_LOG a file path instead of true. A path outside the public web folder is safer, because visitors cannot download it.
If no file appears, either nothing has been logged yet or the folder is not writable. Trigger the problem again and check folder permissions.
For help understanding the entries, see our guide on how to read the WordPress debug log.
How do you find PHP error logs from your host?
Most hosts keep a PHP error log that records fatal errors even when WordPress debugging is off, and you reach it through your hosting control panel or file manager.
On cPanel hosting, look for a file named error_log in your site's folder, or open the Errors tool under Metrics. cPanel documents this in its Errors interface guide.
Managed WordPress hosts usually have a Logs section in their own dashboard. Look for labels such as PHP logs, error logs or site logs.
The location is controlled by the PHP error_log setting, described in the PHP manual's error configuration page. Our guide on how to check PHP error logs covers common host layouts.
How do you see server access and error logs?
Server access logs list every request with its IP address, URL and status code, and error logs list server-level failures; both are found in your hosting panel.
On cPanel, the Raw Access tool lets you download access logs. Other panels show logs under names such as Access logs or Web server logs.
Access logs help when you suspect bots, brute force login attempts, or a spike in 404 errors. Search for wp-login.php or xmlrpc.php to spot attacks.
Server error logs help with 500 errors and timeouts. If you see a 500 error with no WordPress entry, the server log often holds the reason. Our guide to fixing the 500 internal server error explains what to look for next.
How do you see user activity logs?
WordPress does not record who changed what, so you install an activity log plugin, which then shows logins, edits, plugin changes and settings updates in the dashboard.
Popular free options include Simple History and WP Activity Log. Both add a log screen in the admin area once activated.
Activity logs only record events from the moment you install the plugin. They cannot show what happened last week if nothing was recording then.
These logs matter on sites with several editors or clients. Our guide on how to audit user activity in WordPress covers what to track and how long to keep records.
How do you see WooCommerce logs?
Go to WooCommerce > Status and open the Logs tab, where WooCommerce and many payment and shipping extensions save their own log entries.
Use the source filter or dropdown to pick a log, such as a payment gateway or the fatal errors log. Each entry has a timestamp and a level.
Payment gateways often need debug logging switched on in their own settings first. Turn it on, reproduce the failed order, then read the log.
Remember to turn gateway debugging off after you finish, since detailed logs can include order data. Our guide to the WooCommerce status report explains the other tabs on that screen.
How do you see email logs in WordPress?
WordPress does not keep a record of sent email, so you need an SMTP plugin with an email log feature or a dedicated mail logging plugin.
An email log shows each message WordPress tried to send, the recipient, the subject and whether it succeeded. That quickly tells you if a problem is in WordPress or further down the line.
If the log shows messages as sent but nobody receives them, the issue is delivery, not WordPress. Check your domain's SPF, DKIM and DMARC records.
If messages never appear in the log at all, the plugin or form sending them is failing before mail is created. Check the debug log at the same time.
Can you see logs inside the dashboard without file access?
Yes, plugins such as Query Monitor and some log viewer plugins show PHP errors and debug information in the admin area, and Site Health shows key server details.
Query Monitor adds a toolbar menu showing PHP errors, slow database queries and hooks for the current page. It is aimed at developers but readable for site owners too.
Tools > Site Health has an Info tab with PHP version, memory limit and server settings. It is not a log, but it often explains why errors happen.
Our guide on how to use Query Monitor explains each panel.
For server details, see how to use Site Health and what each section of the Info tab means.
How do you keep logs safe and small?
Turn debug logging off when you are done, keep log files out of public reach, and delete or rotate old logs so they do not fill your disk.
A debug.log in wp-content can be downloaded by anyone who guesses the URL. It may include file paths and plugin names that help attackers, so do not leave it in place.
Large logs also slow down file managers and backups. Clear the file after you have copied any lines you need.
When you share a log with a developer or support team, remove email addresses, order details and anything personal first.
What should you do with what you find?
Use the log to find the plugin, theme or file named in the error, then update, replace or disable that component and test again.
Look for the first fatal error near the time of the problem. Later lines are often side effects of the first failure.
If a plugin path appears, such as wp-content/plugins/plugin-name, test with that plugin disabled. If a theme path appears, switch to a default theme to confirm.
When you cannot fix it yourself, send the relevant lines to the plugin's support forum or your host. A clear log excerpt gets a faster, more accurate answer than a description of the symptom.
Frequently asked questions
Does WordPress keep logs by default?
Not in a way you can view from the dashboard. WordPress only writes a debug log when you enable it in wp-config, and it does not record user activity or sent emails. Your host usually keeps PHP and server logs separately, which you reach through the hosting panel.
Is it safe to leave WP_DEBUG on?
It is not a good idea on a live site. Even with display turned off, the log file can grow large and may be downloadable from the web. Turn debugging on while you investigate, then switch it off and delete the log file once you have what you need.
Why is my debug log empty?
Either no errors have occurred since you enabled logging, or WordPress cannot write to the wp-content folder. Repeat the action that fails, check the folder permissions, and confirm your constants are placed above the line that says to stop editing in wp-config.
How do I see who logged in to my WordPress site?
Install an activity log plugin such as Simple History or WP Activity Log. They record logins, failed logins and other user actions from the moment they are activated. Server access logs can also show requests to the login page by IP address.
Where are WooCommerce payment logs?
Open WooCommerce, then Status, then the Logs tab, and pick the gateway from the list. Many gateways only log details when debug logging is enabled in their own settings, so turn it on, reproduce the problem, read the log and then turn it off again.
Sources
- Debugging in WordPress WordPress Developer Resources
- Runtime configuration for errors PHP Manual
- Errors cPanel Docs
- Simple History WordPress.org Plugins
- WP Activity Log WordPress.org Plugins
- Query Monitor WordPress.org Plugins
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


