Block themes vs Classic themes: WordPress theme choice

Short answer: this page helps site owners and agencies choose between block (Full Site Editing) themes and classic (PHP template) themes by listing shared capabilities, core differences, concrete consequences for editing workflow, tech stack, extensibility, performance and patterns, and a verdict by usage profile. Facts below were checked on September 27, 2026 against WordPress developer and documentation pages cited in the methodology section.

What block themes and classic themes have in common

Block and classic themes share a number of baseline responsibilities and capabilities as WordPress themes. The points below are documented in the WordPress Theme Handbook and companion resources.

These commonalities mean the decision is not about whether a site can look or behave like a WordPress site, but about how templates are authored, edited and extended.

Core difference in one line (developer footprint)

Block themes express templates as block markup plus theme.json and are editable in the Site Editor; classic themes rely on PHP template files and template tags which are edited in code or via the customizer/page builders.

Editing workflow and non‑developer control

Block themes are designed around the Site Editor and Full Site Editing (FSE). Templates, template parts and many structural elements are represented as blocks, which makes header/footer and other layout edits accessible via the editor interface documented in the Block Editor how‑to guides.

Classic themes use PHP templates and template tags; structural changes often require code edits or the use of the Customizer or page builder plugins. The practical consequence is that content teams and editors can often perform layout adjustments more directly with block themes, while classic themes sometimes need developer work for equivalent template changes.

File structure and templating

Block themes store templates and template parts as HTML files containing block markup and include a theme.json for global settings and styles. Classic themes use PHP template files and template tags such as the_title() and the_content(). The difference is visible in repository structure: block themes use the pattern/template model defined in block theme documentation; classic themes follow the PHP template file conventions in the Theme Handbook.

Extensibility and compatibility with plugins and page builders

Both theme types can work with plugins and page builders, but integration patterns differ. Some page builders historically targeted PHP template flows and offer integrations tailored to classic themes; hybrid approaches that mix block and classic techniques are a recognized path to bridge capabilities and retain specific integrations. The hybrid model is documented in developer discussions about bridging the gap between theme types.

theme.json, global styles and design system

Block themes can centralize global styles, presets and design tokens in theme.json, which is native to the Full Site Editing workflow. Classic themes typically centralize design via CSS and the Customizer. The centralized theme.json approach provides a native way to expose and manage design tokens for blocks in block themes.

Patterns and reusable blocks

Block patterns and reusable blocks are tightly integrated in the Site Editor and block theme ecosystem. Classic themes can register patterns, but block themes integrate pattern usage and pattern/template composition more natively into the Site Editor experience and pattern directory workflows.

Child themes and portability

Child themes still exist for block themes, but their override mechanisms interact with theme.json and block markup differently than with PHP template overrides. For specifics and edge cases, consult the developer handbook pages about child themes and block theme structure.

Performance considerations

Performance factors depend on many choices: how styles are loaded, whether block styles are conditionally loaded, server configuration and assets. Block themes can leverage block-based style handling; classic themes rely on server-side rendering of PHP templates. Documentation around WordPress releases and block editor evolution includes notes relevant to performance improvements introduced with Full Site Editing and recent core releases.

Accessibility and standards

Both block and classic themes can meet accessibility standards when the theme author follows best practices. Accessibility outcomes depend on authoring practices and quality control rather than the theme model alone. Refer to WordPress accessibility resources for guidance.

What it means in practice — verdicts by usage profile

No single winner applies to every project. Below are practical profiles with the approach that typically fits best given the documented differences.

Each profile recommendation links back to a trade-off: editability vs. server-side control, native FSE tooling vs. legacy plugin integrations.

Compact comparison table

Practical next steps & links

Methodology and consulted pages (state of facts)

Pages consulted on September 27, 2026 to build the factual points above:

No first‑party testing was performed; content is based on the documentation and developer resources listed above as of September 27, 2026.

What we do not know (open points)

Related guides

• The Hidden Dangers of Using Outdated PHP Versions on Your WordPress Site
• What is a WordPress child theme and when to use one
• How to choose a WordPress theme
• WordPress Themes