SYNCED BLOCKS in Notion: How & When to Use — Replacing Global Blocks
Based on August Bradley's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Synced blocks link identical Notion content across multiple pages so edits propagate automatically.
Briefing
Notion’s new “synced blocks” feature replaces a clumsy workaround for “global blocks” by letting users link the same content in multiple places—so edits propagate everywhere automatically. Instead of cutting up URLs and embedding fragile snippets, a synced block is created directly inside Notion, then copied into other pages. Notion tracks how many locations it’s synced to and lists those destinations, making it easier to manage large, interconnected systems.
A synced block is built from any Notion “block,” meaning the units with the six-dot drag handle—ranging from single lines to groups, pages, tables, and even embedded widgets. Blocks can contain nested structures: toggles can hold multiple blocks under them, and table entries can be pages that behave as blocks when embedded. Once a block is selected and turned into a synced block, every instance stays linked. Changes and additions made in one location update all other synced copies, regardless of where they appear in the workspace.
The practical payoff is efficiency and consistency. When a block is updated in one place, the corresponding content elsewhere updates automatically—ideal for systems that need identical views or shared reference material. The feature also supports a clear workflow: create a synced block, copy it, paste it into other pages, and optionally “unsync” later to break the link.
One of the most useful applications is syncing database or table views. Users can create a table (including Kanban, calendar, timeline, or other filtered views), then drag that view into a synced block so multiple pages display the same filtered configuration and property ordering. If the goal is an identical view across locations—same filters, sorts, and layout—synced blocks provide a true “mirrored” database experience. If the goal is only similar information without strict identity, duplication is the better fit.
Synced blocks also work well for shared navigation and recurring structure. A user can place the same header or footer content at the top of many pages by turning the navigation block into a synced block and pasting it across the relevant pages. That way, updating the navigation once updates it everywhere.
In knowledge management, synced blocks help handle content that belongs to multiple topics. For example, a knowledge vault entry can be synced into several topic pages so that work done in one location stays current across all related topic areas. The same mechanism supports templates: a synced “guiding principles” block can be embedded into a weekly review template so that any edits made during the review automatically update the source principles, keeping them top of mind.
Overall, synced blocks turn a previously hacky, slow approach into an official, manageable feature—especially valuable for building comprehensive “life operating system” style workspaces in Notion where consistency, shared views, and cross-topic updates matter.
Cornell Notes
Synced blocks let Notion users link the same content across multiple pages so edits propagate automatically. Any Notion “block” (including lines, groups, pages, tables/views, and embedded widgets) can be turned into a synced block, then copied and pasted elsewhere. Notion shows how many synced locations exist and where they are, and users can unsync to break the link. The biggest value comes from keeping identical table/database views consistent across pages, sharing navigation headers/footers, and maintaining knowledge entries that belong to multiple topic areas. Synced blocks also pair naturally with templates, ensuring updates to shared reference content flow into every instance.
What exactly qualifies as a “block” that can be synced in Notion?
How does syncing differ from duplication when building multiple views of the same data?
Why are synced blocks especially useful for database or table views?
How can synced blocks support shared navigation across many pages?
How do synced blocks help when one note belongs to multiple topic areas?
What role do synced blocks play in templates and recurring workflows?
Review Questions
- When would duplication be the better choice than a synced block for multiple pages showing similar information?
- Describe a scenario where a synced block would prevent inconsistencies in a Notion workspace.
- What nested structures (like toggles or table entries) can still be treated as blocks for syncing purposes?
Key Points
- 1
Synced blocks link identical Notion content across multiple pages so edits propagate automatically.
- 2
Any Notion block—single lines, grouped lines, pages, tables/views, and embedded widgets—can be turned into a synced block.
- 3
Notion provides a count and a list of all synced locations, making it easier to track where shared content appears.
- 4
Synced blocks are ideal for identical database/table views (same filters, sorts, properties, and ordering) across multiple pages.
- 5
Shared navigation headers/footers can be maintained in one place and updated everywhere by syncing the navigation block.
- 6
Knowledge vault entries that belong to multiple topics can be kept consistent by syncing the relevant passage across topic pages.
- 7
Synced blocks work well with templates so edits to shared reference content (like guiding principles) update the source and all synced instances.