If you’ve been following WordPress development over the past few years, you’ve probably heard the debates: Will WordPress eventually ditch classic themes in favor of Full Site Editing (FSE)? With block themes getting all the attention and the push toward a no-code editing experience, many wonder if the classic PHP-based theme system has an uncertain future.
The short answer? No, classic themes aren’t going anywhere—at least not anytime soon. But let’s break down why this topic keeps coming up, what the future actually looks like, and whether there’s a plan B for those who want to stick with classic themes no matter what.
Why the Debate?
When WordPress introduced the Gutenberg editor in 2018, it wasn’t just a new way to write posts—it was the beginning of a much bigger shift in how WordPress themes work. That vision eventually led to Full Site Editing (FSE), where every part of a website—header, footer, and everything in between—can be edited visually using blocks.
This shift is exciting for non-developers and those who prefer drag-and-drop design. But it also raises concerns for developers and long-time WordPress users who are used to the flexibility of classic themes. The question is:
- Will WordPress one day force everyone to move to block themes?
- What happens to classic themes in the long run?
Classic Themes Aren’t Going Anywhere
Despite all the focus on FSE, WordPress has no plans to remove support for classic themes. Here’s why:
1. Too Many Websites Still Use Classic Themes
WordPress powers over 40% of all websites that use a content management system (CMS), making it the dominant platform. The vast majority of those sites still rely on classic themes. Cutting them off would be disastrous, not just for users but for WordPress itself. Backward compatibility has always been one of WordPress’s biggest priorities, and there’s no reason to believe that will change.
2. FSE Isn’t for Everyone
Block themes are great for people who want a fully visual experience, but they don’t suit every use case. Many developers prefer working directly with PHP, custom templates, and theme files. Agencies building custom sites for clients also often rely on traditional development workflows that block themes don’t fully replace.
3. WordPress Still Supports Legacy Features from a Decade Ago
Just look at shortcodes and classic widgets—features introduced more than a decade ago that are still around. Even though WordPress has moved to blocks, they’ve kept these older tools for compatibility reasons. The same will likely happen with classic themes.
4. Hybrid Approaches Are Emerging
Many modern themes are adopting a hybrid approach—offering block-based customization for some elements while keeping PHP-based templates for others. This middle ground allows users to benefit from new tools without losing the flexibility of traditional theming.
But What If WordPress Did Drop Classic Theme Support?
Even though it’s unlikely, what would happen if WordPress decided to phase out classic themes completely?
1. Using Older WordPress Versions
Since WordPress is open-source, no one can force you to upgrade. Some users could simply stick with an older version that still supports classic themes. However, this comes with risks:
- No security updates from the WordPress team.
- Incompatibility with future PHP versions.
- Many plugins would stop working as they evolve with new WordPress updates.
2. Community-Led Forks of WordPress
A more radical solution would be for developers to fork WordPress and create a version that maintains classic theme support. This wouldn’t be the first time it happened—when WordPress introduced Gutenberg, some users created ClassicPress, a fork of WordPress 4.9 that still works without blocks.
If the official WordPress team ever removed classic themes, a similar fork would likely appear, keeping the old system alive.
3. Emulation Layers or Compatibility Plugins
Another possible workaround would be a plugin that allows classic themes to run inside a future block-based WordPress. For example:
- A compatibility layer that translates classic PHP templates into block-based equivalents.
- A plugin that restores the traditional theme system within a newer WordPress version.
While this would be a temporary fix, it could help users transition gradually rather than being forced to change overnight.
The Future of WordPress Themes
So what’s next? While classic themes will stick around, the trend is clear: WordPress is pushing hard toward block-based design. That doesn’t mean you have to switch, but it does mean that:
- New default themes (like Twenty Twenty-Four) will likely be block-based.
- Future features and updates will prioritize FSE over classic methods.
- More theme developers will embrace block templates, at least partially.
That said, WordPress has never been about forcing changes on users. Even if they focus on block themes, classic themes will likely remain an option for a very long time.
Should You Still Use Classic Themes?
It depends on your needs.
Stick with classic themes if:
- You prefer working with PHP and custom templates.
- You build highly customized client sites that don’t need block-based layouts.
- You want full control over your theme structure and performance.
Consider hybrid or block themes if:
- You want to future-proof your projects.
- You like the idea of mixing classic PHP templates with block-based customization.
- You build themes for a wide audience and want to support newer WordPress features.
Go all-in on block themes if:
- You don’t want to touch PHP and prefer a visual editor.
- You build websites for clients who need to edit everything themselves.
- You want to fully embrace the latest WordPress innovations.
Final Thoughts
For now, classic themes aren’t going anywhere. WordPress is all about choice, and for the foreseeable future, that means you can continue using classic themes if they work best for you. But with the rapid evolution of Full Site Editing, it’s worth keeping an eye on how the landscape changes.
Do you think classic themes will remain relevant in the long run? Or have you already made the switch to block-based themes?