Synced vs Standard WordPress Patterns: Choose Before Reusing a Block

Before reusing a section in WordPress, decide what should happen after it appears on several pages. Should a later edit change every copy, or should each page retain its own content? That decision determines whether to use a synced pattern, a standard pattern, or a detached copy of a synced pattern. The sections may look identical on insertion, so appearance alone cannot tell an editor which behaviour to expect.

WordPress lists custom patterns under Appearance → Editor → Patterns → My patterns on sites using a block theme. The list distinguishes Synced from Standard patterns. WordPress’s Site Editor pattern guide describes the labels and the controls for managing saved patterns. On other themes or editor configurations, use the available pattern controls and check the saved item before editing an instance.

What changes when a pattern is reused?

Imagine an “About this guide” section on three service pages. It contains a heading, a paragraph and a button. All three copies initially show the same words. Later, an editor changes the button label on page A. What happens on pages B and C depends on the kind of pattern and on whether the editor changes the shared pattern or a local copy.

With a synced pattern, the placements share the same saved content. Editing that content changes it wherever the pattern is used. This suits a statement that must stay consistent, but a small change made while viewing one page may affect many others. WordPress’s synced pattern documentation explains both the shared update and the option to detach an instance.

With a standard pattern, each insertion is a starting copy. An edit to the section on page A leaves the copies on B and C alone. Editing the saved standard pattern later changes the starting point for future insertions; it does not update content already placed on pages. Choose this when the layout repeats but the words, links or destinations belong to individual pages.

A detached instance starts as a synced placement but becomes independent. If page C needs different wording, detach its instance before editing. Pages A and B remain connected to the saved pattern, while C stops receiving its later changes. Detaching C does not convert the saved pattern or alter other placements.

Choose according to the next edit

A synced pattern is appropriate when one editorial decision should apply everywhere it appears. Examples include a short shared explanation or a recurring notice with approved wording. Before saving a change, check which pages use it and review the items named in the save flow. A link change deserves particular care: its label and destination may need to make sense in every placement, not just on the page open in the editor.

A standard pattern is appropriate when the repeated element is the structure. A service introduction might consistently use a heading, two paragraphs and a button, yet each page needs its own subject and destination. Insert the pattern, then write for that page. If the starting layout or copy improves later, update the saved pattern for new insertions and decide separately whether existing pages need changes.

Detach a synced instance when one page needs a lasting exception and the remaining placements should still share updates. The exception has a cost: that page will no longer receive corrections to the synced original. If many pages now need different content, a standard pattern may provide a clearer starting point for future work. Existing synced placements still need to be reviewed individually; creating a new standard pattern does not convert them.

A useful test is to identify who should own the next change. If the shared message owns it, keep the pattern synced. If the page editor owns it, use a standard pattern. If one existing page has become exceptional, detach only that instance. Name saved patterns clearly enough that another editor can recognise the intended behaviour before using them.

What happens to existing copies?

• Edit a synced pattern: every instance still connected to it receives the shared change.
• Edit one standard-pattern copy: only that page changes; other inserted copies remain independent.
• Edit a saved standard pattern: new insertions use the revised starting point; existing copies keep their content.
• Detach one synced instance: it becomes independent, while other instances continue to follow the saved pattern.

There is a narrower exception to the usual synced behaviour. A synced pattern can use pattern overrides so that specified text or media differs between instances while the underlying design remains shared. Those overrides have to be configured for the relevant blocks. Do not assume that any field in an ordinary synced pattern can be changed locally. The WordPress Developer Blog’s explanation of overrides describes how the configured fields differ from the shared pattern.

Check the state before editing

In the Site Editor, open My patterns and check whether the saved item is labelled Synced or Standard. Then inspect the placement on the page you intend to change. Selecting a paragraph inside a pattern and selecting the whole pattern are different actions. Read the available action labels and the save summary before confirming. WordPress provides a Detach pattern action for an eligible synced instance; a locked pattern may restrict that action.

Editor screens and controls can vary with the installed WordPress version, theme and permissions. Follow the labels in the editor you are using rather than an older screenshot. If the section's state is unclear, make a small test on a draft page before changing public content. Inspect another page that uses the same saved pattern to establish whether the test stayed local or followed the shared original.

Check the button destination as well as its wording during that test. A shared button may lead to a page that suits one placement but not another. If the destinations must differ, use independent copies or confirm that an override has been configured for that specific field.

Make a recoverable change

Before a substantial change to a synced pattern, identify known placements and record their current wording and links. A global edit is easier to judge when you can see the contexts it will affect. If the Site Editor offers Export as JSON for the saved pattern, keep that export with the editorial work. It preserves a copy of the pattern; it does not by itself back up every page where the pattern appears. Use the site's normal revision or backup process for any page content you also need to preserve.

For a local exception, detach the intended instance, change a small piece of visible text, and save the page. Check that page and one that should remain synced. The first should show the local edit; the second should still show the shared content. This check helps catch a mistaken selection before a larger rewrite. For a global change, edit the synced pattern, inspect the save summary, then check representative pages after saving, including one you did not open for editing.

If an older synced pattern has a useful layout but future insertions should be independent, create a new standard pattern from the appropriate blocks and give it a distinct name. Confirm that its Synced option is off. Test it on a draft page by inserting it twice and editing only one copy. Keep the old synced pattern while existing pages depend on it, and move those pages to independent content deliberately. Removing a shared pattern before checking its placements can disrupt content that still uses it.