If your database cover images are not appearing on the live site, the issue may be related to how the card preview is configured in Notion.
Using Page Content as the Card Preview
When a database view is set to use Page Content for its card preview, Notion automatically attempts to extract an image from within the page itself. In some cases, this can result in missing or inconsistent thumbnails on the published site.
Common reasons include:
The first image in the page is not immediately available during synchronization.
The page contains multiple images, making it difficult to determine which one should be used as the preview.
Embedded or externally hosted images may not be accessible when generating thumbnails.
Recently updated content may require additional time for changes to propagate.
Because Page Content covers rely on dynamic extraction, they are generally less reliable for published sites.
Recommended Workaround:
Use a dedicated Files & Media property instead of Page Content for database thumbnails and covers.
Then, don't forget to set this as card preview on Layout Section
Benefits of using a Files & Media property:
More consistent rendering on the live site.
Faster and more reliable synchronization.
Explicit control over which image is displayed.
No dependency on the position of images within the page content.
Better compatibility with custom themes and database layouts.
Best Practice:
For important collections such as blogs, portfolios, products, or case studies, store featured images in a dedicated Files & Media property and configure the database view to use that property as the card preview source rather than relying on Page Content.
This approach minimizes rendering issues and provides a more predictable experience for both site owners and visitors.