Notion offers two ways to display the same database content in multiple places: Linked Database and Synced View. Many users confuse these features because both show data from a source database. However, they work differently and serve distinct purposes. This article explains the core differences between Linked Database and Synced View, including their behavior, editing capabilities, and ideal use cases.
Key Takeaways: Linked Database vs Synced View
- Linked Database (the /linked command): Creates a full copy of the source database that can be filtered, sorted, and edited independently while syncing all changes back to the source.
- Synced View (the /synced command): Creates a read-only mirror of a specific view from the source database; edits are not allowed in the synced block.
- Choose based on need: Use Linked Database for editing and custom views; use Synced View for displaying content without risk of accidental changes.
What Are Linked Database and Synced View in Notion?
Notion databases are the backbone of structured content. A single database can contain hundreds of pages, each with properties like text, dates, and relations. When you want to show the same data in another location — such as a different page or workspace — you have two options.
A Linked Database is a dynamic duplicate of the original database. It appears as a full database block that you can customize with filters, sorts, and different views (table, board, calendar, etc.). Any change you make in the linked version — adding a new page, editing a property, or deleting a row — applies to the source database and all other linked copies. Linked databases are created using the /linked command.
A Synced View is a block that mirrors a specific view of the source database. It is read-only within the block itself. You cannot edit data, change the view type, or apply filters inside the synced block. Synced views are created using the /synced command and are best for displaying content that should remain unchanged.
How the Source Database Works
Every database in Notion has a unique ID. Both Linked Database and Synced View reference this ID. The source database is the single point of truth. When you edit the source, all linked and synced instances update automatically. The difference lies in whether you can edit from the remote location.
How to Create a Linked Database vs a Synced View
The creation process is similar but the resulting behavior is different. Follow the steps below to set up each type.
Creating a Linked Database
- Open the target page
Navigate to the Notion page where you want the linked database to appear. - Type /linked
In the page body, type a forward slash followed by the word linked. Select Linked view of database from the menu. - Choose the source database
A pop-up window appears. Search for and select the database you want to link. - Select a view
Pick the initial view type and any existing saved view from the source. You can change this later. - Customize the linked view
Use the view menu to add filters, sorts, and properties. The linked database is fully editable.
Creating a Synced View
- Open the target page
Go to the page where you want the synced block to appear. - Type /synced
Type a forward slash followed by synced. Select Synced block from the menu. - Paste the source database link
Copy the link to the source database view you want to mirror. Paste it into the synced block. - Confirm the sync
The block displays the content. You cannot edit any data inside the synced block. - Update the source to refresh
Any changes to the source database automatically appear in the synced block, but you cannot modify anything from the synced location.
Common Misconceptions and Limitations
Users often assume both features work identically. Here are the most frequent misunderstandings and how to avoid them.
Linked Database Does Not Create a Separate Database
A linked database is not a copy. It is a live view of the original. Deleting a page in a linked database removes it from the source and all other linked instances. To create an independent copy, duplicate the entire database instead.
Synced View Cannot Be Filtered or Sorted
The synced block shows exactly what the source view displays. You cannot apply local filters or sorts. If you need different filters in different locations, use a linked database and apply separate filters to each instance.
Synced View Does Not Support Inline Editing
Clicking on a row in a synced block opens the source database page, but you cannot edit properties directly in the synced block. For editing, use a linked database or go to the source.
Linked Database Views Are Independent
Each linked database can have its own view type, filters, and sorts without affecting other linked copies or the source. This is useful for dashboards where different teams need different perspectives on the same data.
Notion Linked Database vs Synced View: Feature Comparison
| Feature | Linked Database | Synced View |
|---|---|---|
| Editable in place | Yes | No |
| Custom filters and sorts | Yes, per instance | No |
| Multiple view types per instance | Yes | No |
| Data syncs to source | Immediately | Read-only |
| Creation command | /linked | /synced |
| Best use case | Collaborative dashboards, project trackers | Display-only reference, documentation |
Both features keep data in sync with the source database. The key difference is whether you need to edit data from the remote location. Choose Linked Database for active work and Synced View for static presentation.
Now you can decide which feature fits your workflow. For a project dashboard where team members update tasks daily, use a linked database with filtered views per person. For a company wiki that references a master employee list, use a synced block to prevent accidental edits. An advanced tip: combine both on the same page — use a linked database for active editing and a synced block below it showing a summary view of the same data for quick reference.