{"id":634,"date":"2026-07-01T03:48:46","date_gmt":"2026-07-01T03:48:46","guid":{"rendered":"https:\/\/brutefort.com\/blog\/wordpress-error-log-location\/"},"modified":"2026-07-15T13:43:23","modified_gmt":"2026-07-15T13:43:23","slug":"wordpress-error-log-location","status":"publish","type":"post","link":"https:\/\/brutefort.com\/blog\/wordpress-error-log-location\/","title":{"rendered":"WordPress Error Log Location: Where to Find It on Any Host"},"content":{"rendered":"\n
\"File
Photo by Pixabay from Pexels<\/figcaption><\/figure>\n\n\n\n

Something on your WordPress site just broke, and you need to check the error log \u2014 but you don’t actually know where it lives. That’s a common problem. The default location is simple, but hosting setups, custom configs, and security plugins can move it without any obvious sign of where it ended up.<\/p>\n\n\n\n

It happens on nearly every host, from cheap shared plans to managed WordPress platforms, each with its own quirks. This guide covers every place the WordPress error log can live, how to find it on any hosting environment, and how to stop hunting for it altogether.<\/p>\n\n\n\n

Quick Answer:<\/strong> By default, WordPress writes errors to \/wp-content\/debug.log<\/code> once WP_DEBUG<\/code> and WP_DEBUG_LOG<\/code> are both enabled. Hosts and plugins can move this to a custom path, so if the file isn’t there, check your wp-config.php<\/code> for a custom WP_DEBUG_LOG<\/code> path or use LogMate’s System Info screen, which shows the exact file path in use on your specific site.<\/p>\n\n\n\n

The Default WordPress Error Log Location<\/h2>\n\n\n\n

When WP_DEBUG<\/code> and WP_DEBUG_LOG<\/code> are both set to true in wp-config.php<\/code>, WordPress writes errors to:<\/p>\n\n\n\n

\/wp-content\/debug.log<\/code><\/pre>\n\n\n\n
This path is relative to your WordPress installation root. On most shared hosting setups, the full server path looks something like \/home\/username\/public_html\/wp-content\/debug.log<\/code>. The exact structure depends on your host’s directory layout.<\/p>\n\n\n\n
The file is plain text and opens in any text editor. Note:<\/strong> it doesn’t exist until the first error is logged after enabling WP_DEBUG \u2014 WordPress creates it on demand, not in advance.<\/p>\n\n\n\n
Custom WordPress Error Log Locations<\/h2>\n\n\n\n
The default path can be changed. When WP_DEBUG_LOG<\/code> is set to a file path string instead of true<\/code>, WordPress writes the log to that custom location:<\/p>\n\n\n\n
define( 'WP_DEBUG_LOG', '\/custom\/path\/to\/my-debug.log' );<\/code><\/pre>\n\n\n\n
Some plugins and hosting environments do this automatically. It keeps the log outside the web root, making it inaccessible via a public URL, or stores it alongside other server logs in a standardized location. So if you’ve enabled WP_DEBUG but can’t find the log at \/wp-content\/debug.log<\/code>, a custom path is likely the reason.<\/p>\n\n\n\n
\"Server
Photo by Christina Morillo from Pexels<\/figcaption><\/figure>\n\n\n\n
WordPress Error Log Locations by Hosting Environment<\/h2>\n\n\n\n
Different hosting types handle WordPress debug logging differently:<\/p>\n\n\n\n
  • Shared hosting (cPanel)<\/strong> \u2014 Default path applies unless you’ve configured a custom one. cPanel’s file manager lets you navigate to \/public_html\/wp-content\/<\/code> and open the file directly. Some cPanel setups also have a separate server-level error log under Metrics \u2192 Error Log, which is separate from the WordPress debug log.<\/li>
  • Managed WordPress hosting (Kinsta, WP Engine, Flywheel)<\/strong> \u2014 These platforms often manage debugging through their own dashboards rather than wp-config.php<\/code>. Kinsta, for example, provides a WordPress error log viewer in MyKinsta. Check your host’s documentation rather than assuming the default path.<\/li>
  • VPS or dedicated server<\/strong> \u2014 Default path applies. You can also configure PHP’s own error_log directive in php.ini<\/code> to write server-level PHP errors to a separate file, distinct from the WordPress debug log.<\/li>
  • Local development (Local by Flywheel, MAMP, Laragon)<\/strong> \u2014 These environments typically configure their own log paths. Local by Flywheel, for instance, stores logs in the site’s logs\/<\/code> directory rather than inside WordPress itself.<\/li><\/ul>\n\n\n\n
    Finding Your Exact Log Path Without Guessing<\/h2>\n\n\n\n
    Rather than navigating every possible location, LogMate’s System Info screen shows the exact file paths for both your PHP debug log and JavaScript log on your specific installation. Go to LogMate \u2192 System Info<\/strong>. The Debug Logs section lists the PHP log path and JS log path your site actually uses, plus the current file size of each. That eliminates the guesswork regardless of your hosting environment or configuration.<\/p>\n\n\n\n
    \"LogMate<\/figure>\n\n\n\n
    LogMate also makes reading the log unnecessary from the server \u2014 once it knows the log path, it reads and displays the contents inside the WordPress admin. Errors are organized in a searchable table, with PHP and JavaScript errors separated, sortable by occurrence count, and exportable when you need to share with a developer.<\/p>\n\n\n\n
    \"LogMate<\/figure>\n\n\n\n
    \n