ThisCalculator

Everyday

Fix Blank Screen on Duplicator Installer in WordPress

Updated · Standard formula, shown below

Fix Blank Screen on Duplicator Installer in WordPress

If you see a blank white screen while running the Duplicator installer in WordPress, it usually means the installer script hit a PHP error that is hidden from display. The fix is to enable PHP error reporting, increase memory limits, and check the installer log file. This article walks you through the exact steps to identify and resolve the blank screen, whether it happens during package creation or installation.

What Causes the Blank Screen in Duplicator

Duplicator is a popular WordPress plugin for migrating or cloning a site. Its installer (installer.php) runs outside WordPress, so it has its own error handling. A blank screen—sometimes called the “white screen of death�—occurs when PHP encounters a fatal error but is set to suppress error messages. Common triggers include:

  • PHP memory limit too low for the installer’s operations
  • A missing PHP extension (e.g., mysqli, zip, cURL) required by the installer
  • Incorrect file permissions on the installer files or the target directory
  • A corrupted or incomplete package download
  • Server timeouts during the extraction or database import phase
  • Conflicts with security plugins or server-level firewalls blocking the installer

Because the installer is a standalone PHP script, it does not load WordPress’s debugging settings. That’s why you often see nothing at all instead of an error message.

Step-by-Step Fixes to Try

Work through these in order. Most blank screens are resolved by the first two steps.

  1. Enable PHP error reporting. Create a file named php.ini in the same folder as installer.php and add: display_errors = On, error_reporting = E_ALL. If you can’t create a new php.ini, edit the existing one if you have access. On some hosts, you can add these lines to a .user.ini file instead.
  2. Increase the PHP memory limit. Add memory_limit = 256M to the php.ini or .user.ini file. If that doesn’t work, try 512M. Some shared hosts restrict this; then use a local test environment.
  3. Check the installer log. Duplicator writes a log file named installer-log.txt (or similar) in the same directory. Open it to see the exact error. Look for lines containing “PHP Fatal error� or “WARNING�.
  4. Re-upload the installer files. Re-download the package from your WordPress admin (Duplicator → Packages → Download) and upload both installer.php and the archive.zip or archive.daf file again using FTP or your host’s file manager. Ensure the upload completed fully—check the file sizes match.
  5. Set file permissions. The installer.php and archive files should be readable by the web server. Usually 644 for files and 755 for directories is safe. If you changed them to 600 or 700, the script may fail silently.
  6. Disable security plugins temporarily. If you have a security plugin that blocks PHP execution in certain directories, it can cause a blank screen. Deactivate it from your WordPress admin, or if you can’t access admin, rename the plugin folder via FTP.
  7. Try a different PHP version. If your host allows it, switch to PHP 7.4 or 8.0. Duplicator generally supports PHP 5.6+, but older versions may have compatibility issues with newer PHP.

If the screen is still blank after these, check your server’s PHP error log (often in error_log file in the root or in cPanel’s “Errors� section).

How to Prevent the Blank Screen on Future Migrations

Prevention is easier than debugging. Before starting a migration, take these steps:

  • Set a PHP memory limit of at least 256M in your wp-config.php with define('WP_MEMORY_LIMIT', '256M');
  • Ensure the target server meets Duplicator’s requirements: PHP 5.6+, MySQL 5.0+, and the mysqli extension enabled.
  • Create the package with the “Archiveâ€� format set to “Zipâ€� if you have issues with the default “DAFâ€� format.
  • Test the installer on a local server (like XAMPP or Local by Flywheel) before moving to production.
  • Keep a backup of the original site so you can revert if something goes wrong.

Common Mistakes and Misconceptions

Many users think the blank screen means the installer is broken. In most cases, it’s a server configuration issue. Another misconception is that you must have shell access to fix it—you don’t; FTP and file manager are enough.

A frequent mistake is editing the wrong php.ini file. There can be multiple php.ini files on a server. Use the “PHP Info� tool in your hosting control panel to find the loaded configuration file path. Also, don’t confuse the Duplicator installer with the WordPress admin—if you see a blank screen in wp-admin after installing, that’s a different issue (usually a plugin conflict or theme error).

Also note that Duplicator’s installer is not a WordPress plugin; it’s a standalone script. So WordPress debugging settings (WP_DEBUG) won’t affect it.

Comparing Duplicator to Other Migration Plugins

Duplicator is one of several migration plugins. Others include UpdraftPlus, All-in-One WP Migration, and BackupBuddy. Each has its own installer approach. Duplicator uses a two-file system (installer.php + archive) that is very portable. All-in-One WP Migration uses a single file that you import through its own interface. UpdraftPlus requires you to install the plugin on the new site first. Duplicator’s advantage is that it works even if the new site has no WordPress installed—you just upload the files and run the installer. Its disadvantage is that the installer is more sensitive to PHP settings, which is why the blank screen issue is more common with Duplicator.

When to Use a Local Testing Environment

If you’re moving a live site to a new host, it’s wise to test the installer locally first. Download the package, set up a local server (e.g., XAMPP), and run the installer there. This isolates server-specific issues. If it works locally but not on your host, the problem is likely a host restriction—contact your host’s support with the error log.

Frequently Asked Questions

Why is the Duplicator installer showing a blank screen but no error?

PHP error display is off by default on many servers. The installer hits a fatal error but doesn’t show it. Enable display_errors in a php.ini file in the installer directory to see the actual error message.

How do I increase the PHP memory limit for the Duplicator installer?

Create a php.ini file in the same folder as installer.php and add memory_limit = 256M. If that doesn’t work, try 512M. On some hosts, you may need to use a .user.ini file or contact support.

Can I fix the blank screen without FTP access?

If you have cPanel or a file manager in your hosting control panel, you can edit files there. If you only have WordPress admin access, you’re stuck because the installer runs outside WordPress—you’ll need to contact your host or use whatever file access they provide.

What does the installer log tell me?

The installer log (installer-log.txt) records every step of the installation and any PHP errors. Look for lines starting with “PHP Fatal error� or “WARNING�. The log is created in the same directory as installer.php.

Is it safe to run the Duplicator installer on a live site?

It’s safe if you run it in a subdirectory or on a temporary domain. Running it on a live site could overwrite your existing database if you enter the wrong details. Always back up your site before running the installer.

Why does the blank screen happen after I click “Next� on the first step?

That’s usually when the installer tries to extract the archive or connect to the database. A memory limit or a missing PHP extension (like zip) is the common cause. Check the log for the exact error at that step.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.