When a Notion page crashes only when you scroll to or interact with a particular block, the problem is almost always isolated to that block’s content or its embedded component. Common root causes include a corrupted block property, a broken third-party embed, or an oversized database view that exceeds browser memory limits. This article provides a systematic diagnostic method to identify which block is causing the crash and offers concrete steps to fix or remove it without losing the rest of your page.
Key Takeaways: How to Isolate and Fix a Crash-Causing Block in Notion
- Duplicate the page to a new workspace: Confirms whether the crash is workspace-specific or follows the block content itself.
- Delete blocks one by one from the bottom up in a backup copy: Locates the exact block that triggers the browser tab to freeze or reload.
- Check the block for embedded content or large database views: Embedded iframes, Google Maps, or linked databases with 500+ rows are common crash sources.
- Use the Notion web clipper to save the page as Markdown: Recovers text content if the block cannot be safely removed from the original page.
Why a Single Block Can Crash a Notion Page
Notion renders each block as a separate React component in the browser. When a block contains a malformed property, an infinite loop in a formula, or an embed from a service that has changed its API, the browser may hang, freeze, or reload the tab. The crash happens only when the block enters the viewport because Notion uses lazy loading — it only renders blocks that are visible on screen. Blocks below the fold do not load until you scroll to them.
The most common crash triggers are:
Corrupted Database Row or Formula
If the crash occurs on a block that is a linked database view or a synced block referencing a database row, the cause is often a formula that references a deleted property or a rollup that loops back to itself. Notion’s formula engine does not always catch circular references during editing, but the browser does when it tries to compute the value.
Broken Third-Party Embed
Embed blocks that load an external URL, such as a YouTube video, a Figma file, or a Google Doc, can crash the page if the external service returns an unexpected response or a very large file. Notion’s embed wrapper does not time out gracefully; it waits for the response and may freeze the entire block rendering pipeline.
Oversized Database View
A database view block that displays more than 1,000 rows without pagination can exceed the browser’s memory allocation for a single component. This is especially common on pages that use a full-page database view with all properties expanded.
Steps to Diagnose and Fix the Crash-Causing Block
Follow these steps in order. Do not skip the backup step. Working on the original page without a copy may cause permanent data loss if a block deletion triggers an auto-save of an empty state.
- Create a full backup of the page
Open the page that crashes. In the top-right menu, select the three-dot icon, then choose Duplicate. Notion creates a copy named “Copy of [page name]” in the same location. Do not open the duplicate yet. This backup preserves all blocks and properties in their current state. - Duplicate the page to a different workspace
If you have access to a second Notion workspace, duplicate the page there using the Move To option. If the crash does not occur in the second workspace, the problem is likely a workspace-specific integration or permission that affects the block. If the crash still occurs, the issue is embedded in the block content itself. - Open the duplicate page in a private browser window
Open an incognito or private browsing window and log into Notion. Open the duplicate page. This disables all browser extensions that might interfere with block rendering. If the page does not crash, an extension such as an ad blocker or a grammar checker is the cause. - Scroll to the crash zone and note the block type
Scroll slowly through the duplicate page. When the browser freezes or the tab reloads, stop scrolling. Look at the last block that was visible before the crash. Write down its block type — text, heading, image, embed, database view, or synced block. This narrows the search to one block type. - Delete blocks from the bottom up in the duplicate page
Start at the very last block on the duplicate page. Select it and press the Backspace key. Continue deleting blocks one at a time, moving upward. After each deletion, scroll to the crash zone. When the crash stops, the block you just deleted was the culprit. Note its position and content. - Inspect and remove the culprit block from the original page
Return to the original page. Scroll to the position of the culprit block. If the block is a text block with corrupted formatting, select all text inside it, copy it, delete the block, and paste the text into a new block. If the block is an embed or database view, delete the block entirely and re-create it from scratch.
If Notion Still Crashes After Removing the Block
Page Crashes on Load Without Scrolling
If the page crashes immediately upon opening, the problem is likely the first block or a page-level property. Open the page in a mobile browser or the Notion desktop app. If it loads there, the desktop or mobile client may handle the block differently. From the mobile app, delete the first block or change the page icon and cover image. Sync the change, then reopen the page on desktop.
Crash Only Occurs in the Notion Desktop App
Desktop app crashes are often caused by a corrupted local cache. Close the app completely. On Windows, press Ctrl+Shift+Escape to open Task Manager and end all Notion processes. On Mac, use Command+Q to quit. Restart the app. If the crash persists, clear the app cache by going to Settings & Members > Settings > Advanced > Clear cache and restarting the app.
Database View Shows “Something went wrong” Instead of Crashing
This error indicates a corrupted view configuration rather than a block crash. Open the database as a full page by clicking its name in the breadcrumb. From the full database view, delete the problematic view from the view switcher and create a new view with the same filters and sorts.
Notion Desktop App vs Web App Crash Behavior Compared
| Item | Desktop App | Web App (Browser) |
|---|---|---|
| Crash symptom | App window freezes or closes without warning | Browser tab reloads or shows “Aw, Snap” error |
| Cache clearing method | Settings > Advanced > Clear cache | Browser settings > Clear browsing data > Cached images and files |
| Third-party extension interference | None — extensions do not run in the desktop app | Extensions can block embeds or modify page scripts |
| Ease of diagnosing block location | Harder — no scroll position indicator after crash | Easier — you can see the last visible block before the tab reloads |
| Recovery after crash | Auto-save usually preserves recent changes | Auto-save depends on browser session restore |
The desktop app is more stable for pages with many embeds because it does not run browser extensions. Use the desktop app for the diagnostic deletion steps if the web app crashes too quickly to scroll.
You can now isolate any crash-causing block on a Notion page using the bottom-up deletion method. If the block is an embed or a database view, re-create it from a clean state rather than trying to repair the broken instance. For advanced recovery, use the Notion API to export the page content as Markdown, which strips all block formatting and embeds, leaving only the raw text.