Let's design Notion's new Basic Tables!

Notion’s new “Basic Tables” bring database-like structure without database-level complexity, letting users build flexible grids that can later be converted into full databases—or simplified back into plain tables. The core tradeoff is straightforward: basic tables remove most database functionality, but they make layout faster and more adaptable for everyday planning, pricing grids, and lightweight tracking.

Creating a Basic Table starts from the block menu: typing “/table” surfaces the Basic Table option. From there, users can add columns by clicking and dragging, and add rows the same way. A key layout control is “Fit table to page width,” which automatically stretches the table to match the available page space after adding columns. Basic tables can also be configured with a header row, a header column, or both.

The feature’s biggest power move is conversion. A Basic Table can be “turned into database,” which transforms placeholder headers into editable properties and automatically assigns property types. For example, once converted, a text column can become a number property, a date property (including inline dates typed with “@” and reformatted via date format options like month/day/year), a select property (rendered as a dropdown), and even a relation property that links entries in one database to another. The transcript demonstrates building two linked “task” entries (e.g., Task A and Task B) and then using relation to connect cells to those records.

Converting back is possible but has constraints. Returning a table to “simple table” requires that the properties match basic-table expectations—specifically, non-text property types (like number, date, select, relation, multi-select) must be converted back to text. Without that cleanup, the “turn into simple table” option doesn’t appear.

Once the mechanics are clear, the transcript shifts to design patterns. Users can create nested header layouts by stacking multiple basic tables under shared column groupings, then aligning them using width controls so the grid looks seamless—an approach used to recreate a pricing-table layout similar to Notion’s own. The transcript also shows how to use KTex for inline formatting (like superscripts for “per month”) and how to style table cells using color commands and curly-brace text styling.

Practical use cases include full-width “inspo” tables such as weekly planners (Monday through Sunday), workout trackers, and classic timetables with time slots down the left. For recurring workflows, the transcript highlights quick cleanup: clearing a specific day by using the column menu to “clear contents,” with the same logic applying to rows. Overall, Basic Tables are positioned as a fast, layout-first alternative for structured content—one that can scale up into databases when relational or typed data becomes necessary.