Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Explainer

What Causes the 500 Internal Server Error in WordPress?

Short answer

A 500 Internal Server Error means WordPress or the server hit an unexpected condition and could not finish the request. In WordPress the usual causes are a corrupt .htaccess file, a plugin or theme conflict, a PHP fatal error, a wrong file permission, or a PHP memory limit that is too low. The browser message never names the cause, so you have to read the error log or narrow it down by what changed last.

Key takeaways

  • A 500 error is a generic catch-all: it says the server failed, not why it failed.
  • A corrupt .htaccess file is the most common WordPress cause, per WordPress.org's own error guide.
  • If the error started right after a plugin, theme or core update, that change is the prime suspect.
  • The PHP error log or wp-content/debug.log usually names the exact file and line behind the error.
  • WordPress tries to give PHP 40MB on a single site and 64MB on multisite, which a heavy site can outgrow.

What does a 500 Internal Server Error mean in WordPress?

A 500 Internal Server Error means the server hit an unexpected condition and could not finish the request.

MDN defines the 500 status as a generic catch-all response the server sends when it cannot find a more fitting error code, and it lists improper server configuration, out-of-memory issues, unhandled exceptions and wrong file permissions among the causes (MDN 500 status).

That vagueness is the hard part. The same blank page can come from a one-line typo in a config file or from a server that ran out of memory. The message in the browser will not tell you which one it is.

WordPress adds its own twist. When a PHP fatal error stops WordPress, the server often returns a 500 instead of the error text.

Since WordPress 5.2, the fatal error handler may show “There has been a critical error on this website” instead, but a plain 500 is still common on many hosts, according to the WordPress common errors guide.

What are the most common causes of a 500 error in WordPress?

Five causes sit behind most WordPress 500 errors: a corrupt .htaccess file, a plugin conflict, a theme problem, a PHP fatal error, and a memory limit that is too low.

A corrupt .htaccess file is first on the list in the WordPress common errors guide, which names it as the most likely issue. The file holds rewrite rules for pretty permalinks, and one bad line can break every page on the site.

Plugin conflicts come next. A plugin can call a function that does not exist, clash with another plugin, or fail after an update. The same guide notes that deactivating all plugins and reactivating them one by one is the standard way to find the culprit.

Theme problems follow the same pattern. A theme that was just activated or updated can throw a fatal error on every page load. Switching to a default theme such as Twenty Twenty-Five rules this out fast.

PHP fatal errors are the fourth cause. These include parse errors from a typo in functions.php, calls to undefined functions, and code written for a newer PHP version than the server runs. WordPress.org recommends PHP 8.3 or greater as of November 2026, while WordPress still works with PHP 7.4 and up (WordPress requirements).

The fifth cause is memory. WordPress tries to raise the PHP memory available to it to 40MB for a single site and 64MB for multisite, per the wp-config handbook. A site with many plugins or a large import can pass that limit and die with a 500.

How can you tell which cause you have?

Start with timing: if the error began right after a change, that change is almost always the cause.

An error that appears on every page, including wp-admin, points at .htaccess, the server config, or a site-wide PHP error. An error on one page or one post points at the content or code behind that page. An error only in wp-admin points at a plugin or theme that loads in the admin area.

ClueLikely causeWhere to check
Started after editing .htaccess or permalinksCorrupt .htaccessSite root .htaccess file
Started after a plugin updatePlugin conflictError log, plugin folder
Started after a theme changeTheme errorError log, theme folder
Only wp-admin failsAdmin-only plugin or theme codewp-content/debug.log
Error names a memory limitPHP memory limitwp-config.php, php.ini
Whole server is downHost or server faultHost status page

The error log is the fastest way to move from guessing to knowing. Enable logging and read the last entries, as described in the next section.

If nothing changed and the whole site failed at once, suspect the host. Cloudflare's 5xx guide advises sharing the exact error code, the time and timezone, and the failing URL with the host, and checking the logs of any proxy or firewall between the visitor and the origin (Cloudflare 5xx errors).

What does the error log tell you about a 500 error?

The error log usually names the exact file, line and error type behind a 500.

WordPress writes PHP errors to wp-content/debug.log when you define WP_DEBUG and WP_DEBUG_LOG as true in wp-config.php, and you should set WP_DEBUG_DISPLAY to false so errors stay out of the page HTML (WordPress debugging handbook).

The handbook warns that these constants must go before the line that reads “That's all, stop editing! Happy blogging.” in wp-config.php. It also warns against leaving WP_DEBUG on a live site, since it is meant for local or staging use.

A typical log line names a fatal error, the file path, and the line number. A line that mentions a plugin folder points at that plugin.

A line that mentions a theme folder points at the theme. A line that says “Allowed memory size exhausted” points at the memory limit, not at a bug in a single plugin.

If your host keeps its own error log, check that too. Some hosts log PHP errors in the control panel, and the server error log can show .htaccess syntax errors that WordPress never sees.

Why does a corrupt .htaccess file cause a 500 error?

A corrupt .htaccess file causes a 500 because Apache reads it on every request and stops when it hits a bad directive.

