WordPress Development

Block Patterns and Synced Patterns: Giving Editors Ready-Made Layouts

Block Patterns and Synced Patterns: Giving Editors Ready-Made Layouts

One of the most common requests I get from clients after launch is “Can you make me another page like the services page?” Before the block editor, that meant duplicating pages, copying shortcodes or asking a developer to build a new template.

Block patterns solved this. A pattern is a pre-designed arrangement of blocks that editors can insert with one click, then edit like any other content. A “services section” pattern, a “call to action” pattern or a “team grid” pattern gives editors professional layouts without designing them from scratch.

Synced patterns go further, letting you reuse the same content across many pages, so updating it once updates it everywhere.

Used well, patterns are one of the most effective ways to keep a WordPress site consistent and easy to edit. Here’s how they work and how I use them.

Patterns versus synced patterns

The terminology has changed over the years, so let’s be clear.

Patterns (unsynced)

A regular pattern is a starting point. When an editor inserts it, WordPress copies the blocks into the page. After that, the copy is independent. Changing it doesn’t affect the pattern or other pages using it.

Use regular patterns for layouts that should look consistent but contain different content each time, like a hero section, feature grid or pricing table.

Synced patterns

A synced pattern is shared content. Every instance points to the same source. Edit it in one place, and every page showing it updates.

Synced patterns were previously called reusable blocks. WordPress 6.3 renamed them and brought them together with regular patterns in one interface.

Use synced patterns for content that must be identical everywhere, like a newsletter signup block, a standard disclaimer, contact details or a current promotion banner.

Pattern overrides

WordPress 6.6 introduced pattern overrides for synced patterns. You can mark specific blocks inside a synced pattern as overridable, so editors can change certain content, like a heading or button text, in each instance, while the structure and design stay synced. It’s a useful middle ground between fully synced and fully independent.

Creating patterns in the editor

The simplest way to create a pattern:

  1. Build the layout in the editor using blocks.
  2. Select the blocks, open the options menu and choose “Create pattern”.
  3. Give it a name, assign categories and choose whether it should be synced.

The pattern appears in the inserter under the Patterns tab. Site owners can manage patterns in the Site Editor, or under Appearance, then Patterns, depending on the theme.

Patterns created this way are stored in the database. That’s convenient for site owners, but for patterns that are part of the site’s design system, I prefer registering them in code.

Registering patterns in a theme

Block themes can include patterns as PHP files in a patterns folder. WordPress registers them automatically. Each file starts with a header describing the pattern:

<!– wp:group {"align":"full","style":{"spacing":{"padding":{"top":"var:presetspacing60","bottom":"var:presetspacing60"}}},"backgroundColor":"primary","textColor":"base","layout":{"type":"constrained"}} –>

The easiest way to create this markup is to build the layout in the editor, switch to the code editor and copy the block markup. Then replace hard-coded text with translatable strings and image URLs with theme file references.

Because pattern files are PHP, you can use functions like get_theme_file_uri for images and escaping functions for translatable text.

Pattern header options

Useful header fields include:

  • Title: what editors see.
  • Slug: a unique identifier, prefixed with your theme name.
  • Categories: where it appears in the inserter. Use core categories like call-to-action, header, footer, text, gallery, or register your own.
  • Keywords: help editors find it through search.
  • Block Types: suggest the pattern for specific blocks or contexts.
  • Post Types: limit where the pattern is available.
  • Template Types: suggest the pattern when creating specific templates.
  • Inserter: set to false to hide it from the inserter, for patterns used only inside templates.

Registering patterns in a plugin

For patterns that should survive theme changes, register them in a plugin using register_block_pattern, with the block markup as content. Register custom categories with register_block_pattern_category.

Page creation patterns

When editors create a new page, WordPress can offer a choice of full-page patterns as starting points. Add the core/post-content block type to a pattern’s Block Types header, and it appears in the page creation dialog:

