Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOn a classic WordPress theme, widget areas can contain both traditional widgets and blocks. On a block theme, you generally manage site areas in the Site Editor rather than the old Widgets screen. So widgets are not universally obsolete: the right editing path depends mainly on your theme and whether a plugin offers a native block.
What is the difference between WordPress widgets and blocks?
A widget is a component registered for placement in a theme-defined area, such as a sidebar or footer. The traditional Widgets screen lets you add, configure, move, and remove these components; a theme may also provide a live preview through the Customizer.
A block is a modular unit edited with the WordPress block editor. Blocks can be arranged and configured as part of a richer layout. Since WordPress 5.8, released July 20, 2021, classic themes that support widget areas can use a block-based editor in those areas. That means widgets and blocks can coexist rather than representing an either-or choice.
| Question | Traditional widgets | Blocks in widget areas |
|---|---|---|
| Where are they edited? | In Appearance → Widgets, or through the Customizer when available. | In the block-based editor under Appearance → Widgets or Appearance → Customize → Widgets, for classic themes that support widget areas. |
| How are they organized? | Assigned to areas a theme registers, such as sidebars or footers. | Added and arranged within those same widget areas. |
| Do third-party widgets work? | Yes, through the widget system for which they were built. | Many can be edited and previewed through the Legacy Widget block, though support can vary. |
| Can they become native blocks? | Only when the widget author provides a migration path, including the data and transform support needed for conversion; there is no universal automatic conversion. | |
Which editor you see depends on your theme
Classic themes: widget areas can mix blocks and legacy widgets
With a classic theme that supports widget areas, the block-based Widgets Editor lets you add blocks alongside existing widgets. The Legacy Widget block provides access to compatible old and third-party widgets, including their controls and a preview. This compatibility path is designed to work with most third-party widgets, but it does not guarantee that every plugin behaves identically in the block editor.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches#1 Best Overall
Block themes: use the Site Editor
Block themes, including Twenty Twenty-Five, use the Site Editor to work with the broader site layout. The traditional Appearance → Widgets menu is generally removed in favor of Site Editor tools such as templates, template parts, and patterns. A missing Widgets menu on a block theme does not by itself mean that saved content has disappeared; it means the theme uses a different editing model.
Are WordPress widgets obsolete?
No. WordPress retains a compatibility mechanism for existing and third-party widgets, and classic themes can continue to use widget areas. The block-based Widgets Editor was introduced in WordPress 5.8 to bring blocks into those areas without requiring every widget to be replaced. Whether you should keep a particular widget depends on whether it still meets your needs and whether its plugin provides a reliable native-block alternative.
Can I convert a widget to a block?
Sometimes, but conversion depends on the widget’s developer. To convert an instance into a native block, the plugin must make the widget data available through the REST API, and the destination block must define a transform from core/legacy-widget. A plugin may also hide its old widget from the Legacy Widget block when it supplies a replacement, avoiding duplicate choices.
If a widget has no such transform, keep using it through the Legacy Widget block where available, or retain the classic editor if its controls do not work well there. Do not assume that switching editors will automatically convert every widget into a native block.
Rank #3
What happens to widgets when you switch to a block theme?
A block theme changes where you edit site structure: you use the Site Editor rather than the traditional Widgets screen. The available official documentation establishes that block themes use this different interface, but it does not promise a universal one-click conversion of every theme’s widget areas into block-theme layouts. Before switching, check the theme and plugin guidance for any widgets your site relies on, then verify their front-end output after the change.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How do I get the old WordPress Widgets screen back?
WordPress documents several ways to restore the classic widget editor. The appropriate option depends on whether you control the site as an administrator, maintain the theme, or are developing site-specific behavior.
Rank #4
- For an administrator: activate the Classic Widgets plugin to restore the classic Widgets screens.
- For a theme developer: call
remove_theme_support( 'widgets-block-editor' )to disable the block-based Widgets Editor for that theme. - For code-level control: use the
use_widgets_block_editorfilter to control whether the block-based editor is enabled.
Core’s block-widget storage is designed to preserve compatibility: blocks saved in widget areas remain visible on the front end and in the classic Widgets screen if the block-based editor is disabled. That fallback concerns saved block widgets; it does not turn them into traditional PHP widgets.
Quick Recap
Best Value
Which should you use?
- Use a native block when your theme supports the relevant layout and the plugin provides a block that meets your needs.
- Keep a Legacy Widget block when a working plugin widget has no suitable native-block equivalent.
- Restore the classic editor when legacy controls are essential and do not work reliably in the block-based Widgets Editor.
- For a block theme, edit in the Site Editor and check the theme’s templates and patterns rather than expecting the old Widgets menu.
Official WordPress references
- WordPress documentation: Block-based Widgets Editor
- WordPress documentation: Appearance Widgets Screen
- WordPress Developer Resources: Using blocks in the WordPress Widget Editor
- Make WordPress Core: Widgets Editor in WordPress 5.8
- WordPress Developer Resources: Legacy Widget block
- WordPress Developer Resources: use_widgets_block_editor
- WordPress Developer Resources: remove_theme_support()
- WordPress 5.8 “Tatum” release notes
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →
