How to create Tables in Notion | Step-by-Step Full Guide (2024)

TL;DR

Notion table views are database-backed: each row is a page with properties, enabling database features beyond simple grids.

Briefing Cornell Notes

Briefing

Notion tables work like database views, where every row is a page with properties—so the real power comes from bulk editing, calculated summaries, grouping, filtering, and sorting rather than spreadsheet-style cell formulas. That distinction matters because it determines what you can automate and how you should structure data for tasks like tracking checklists, managing tags, or producing quick rollups (sum, average, median, min/max) across many entries.

Creating tables in Notion starts with three main paths. An empty page can generate a new table database via “Table” (creating a fresh database from scratch). Alternatively, typing “/table view” creates an inline table view database that can live within a page alongside other content. If the data already exists elsewhere, “/linked view of database” adds a linked table view so edits in the view reflect in the original database. Notion databases also support multiple layouts: switching from board to table view is done through layout options in the database menu.

Once a table view database is in place, each row functions as a page that can hold text and additional properties. Layout settings control how the table looks and behaves—vertical lines, column wrapping, and how pages open (side panel, centered panel, or full page), plus whether a page icon is shown. Properties are added through the “+” controls (including number, checkbox, and other property types) or from inside an entry via “+ add a property.” Properties can be hidden from the main table view without deleting them, and visibility can be tuned further so empty properties can be hidden or always shown.

For readability, Notion supports freezing columns so the left-side page name stays visible as more properties are added. Adding rows is flexible: use “+ new,” create from within an open cell, or press Shift+Enter to add a new row quickly. Row-level controls live behind the six-dot handle on the left, offering actions like duplicate, delete, open in a new tab/window, copy link, rename, edit property, move to, and favorite.

Bulk editing is a standout feature. By selecting multiple rows at once, users can apply changes across many entries—sorting, deleting, copying links, or editing a shared property value (for example, renaming multiple rows to “page one”). Columns and rows can be rearranged by dragging to adjust widths or reorder items when no sort is active.

Calculated columns provide spreadsheet-like rollups, but they operate at the column level. Using the calculate option, users can compute sum, average, median, min, max, range, percent empty/not empty, count values, and unique values. With checkbox properties, Notion can calculate percent checked—useful for habit trackers and daily task lists.

Tables also support grouping (turning on tag grouping to separate items into “tag one” and “tag two” groups), plus filtering and sorting. Filters can show only checked or unchecked items, enabling completed vs. incomplete views. Sorting can be applied by name, checkbox, number, tags, or date (ascending/descending). A search bar inside the table helps locate specific entries instantly.

Finally, Notion’s database tables differ from simple tables. “/table” creates a free-form table with manual formatting options like colored rows and header styling, which is convenient for presenting structured information but lacks the database-style property system. Notion can do row-wide calculations between number properties, yet it doesn’t support the full spreadsheet model of placing formulas into individual cells, so spreadsheet functionality remains limited by design.

Cornell Notes

Notion table views are database-backed: each row is a page with properties, and the table’s value comes from database features like bulk editing, grouping, filtering, sorting, search, and column-level calculations. Users can create tables from scratch (“Table”), embed them inline (“/table view”), or reuse existing data via linked views (“/linked view of database”). Table settings control layout (vertical lines, wrapping, page opening style, icons), while property controls let users add types like number and checkbox, hide properties from the main view, and freeze columns for readability. Calculations support rollups such as sum, average, median, min/max, percent empty, and percent checked for checkbox tracking. Notion’s approach differs from spreadsheets: formulas are limited compared with true cell-by-cell spreadsheet logic, and simple “/table” is a free-form alternative to database tables.

What’s the practical difference between a Notion table database and a simple Notion table created with “/table”?

A table view database treats each row as a page with properties, enabling database behaviors like bulk edit, grouping by tags, filtering/sorting, and column-level calculations (sum, average, percent checked, etc.). A simple table created with “/table” is more free-form: it’s mainly a structured grid for displaying information, with formatting options like turning on a header row and applying row colors, rather than a property-driven database system.

