Last updated: May 9, 2026 · Based on Notion 3.x desktop, iOS, and web
If you've landed here, Notion is doing one of three things: refusing to open at all, opening but stuck on the loading spinner forever, or loading the sidebar but showing a blank page when you click anything. They look similar but have different causes, and the fix depends on which one you're hitting.
Notion is unusual among productivity apps because it ships three meaningfully different clients: an Electron-based desktop app on Mac and Windows, native iOS and Android apps, and a fully-featured web version at notion.so. They share a backend but their failure modes are surprisingly different. The same workspace might load fine on web and hang on desktop, or load on your phone and refuse to open on your laptop.
Before touching cache, settings, or reinstalling anything, take 10 seconds to check whether Notion itself is having problems.
If any of these show a current incident, your fix is to wait. Most Notion outages clear within 30 to 90 minutes. Repeatedly relaunching the app will not help and may extend your sign-in cooldown if Notion's auth service is the part that's degraded.
If everything looks green and your specific workspace is the only thing failing, keep reading.
The exact wording of the error narrows the cause down significantly. Notion has a small handful of distinctive failure messages, and each maps to a different fix.
You're online (other sites work) but Notion insists you aren't. Notion's connection check is genuinely flaky. It calls a heartbeat endpoint and if the response is delayed or filtered, it concludes you're offline even when you're not.
The most common triggers I see: captive portals on cafe and hotel Wi-Fi (open any HTTPS website first to authenticate), corporate firewalls that block msgr.notion.so (the messaging endpoint Notion uses for live updates), and some VPN setups with strict DNS filtering. Switching to mobile data for 30 seconds will tell you which one it is — if Notion connects on cellular, your network is the problem.
The frustratingly vague error. In practice it means one of: a sync conflict on a block you currently have open, a permission change happened on a parent page while you were viewing a child, or Notion's backend returned a soft error to a specific request.
Reload the page (Cmd+R or Ctrl+R). If it persists on a specific page, that page has a corrupted block somewhere. The reliable fix is to open the page in the web app, click into the area where the error appears, and delete the most recent block you added before the error started showing up.
The sidebar loads, you click a page, and you get a white screen with no error. This almost always means the page contains content that's choking Notion's renderer. The usual culprits: a database with no filters showing 500+ rows, a synced block referencing a deleted source, or an embedded iframe pointing at a service that's now blocked.
Workaround: navigate to the page from its parent rather than directly via URL. If that loads, the parent is fine and the child page itself has the problem. From there, ask someone else with access to open the page and identify what's there — you may need them to delete the offending block since you can't open it yourself.
You're logged in but Notion claims your workspace doesn't exist or you've been removed. Two scenarios produce this. Either an admin actually changed your access (rare but check Slack/email for any team announcements), or Notion's workspace switcher cached the wrong workspace ID after you logged into multiple workspaces in sequence.
Sign out completely (avatar menu › Log out), close Notion, reopen, and sign in again. If you have multiple workspaces, pick the one you need from the explicit list rather than relying on auto-load.
The launcher splash appears with the Notion logo and never progresses. This is a local cache problem 90% of the time. The other 10% is an Electron rendering issue specific to your GPU drivers.
Fix the cache first (instructions further down in "The Hard Reset"). If that fails, launch Notion with hardware acceleration disabled by passing --disable-gpu as a command-line flag, or by toggling the setting in Settings & members › My settings › Hardware acceleration.
This deserves its own section because it's the most common failure mode and the least obvious to fix. Notion's sidebar loads, you can navigate, but every time you click a specific page or database, it spins forever or shows a blank.
Notion fetches and renders pages on demand. A heavy page can take 30+ seconds to render even on a fast connection. The biggest offenders are databases with thousands of rows and no filter, pages with deeply nested toggles (10+ levels), and pages packed with embeds (Figma, Loom, YouTube, Google Maps).
notion.so in Chrome. The web app uses different rendering paths from the Electron desktop client and frequently loads heavy pages the desktop app gives up on. If web works, you've confirmed it's a desktop-specific render issue, not a server problem.
If that confirms a desktop render issue, work down this list:
Notion's three clients have separate failure modes. If you've already tried "restart the app," the next step depends on which client is failing.
The desktop app is Electron, which means it bundles its own Chrome and runs as a heavyweight process. When it hangs, the cause is usually the local SQLite cache, which lives at:
~/Library/Application Support/Notion%APPDATA%\NotionQuit Notion completely (on Mac, Cmd+Q in the app or right-click the dock icon › Quit). Then delete that folder. Relaunch and sign in. None of your content lives in this folder — it's all cache and pulled from the server on next sync. You will need to re-enable any per-device settings.
On Apple Silicon Macs, also confirm you're running the native ARM build, not the Intel build through Rosetta. Activity Monitor › CPU tab › check the "Architecture" column. If it shows "Intel," uninstall and download the universal/Apple Silicon build from notion.so/desktop.
The web app's failure modes are mostly cookie and extension related. Open Notion in an Incognito window first — it eliminates extensions and cookies in one step. If Notion works there, the issue is in your normal browser session.
If you need to clear web Notion's storage without losing other browser data: open notion.so, press F12 to open DevTools, go to Application › Storage, click "Clear site data" while only notion.so is selected. This is surgical and won't affect any other site.
Common extensions that break Notion: aggressive ad blockers (uBlock Origin with custom filters), Honey, Grammarly's heavier modes, and anything that injects scripts into pages.
The iOS app's biggest issue is splash-screen hangs after iOS updates. Apple's WebKit changes can invalidate locally cached schema, leaving the app waiting on a sync handshake that never completes. The fix is annoying but reliable: uninstall the Notion app, reinstall from the App Store, sign in fresh. Your content is all on Notion's servers, so nothing is lost.
iOS Notion has no in-app cache clear. The "Force Stop" trick from Android does not exist on iOS — reinstall is the only option short of waiting for the next app update.
On Android, "Notion not loading" is more often a battery-optimization issue than a real bug. Aggressive battery management on Samsung One UI, Xiaomi MIUI, and Oppo ColorOS will kill Notion's background sync threads, and when you next open the app it has to rebuild state from scratch — which can hang.
Open Settings › Apps › Notion › Battery › set to Unrestricted. Then clear the cache (Settings › Apps › Notion › Storage › Clear cache — not Clear data, that signs you out). Force-stop and reopen.
If you've checked Notion's status, your error doesn't match any specific message above, and the platform-specific fixes haven't worked, the hard reset clears every piece of local state and forces Notion to rebuild from scratch. It works ~95% of the time but will sign you out and reset all per-device preferences.
Q: Is Notion down right now?
A: Check status.notion.so for Notion's official status page. Cross-check at downdetector.com/status/notion-so for community reports. If both show problems, the only fix is to wait — outages typically resolve in 30 to 90 minutes.
Q: Why does Notion say "connect to the internet" when I'm online?
A: Notion's connection check is overly cautious and misfires on networks with captive portals (hotels, cafes), strict corporate firewalls, or DNS-blocking VPNs. Open notion.so in a browser first to clear any captive portal. If you're on a VPN, try briefly without it. Switching to mobile data confirms whether your network is the issue.
Q: Why is Notion stuck on the loading screen on Mac?
A: The most common cause is a corrupted local cache. Quit Notion (Cmd+Q), delete ~/Library/Application Support/Notion, and reopen. No content is lost — it all syncs from the server. If the issue persists on Apple Silicon Macs, confirm you're running the native ARM build via Activity Monitor's Architecture column.
Q: Why does Notion show a blank page after I click on it?
A: A blank page that loads but renders nothing usually means the page contains a heavy database, a broken integration, or content the renderer is choking on. Try opening it on web at notion.so — the web client uses a different render path from desktop. As a last resort, navigate via the parent page rather than direct URL, or have a teammate open it and tell you what's there.
Q: How do I clear Notion's cache?
A: On Mac, delete ~/Library/Application Support/Notion. On Windows, delete %APPDATA%\Notion. On iOS and Android, you must uninstall and reinstall (no in-app cache clear exists). On the web, F12 › Application › Storage › Clear site data. None of these delete content; everything is on Notion's servers.
If everything here has failed and Notion's status page is green, the issue is likely workspace- or account-specific. Contact Notion support directly at notion.so/help — include your workspace URL, the error message verbatim if any, and which client (desktop, web, mobile) you're hitting it on. Plus, Business, and Enterprise customers get faster response times.