Why Notion ‘Database Filter Cannot Be Cleared’ on Linked View

When you try to clear a filter on a linked database view in Notion, the filter options may appear grayed out or the Clear button does nothing. This happens because the filter is inherited from the original database and cannot be removed locally on the linked view alone. In this article, you will learn the specific technical reason for this behavior and the exact steps to work around it.

Why the Filter Cannot Be Cleared on a Linked View

A linked view in Notion is not a copy of a database. It is a reference that displays the same data as the original database but with its own set of view-level settings such as sort order, group, and filter. However, when a filter is applied to the original database, that filter is inherited by every linked view. The linked view’s filter section shows the inherited filter as read-only. You cannot modify or remove it from the linked view itself because the filter is defined at the database level, not at the view level.

This design prevents data inconsistency. If every linked view could override the original filter, the same database could display different subsets of data on different pages, leading to confusion about what the database actually contains. Notion enforces that the original database’s filter remains the master filter. All linked views must respect that master filter. Any additional filters you add on top of the linked view are local and can be cleared, but the inherited filter stays permanent.

What Counts as an Inherited Filter

An inherited filter is any condition applied to the original database that restricts which rows appear. Examples include filtering by a checkbox property where the box must be checked, or filtering by a date property to show only items due this week. When you create a linked view of that database, the linked view automatically shows only the rows that pass the original filter. The linked view’s filter panel displays that condition with a lock icon or a grayed-out remove button.

What You Can Still Control on a Linked View

Even with an inherited filter, you can still add new filters on top of it. For instance, you can add a filter that shows only tasks assigned to a specific person, further narrowing the results. These local filters can be cleared or changed at any time. The inherited filter remains untouched. You can also change the sort order, group by property, and toggle between table, board, calendar, and gallery views on a linked view without affecting the original database.

Steps to Remove or Bypass the Stuck Filter

Because you cannot clear the inherited filter directly, you must choose one of the following workarounds. Each method gives you a linked view that has no inherited filter, allowing you to see all rows from the original database.

Method 1: Create a New Linked View Without Filters

1. Open the original database
   Navigate to the page that contains the original database. This is the database you linked from.
2. Remove the filter from the original database
   Click the Filter button in the top-right corner of the database. Click the X next to each active filter condition to remove them. The original database now shows all rows.
3. Create a new linked view on the target page
   Go to the page where you want the linked view. Type /linked view and select the original database from the list. Notion inserts a fresh linked view that inherits no filters because the original database has none.
4. Delete the old linked view
   Click the view tab name of the old linked view. Click the three-dot menu on the tab and select Delete. Confirm the deletion. You now have a clean linked view showing all rows.

Method 2: Duplicate the Original Database

1. Duplicate the original database
   Open the original database page. Click the three-dot menu in the top-right corner. Select Duplicate. Notion creates a copy of the database with all data but no filters.
2. Rename the duplicate
   Give the duplicate a distinct name so you can identify it later.
3. Create a linked view from the duplicate
   On your target page, type /linked view and select the duplicate database. The linked view inherits no filters because the duplicate has none.
4. Delete the original linked view
   Remove the old linked view tab as described in Method 1. You now have a linked view that shows all rows from the duplicate database.

If Notion Still Shows the Inherited Filter After These Steps

Linked View Still Shows the Old Filter

If you removed the filter from the original database but the linked view still shows it, refresh the page. Press F5 or close and reopen the browser tab. Notion caches view settings locally. A page refresh forces the linked view to re-read the original database’s current filter state.

Linked View Shows No Data After Removing the Filter

If the original database had a filter that hid certain rows, removing that filter makes those rows visible again. If the linked view still shows no data, check that the linked view does not have any local filters active. Click the Filter button on the linked view and remove any local conditions. Also verify that the original database actually contains rows that match no filter at all.

Linked View Tab Won’t Delete

If you cannot delete the old linked view tab, you may be on the last view tab of the database. Notion requires at least one view tab to remain. Add a new view tab first, then delete the old one. Click the + button next to the view tabs to add a new view, then delete the unwanted tab.

Linked View vs Original Database: Filter Behavior Compared

Item	Original Database	Linked View
Can add filters	Yes	Yes
Can remove filters	Yes	Only local filters; inherited filters cannot be removed
Inherits filters from original	No (it is the original)	Yes, automatically
Filter lock icon	None	Grayed-out remove button on inherited conditions
Data source	Direct	Reference to original database

Understanding this difference helps you plan your workspace structure. If you need multiple views of the same data with different permanent filters, apply those filters on the original database and create separate linked views for each subset. If you need a view that shows all rows without any filter, keep the original database unfiltered.

Now you know why the filter cannot be cleared and how to work around it. Use the new linked view method when you need a fresh view quickly. Use the duplicate method when you need a separate copy that you can filter independently. As an advanced tip, you can combine both methods: keep the original database unfiltered, create linked views with local filters for specific pages, and use a separate duplicate only when you need to modify the underlying data set.