You want to show only certain pages in a Notion database that match a specific tag. Notion databases store all your entries in one table, but you often need to see a focused subset without affecting the original data. A sub-view is a saved view inside the same database, and adding a filter by tag lets you instantly display only the records that carry that tag. This article explains how to create a sub-view that filters by a tag property, customize it, and avoid common mistakes.
Key Takeaways: Filtering a Notion Sub-View by Tag
- Database view menu > Add a view: Creates a new sub-view without altering the original view.
- Filter button > Add a filter > Select the tag property: Limits the sub-view to rows whose tag value matches your chosen tag.
- View name and icon: Lets you rename the sub-view and assign an emoji for quick identification.
How Notion Sub-Views and Tag Filters Work
A Notion database can contain multiple views. Each view is a saved configuration of sorting, filtering, grouping, and layout options. The original data in the database never changes when you create a sub-view. You are simply applying a different lens to the same set of pages.
A tag property in Notion is a Select or Multi-Select column. Select lets you pick one tag per row. Multi-Select lets you assign multiple tags. When you filter a sub-view by a tag, the view displays only the pages where the tag property matches the value you specify. This works for both Select and Multi-Select properties.
No prerequisites are needed. You must already have a database with at least one tag property and some pages that carry tags. The steps below assume you have this setup ready.
Steps to Create a Sub-View Filtered by Tag
- Open your database
Navigate to the page that contains your Notion database. Click anywhere inside the database to make the database toolbar appear at the top. - Open the view menu
At the top-left corner of the database, you see the current view name. Click the downward arrow next to the view name to open the view menu. - Add a new view
From the view menu, click Add a view. A dialog box appears. Type a name for the new sub-view, for example “Tagged: Urgent”. Optionally, select an icon emoji. Click Create. The new sub-view opens as a tab next to the original view tab. - Open the filter menu
In the database toolbar, locate the Filter button. It looks like a funnel icon. Click Filter to expand the filter panel. - Add a filter condition
In the filter panel, click Add a filter. A dropdown list of all database properties appears. Select the tag property you want to filter by, for example “Status” or “Priority”. - Set the filter operator and value
After selecting the property, a second dropdown appears with operators. For a single tag, choose is. For Multi-Select, choose contains if you want pages that include that tag among others, or is if you want pages that have exactly that tag. Then select the specific tag value from the next dropdown. For example, choose is then Urgent. - Confirm the filter works
As soon as you set the filter, the sub-view updates to show only the rows that match the tag. Scroll through the list to verify that the correct pages appear. You can add additional filters by clicking Add a filter again and repeating the process. - Save and name the sub-view
The sub-view is saved automatically. To rename it later, click the view name, select Rename, and type a new name. To reorder the view tabs, drag the tab left or right.
Common Mistakes When Filtering by Tag in a Sub-View
Filter shows no results even though tags exist
This happens when the filter operator is set incorrectly. If your tag property is Multi-Select and you use is, the filter requires the page to have exactly that tag and no others. Use contains instead to match pages that include the tag among multiple selections. If the property is a single Select, is works correctly.
New pages with the tag do not appear in the sub-view
The filter applies to all pages in the database. If a new page has the tag, it appears automatically. If it does not appear, check that the tag value is spelled exactly the same as the filter value. Tag values are case-sensitive. Also confirm that the filter is not combined with other filters that exclude the new page.
The sub-view accidentally changes the original view
This occurs when you modify the original view instead of creating a sub-view. Always use Add a view from the view menu before applying filters. If you click Filter on the original view, you alter that view. To undo, click the view name, select View options, and remove the filter, or simply create a new sub-view from scratch.
Sub-View vs Linked Database View for Tag Filtering
| Item | Sub-View | Linked Database View |
|---|---|---|
| Data source | Same database, no copy | Separate block that references the original database |
| Filter scope | Filters apply to the sub-view only | Filters apply to the linked view only |
| Location | Stays inside the original database page | Can be placed on any other page |
| Editing ability | You can edit pages directly | You can edit pages directly |
| Use case | Quick tag-based filtering inside the main database | Showing a filtered tag set on a dashboard or report |
The sub-view is best when you want to stay within the same database page and toggle between different tag filters. The linked database view is better when you want to display a filtered tag set on a completely different page, such as a project dashboard or a weekly report.
You can now create a sub-view filtered by any tag property in your Notion database. Use the view menu to add a new view, apply the filter, and name it for quick access. For more advanced filtering, combine multiple tag conditions using the Add a filter button. A useful next step is to group the sub-view by the same tag property to see pages organized under each tag heading.