Elementor Widgets Not Showing or Not Updating: Causes and Fixes

This article is a localized edition of the Japanese original. Read the Japanese original

When Elementor widgets "don't show up", the cause usually falls into one of four groups: old CSS or caches are still being served, the widget is disabled or not registered, the editor itself fails to load, or an update introduced a bug. This article narrows down the cause from the symptom and fixes it step by step. Screen names and commands match Elementor 4.4 as of November 2026.

Back up your site before you start. Do the checks that involve deactivating plugins on a staging site if you can.

Narrow down the cause from the symptom

Step 1: Clear old CSS and caches

Elementor writes each page's design to a CSS file (wp-content/uploads/elementor/css/) and loads it on the live page. If that file is outdated, the page looks right in the editor but different on the live site.

1. Open Elementor's "Tools" in the admin screen, and under "Elementor Cache" on the "General" tab, click "Clear Files & Data". The CSS files and the generated data stored in the database are deleted and rebuilt the next time a page is viewed. Your post content is not deleted.
2. Clear the caches of your caching plugin, your server cache and any CDN such as Cloudflare, each from its own dashboard.
3. Do a hard reload in the browser (Ctrl+F5 on Windows, Command+Shift+R on a Mac) and check again.

In Elementor 4.x, "Settings", "Tools" and similar items are grouped under "Elementor" → "Editor" in the admin screen. In older versions they sit directly under the "Elementor" menu.

If you can use WP-CLI, the first item in Step 1 can also be done with this command. Adding --regenerate rebuilds the files right away instead of waiting for the next page view.

wp elementor flush-css --regenerate

# If you use a persistent object cache such as Redis, clear it too
wp cache flush

If that does not fix it, change "CSS Print Method" on Elementor's "Settings" → "Performance" tab to "Internal Embedding" and check again. This method writes the CSS directly into the page HTML, so if it fixes the problem, something is wrong with writing or loading the CSS files (check the permissions in Step 6 and your cache and CDN settings). Once you find the cause, switch back to the recommended "External File".

Step 2: Check whether the widget is disabled or unregistered

Element Manager

Elementor's "Element Manager" in the admin screen lets you enable or disable each widget. A widget disabled here is no longer registered, so it not only disappears from the editing panel but also stops showing on pages where it was already placed.

Check that the widget is not disabled in the list, and enable it again if needed. With WP-CLI, you can list the names of disabled widgets with this command:

wp option get elementor_disabled_elements --format=json

Unregistered in code

If your child theme's functions.php or a customization plugin calls unregister() on the elementor/widgets/register hook, that widget is not registered either. Search for the widget's name (such as counter or progress) to see whether such code exists.

Elementor Pro and add-ons

Pro widgets such as Form and Popup are registered by the Elementor Pro plugin. If Pro is deactivated, those widgets are not registered and do not show. The same goes for widgets added by add-on plugins. Check in the "Plugins" list that the relevant plugin is active.

If only one of Elementor and Elementor Pro is out of date, things may not work correctly. Update both to the latest version.

Step 3: Check how your custom widget is registered

If a custom widget does not appear in the panel, check the registration code. In the example in Elementor's developer documentation, you pass an instance of the widget to the register() method of the widgets manager received on the elementor/widgets/register hook.

<?php
// Example for your plugin's main file
add_action( 'elementor/widgets/register', function ( $widgets_manager ) {
	require_once __DIR__ . '/widgets/class-my-widget.php';
	$widgets_manager->register( new \My_Widget() );
} );

Things to check:

• Does the widget class extend \Elementor\Widget_Base?
• Is the name returned by get_name() unique among all widgets?
• Does get_categories() return registered categories (such as basic or general)? If you use your own category, register it first with the elementor/elements/categories_registered hook
• Is the file path in require_once correct (is a PHP error stopping execution)?

You can check PHP errors in the debug log. To set it up with WP-CLI, do the following. Errors are written to wp-content/debug.log instead of the screen.

wp config set WP_DEBUG true --raw --type=constant
wp config set WP_DEBUG_LOG true --raw --type=constant
wp config set WP_DEBUG_DISPLAY false --raw --type=constant
tail -n 50 wp-content/debug.log

