Patterns or Synced Blocks: Which One You Actually Want
The block editor offers two ways to reuse a chunk of layout, and the difference between them is the single most useful thing to understand about building with blocks.
The short version
- A pattern is a starting point. Insert it, then edit freely.
- A synced block is one source of truth. Edit it once, it changes everywhere.
- Patterns for layouts. Synced blocks for content that must stay identical.
- Getting this wrong is annoying in both directions.
Patterns: copies
Inserting a pattern drops a copy of its blocks into your content. From that moment it has no connection to the original. Change the pattern later and existing pages are unaffected.
This is what you want for layout: a three-column feature section, a call-to-action band, a post intro structure. Each use will have different text, and you do not want editing one to change the others.
Synced blocks: references
A synced block is stored once and referenced wherever it appears. Edit it in one place and every instance updates immediately, including on published pages.
This is what you want for content that must be identical and current everywhere: an affiliate disclosure line, a standard author note, a promotional banner with an expiry date, a legal notice.
| You want to… | Use |
|---|---|
| Reuse a layout with different text each time | Pattern |
| Keep a disclosure identical on 60 posts | Synced block |
| Give an editor a starting structure | Pattern |
| Update a banner across the whole site at once | Synced block |
| Standardise a post intro format | Pattern |
| Maintain a table of prices used in several posts | Synced block |
The failure modes
Pattern where you needed synced: you update your affiliate disclosure wording and discover it is baked into sixty posts as separate copies. Find and replace across the database, carefully.
Synced where you needed a pattern: an editor adjusts the heading on one landing page and changes it on all twelve. Worse, nothing warns them, and the change is live immediately.
Watch out
Synced blocks apply instantly to published content with no review step. Treat any synced block containing a price, a date or a claim as something only specific people should edit.
A practical setup
- Build your recurring layouts as patterns, registered in the theme so they survive content changes.
- Create synced blocks only for genuinely global content — disclosure, author note, current promotion.
- Name synced blocks with a clear prefix so nobody edits one by accident.
- Document which is which somewhere the editors will actually see.
Common questions
Can I convert between them?
Yes, in both directions. Converting a synced block to a copy detaches that one instance, which is a useful escape hatch.
Where should patterns live?
Register them in your theme or a small plugin rather than creating them in the admin, so they are version-controlled and portable.
Do synced blocks slow anything down?
No meaningfully. They are resolved at render time and cached like any other content.
Sumit
Writes everything on TechMozz.