Notion Database Not Loading? How to Diagnose and Fix It

A Notion database usually fails to load for one of four reasons: a live service incident, a stale local cache in the desktop or mobile app, a network rule blocking Notion, or the database itself hitting a real performance ceiling. Check them in that order, because the fixes are completely different and the wrong one wastes an afternoon.

Rule out the things you cannot fix first

Before touching a view or property, confirm the problem is yours. Notion runs a public status page, and its troubleshooting docs point there first. If a database hangs for every member at once, starting at a specific minute, that is an incident, not a configuration issue.

Next, note which message you are seeing. Notion’s documented list of common error messages includes “Something’s not right,” “There was an issue persisting your edits,” “Cannot save changes,” and “Storage operation did not complete.” These are not interchangeable: a persistence error means writes are failing, which is connectivity or permissions. A blank view with no error is usually rendering or sync. Record the exact string before changing anything.

Symptom, cause, and the fix that matches it

The limits Notion publishes, and the one it does not

Notion documents several hard ceilings, and hitting one produces a failure that looks like a loading bug but is not. Each database holds up to 250,000 rows; at or over that, requests to add rows return an error. Each database allows up to 500 properties, beyond which new ones will not be created. Each page’s property data is capped at 2.5MB, and the database schema — every property and select option — at 1.5MB.

These explain silent failures. Notion states that once the limits are hit, new changes will not be saved — so “our database stopped updating” is often a ceiling, not an outage.

Here is what Notion does not publish: any number at which a database starts feeling slow. The official database performance documentation says only that “if your database has a ton of pages, it might be slower to load.” There is no stated row count, no property count, and no benchmark. Anyone quoting you a specific threshold for when Notion databases become sluggish is inventing it. In practice you have to measure your own workspace, because the ceiling depends on property types, view configuration, and how much else is on the page.

One useful detail from the same documentation: the 2.5MB per-page limit explicitly excludes formulas and rollups. Computed properties do not consume your storage budget. They cost you time instead, on every single load.

Reference chains are the slowdown teams build for themselves

Notion names three things that slow a database down: the number of pages, the number of visible properties, and complex sorts or filters on title, text, formula, or rollup properties. The third is underestimated.

A sort or filter on a select, status, number, or date property is cheap — Notion explicitly recommends filtering on these simple types. A sort on a formula that reads a rollup that aggregates a relation is expensive, because the value has to be computed before it can be ordered. Do that on a large table and the view cannot render until the whole calculation finishes. This is why a database can look fine at 500 rows and become unusable at 5,000 without anything else changing.

Notion blocks rolling up a rollup outright, because it could create unintended loops — so pure rollup nesting is bounded at one level. The expensive chains form differently, through formulas referencing rollups that other formulas then reference. Notion’s performance docs warn about exactly this. Our guide to Notion formulas 2.0 covers collapsing them, and the walkthrough of relations and rollups explains where aggregation happens.

Fixes in order of payoff: hide properties the view does not need, move sorts and filters onto simple property types, and cut the rows a view must process. Notion suggests filtering on Created time to exclude old pages when a database is too large to prune.

Why your dashboard is the slowest page you own

If one page hangs while everything else is responsive, count the databases on it. Notion’s guidance is blunt: in a large workspace, avoid having lots of inline databases on high-traffic pages, because the more databases viewed simultaneously, the more stress on your setup.

The mechanism points to a non-obvious fix. Each inline database listens for updates independently, so ten of them means ten live subscriptions competing on one page load. Notion’s alternative: house each database on its own page, then build one linked database carrying multiple views that point at different sources. Only one view is open at a time, so only one database is listening — the same dashboard at a fraction of the load.

This is the highest-value change most teams can make. If you are rebuilding a dashboard around views rather than stacked databases, our guide to charts and database views covers the view types worth using.

A structural note for 2026: every Notion database is made up of at least one data source, and can hold several. If a view is empty or an option is missing, check Manage data sources. Notion documents one such case — if your source sits under Linked rather than Sources, you cannot add a form to it and must use the original database. Missing options are often a data-source problem masquerading as a bug. Our overview of how Notion databases are structured covers the distinction.

Resetting the client properly

If the database loads on another device or in incognito, the problem is local. Notion prescribes an escalation rather than one fix. Resetting logs you out, so have credentials ready.

On desktop:

1. Select View → Force reload from your device’s menu bar. On Windows you may need to press alt to make the menu bar appear.
2. If that fails, select Help → Troubleshooting → Reset & Erase All Local Data.
3. If it still fails, quit Notion completely and confirm no Notion processes remain in Task Manager, then delete the app data folder — /Users/<USERNAME>/Library/Application Support on Mac, or C:\Users\<USERNAME>\AppData\Roaming on Windows.
4. Reinstall the desktop app from Notion’s download page.

In Chrome or Edge:

