Black Friday: 30% OFF on all plans, applied automatically at checkout View plans
Log in Cart

Importing the theme demo: why it fails and how to fix it

The import stops halfway, comes back incomplete or throws a 500. It's almost always a server limit, and four numbers fix it.

Updated on Sep 2, 20262 min read
Demos and templates

Importing the demo is the heaviest operation a WordPress theme performs: it creates dozens of pages, downloads hundreds of images, writes menus, widgets and options, all in a single request. That’s why it’s the first thing to hit the server’s limits, and when it fails, the problem is almost never the theme.

The signal is characteristic: the bar stops at 30%, the screen goes blank, a 500 error appears, or the import “finishes” but the site ends up with no images and no menu.

Before touching anything: check the requirements

Every author publishes the theme’s minimum requirements, either in the documentation or in its options panel. Compare them against what your server delivers today under Tools > Site Health > Info > Server.

Many themes come with their own check screen before importing, with items shown in red when something is below the recommended value. If it exists, it’s the fastest way to read the situation.

The four numbers that solve most cases

You don’t need to understand each one; you need them not to be too small:

  • max_execution_time: how long PHP is allowed to run before giving up. This is what causes the mid-import stop. Raise it to 300 or more.
  • memory_limit: available memory. This is what causes the blank screen. Raise it to 300M.
  • max_input_vars: how many fields PHP accepts at once. This is what makes the import finish incomplete, with no error at all. Raise it to 5000.
  • upload_max_filesize and post_max_size: 100M for both.

Where to set this depends on your hosting, and the path is the same as in the upload limit article: .user.ini in the WordPress root, .htaccess if the server is Apache, php.ini where you have access, or the PHP configuration screen in the hosting panel, which is the quickest route when it’s available.

Watch out for a silent trap: if the server runs nginx, .htaccess is ignored entirely. No error shows up: the lines simply have no effect.

Import on a clean site

Demos are built to go into a fresh install. Importing on top of a site that already has content mixes the two together, and undoing that usually takes more work than redoing it. If the site already has content that matters, test first in a staging environment.

Install the plugins the demo requires

Most demos depend on plugins from the theme author or third parties: slider, page builder, form. The theme usually lists these on a “recommended plugins” screen right after activation. Without them, the import runs but the result comes out broken, with empty blocks where the elements should be.

If it failed midway

Don’t run the import again on top of it. It has already created part of the content, and a second pass duplicates everything. Adjust the limits first, delete whatever came in half-finished, or roll the install back to the previous point, then import just once.