When you are done, set the three constants back to false.

Step 4: If the editor will not open, check memory and conflicts

Memory limit

Elementor's official system requirements (updated October 16, 2026) call for a WordPress memory limit of at least 256MB, with 512MB recommended. Because the editor runs inside the admin screen, the admin-side limit WP_MAX_MEMORY_LIMIT also matters. Add the following to wp-config.php, before the comment that says to stop editing.

<?php
define( 'WP_MEMORY_LIMIT', '512M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

These constants only work if the server allows changing PHP's memory_limit. If the value does not change, raise it in the server settings (php.ini or your hosting control panel). For details, see how to fix the WordPress PHP memory error.

Isolate conflicts with Safe Mode

Enabling "Safe Mode" on the "General" tab of Elementor's "Tools" runs the editor without loading your theme or other plugins. What visitors see does not change.

1. Enable "Safe Mode" and save.
2. Reopen the editor and check whether the problem still happens.
3. If Safe Mode fixes it, the cause is your theme or another plugin. Disable Safe Mode again, then deactivate plugins one at a time, for example on a staging site, to find the cause.

If you deactivate plugins with WP-CLI, save the list of active plugins first so you can restore it.

# Save the list of currently active plugins
wp plugin list --status=active --field=name > active-plugins.txt

# Deactivate everything except Elementor and Elementor Pro
wp plugin deactivate $(grep -v -x -e elementor -e elementor-pro active-plugins.txt)

# Activate plugins one at a time and check whether the problem comes back each time
wp plugin activate contact-form-7

# When you are done, restore the original state
wp plugin activate $(cat active-plugins.txt)

This method also affects what visitors see, so on a live site try it on staging first or do it during low-traffic hours.

For cases where the editor fails to load because of the server configuration, Elementor's "Settings" → "Advanced" tab has a "Switch Editor Loader Method" option. Enable it and try again if the methods above do not reveal the cause.

If you cannot save, or saving returns 403 or 500, how to fix Elementor errors explains how to inspect the request and check your WAF.

Step 5: If an update broke things, roll back to the previous version

If the layout broke right after an Elementor update, roll back to the previous version and see whether that helps. Back up the database before rolling back (Elementor's screen shows the same warning).

1. Open the "Version Control" tab in Elementor's "Tools".
2. Under "Rollback to Previous Version", choose the version you want and click the "Reinstall" button.

To reinstall a specific version with WP-CLI, do the following. Replace 4.3.6 with the version you want to go back to. Also turn off auto-updates so that the plugin is not updated again while you are on the older version.

wp plugin install elementor --version=4.3.6 --force
wp plugin auto-updates disable elementor

Once a version with the fix is released, turn auto-updates back on (wp plugin auto-updates enable elementor) and update to the latest version. Staying on an old version means you miss security fixes.

Step 6: Check the permissions of the CSS files

If wp-content/uploads/elementor/ is not writable, the CSS files cannot be rebuilt. As WordPress recommends, use 755 for directories and 644 for files as the baseline. Setting directories to 644 as well, as with chmod -R 644, makes the files inside inaccessible, so set directories and files separately.

# Check the current permissions and owner
ls -la wp-content/uploads/elementor/css/

# Set directories to 755 and files to 644
find wp-content/uploads/elementor -type d -exec chmod 755 {} \;
find wp-content/uploads/elementor -type f -exec chmod 644 {} \;

If the owner differs from the user the web server runs as, the files may not be writable even with the right permissions. If you need to change the owner on shared hosting, ask your host's support.

Summary

• If the live page does not update, run "Clear Files & Data" or wp elementor flush-css --regenerate, then clear the page cache and CDN too
• If a widget disappeared, check Element Manager, any unregister() code, and whether Pro and add-ons are active
• For a custom widget, check that it is registered with register() on elementor/widgets/register and that the class and categories are correct
• If the editor will not open, raise the memory limit and isolate conflicts with Safe Mode
• If an update broke things, back up first and roll back with "Version Control"

Questions about WordPress? The publisher of this site is based in Japan and replies in Japanese. Contact (Japanese)