Why Notion is slow (and what to do about it)

If your Notion workspace has been getting slower, you're not imagining it. A 2024 survey found that 65% of Notion users managing large datasets experienced noticeable slowdowns in database interactions. The problem is structural: Notion's flexible block-based architecture, the thing that makes it so adaptable, becomes a performance liability as workspaces grow.

The slowdown typically begins when databases exceed a few thousand rows, when pages contain multiple inline databases, or when relations and rollups create computational chains that Notion has to resolve every time a page loads. One operations manager reported their CRM going from 15-second load times to 2 seconds after splitting a 3,500-page database into an active set of 300 and an archive of 3,200. That improvement is real but the fact that it requires manual restructuring to achieve basic usability tells you something about the underlying architecture.

What causes the lag

Large databases. Notion databases start showing performance issues around 10,000 rows. The more properties (columns) each entry has, the earlier the slowdown begins. A database with 5,000 rows and 30 properties can feel sluggish where the same database with 10 properties would be fine.

Relations and rollups. These are the most computationally expensive features in Notion. Every time you open a page, Notion follows the relation links, calculates the rollup formulas, and displays the results. A database with 50 properties and 500 pages, many of which involve relations and rollups, creates a computation chain that can increase load times dramatically. Circular relations (Database A relates to Database B which relates back to A) can increase load times by 300% or more.

Inline databases on high-traffic pages. Dashboard pages with multiple inline databases are particularly slow because each database loads simultaneously when the page opens. Notion's own help documentation recommends against this pattern, suggesting linked views that load one database at a time instead.

Gallery and timeline views. Not all database views are equal in terms of performance. Table view is the fastest. Gallery view is the slowest because it loads all images. Timeline and board views fall somewhere in between. Using gallery view on a large database compounds the performance issue.

Deep page nesting. Pages nested several levels deep take longer to load because Notion has to traverse the page tree. Flatter workspace structures load faster.

What you can do

These workarounds help, though they all involve working around the architecture rather than the architecture working for you.

Archive aggressively. Move completed or inactive items to a separate archive database. Keep the active database small. Use linked views if you occasionally need to reference archived items.

Reduce relations and rollups. If a relation or rollup isn't actively used, remove it. Each one adds computational overhead even when you're not looking at the column. Avoid circular relations entirely.

Use linked views instead of inline databases. Instead of embedding three databases on a dashboard page, create one linked view that can switch between different source databases. Only one database loads at a time.

Prefer table view. If performance matters more than visual presentation, table views load significantly faster than gallery, board, or timeline views.

Flatten your page structure. Reduce nesting depth where possible. A page three levels deep loads faster than one seven levels deep.

Split large databases. Instead of one master database for everything, create smaller purpose-driven databases connected through relations. Each individual database loads faster, even if the total data is the same.

When workarounds stop being enough

There's a point where the workarounds become their own overhead. You're spending time restructuring databases, managing archives, optimising views, and constraining how you use the tool rather than using the tool to do your work. The meta-productivity problem, where maintaining the system consumes more time than the system saves, becomes acute when the system also requires performance optimisation on top of structural maintenance.

If you've reached this point, the question isn't how to make Notion faster. It's whether a tool that requires this much accommodation is the right architecture for your knowledge.

Fabric is built on a different architecture that handles large libraries natively. Semantic search works across thousands of documents without performance degradation. Smart organisation replaces the manual database structuring that Notion requires. And importing from Notion means you don't lose what you've built.

The choice depends on where you are. If your Notion workspace is small and the workarounds above are sufficient, they're worth trying. If you're spending meaningful time optimising Notion's performance rather than doing your actual work, the architecture itself may be the problem.

Frequently asked questions

Will Notion fix the performance issues? Notion has been making incremental improvements to database performance, and their recent updates have helped with some scenarios. But the fundamental architecture (every page is a tree of blocks, every database view requires computation of all properties) creates inherent scaling limits that incremental improvements can only partially address.

How much data can Notion handle before it slows down? The threshold depends on the complexity of your databases (number of properties, relations, rollups, formulas) as well as the row count. Simple databases with few properties can handle tens of thousands of rows. Complex databases with many relations and rollups start showing issues around a few thousand rows.

Is the performance issue specific to the desktop app? The web app and desktop app have similar performance characteristics since both rely on the same cloud-based rendering. The mobile app is generally slower due to device constraints.

Related reading: Your Notion workspace is a second job, Why people are leaving Notion, Why Notion search doesn't work. Related pages: Fabric vs Notion, Notion connection, Best Notion alternative.