← Back to Blog

WordPress Patterns and Synced Patterns

A WordPress pattern is a preconfigured group of blocks that can be inserted as a reusable design.

Veyra Admin

5 min read

  • Guide
  • Beginner
  • 5 minutes read
  • Reviewed August 5, 2026
  • WordPress themes and templates

A WordPress pattern is a preconfigured group of blocks that can be inserted as a reusable design.

Patterns help teams create consistent layouts without rebuilding the same arrangement from scratch. They can be supplied by WordPress, a theme, a plugin or the website itself.

The most important distinction is whether inserted copies remain independent or synchronized.

Unsynced Patterns

An unsynced pattern acts as a starting layout.

When you insert it, WordPress copies its blocks into the current post, page or template. You can then edit that copy independently. Later changes to the original pattern do not update existing copies.

Use unsynced patterns for:

  • Hero sections with replaceable content.
  • Pricing layouts.
  • Testimonial arrangements.
  • Article callouts.
  • Contact sections.
  • Standard page structures that need local variation.

They provide consistency at creation time without creating a permanent dependency.

Synced Patterns

A synced pattern is a reusable entity whose content remains connected across every placement.

Editing it in one location updates all uses. Synced patterns replaced the terminology previously used for reusable blocks.

Use them for content that should remain identical, such as:

  • A current promotional notice.
  • A legal disclosure.
  • A repeated subscription call to action.
  • Shared contact details.
  • A centrally managed announcement.

Because one edit can affect many pages, assign permissions and review processes appropriately.

Overrides and Controlled Variation

Modern WordPress can allow selected blocks inside a synced pattern to be overridden per instance while preserving the shared design.

This supports components such as team cards or calls to action where the layout remains governed but text or images vary.

Availability and behavior depend on WordPress and block support, so test the intended workflow before relying on it across a large site.

Theme and Directory Patterns

Themes can register patterns as part of their design system. WordPress can also surface patterns from the Pattern Directory.

Theme patterns should use broadly available blocks or clearly document dependencies. A pattern containing blocks from an unavailable plugin cannot be reproduced correctly.

Patterns can also be categorized to help editors find appropriate layouts.

Patterns vs Templates

A pattern is a group of blocks that can be inserted into content or templates.

A template defines the structure used to display an entire page type. It may include patterns, but it has a different responsibility.

For example, a Single Post template can contain a header template part, Post Title, Post Content and a related-content pattern.

Patterns vs Template Parts

Template parts represent repeated structural regions used by templates, especially headers and footers.

They participate in the theme template system and are edited within the site-design workflow. Patterns are more general reusable block compositions.

The WordPress interface may list template parts within the Patterns area, but the concepts remain distinct.

Planning a Pattern Library

A useful library should be curated rather than enormous.

Define:

  • Naming conventions.
  • Categories.
  • Intended context.
  • Required blocks and plugins.
  • Whether the pattern is synced.
  • Which content can be overridden.
  • Responsive and accessibility expectations.
  • Ownership and review process.

Remove outdated or duplicated patterns so editors can find the approved choice quickly.

Frequently Asked Questions

Do changes to a normal pattern update existing pages?

No. Unsynced patterns are copied when inserted. Existing copies remain independent.

Are synced patterns the same as template parts?

No. Both are reusable, but template parts belong to the template structure while synced patterns are reusable block content.

Can a pattern contain custom blocks?

Yes, but those blocks must be available wherever the pattern is used.

Applying WordPress Patterns and Synced Patterns in a Real WordPress Project

Separate content, presentation and permanent functionality. Test the editing workflow as well as the public output, because a theme decision affects templates, design controls, accessibility, performance and future redesign work.

A connected concept is WordPress Templates and Template Parts. Reading the two together helps separate the immediate task from the wider WordPress responsibility.

A useful implementation begins by writing down the current state, the intended outcome and the evidence that will prove the change worked. This prevents a configuration screen, plugin recommendation or code snippet from becoming the entire strategy.

A Practical Example

Imagine a team making this decision for a production WordPress site. The useful question is not only “Can WordPress do this?” but “Which layer owns it, who maintains it, what data does it affect and how will we verify it after an update?”

Write the answer in operational terms. Name the content, user, setting, file, API or service involved. Then identify what should remain true if the theme changes, a plugin is replaced or the site is migrated.

Questions to Ask

  • What user or system problem does this solve?
  • Which WordPress layer owns the behaviour?
  • What data is created or changed?
  • Who may perform the action?
  • What can fail, and how will that failure be visible?
  • How is the result tested after updates?
  • What is the migration or removal path?

Review Editor and Frontend Behaviour

A block feature has at least two user experiences: the editor used to create it and the frontend used to consume it. Dynamic data, responsive behaviour and accessibility can differ between the two.

Test insertion, selection, keyboard operation, saved markup, server rendering, theme styles and backward compatibility with previously saved content.

Official Reference Context

The Block Editor Handbook is the primary version-specific reference for this topic. Use the current documentation to verify interface labels, supported APIs and behaviour before applying instructions to a production site.

How to Verify the Result

  • Test representative templates on mobile and desktop.
  • Check keyboard navigation, headings, contrast and focus.
  • Switch editing contexts and confirm that the team knows where each design decision is stored.

Sources and Further Reading

Continue Learning