WordPress Patterns: Synced Patterns, Overrides and Reuse

A WordPress pattern is a ready-made group of blocks, such as a hero section, a pricing table, a testimonial row or a footer, that you insert into a page and then edit like any other content. The official developer handbook puts it simply: a block pattern is "one or more blocks that have been pre-configured and presented to the end-user." Patterns save time, keep layouts consistent and let a small team build pages that look designed rather than improvised.

There are two kinds. An unsynced pattern is a starting point: once inserted, its blocks are independent. A synced pattern (called a reusable block before WordPress 6.3) stays linked, so editing it once updates every place it appears. Since WordPress 6.6, synced patterns can also have overrides, which keep the design locked while letting editors change specific text, links or images in each instance.

This guide covers where patterns come from, how to create and manage them, how overrides work, how developers register patterns in themes and plugins, and how to build a small pattern library for a business site. Everything here reflects WordPress 7.1.2, the current version as of October 2026.

Where patterns come from

Open the block inserter (the + button) and switch to the Patterns tab. What you see is a mix of sources:

• WordPress core ships a set of standard patterns.
• Your theme can bundle patterns designed for its styles. Block themes such as Twenty Twenty-Five rely heavily on them.
• Plugins can register patterns, for example a forms plugin adding contact form layouts.
• The WordPress.org Pattern Directory at wordpress.org/patterns hosts community patterns. Its guidelines note that "people will be able to use submitted patterns without cost or attribution." Themes can also pull specific directory patterns into the inserter through theme.json.
• Your own patterns, created from blocks on your site.

Synced patterns you create appear under their own Synced Patterns section of the inserter. You can also type / followed by a pattern name in an empty paragraph to insert it quickly.

Synced vs unsynced patterns

When you create a pattern, you decide whether it is synced. The choice depends on whether the content should stay identical everywhere.

The official documentation explains the history: "WordPress 6.3 renamed Reusable Blocks to Patterns. A synced pattern will behave in exactly the same way as a reusable block."

How to create a pattern

You can create a pattern from any blocks in the post editor or Site Editor:

1. Select the block or blocks you want to save (List View makes selecting a whole section easy).
2. Open the three-dot options menu in the block toolbar.
3. Choose "Create pattern."
4. Enter a name for the pattern.
5. Turn the Synced option on or off.
6. Click Create.

Group the blocks first (Ctrl+G or ⌘+G) so the pattern is a single tidy unit, and name the Group in List View so the structure is clear to whoever edits it later. Our block editor guide covers these tools in more detail.

Managing, editing and detaching patterns

With a block theme, manage patterns in the Site Editor under Appearance > Editor > Patterns, which also lists template parts such as headers and footers. With a classic theme, Appearance > Patterns has opened the same Site Editor Patterns view since WordPress 6.6. From the editor you can also reach this screen from a block's options menu via "Manage patterns."

Three actions matter most:

• Edit a synced pattern from the Patterns screen or directly where it is inserted. Saving a post that contains a changed synced pattern will list the pattern in the save flow, because the change applies everywhere.
• Detach a synced pattern instance (formerly "Convert to regular block") when one page needs a different version. The instance becomes normal blocks and stops receiving updates. This is not available if the pattern is locked.
• Delete carefully. When a synced pattern is removed, every place that used it shows a message that the block has been deleted or is unavailable.

Pattern overrides: shared design, local content

Overrides solve a common problem: you want five service cards with an identical design that you can restyle in one place, but each card needs its own heading, text, link and image. Before WordPress 6.6, you had to choose between a synced pattern (same content everywhere) and an unsynced one (design drifts apart).

According to the WordPress 6.6 release documentation, overrides "allow specific pieces of content to be customized in each instance of a synced pattern while keeping a consistent style for all instances." The WordPress Developer Blog lists the supported blocks and attributes at launch:

