How to Use Synced Block With a Notion Database View

You want to display the same Notion database view in multiple pages without duplicating data or manually updating each copy. A synced block lets you mirror a database view, so any change you make in one location automatically appears everywhere the block is synced. This article explains how to create a synced block for a database view, how to manage its content, and what limitations you should know before using it.

What Is a Notion Synced Block and How It Works With Database Views

A synced block is a container that mirrors its content across every instance you paste. When you create a synced block and place a database view inside it, that view — including its columns, filters, sort order, and layout — is duplicated to all other synced copies. Any modification to the view inside the original synced block updates every copy instantly.

This is different from a linked database view. A linked database view shows the same database content but allows each instance to have independent filters, sorts, and layouts. A synced block forces the exact same view configuration everywhere. Use synced blocks when you need identical presentations of the same data set across multiple pages, such as a project status board shown on both a team dashboard and a client-facing page.

Before you start, make sure you have a Notion page that contains a database view — a table, board, gallery, list, or calendar view of a database. The database itself can be inline or full-page. The synced block works with any view type.

Steps to Create a Synced Block for a Database View

1. Open the page that contains the database view
   Navigate to the Notion page where the database view you want to mirror is located. The view must already exist and be visible on the page.
2. Create an empty synced block on the same page
   Type /synced block in a blank line on the page. Select Synced block from the menu. A gray box with a sync icon appears. This is the master synced block.
3. Drag the database view into the synced block
   Click and hold the six-dot handle to the left of the database view. Drag it directly into the synced block box. Drop it inside the gray area. The database view now lives inside the synced block.
4. Copy the synced block to other pages
   Hover over the synced block and click the Copy icon that appears in the top-right corner of the block. Alternatively, press Ctrl+C on Windows or Cmd+C on Mac. Navigate to the target page and paste with Ctrl+V or Cmd+V.
5. Verify the sync
   On the target page, the pasted block shows the same database view. Make a change to the view in the original synced block — for example, add a filter or change the sort order. Return to the pasted copy. The change appears automatically.

Alternative Method: Turn an Existing Database View Into a Synced Block

1. Right-click the database view
   Click the six-dot handle to the left of the view or right-click the view title area. A context menu opens.
2. Select Turn into synced block
   From the menu, choose Turn into synced block. The view is now wrapped inside a synced block. A sync icon appears in the top-right corner of the block.
3. Copy and paste the synced block to other pages
   Click the Copy icon in the top-right corner of the synced block. Paste it into any other page. All copies remain synced to the original.

Managing the Synced Block

To stop syncing a copy, click the sync icon in the top-right corner of any pasted synced block and select Unsync. The block becomes a standalone copy of the database view with no connection to the original. Changes to the original will no longer affect it.

To delete the master synced block, click the six-dot handle and select Delete. All synced copies become unsynced and turn into standalone blocks. The underlying database data is not deleted.

Things to Avoid and Common Limitations

You cannot sync a database view across different databases

A synced block mirrors the view configuration, not the database itself. If you need the same data to appear in multiple databases, use a linked database instead of a synced block.

Filters and sorts must be identical everywhere

Because a synced block forces the exact same view settings, you cannot have different filters on different copies. If you need independent filters per page, use a linked database view.

Adding new properties to the database does not update the view inside the synced block

If you add a new property to the underlying database, the synced block view does not automatically show it. You must manually add the property to the view inside the master synced block. The change then syncs to all copies.

Synced blocks do not work with inline databases in full-page databases

If your database is a full-page database, you cannot drag its inline view into a synced block on the same page. Instead, create a linked database view on a separate page, then wrap that linked view in a synced block.

Copying a synced block to a different workspace breaks the sync

Synced blocks only work within the same workspace. Pasting a synced block into a different workspace creates an unsynced copy. To share a view across workspaces, export the database or use the Notion API.

Synced Block vs Linked Database View: Key Differences

Feature	Synced Block With Database View	Linked Database View
View configuration sync	Filters, sorts, layout, and properties are identical in all copies	Each view can have independent filters, sorts, and layout
Data source	Same underlying database	Same underlying database
Editing a view property	Edit the master, all copies update	Edit one view, other views remain unchanged
Best use case	Identical dashboards or client reports	Different perspectives on the same data
Copy to other workspace	Breaks sync	Works with linked database permission

Conclusion

You can now create a synced block for any Notion database view and mirror it across multiple pages. Start by dragging an existing view into a synced block or by right-clicking the view and selecting Turn into synced block. Remember that only the view configuration syncs, not the underlying data. For more control, use linked database views instead. A practical next step is to build a weekly status dashboard that uses a synced block for a board view, ensuring your team sees the same task layout on every page.