How can someone create a table in Notion depending on whether data already exists?

If starting from an empty page, use “Table” to create a new table database from scratch. To place a table inside a page alongside other content, type “/table view” and choose “Table view,” then “+ new table.” If the data already exists as a Notion database, use “/linked view of database,” select the existing database, and add a linked view—changes made in the linked view reflect in the main database.

Which table settings and property controls affect how the table looks and stays usable as it grows?

Layout settings (via the three-dots menu) include toggling vertical lines, wrapping columns, choosing how pages open (side panel, center panel, full page), and showing or hiding page icons. For properties, users can add new property types via “+” or from inside an entry, hide properties from the main view without removing them, and set visibility rules like hiding empty properties. Freezing columns keeps the left-side page name visible when many properties are present.

What are the main ways Notion tables support editing at scale?

Row-level actions are available through the six-dot handle on each row (duplicate, delete, open in new tab/window, copy link, rename, edit property, move to, add to favorites). For scale, multiple rows can be selected at once, enabling bulk operations like deleting many rows, copying links for all selected rows, and editing a property across all selected entries (e.g., renaming multiple rows to “page one”).

How do calculations work in Notion tables, and what’s the limitation compared with spreadsheets?

Calculations are column-level rollups accessed through the calculate option at the bottom of the table view. Options include sum, average, median, min, max, range, percent empty/not empty, count values, and unique values. With checkbox properties, Notion can compute percent checked. The limitation is that Notion doesn’t support full spreadsheet-style cell formulas in arbitrary cells; it can calculate between number properties row-wide, but true cell-by-cell spreadsheet logic is not available.

How do grouping, filtering, and sorting work together for task-style workflows?

Grouping can be enabled for tags so items appear under separate tag groups (e.g., tag one vs. tag two), with options to hide empty groups and reorder visible groups. Filtering can restrict the view to only checked or only unchecked items using a checkbox property—useful for completed vs. incomplete tabs. Sorting can then order results by name, checkbox, number, tags, or date (ascending/descending), and the table’s search helps find specific entries quickly.

Review Questions

When would a linked view of a database be preferable to creating a new table from scratch in Notion?
What calculation options are available for checkbox properties, and how could that support a habit tracker?
Why might someone choose “/table” instead of a table view database when building a Notion table?

Key Points

1
Notion table views are database-backed: each row is a page with properties, enabling database features beyond simple grids.
2
Create tables via “Table” (new database), “/table view” (inline table view database), or “/linked view of database” (reuse and sync with an existing database).
3
Use layout settings to control vertical lines, column wrapping, page-opening style, and page icons for better readability.
4
Manage properties by adding new property types, hiding properties from the main view, and using visibility rules for empty fields; freeze columns to keep page names visible.
5
Bulk editing is powerful: select multiple rows and apply actions like sorting, deleting, copying links, and editing properties across all selected entries.
6
Column calculations support rollups like sum, average, median, min/max, percent empty, and percent checked for checkbox tracking, but Notion doesn’t offer full spreadsheet cell-by-cell formula flexibility.
7
Group, filter, and sort tables using tags, checkbox states, and date ordering to build practical workflows like completed vs. incomplete lists.

Highlights

Each row in a Notion table view behaves like its own page, letting properties store structured data rather than just text in cells.

Notion can compute percent checked from a checkbox property—ideal for habit trackers and daily task lists.

Column-level “calculate” rollups (sum, average, median, min/max, unique values) provide spreadsheet-like summaries without full spreadsheet formula placement.

Linked views keep table views synchronized with the original database, so edits propagate automatically.

Simple “/table” is a free-form grid with formatting options, while “table view” is a property-driven database experience.

Topics

Creating Table Databases
Inline Table Views
Linked Database Views
Table Properties
Column Calculations
Grouping Filtering Sorting
Simple Table vs Table View