Black FridayCyber Monday 2026
14Days
15Hrs
03Mins
10Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
Elementor

How to Fix “Preview Could Not Be Loaded” in Elementor

The Elementor preview could not be loaded error has several causes. Read the status codes, test one layer at a time and fix permalinks, firewall, plugin or memory problems safely.

wpallsolution 10 min read

When the Elementor preview could not be loaded, the editor panel opens but the page canvas will not render. Elementor’s help centre says the error appears when the editor is blocked from rendering its live preview. Its causes include a low PHP memory limit, plugin or theme conflicts, broken permalinks or a damaged .htaccess file, server firewalls, Cloudflare Rocket Loader and even a leftover index.html file. Because the causes are so different, the quickest route is to read what the server is saying and then test one layer at a time.

Quick answer

Check whether you are trying to edit an archive page (such as the blog index or shop page), because those cannot be opened directly. Next, test in a private window, then read the HTTP status in the browser console: 401, 403 and 500 each point somewhere different. After that, use Safe Mode to separate plugin and theme conflicts from server problems, and only then look at permalinks, .htaccess, root files, Rocket Loader and the memory limit.

How this guide was prepared: the steps follow Elementor’s help articles and the WordPress documentation listed under Sources, read on October 19, 2026. We did not reproduce the error on a live Elementor site for this guide, so the steps are research-based. Menu names change between versions, and hosting setups differ, so no single fix works everywhere.

Before you change anything

  • Take a full backup of files and database. Elementor’s article says so before you deactivate plugins or switch themes. See Is your WordPress backup really safe? if you are unsure yours restores.
  • Prefer a staging copy for anything that changes how the site behaves.
  • Change one thing at a time and note the result.
  • Do not share passwords, private logs or customer data when you ask for help. Redact them first.

Elementor preview could not be loaded: the decision tree

Flowchart of five questions to find why the Elementor preview could not be loaded: page type, browser, HTTP status code, plugin or theme conflict, and permalinks or server files
Five questions, asked in order, point to the right step.
  1. Are you editing a dynamic archive, such as the blog index or shop page? If yes, use Theme Builder (Step 1).
  2. Does it load in a private window with extensions off? If yes, the cause is your browser (Step 2).
  3. Which HTTP status does the console or network tab show for the failing request? Each code points somewhere different (Step 3).
  4. Does Safe Mode, or a default theme, fix it? If yes, a plugin or theme is involved (Step 4).
  5. If not, check addresses, permalinks, .htaccess, root files and Rocket Loader (Steps 5 to 7), then the memory limit (Step 8).

Likely causes at a glance

What you seeLikely causeStart with
Error only on the blog index or the shop pageArchive pages cannot be edited directlyStep 1
Works in a private windowBrowser extension or cacheStep 2
Status 401Password protection on an admin folderStep 3
Status 403Firewall rule or file permissionsStep 3
Status 500PHP error or memorySteps 3 and 8
Works in Safe ModePlugin or theme conflictStep 4
Started after switching to https or changing the URLAddress mismatchStep 5
Admin pages work but the preview URL failsRewrite rules, .htaccess or a root index.htmlSteps 6 and 7

8 steps to fix the Elementor preview could not be loaded error

Step 1: Edit archive pages through Theme Builder

Elementor’s article says that clicking Edit with Elementor directly on a dynamic archive, such as your main blog index or a WooCommerce shop page, triggers a preview loading error. Instead, go to Elementor → Theme Builder, choose the template type (for example Single Post, Products Archive or Single Product) and edit the assigned template there. Theme Builder is part of Elementor Pro, so on the free plugin you cannot design those templates with Elementor.

Step 2: Rule out browser extensions and cache

Ad blockers and privacy tools can block the scripts Elementor needs. Open a private window (Ctrl+Shift+N in Chrome), log in, and open the page in the editor. If it loads, disable extensions one by one in your normal browser, starting with ad blockers and privacy shields. If it does not load, continue.

Step 3: Read the HTTP status code

Press F12 to open developer tools, choose the Console tab and look for red status codes. Elementor’s article gives this lookup, which we have summarised:

  • 401 Unauthorized. Password protection (for example directory authentication) is blocking an admin folder. Disable it in your hosting control panel or security plugin.
  • 403 Forbidden. A server firewall such as mod_security or incorrect file permissions can block the request. Elementor suggests asking your host to review the rule for Elementor requests, and setting directories to 755 and files to 644. Ask your host to look at the blocked request in their logs. Do not ask them to switch security off for the whole site.
  • 500 Internal Server Error. The server ran out of PHP memory or hit a critical script error. Check the PHP error log, or turn on debug logging (below). If you see this on the editor, Elementor also has a dedicated 500 error guide.

