Blank Screen on Your WordPress Site? Here’s How to Fix It (Updated for WordPress 7.0)

If you've opened your WordPress site only to find a completely blank white page with no content, no error message, and no way into your dashboard, you're dealing with what's commonly known as the White Screen of Death. This guide has been updated for WordPress 7.0 (released May 20, 2026) and covers both modern and traditional methods to get your site back online fast.

The blank screen almost always comes down to one of three things: a plugin conflict, a broken or incompatible theme, or PHP running out of memory. Here's how to systematically work through each one. If you find the technical steps overwhelming, you can always check out our WordPress maintenance plans to have a expert handle it safely.

Before You Start: Check Your Admin Email

Since WordPress 5.2, the platform automatically detects fatal errors and sends a notification email — including an error description and a direct recovery mode link — to your site's admin email address. This feature is still active in WordPress 7.0, so before you open an FTP client, check your inbox first. The fix might already be one click away.

If there's no email or the recovery link didn't resolve it, continue with the steps below.

Step 1: Turn Off All Plugins Through FTP

Plugins are the most frequent trigger for a blank screen, so rule them out first.

1. Open your FTP client (such as FileZilla or Cyberduck) and connect to your server.
2. Browse to your WordPress root directory and open the wp-content folder.
3. Find the folder named plugins.
4. Right-click it and rename it to anything else — plugins_off works fine.
5. Reload your website in the browser.

If the site comes back up, a plugin was the problem. To find the exact one, rename the folder back to plugins, then go inside it and rename each individual plugin folder one at a time (for example, append _off to the name). After each rename, reload the site — when the white screen returns, you've found the culprit.

Modern alternative (WordPress 5.1 and later, including 7.0): The free Health Check & Troubleshooting plugin includes a "Troubleshooting Mode" that deactivates all plugins only for your browser session. Your visitors continue seeing the live site while you diagnose the problem — no FTP or file renaming required.

Step 2: Switch to a Default Theme

If disabling plugins didn't fix it, your active theme may be the issue — especially if it hasn't been updated for compatibility with WordPress 7.0's block editor changes.

1. Through FTP, navigate to wp-content/themes.
2. Find the folder for your currently active theme.
3. Rename it to something temporary like mytheme_backup.
4. Reload your site — WordPress will automatically fall back to one of its built-in default themes.

If the site loads normally after this, your theme was the cause. Check with the theme developer for a WordPress 7.0 compatible update.

Step 3: Give PHP More Memory

A script running out of server memory mid-execution often results in a blank page rather than a proper error. This is worth checking, especially if you've recently upgraded to WordPress 7.0, which recommends PHP 8.3 — switching PHP versions can sometimes expose memory issues that weren't visible before.

Easy method (no FTP needed):

In your WordPress dashboard (if accessible), go to Tools > Site Health > Info > Server to see your current PHP memory limit.

Manual method via FTP:

1. Locate wp-config.php in your root directory and open it in a text editor.
2. Just above the line that reads /* That's all, stop editing! Happy blogging. */, add:
   define('WP_MEMORY_LIMIT', '256M');
3. Save the file, re-upload it if needed, and reload your site.

Note on PHP versions: WordPress 7.0 supports PHP from version 7.4 onwards, but the recommended minimum is PHP 8.3. If your hosting environment is running an older version, that alone could be causing the white screen — and is worth updating regardless.

Step 4: Turn On Debug Mode to Expose the Actual Error

If none of the above has worked, you can force WordPress to display the underlying error message instead of a blank page — which makes pinpointing the fix much faster.

1. Open wp-config.php via FTP.
2. Find the line: define('WP_DEBUG', false);
3. Change false to true, then save and reload your page.

You should now see a specific error pointing to the exact file or line of code causing the problem. Once you've identified and fixed the issue, remember to set WP_DEBUG back to false.

Still stuck? It helps to know:

If you've run through these steps and your screen is still blank, don't worry. You can skip the stress entirely by booking a priority assistance slot via our Ducos Design Technical Support Options to get your system restored immediately.

• What changed on your site just before the blank screen appeared — a plugin update, a theme switch, a WordPress 7.0 upgrade, or custom code edits?
• What PHP version is your server running? (You can check this under Tools > Site Health if your dashboard is accessible.)
• Did the recovery email from WordPress arrive in your inbox, and if so, what error did it describe?
• After enabling debug mode, what error message appeared on the screen?