Learn why your Notion databases may not render properly on Super and how to fix common issues with unsupported properties, view types, and page settings to ensure your site displays data correctly.
Why Is My Notion Database Not Rendering Properly?
If your Notion database looks broken, incomplete, or different on your Super site, it’s usually caused by unsupported properties, view limitations, or page visibility settings. This guide explains the most common causes and how to fix them in both Notion and Super.
Common causes and fixes
1. Unsupported Notion properties
Cause
Some Notion database properties are not fully supported in Super or are rendered differently on the web.
Common examples:
- Formula properties
- Buttons or automations
Fix
- Replace formula values with:
- Manual number or text properties
- Synced database fields
- Static text blocks for display purposes
- For progress trackers or computed values, pre-calculate the result and store it in a Number or Select property.
- Hide unsupported properties from the public database view.
2. Database view type is not supported
Cause
Certain database views don’t render properly or at all.
Examples:
- Timeline view
- Notion Charts
- Views with heavy filtering or sorting logic
Fix
- Switch to supported views:
- Table
- Gallery
- List
- Create a separate “Website View” specifically optimized for Super.
- Avoid advanced grouping, nested filters, or formulas in public views.
- For Notion charts:
- Create your chart in Notion or another tool or create it directly on another page in Notion.
- Take a screenshot or export the chart as an image.
- In Notion, upload the image to your page where you want it to appear.
3. Database is not shared publicly in Notion
Cause
If the database or its parent page is not public, Super cannot render it correctly.
Fix
- Open the database in Notion
- Click Share
- Enable Share to web
- Ensure Allow duplicate as template is enabled if needed
- Confirm the database is not inside a private or locked page
4. Hidden properties causing layout issues
Cause
Properties that are hidden or reordered inconsistently can cause the database to look broken on the site.
Fix
- Open the database view settings
- Reorder properties logically
- Hide unused or unsupported properties
- Use consistent property visibility across all public views
5. Mobile layout limitations
Cause
Notion databases are not fully responsive by default, especially tables with many columns.
Fix
- Reduce the number of visible columns
- Use Gallery or List views for mobile users
- Avoid wide tables with long text fields
- Test your database on mobile before publishing
6. CSS customizations interfering with rendering (Super only)
Cause
Custom CSS added in Super may unintentionally override Notion database styles.
Common issues:
display: noneoverflow: hidden- Fixed heights or widths
- Aggressive flex or grid rules
Fix
- Temporarily disable custom CSS in Super
- Check for styles targeting:
.notion-database.notion-collection.notion-table- Reintroduce CSS changes gradually and test after each update
7. Cached content or site not republished
Cause
Changes made in Notion may not immediately appear on your Super site.
Fix
- Refresh your site in Super Dashboard Preview
- Clear your browser cache
- Test in an incognito window
- Allow a few minutes for updates to propagate
Best practices
- Create a dedicated Website View for every database
- Avoid formulas and rollups for public-facing content
- Keep layouts simple and mobile-friendly
- Test databases directly in Notion’s public view before publishing
- Republish your Super site after major database changes
When to contact support
If your database:
- Appears completely blank
- Displays incorrect data after republishing
- Breaks only on Super but not in Notion
Reach out to Super support with:
- Your site URL
- The database page link
- Screenshots of the issue