The WordPress debugging documentation shows how to log errors without displaying them to visitors, by adding these lines to wp-config.php (back the file up first):

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Reload the editor once, then read wp-content/debug.log. Redact private details before sharing it, and set debugging back to false when you finish.

Step 4: Use Safe Mode, then isolate the plugin or theme

  1. In WP Admin, go to Elementor → Tools → General (Elementor’s current article names this path), set Safe Mode to Enable and save.
  2. Reopen the page. Elementor says that if the editor loads in Safe Mode, a plugin or theme is the cause. If it still fails, the cause is more likely server configuration, memory or permalinks.
  3. If Safe Mode helped, deactivate every plugin except Elementor and Elementor Pro, then reactivate them one by one. Elementor suggests starting with performance tools such as caching and optimisation plugins and reloading the editor after each.
  4. If plugins are not the cause, switch to a default theme such as Hello Elementor on staging.

Our guide How to find the plugin that broke your site explains the one-at-a-time method in more detail.

If you get locked out of WP Admin: Elementor’s article suggests connecting by FTP or your host’s File Manager and renaming the folder of the plugin you just deactivated under wp-content/plugins/. Rename only the suspect, and rename it back afterwards. Or restore the backup you took before you started.

Step 5: Check the WordPress and Site addresses

If you recently added an SSL certificate or changed the URL, Elementor’s help says to update the site address. Under Settings → General, the WordPress Address (URL) and the Site Address (URL) should be identical, both on https:// or both on http://. Take a backup before changing them.

Out-of-sync rewrite rules can stop the editor from reaching the page path.

  1. Go to Settings → Permalinks and click Save Changes without changing the setting. This regenerates the rewrite rules.
  2. If it still fails, Elementor’s article suggests choosing Plain and saving. On a live site that changes every URL, so do it only on a staging copy and restore your real structure afterwards.
  3. For a damaged .htaccess, Elementor suggests deleting it and saving permalinks again so WordPress writes a clean one. Safer: download a copy, or rename it to .htaccess-old, then save permalinks. Your host or security plugin may have added rules you need to keep.

Step 7: Look for a root index.html and Cloudflare Rocket Loader

  • Static file. A file named index.html in your site’s root folder can override WordPress’s index.php. If you find one that is not part of your site, move it somewhere safe rather than deleting it, so the server falls back to WordPress.
  • Rocket Loader. If you use Cloudflare, turn Rocket Loader off under Speed → Optimization, then purge the cache. Elementor’s separate guide explains how to bypass it with rules for Elementor URLs instead.

Step 8: Check the PHP memory limit

Elementor requires at least 256 MB of PHP memory and recommends 512 MB for complex sites. If your host allows it, back up wp-config.php and add this line directly above the comment that tells you to stop editing:

define( 'WP_MEMORY_LIMIT', '512M' );

To undo, remove the line. Many hosts cap memory on the server, so it may not change anything. Then ask them. Reopen the editor to test.

Version and hosting differences

  • Menu names change between Elementor versions. If you cannot find Safe Mode, look under Elementor → Tools or Elementor → Editor → Tools.
  • Hosts differ in firewall rules, caching and PHP limits. A 403 often needs a host to change something you cannot reach.
  • Elementor Hosting users have extra tools such as backups and file access in the My Elementor dashboard.

How to verify the fix

  • The preview canvas loads, you can select a widget and Update saves.
  • It works in your normal browser and in a private window.
  • Anything you turned off for testing is back on, one item at a time, with a test after each.
  • You noted the cause and what fixed it.

How to prevent it from happening again

Frequently asked questions

Is this the same as the editor being stuck on a grey screen?

Related, but different. Here the editor reports that the preview could not be loaded. A grey screen that never finishes loading has its own causes.

Why can I not edit my shop or blog page directly?

Those are dynamic archive pages. Elementor says to edit the assigned template in Theme Builder instead (Step 1).

It changes your page URLs, which can break links and hurt search visibility on a live site. Test it on staging and keep your normal structure.

Should I ask my host to turn off ModSecurity?

No. Ask them to check the logs for the blocked request and allow that one, once you have evidence of a 403.

What to do next

Work through the steps in order and stop at the first that works. If the Elementor preview could not be loaded after all eight, send your System Info (Elementor → Editor → System), the status code and the first console error to Elementor support or your host. If you would like a person to look, wpallsolution offers independent plugin support, and our Elementor development page explains how we build and tidy Elementor sites. We cannot promise a fix without seeing your site.

Sources and official documentation

Last reviewed: October 19, 2026. Elementor is a trademark of its owner. wpallsolution is not affiliated with or endorsed by Elementor.

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us