WordPress Widgets After the Block Editor

Three different things are called widgets, and most confusion about them is really confusion about which one you are looking at:

The advice you find online is usually written for one of these and applied to another. Work out which you have first: if Appearance → Widgets exists, you are on a classic theme. If it does not, you are on a block theme and widgets have been replaced by template parts.

What a widget actually is

A widget is a small piece of content placed into an area the theme defines — a sidebar, a footer column, a header slot. The theme decides where the areas are; you decide what goes in them.

That relationship is the important part. Widget areas belong to the theme. Switch themes and your widget placement is lost, because the new theme defines different areas. The widgets themselves are not deleted — they are moved to an inactive list — but the arrangement is gone. This is a normal part of changing a WordPress theme and worth knowing before you spend an afternoon arranging a footer.

The block widget screen

On a classic theme, Appearance → Widgets is now a block editor. Practically:

• You add blocks, not widgets, and every block is available — headings, images, columns, groups.
• Old widgets still work, wrapped in a Legacy Widget block that renders the original form.
• Widgets a plugin registers appear the same way, so nothing you had stops working.
• You can build genuinely complex footers now, because columns and groups are available where they never were before.

The gain is real: a footer with three columns, an image and a call to action used to need a plugin or a theme feature. The loss is familiarity, and on a site where a client arranges their own sidebar that loss is not trivial.

To restore the old screen, install the Classic Widgets plugin from the official directory. It is maintained and it works. Treat it as time to plan a move rather than a permanent answer — the same reasoning as restoring the classic editor.

Block themes have no widgets at all

This surprises people who switch: a block theme has no Appearance → Widgets screen and no widget areas.

Instead, the header, footer and sidebar are template parts you edit directly in the Site Editor. Whatever you would have put in a widget area, you place as a block in the part itself. It is a better model — you see the real layout while editing rather than a list of boxes — and it means widget-era instructions do not apply.

Two consequences worth knowing:

• Plugin widgets may not have block equivalents. A plugin that only registers a classic widget has nothing to offer a block theme unless it also ships a block or a shortcode.
• Your existing widgets are not migrated. Switching from a classic to a block theme means rebuilding those areas by hand.

A page builder's widgets are something else

If you use a page builder, its elements are frequently called widgets too — a heading widget, an image widget, a form widget. These have nothing to do with WordPress widget areas. They live inside builder-made pages, they are stored by the builder, and they disappear with it. Which is one more reason to understand the storage model before committing, as covered in choosing a page builder.

If someone tells you to "drag the widget onto the page" and your Appearance → Widgets screen has no such thing, they are describing a builder.

Things people commonly want

A widget on some pages only. Core has no conditional display. Either the theme provides it, or a plugin does, or you build a separate template.

A map or a form in the sidebar. Use the plugin's block or shortcode rather than hunting for a widget; most plugins ship blocks now and maintain the widget only for compatibility.

Widgets in the header. Only if the theme registers a header area. On a block theme, just edit the header template part.

A custom sidebar per section. This is a theme or plugin feature, not a core one. On a block theme it is a template with a different sidebar part, which is cleaner than the classic equivalent ever was.

Common mistakes

• Expecting widget placement to survive a theme switch. It never does.
• Following block-theme instructions on a classic theme, or the reverse, then concluding the screen is broken.
• Installing Classic Widgets and stopping there. It postpones the work; it does not remove it.
• Confusing builder widgets with WordPress widgets, which sends you looking for a screen that does not apply.
• Putting site-critical content only in a widget area. It is theme-owned, so it is the first thing lost in a redesign.
• Assuming an inactive widget is deleted. Old widgets sit in the inactive list with their content intact — check there before rebuilding something from scratch.

If the screen is not behaving

A widget screen that will not save or renders blank is usually a JavaScript problem rather than a widget problem. Check the browser console, disable script optimisation in your performance plugin, and try with only the default theme active — the process is in how to fix plugin conflicts. If changes save but do not appear on the front end, that is caching, not widgets: see WordPress changes not showing.