This is a great way to give editors complete page layouts, like a service page, landing page or about page, so they never start from a blank canvas.

Locking patterns

Editors sometimes accidentally move or delete important parts of a layout. Block locking prevents that. You can lock blocks so they can’t be moved or removed, while their content can still be edited:

For stricter control, the templateLock attribute on container blocks can prevent adding, moving or removing child blocks entirely, or restrict editing to content only. WordPress’s content-only editing mode lets editors change text and images in a pattern without touching its structure or design settings.

Use locking thoughtfully. Too much locking frustrates editors. Lock the structure where design matters, and leave content flexible.

Building a pattern library

For client sites, I build a pattern library that covers the most common needs:

  • Heroes: two or three variations, such as image with text, full-width background and simple heading.
  • Features: icon grids, alternating image and text rows.
  • Social proof: testimonials, logo rows, review highlights.
  • Calls to action: banners and inline CTAs.
  • Content sections: FAQs, team grids, pricing tables, timelines.
  • Full pages: service page, landing page, about page.

Each pattern uses the theme’s colours, fonts and spacing from theme.json, so everything fits together. Editors can mix and match sections to build pages that always look on brand.

Organise and name clearly

Name patterns by purpose and layout, like “Testimonials – three columns” rather than “Pattern 4”. Use categories and keywords so editors find what they need quickly. Remove patterns nobody uses; a cluttered library is as confusing as no library.

Hide core patterns if needed

WordPress includes core patterns and can load patterns from the WordPress.org pattern directory. On client sites with a strict design system, these may not match the brand. You can remove core patterns with:

And disable remote patterns from the directory with the should_load_remote_block_patterns filter.

Synced patterns in practice

Synced patterns are ideal for:

  • Calls to action used across many pages.
  • Contact details or office hours.
  • Legal disclaimers.
  • Promotional banners that change seasonally.

Be careful with synced patterns in large sites. Editors sometimes edit a synced pattern on one page, not realising they’re changing it everywhere. WordPress shows clear indicators when you’re editing a synced pattern, but training editors on the difference helps avoid surprises.

Patterns and performance

Patterns are just blocks, so they perform like any other content. Keep images optimised and avoid nesting excessive groups and columns, which creates heavy markup. Patterns built with core blocks benefit from WordPress loading only the styles for blocks used on the page.

Train editors on patterns

Patterns only help if editors know they exist and how to use them. After launch, I run a short session showing editors where patterns live in the inserter, how to insert and customise them, the difference between synced and unsynced patterns and how to build a new page from a full-page pattern. I also add a simple reference page in the dashboard, or a short document, listing the available patterns with screenshots and suggested uses.

A little training changes how editors work. Instead of copying old pages and editing them, which spreads outdated content and odd formatting, they start from clean, current patterns every time. That keeps the site consistent long after the original build.

Review the pattern library every six months and retire patterns nobody uses.

A smaller, well-used library is far more valuable than a large one editors ignore or find confusing.

Frequently asked questions

What’s the difference between a pattern and a template?

Templates define the structure of whole page types, like single posts or archives, in block themes. Patterns are reusable sections or layouts inserted into content or templates. Templates often include patterns.

Will editing a pattern update pages that already use it?

Not for regular patterns. Inserted copies are independent. Synced patterns update everywhere they’re used.

Can I convert a synced pattern into regular blocks?

Yes. Editors can detach a synced pattern instance, converting it into regular blocks that no longer update with the source.

Should patterns live in my theme or a plugin?

Design-specific patterns belong in the theme. Patterns tied to content structures or functionality that must survive a theme change belong in a plugin.

Final thoughts

Patterns give editors a library of professional, on-brand layouts and turn page building into assembly rather than design. Register core patterns in your theme, offer full-page patterns for common page types, use synced patterns for content that must stay identical and lock structure where it matters. A thoughtful pattern library is one of the best gifts you can give a client after launch.