New 24/7 monitoring and daily cloud backups now included in every Shield Pro plan.

Themes

Learn how to fix the WordPress theme customizer not loading.

The Customizer loads your site in a preview iframe and talks to wp-admin over AJAX. When it hangs on “Loading…” the cause is usually JavaScript, a plugin conflict, or HTTPS issues.

Time: 20-40 minutes Level: Intermediate
Neil McNaught, founder of BugShield and WordPress author
Written by
Written by
Updated
Updated

What this problem looks like

A stuck Customizer spinner means the preview frame or customize.php AJAX never finished. Classic themes and older commercial themes still rely on it even as Site Editor grows.

Because the Customizer runs admin and front end together, security plugins, ad blockers, and CDN caches often break it before the theme itself is at fault.

Quick checks in the browser

  1. Try a private window with extensions disabled.
  2. Open DevTools → Console and reload Appearance → Customize.
  3. Look for blocked scripts, CORS errors, or net::ERR_SSL messages.
  4. Switch to another browser to rule out a local extension.

Disable plugins that hook into admin

Caching plugins, firewall plugins, and admin optimizers commonly break customize_controls_print_scripts.

Disable them one at a time or use Health Check troubleshooting mode, then reload the Customizer.

Fix HTTPS and URL mismatches

If siteurl is https but assets load over http, the preview iframe may stay blank.

Open wp-config.php in your site root, next to wp-admin and wp-content. Search for WP_HOME and WP_SITEURL first. If those lines already exist, update them instead of adding duplicates. If neither exists, paste the constants above the line that says stop editing:

php
define( 'WP_HOME', 'https://example.com' );
define( 'WP_SITEURL', 'https://example.com' );

Raise PHP limits for heavy themes

Large theme option panels can exceed default limits on budget hosting. Open wp-config.php in your site root, next to wp-admin and wp-content, or raise limits in hosting PHP settings. Check wp-content/debug.log if PHP fatals when Customizer loads.

php
define( 'WP_MEMORY_LIMIT', '256M' );
@ini_set( 'max_execution_time', '120' );

When the theme itself is the problem

Switch temporarily to a default theme. If Customizer works, update the commercial theme or ask the author about Customizer compatibility with your PHP version.

Block-based themes may steer you to Appearance → Editor instead. That is expected for full site editing themes.

When to stop DIY and hire help

Customizer failures that survive plugin isolation often need theme-level debugging. BugShield developers fix theme errors and AJAX failures at a confirmed fixed price without hourly surprises.

Questions answered

WordPress theme customizer not loading FAQs

Answers about blank previews, JavaScript errors, plugin conflicts, HTTPS settings, PHP failures, and block-theme differences.

Why does Customizer show a 404 in the preview?

Permalink or HTTPS mismatch is common. Resave Settings → Permalinks and confirm the preview URL matches the live domain.

Does Cloudflare break the Customizer?

Rocket Loader and aggressive minify can break admin JavaScript. Create a page rule to bypass cache for wp-admin and customize.php.

Can I edit the theme without Customizer?

Many themes offer standalone option panels. Block themes use the Site Editor under Appearance → Editor.

Will disabling plugins affect live visitors?

Health Check troubleshooting disables plugins only for your session. Renaming wp-content/plugins to plugins.disabled via File Manager, SFTP, or FTP affects everyone until you restore it.

What causes the WordPress theme customizer not to load?

Plugin or theme JavaScript errors, PHP fatals, blocked REST or AJAX requests, mixed HTTP and HTTPS URLs, caching, low memory, or an unsupported theme can stop the preview.

How do I inspect a blank WordPress Customizer preview?

Open browser Console and Network tools before loading the Customizer, then record failed scripts, REST or AJAX requests, redirects, and the first meaningful error.

Does a block theme use the WordPress Customizer?

Many block themes use Appearance > Editor instead. A missing Customizer menu may be expected when the theme relies on full-site editing.

Can a plugin stop the WordPress Customizer loading?

Yes. Test on staging by disabling likely optimisation, security, page-builder, and custom-field plugins, then reactivate them one at a time.

Can low PHP memory break the WordPress Customizer?

Yes. The preview can load the theme and many plugins in one request. Confirm an exhausted-memory message in the PHP log before raising limits.

When should a developer fix the WordPress Customizer?

Get help when custom theme code fails, the preview request returns a server error, or live changes could be lost while you isolate the problem.

Would you rather a developer fixed it?

Request a fix at a confirmed price and speak directly with the BugShield developer working on your site.

Request a Fix