Export to pdf at dashboard level

[sunilreddy0720]

I have a dashboard with around 3-4 tables and some line charts and databoxes.
when i do export to .pdf after few seconds my chrome browser results in page unresponsive.

when i click wait then page gets hanged.

[dosubot[bot]]

This is a known issue in Superset when exporting dashboards with multiple or large tables—browser unresponsiveness often happens because the PDF export process is resource-intensive, especially with complex dashboards. The frontend export uses the dom-to-pdf library, which can consume a lot of memory, particularly if the dashboard has many rows or the html2canvas scale is set high (default is 2) [source].

To improve your chances of a successful export:

• Limit the number of rows displayed in each table before exporting [source].
• Try exporting a smaller or simpler dashboard to see if the issue persists.
• If you’re using Superset 5.0.0 or later, make sure all charts generate thumbnails, and consider setting WEBDRIVER_TYPE to "chromium" and reducing the WEBDRIVER_WINDOW size and pixel_density in your config for better performance [source].
• If your dashboard includes images from external domains, check your Content Security Policy (CSP) settings—add those domains to the connect-src directive to avoid export failures [source].

Recent Superset versions have improved PDF export with multi-page support and full table data export, but if data-based generation fails, it falls back to screenshot-based export, which can still be heavy for the browser [source].

If you can share your Superset version and export method (built-in export vs. browser print), I can suggest more targeted steps.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[sunilreddy0720]

I'm using superset vesion 4.1.1 and using built-in export

[dosubot[bot]]

This is a known limitation in Superset 4.1.1: exporting dashboards with multiple or large tables to PDF using the built-in export can cause the browser to become unresponsive or hang. The export relies on the dom-to-pdf library with high-fidelity settings (like html2canvas scale: 2), which is very resource-intensive for complex dashboards and large tables. The most effective workaround is to limit the number of rows displayed in each table before exporting—smaller datasets are much less likely to trigger browser hangs or JavaScript errors during export. There isn’t a permanent fix for this in 4.1.1, and configuration options for PDF export are limited in this version. Improvements like configurable PDF compression and better handling of large exports are only available in newer releases.
Reference
Reference (code)

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}