To set it up, edit the synced pattern, select a supported block, open the Advanced panel in the block settings, click "Enable overrides" and give the override a unique name. Each instance of the pattern then accepts its own content for that block. Overrides are built on the Block Bindings API. Read the Developer Blog's introduction to overrides in synced patterns for technical details.

Registering patterns in a theme or plugin

For developers, patterns are the main way to ship layouts with a theme or plugin. There are three approaches.

The /patterns folder

Since WordPress 6.0, a theme can store each pattern as a PHP file in a /patterns folder, and WordPress registers it automatically. The developer handbook says WordPress "will recognize any pattern file placed in your theme's /patterns folder, and it will automatically register it for you." Each file begins with a header comment. The key fields are Title (a translatable, human-readable name), Slug (unique and namespaced, such as mytheme/hero-split) and Categories. Optional fields include Keywords, Block Types, Post Types, Viewport Width, Inserter and Template Types. The block markup follows the header.

register_block_pattern()

Plugins, and themes that need conditional logic, can call register_block_pattern() with a name and an array of properties (title, content, categories, description and so on). This is the long-standing programmatic method. WordPress 7.0 also added server-side, PHP-only registration of blocks and patterns, which helps developers who do not want a JavaScript build step.

Directory patterns through theme.json

A theme can list Pattern Directory slugs in the patterns key of theme.json to bundle those patterns. See theme.json explained for how that file is structured.

Starter and template patterns

Patterns can target specific situations. Setting Block Types to core/post-content makes a pattern a page creation pattern, offered when someone creates a new page (a WordPress 6.0 feature). Template Types associates a pattern with specific template types, such as a 404 page.

Patterns, block themes and classic themes

Patterns work in both theme types. In block themes, patterns are everywhere: templates are often assembled from them, and the Site Editor uses them for headers, footers and menu overlays (WordPress 7.0 added block-built menu overlays). Classic themes can register and use patterns in the post editor, and since 6.6 they share the Site Editor's Patterns screen. If you are deciding between theme types, our comparison of block themes vs classic themes explains the trade-offs.

Building a pattern library for a business site

A focused library makes it hard for content to look off-brand. A practical starter set for a service business:

• Page heroes: two or three variations (image left, image right, full-width cover), unsynced.
• Service blocks: a card grid as a synced pattern with overrides for each card's heading, text, button and image.
• Calls to action: a synced sitewide CTA, plus an unsynced version for campaign pages.
• Social proof: testimonial row and logo strip, unsynced.
• FAQ section: unsynced, so each page has its own questions.
• Contact block: synced, so phone numbers and hours change in one place.
• Legal and compliance text: synced and locked.

Write alt text guidance and heading levels into each pattern so editors inherit good habits. Check that every pattern's headings make sense in a page outline, since a pattern that starts with an H2 dropped under another H2 can confuse readers and search engines alike. Our guide to high-converting landing pages on WordPress is a good companion when designing the CTA and hero patterns.

Common pattern mistakes

• Syncing what should not be synced. A synced hero means every page has the same headline. Use overrides or unsynced patterns.
• Deleting a synced pattern in use. Every instance breaks. Search the site before deleting.
• Hard-coded colors and sizes. Patterns that use theme presets adapt when the brand changes; patterns with custom hex values do not.
• Placeholder content left live. Sample text and stock images from theme patterns end up on published pages more often than you would think.
• Too many patterns. Hundreds of options slow editors down (our tips on speeding up a WordPress design workflow apply here too). Developers can unregister patterns you do not want editors to use.

Conclusion

Patterns are the most practical way to keep a WordPress site consistent while letting non-designers build pages. Use unsynced patterns as starting points, synced patterns for content that must stay identical and overrides when you need shared design with local content. Developers can ship patterns from a /patterns folder with minimal code. For more guides, visit the WordPress resource hub. If you want a custom pattern library designed and built for your brand, eSEOspace offers WordPress website development.

Frequently asked questions