1. Open Developer Tools with ctrl + shift + i on Windows, or cmd + option + i on Mac.
2. With Developer Tools open, right-click the browser refresh button and select Empty Cache and Hard Refresh.
3. In Developer Tools, go to Application and expand Cookies in the left sidebar.
4. Right-click the Notion entry and select Clear.

On mobile, there is no cache-clearing menu. Notion’s instruction is to delete the app and reinstall it. Your content is in the cloud, so nothing is lost.

If it only breaks on mobile, check offline mode before anything else

This is the least understood cause of a half-loaded database, and it is not a bug.

Per Notion’s offline documentation, offline access works in the desktop and mobile apps only — not in a web browser. Members on every plan can mark a page Available offline from the ••• menu. On Plus, Business, and Enterprise, recently visited and favorited pages download automatically.

The detail that explains the symptom: when you download a database, or a page containing one, only the first 50 rows of the first view come with it. So a mobile device on a weak connection can show you a database that renders correctly but contains a fraction of your records. Nothing is broken. You are looking at a cached slice.

So make the first view of any database the one you need offline, since that is what gets cached, and remember subpages of a downloaded page do not download automatically. Audit what is cached under Settings → Offline, where you can also toggle Automatic downloads off.

There is a genuine data risk here that Notion states plainly and most write-ups skip. Text edits made offline are merged automatically where possible, but non-text edits are riskier: if two people update the same select property while offline, only one of those updates can ultimately be saved. For a shared status field on a team database, that is a silent overwrite. Sync before editing when you can.

When the network is the problem

Corporate networks break Notion in ways that look like application faults. Notion’s remedy is to allowlist the URL *.notion.com across firewalls, secure web gateways, DNS filtering, proxy allow and deny lists, and any security tooling that blocks newly seen domains.

The clearest tell is images. If a database renders but images show “Go online to view this image” while you are demonstrably online, Notion identifies a VPN as the most common cause, especially when several teammates hit it at once. Firewalls, proxies, DNS filters, ad blockers, and iCloud Private Relay do the same. Turn the VPN off and reload before escalating to IT.

Two platform constraints also generate tickets: ChromeOS devices are unsupported and should use a browser, and iOS 15 or earlier is unsupported. On a personal network, Notion suggests switching DNS to 1.1.1.1 or 8.8.8.8.

Separately, if a database looks fine but its automations have stopped firing, that is a different diagnostic path — see our breakdown of why Notion automations stop working. Note the plan gating: database automations require Plus, and Notion’s own pricing comparison lists the automations row for both Business and Enterprise as “Same as plus.” Upgrading past Plus buys you nothing on that specific feature.

Where Notion’s own documentation leaves you guessing

Two gaps are worth naming, because guessing at them causes real damage.

First, the two-way relation cap. Notion states that once you have referenced the same page from Database A 10,000 times in Database B, further references will not reflect back in Database A. The published sentence is literally incomplete — it reads “the next time you try to reference the in Database B” — and never says whether you get an error or a silent failure. Notion describes other limits as returning an error and this one only as not reflecting, which reads like silent failure, but it does not confirm that. Test large many-to-many relations rather than assuming.

Second, there is no published performance threshold. Notion names the hard limits and names the slow patterns, but never connects the two with a number — defensible, given how differently workspaces are shaped. It does mean benchmarking your own build: duplicate a heavy view, strip the computed sorts, compare.

Frequently asked questions

How many rows can a Notion database hold before it stops working?

Notion caps each database at 250,000 rows. You will see a warning as you approach it, and once at or over the limit you cannot add rows — requests return an error. Performance typically degrades well before that ceiling, but Notion publishes no specific number for when slowdown begins.

Why does my database load on desktop but not on my phone?

Most often this is offline caching rather than a fault. Downloading a database only stores the first 50 rows of its first view, so a phone on a poor connection shows a partial table. Check Settings → Offline to see what is cached, and reconnect to load the full data source.

Does clearing the Notion cache delete my content?

No. Your pages, databases, and files are stored in Notion’s cloud, so clearing a local cache or reinstalling the app removes only the local copy. Resetting does sign you out of active accounts, so have your login details available before you start. Unsynced offline edits are the one genuine risk.

Will upgrading my plan make my databases load faster?

No. Notion’s paid tiers gate features such as unlimited charts, granular database permissions, and longer page history — 7 days on Free, 30 on Plus, 90 on Business, unlimited on Enterprise. None of them raise the 250,000-row or 500-property limits, and none change how fast a view renders.

Why do my rollup columns stay empty when the rest of the table loads?

Rollups are computed at load time from related pages, so they populate after the base rows render. Persistent blanks usually mean a broken relation, a rollup pointing at a deleted property, or a chain deep enough to time out. Also note that rollups can only be sorted when they output a numeric value.

Sponsored