The .htaccess file in the site root holds rewrite rules, redirects and access rules. WordPress rewrites it when you save Settings > Permalinks. A failed save, a plugin that adds its own rules, or a hand edit with a typo can leave a broken line behind.

The clue is scope: a bad .htaccess breaks the whole site at once, front end and admin alike. That matches what the WordPress common errors guide describes, and it is why the guide suggests renaming the file to .htaccess_old and reloading the site as the first check.

If the site loads after the rename, the file was the cause. Visit Settings > Permalinks and save again to let WordPress write a fresh .htaccess file. The full fix steps are in our guide on how to fix the 500 Internal Server Error.

How do plugin and theme conflicts cause a 500 error?

A plugin or theme causes a 500 when its code throws a PHP fatal error during the page load.

The error can be a parse error from a missing semicolon, a call to a function that does not exist, or code that needs a newer PHP version. Any of these stops PHP before the page is built, so the server answers with a 500.

The clue is timing. If the error started right after installing, updating or activating a plugin or theme, that item is the prime suspect. The WordPress common errors guide suggests deactivating all plugins by renaming the wp-content/plugins folder over FTP when wp-admin is unreachable.

If the site loads with plugins off, reactivate them one at a time until the error returns. The last one reactivated is the cause.

The same one-by-one method works for themes: switch to a default theme and see if the error clears. For the full process, see our guide on how to fix plugin conflicts.

When is a 500 error a memory or server problem?

A 500 is a memory problem when the error log says the allowed memory size was exhausted, and a server problem when nothing in WordPress changed.

PHP ships with a default memory_limit of 128M, according to the PHP manual. Hosts can set it lower, and the WordPress handbook notes that some hosts set the PHP limit as low as 8MB (wp-config handbook).

A memory error usually appears on heavy actions: importing content, saving a large page, running a backup, or loading a page with many plugins. If the same action fails every time while light pages load fine, memory is the likely cause.

The handbook also warns that raising the limit can hide the real problem. A plugin that leaks memory will hit the new limit later, so a raised limit is a short-term fix and the faulty code still needs attention.

A server problem looks different: the whole site and the host control panel fail together, or the host reports an outage. In that case no WordPress change will help, and the host has to fix it.

A 500 that follows a core update can also mean damaged core files, so re-uploading wp-admin and wp-includes from a fresh WordPress download is one of the steps in our guide on how to fix a site broken after a WordPress update.

What mistakes should you avoid?

Do not edit files on the live site without a backup, and do not leave debug mode on after you finish.

A backup matters because the most common fixes involve renaming .htaccess, deactivating plugins, or editing wp-config.php. Each of these can make things worse if done wrong, and a backup is the only quick way back.

Do not raise the memory limit again and again instead of finding the cause. The wp-config handbook warns that this hides the root issue, which returns as you add more plugins.

Do not ignore the error log. Guessing at fixes wastes time and can add new faults. One log entry often names the plugin, theme or file behind the error.

Finally, do not assume a 500 means your site was hacked. A hacked site is one possibility, but an update, a bad edit, or a low limit is far more common. Check the log first, then scan for malware if the log points that way.

A white screen with no message at all is a related but separate fault, covered in our guide on how to fix the WordPress white screen of death.

Frequently asked questions

Does a 500 error mean my WordPress site is hacked?

Not usually. A hack is one possible cause, but a corrupt .htaccess file, a plugin conflict, a theme error or a low memory limit is far more common. Read the PHP error log first. If the log names a plugin, theme or config file, that is your cause. Scan for malware only if the log gives no clear cause or shows files you did not add.

Why does a 500 error show a blank page with no details?

The server hides the details on purpose so visitors never see raw PHP errors. The 500 status is a generic catch-all, so the browser message cannot name the cause. The real detail sits in the PHP error log or in wp-content/debug.log once WP_DEBUG and WP_DEBUG_LOG are turned on in wp-config.php.

Can a 500 error fix itself?

Sometimes, if the cause was a brief server overload or a host restart. If the error stays for more than a few minutes, it will not clear on its own. A corrupt .htaccess file, a broken plugin and a low memory limit all need a real fix, so check the error log and work through the cause instead of waiting.

Is a 500 error the same as the white screen of death?

No, but they overlap. A white screen of death is a blank page with no error code, often from a PHP fatal error that WordPress cannot display. A 500 is an HTTP status the server returns when it cannot finish the request. Both can come from the same plugin or theme fault, and both are diagnosed from the error log.

Should I contact my host about a 500 error?

Yes, if the error log shows nothing in WordPress, if the whole server is down, or if you cannot raise the memory limit yourself. Give the host the exact error, the time it started, the failing URL and the last lines of your error log. That detail lets them check server logs you cannot see.

Sources

  1. 500 Internal Server Error MDN Web Docs
  2. Common WordPress Errors WordPress Developer Resources
  3. Debugging in WordPress WordPress Developer Resources
  4. Editing wp-config.php WordPress Developer Resources
  5. Description of core php.ini directives PHP Manual

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.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test