When you add a database in Notion, you must choose between an inline database and a full-page database. The inline version sits inside a page alongside other content. The full-page version lives on its own dedicated page. This article explains the structural differences, use cases, and limitations of each format so you can pick the right one for your workflow.
Key Takeaways: Inline vs Full-Page Database Tradeoffs
- Inline database: Embeds the database inside a page, allowing surrounding text and media — best for dashboards and reports.
- Full-page database: Creates a dedicated page for the database, offering more screen space for complex views — best for primary data stores.
- Conversion between types: You can convert an inline database to a full-page database and vice versa at any time without data loss.
Inline Database vs Full-Page Database: Structural Differences
Notion databases store their data in the same way regardless of how you display them. The difference is purely visual and structural. An inline database is a block you insert into a page. A full-page database is itself a page that contains the database as its primary content.
When you create a new database using the /table or /database command, Notion places the database inline by default. You can then convert it to a full-page database using the menu. Alternatively, you can create a full-page database directly from the sidebar by clicking the + New Page button and selecting a database type.
Inline Database Characteristics
An inline database appears as a block within a parent page. You can add text, images, callouts, or other blocks above and below it. This makes inline databases ideal for dashboards, project overviews, or reports where you want to mix data with context. The inline database occupies a fixed width within the page layout. You can resize it or change its view without affecting other content on the page.
Full-Page Database Characteristics
A full-page database exists as its own page in the sidebar. When you open it, the database fills the entire content area. This gives you more room to work with complex views, such as board view with many columns or calendar view with many items. Full-page databases are easier to navigate when you have a large number of records because you are not constrained by the width of a parent page.
How to Choose Between Inline and Full-Page Database
Select the format based on how you intend to use the database in your workspace.
- Use an inline database when the database supports a parent page
If you are building a project dashboard, a weekly report, or a meeting notes page that includes a database as one component, use an inline database. You can add a table of action items inline with meeting notes, for example. - Use a full-page database when the database is the primary destination
If the database is the main resource you or your team will visit — such as a master task list, a client CRM, or a content calendar — create it as a full-page database. It will appear in the sidebar for quick access and have more screen real estate. - Convert an inline database to full-page if you need more space
Open the inline database, click the … menu in the top-right corner of the database block, and select Turn into page. The database becomes a new page with the database as its content. The parent page will show a link to the new page instead of the inline block. - Convert a full-page database to inline to embed it in a report
Open the full-page database, click the … menu in the top-right corner, and select Turn into inline. Choose the destination page. The database moves to that page as an inline block.
Limitations and Things to Avoid
Inline Database View Options Are Limited by Page Width
An inline database cannot expand beyond the width of its parent page. If your parent page is narrow, you may have to scroll horizontally in gallery view or board view. To fix this, widen the parent page by dragging the right edge of the page content area, or convert the database to full-page to use the full window.
Full-Page Databases Cannot Have Surrounding Content
A full-page database page contains only the database. You cannot add text, images, or other blocks on the same page. If you need context around the database, you must create a separate parent page and embed the database as an inline block.
Sidebar Clutter From Too Many Full-Page Databases
Each full-page database adds a new entry to the sidebar. If you create many small databases as full pages, the sidebar becomes crowded. Use inline databases for small, auxiliary databases and reserve full-page databases for primary data stores.
Linked Database Views Behave the Same for Both Types
A linked database view can reference either an inline or a full-page database. The source database type does not affect the behavior of the linked view. However, if you delete the source database, all linked views stop working. Keep this in mind when reorganizing your workspace.
Inline Database vs Full-Page Database: Key Differences Compared
| Feature | Inline Database | Full-Page Database |
|---|---|---|
| Location | Inside a parent page as a block | Its own page in the sidebar |
| Screen space | Limited by parent page width | Full content area |
| Surrounding content | Text, images, and other blocks above and below | None — database is the only content |
| Sidebar entry | No — only the parent page appears | Yes — appears as a page in the sidebar |
| Best for | Dashboards, reports, meeting notes | Master task lists, CRM, content calendars |
| Conversion | Can convert to full-page at any time | Can convert to inline at any time |
Inline and full-page databases store data identically. The choice affects layout and navigation only. Start with inline databases for embedded context and switch to full-page when the database becomes a primary workspace destination. Use the Turn into page and Turn into inline options to reorganize as your needs change. A practical tip: use full-page databases for your three most-used tables and inline databases for everything else to keep your sidebar clean.