When you export an entire Notion workspace, you may notice that some content is missing from the output files. Certain block types, such as linked databases, embedded content, and specific media files, are not included in the export. This happens because Notion’s export feature processes each block independently and cannot resolve dynamic or external references during the export. This article explains which block types are excluded, why they are omitted, and how to work around the limitation to capture your data.
Key Takeaways: Notion Workspace Export Block Type Restrictions
- Settings & Members > Settings > Export entire workspace: Initiates a full workspace export but skips linked databases, embeds, and synced blocks.
- Linked database views and relations: These blocks are not exported because they depend on live database connections that cannot be serialized.
- Embedded content and third-party integrations: External URLs, videos, and widgets are omitted because the export does not fetch remote resources.
Why Notion Excludes Certain Block Types from Workspace Exports
Notion’s workspace export generates static files such as Markdown, HTML, or CSV. The export process walks through every page and block in the workspace, but it cannot preserve dynamic or externally dependent content. The root cause is that Notion stores references to data rather than the data itself for certain block types. For example, a linked database view references a source database by its ID. During export, Notion does not resolve that reference into the actual database rows. Instead, it skips the block entirely or replaces it with a placeholder.
Another reason is that some blocks rely on live network requests. Embedded content, such as a YouTube video or a Google Calendar widget, requires fetching data from an external server. The export process does not make HTTP requests to third-party services, so these blocks are omitted. Similarly, synced blocks that mirror content from another page are not exported because the sync relationship is a live connection that cannot be replicated in a static file.
Block Types That Are Excluded
The following block types are not included in a workspace export:
- Linked database views: Any database view that references another database (inline or full-page) is omitted.
- Relations and rollups: Relation properties and rollup columns are not exported because they depend on database connections.
- Embed blocks: Content from embed URLs, including YouTube, Twitter, and Google Maps, is skipped.
- Synced blocks: Blocks that are synced from another page are not included in the export.
- Third-party integration blocks: Blocks created by integrations like Figma, Jira, or GitHub are omitted.
- Code blocks with live preview: Some code blocks that show a live preview are exported as plain text, not the rendered output.
Steps to Identify Missing Block Types in an Export
Before you export, you can check which blocks will be missing by reviewing your workspace structure. The steps below help you locate common excluded blocks and decide whether to replace them with exportable alternatives.
Check for Linked Databases
- Open a page that uses a linked database
Navigate to any page that contains an inline linked database view or a full-page linked database. Look for the database name in the top-left corner of the view. - Identify the source database
Click the database name to open the source database. If the source database is in the same workspace, you can export it separately. If it is a cross-workspace link, it will not export. - Replace with a duplicate database
Create a duplicate of the source database by right-clicking the database title and selecting Duplicate. Replace the linked view with the duplicated database to ensure the data exports.
Review Embedded Content
- Search for embed blocks in your workspace
Use the search bar at the top of the Notion window and type /embed to find pages that contain embed blocks. Notion does not have a global search for block types, so you must manually review pages. - Replace embeds with static links
For each embed block, copy the URL and paste it as a regular link in the page. Exporting a page with links preserves the URLs, though it does not download the content. - Download external content manually
If you need the actual file from an embed, download it from the source website and upload it as a file block in Notion. File blocks are included in exports.
Handle Synced Blocks
- Locate synced blocks in your workspace
Synced blocks show a small sync icon in the block handle area. Hover over any block and look for the icon next to the drag handle. - Unsync the block
Click the sync icon and select Unsync from the menu. This converts the block into a regular copy. The copy will be included in the export. - Repeat for each synced instance
If the same synced block appears on multiple pages, you must unsync each instance individually. Note that unsyncing breaks the link to the original block.
If Notion Still Omits Blocks After Your Changes
Linked Database View Shows Empty After Export
If you exported a page that contains a linked database view and the output file shows an empty placeholder, the original database was not included in the export. To fix this, open the source database and export it separately using the database export option. Then manually combine the files after export.
Embedded Video or Map Does Not Appear in HTML Export
HTML exports do not include embedded videos or maps because Notion does not fetch the remote content. Replace the embed with a direct link to the URL. For videos, consider downloading the video file and uploading it as a file block before exporting.
Rollup Property Values Are Missing in CSV Export
Rollup properties depend on relation properties. When you export a database as CSV, rollup columns are empty because the relation is not resolved. Create a formula property that replicates the rollup value using the same logic. Formula properties export correctly in CSV files.
Notion Export Formats and Block Support Compared
| Block Type | Markdown Export | HTML Export | CSV Export |
|---|---|---|---|
| Text and headings | Included | Included | Not applicable |
| Images (uploaded) | Included as links | Included as links | Not applicable |
| File blocks | Included as links | Included as links | Not applicable |
| Simple tables | Included | Included | Not applicable |
| Database views (full-page) | Included | Included | Included |
| Linked database views | Omitted | Omitted | Omitted |
| Relation properties | Omitted | Omitted | Omitted |
| Rollup properties | Omitted | Omitted | Omitted |
| Embed blocks | Omitted | Omitted | Not applicable |
| Synced blocks | Omitted | Omitted | Not applicable |
Now you know exactly which block types are excluded from Notion workspace exports and why. To capture all your data, replace linked databases with duplicates, convert embeds to file blocks, and unsync synced blocks before exporting. For advanced scenarios, consider using Notion’s API to programmatically export content that the built-in export cannot handle.