How do I create a synced block in Notion?

Creating a synced block in Notion starts with selecting the content you want to appear across multiple pages and typing /synced or right-clicking to choose "Turn into Synced block." This transforms your selected blocks into a powerful tool that maintains consistency across your workspace—when you edit the content in one location, it automatically updates everywhere else the block appears. You'll immediately notice a distinctive red border around your synced content, along with a dropdown menu showing all locations where this block exists. This feature has been available since June 2021 for both free and paid users across all Notion platforms.

The process itself is refreshingly straightforward. After creating your initial synced block, you can add any content inside it—text, images, toggles, or lists—and then use the "Copy and Sync" option from the three-dot menu. Paste this synced block anywhere in your workspace, and you've established a real-time connection between all instances. Whether you're working on desktop, mobile, or web, the experience remains consistent, though mobile users will tap and hold instead of right-clicking.

The practical applications for synced blocks are compelling. Teams frequently use them for project instructions that need to appear across multiple documents, navigation menus that should remain consistent throughout a workspace, or status updates that multiple stakeholders need to access. This eliminates the tedious process of manually updating the same information in various locations and reduces the risk of version mismatches that can confuse collaborators.

However, synced blocks do come with considerations worth understanding. Performance can suffer with extremely large blocks or numerous nested synced elements, potentially causing sync delays or failures. Additionally, managing permissions becomes crucial—all users who need to edit synced content must have editing rights across every page where the block appears. This can create access complications in workspaces with varied permission levels.

The key to successful synced block implementation lies in starting small and being mindful of your team's workflow patterns. Consider which content truly benefits from synchronization versus what might be better left as independent blocks. Remember that deleting any instance removes the content everywhere, though you can always "unsync" a block to make it independent again, preserving flexibility as your workspace evolves.