How to Fix a WordPress 500 Error After Installing a Plugin

Most WordPress troubleshooting guides will tell you to check your .htaccess file first. That is usually a waste of time. When a plugin you just activated throws a white screen or a 500 Internal Server Error, the culprit is almost always a fatal PHP error, a memory limit hit, or a conflict with an existing theme or plugin. The quickest fix takes about 30 seconds: rename the offending plugin folder via FTP or your hosting file manager. No code editing required.

In this guide, you will learn the exact steps to recover your site, starting with the fastest fix and working through eight distinct causes. Each solution includes the exact menu path, FTP step, or code snippet you need. Follow them in order; the first fix works for more than half of all cases.

Before you start: back up your site and database

Every fix on this list modifies live files or database records. If you make a mistake, a current backup saves you hours of recovery time. Use a plugin like UpdraftPlus or your hosting panel's backup tool to export both files and database.

If you cannot access the admin dashboard, many hosts provide a one-click backup through cPanel or a custom control panel. Do not skip this step — 15 minutes of caution prevents days of regret.

Common causes of a WordPress 500 error after installing a plugin

• Fatal PHP error — the plugin's code conflicts with your PHP version or another plugin.
• PHP memory limit exhausted — the plugin demands more memory than your site allows.
• .htaccess corruption — the plugin modified rewrite rules incorrectly.
• Plugin conflict — two plugins try to use the same function or hook.
• Theme conflict — the plugin is incompatible with your active theme.
• File permission errors — the plugin cannot read or write necessary files.
• Server configuration — modsecurity or a server-level rule blocks the plugin.
• Corrupted plugin files — the download or installation did not complete cleanly.

How to fix a WordPress 500 error after installing a plugin (step by step)

1. Rename the offending plugin folder via FTP

This is the fastest fix and works in roughly 60% of cases. The 500 error disappears the moment you rename the folder because WordPress can no longer load the broken plugin.

Steps:

1. Connect to your server using an FTP client (FileZilla) or your hosting file manager.
2. Navigate to wp-content/plugins/.
3. Find the folder of the plugin you just installed — for example, bad-plugin.
4. Right-click and rename it to something like bad-plugin-disabled.
5. Refresh your site. The 500 error should be gone.

Once the site is back, you can investigate the error log (see step 4) or contact the plugin developer. To permanently remove the plugin, delete the folder from the same location.

2. Increase PHP memory limit

A plugin that processes large datasets or images can exceed your PHP memory limit. The default is often 64 MB or 128 MB. Raising it to 256 MB resolves many 500 errors immediately.

Edit wp-config.php:

define('WPMEMORYLIMIT', '256M');

Add this line just above the / That's all, stop editing! Happy publishing. / comment. If your host allows, you can also increase it via the .htaccess file:

phpvalue memorylimit 256M

Some hosting panels have a PHP settings editor under "Software" or "PHP Configuration." Set memorylimit to 256M or 512M. Test the site after saving.

3. Enable WPDEBUG to see the actual error

The white screen hides the real error message. Enable debugging in wp-config.php to reveal exactly which file and line number caused the failure.

Edit wp-config.php and add or update these lines:

define('WPDEBUG', true);
define('WPDEBUGLOG', true);
define('WPDEBUGDISPLAY', false);

Visit your site to trigger the error again. Then check the file wp-content/debug.log. The log will show the actual PHP error — for example, "Call to undefined function" or "Allowed memory size exhausted".

Once you have the error, you can search for a specific fix or share the log with the plugin author. After troubleshooting, set WPDEBUG back to false to avoid exposing sensitive data.

4. Deactivate all plugins via FTP

If renaming one folder did not work, deactivate every plugin at once. This rules out a conflict between the new plugin and an existing one.

Steps:

1. In FTP, go to wp-content/.
2. Rename the entire plugins folder to plugins-old.
3. WordPress will automatically deactivate all plugins because it cannot find the folder.
4. Refresh your site. If the 500 error disappears, a plugin conflict exists.

Now create a new empty folder called plugins and move your plugins back one by one. After moving each plugin back, check the site. When the error returns, you have found the conflicting plugin.

5. Switch to a default theme

Sometimes the new plugin is not the problem — your theme is. A theme with outdated code can trigger a 500 error when combined with a modern plugin.

Steps:

1. In FTP, go to wp-content/themes/.
2. Locate your active theme folder — for example, my-custom-theme.
3. Rename it to my-custom-theme-old.
4. WordPress falls back to a default theme (Twenty Twenty-Four or similar).
5. Refresh your site. If the error clears, the theme is the issue.

Update or replace the theme. You can also contact the theme developer with the error log from step 3.

6. Restore a default .htaccess file

Some plugins add rewrite rules to .htaccess that break your site. A corrupted .htaccess is less common than a PHP error, but it is easy to test.

Steps:

1. Connect via FTP and locate .htaccess in your WordPress root folder.
2. Rename it to .htaccess-old.
3. Refresh your site. If the error disappears, the file was the problem.
4. Go to Settings → Permalinks in your admin dashboard and click "Save Changes" to generate a fresh .htaccess.

If you cannot access the admin, create a new .htaccess with the default WordPress rules:

# BEGIN WordPress
<IfModule modrewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTPAUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUESTFILENAME} !-f
RewriteCond %{REQUESTFILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

7. Check file permissions

Incorrect file permissions can cause a 500 error when a plugin tries to read or write files. Directories should be 755, and files should be 644.

Steps:

1. In FTP, right-click the wp-content folder and select "File Permissions…"
2. Set directories to 755 and files to 644. Check "Recurse into subdirectories."
3. Apply the same permissions to the entire WordPress root if needed.

Most shared hosting environments default to these permissions, but a plugin installation can sometimes change them. Resetting them to the standard values eliminates this rare cause.

8. Disable modsecurity via .htaccess

Some server security modules like modsecurity block plugin requests, mistaking them for attacks. Disabling it for your site is safe and often resolves stubborn 500 errors.

Add these lines to .htaccess above # BEGIN WordPress:

<IfModule modsecurity.c>
SecFilterEngine Off
SecFilterScanPOST Off
</IfModule>

If the error disappears, contact your host about whitelisting the plugin or adjusting the rules. Re-enable modsecurity after troubleshooting if you prefer.

How to prevent a 500 error when installing future plugins

Prevention is faster than recovery. Before installing any plugin, check its last update date, WordPress compatibility, and user reviews. A plugin not updated in two years is a red flag.

Test new plugins on a staging site whenever possible. If your host does not offer staging, use a local environment like Local WP. Only install on production after confirming the plugin works with your theme and other active plugins.

Keep your PHP version up to date. Many 500 errors come from deprecated functions removed in newer PHP versions. Check your PHP version in Tools → Site Health → Info → Server, and upgrade to 8.1 or 8.2 through your hosting panel.

Once your site is stable and healthy again, nativeWP helps you publish SEO content on autopilot — bulk-generate articles with your own OpenRouter API key and auto-publish them to WordPress. No plugin conflicts, no errors, just clean content automation.

Frequently asked questions