How to Use Notion Database Footer Calculations Across Filtered Subsets

Notion database footers display sums, averages, counts, and other calculations at the bottom of a table or board view. Many users assume these footers always calculate against the entire database, but they actually respect the current view filter and sort. This behavior is useful when you need to see totals for a specific subset of items, like all tasks in a certain status or all invoices over a given amount. This article explains how to set up filtered views, configure footer calculations, and avoid common pitfalls when working with filtered subsets.

How Database Footers Work with Filters

Every Notion database view has its own filter and sort settings. The footer row at the bottom of a table view calculates only the rows that are currently visible in that view. If you apply a filter that shows only tasks with a Status of In Progress, the footer sum or count reflects only those tasks. This is not a bug — it is the intended behavior for working with subsets of data.

The footer row appears automatically when you add a database to a page. It shows a default calculation for each column based on the column type. For example, a Number column shows Sum by default, a Date column shows Count, and a Text column shows Count. You can change each column’s calculation by clicking the calculation name in the footer and selecting a different function from the dropdown menu.

To calculate across a filtered subset, you must first create a view that contains only the rows you want. This is done by adding a filter to the view. Filters can be based on any property: Status, Date, Select, Person, or even a Formula that evaluates to true or false. The footer then updates automatically when the filter changes.

Steps to Create a Filtered View with Footer Calculations

1. Open your database as a table view
   Navigate to the page containing your database. If the database is not already in table view, click the view name at the top left and select Table from the view type menu.
2. Add a filter to the view
   Click the Filter button near the top right of the view toolbar. A filter row appears. Click Add a filter and choose a property to filter by. For example, select Status and set the condition to Is and In Progress. The table now shows only rows that match that filter.
3. Check the footer row
   Scroll to the bottom of the table. The footer row shows calculations based only on the visible rows. If you see Sum for a Number column, it reflects the sum of the filtered subset.
4. Change the footer calculation type
   Click the calculation name in the footer (for example, Sum). A dropdown menu appears with options: Sum, Average, Median, Min, Max, Count, Count Values, Count Unique Values, Empty, Not Empty, Percent Empty, Percent Not Empty, Range, and Standard Deviation. Select the calculation you need.
5. Duplicate the view for additional subsets
   Click the view name at the top left and select Duplicate view. Rename it to describe the subset, such as “In Progress Totals.” Apply a different filter to this duplicate view. Each view retains its own footer calculations.

Limitations and Things to Avoid

Footer calculations do not aggregate across all views

Each view is independent. If you want a grand total of all subsets combined, you must create a separate view with no filter, or use a Rollup or Formula property to sum across related databases. The footer cannot show a total of multiple filtered views at the same time.

Grouped tables change footer behavior

When you enable grouping in a table view, the footer shows subtotals for each group. The overall footer row at the bottom still calculates against the filtered subset, but the group subtotals are calculated per group. If you need a grand total across groups, the footer at the bottom of the page already provides that.

Board view footers show limited calculations

In Board view, the footer appears at the bottom of each column (status group). It calculates only the cards in that column. To see a total across all columns, switch to Table view or use a linked database with a filter that groups by status.

Formula properties do not show in the footer

The footer only supports Number, Date, and Text-based columns. If you need to calculate a formula property, first convert the formula output to a Number or string. Then add that property to the table and configure its footer calculation.

Table View vs Board View: Footer Calculation Differences

Feature	Table View Footer	Board View Footer
Calculation scope	All visible rows in the filtered view	Only cards in that column group
Available calculations	Sum, Average, Median, Min, Max, Count, Count Values, Count Unique Values, Empty, Not Empty, Percent Empty, Percent Not Empty, Range, Standard Deviation	Count only
Multiple footer rows	One footer at the bottom of the table	One footer per column
Respects view filter	Yes	Yes

Table view is the most flexible for filtered subsets because it exposes all calculation types and shows a single aggregated total. Board view is better for visual pipeline tracking but lacks advanced footer math.

You can now create filtered views that show only the rows you need and configure the footer to calculate sums, averages, or counts for that specific subset. Try duplicating your main view and applying different filters to monitor separate project phases or team assignments. For more advanced analysis, use Rollup properties in a separate database to aggregate filtered values across multiple views.