Forum Discussion
PDF Export Missing HTML Table Content
I'm facing a limitation when exporting a Power BI Service report page to PDF.
The page contains a table built using the HTML Content visual. Filters are applied to the table, which dynamically change the number of rows displayed. As a result, the table can become larger or smaller depending on the selected filters.
When the content exceeds the available space, the table displays a vertical scroll bar. The problem is that, when exporting the report page to PDF, only the visible portion of the table is included in the export. Any content located within the scroll area is not captured in the PDF.
Simply increasing the report page size is not a viable solution because the amount of data varies significantly based on the selected filters. In some cases, the page would become excessively large, while in others it would contain a lot of unused blank space.
Is there a way to automatically split the content across multiple PDF pages during export, eliminating the need for scrolling and ensuring that all table data is included in the exported document?
What would be the best approach for handling this scenario?
Hi Dynizju,
Unfortunately, I don't believe there is a native way for Power BI report exports to automatically split a scrollable visual across multiple PDF pages. The same has been answered in another post - PDF export do not show full table
What you're seeing is expected behaviour. When exporting a standard Power BI report to PDF, only the visible portion of a scrollable visual is captured. Any rows that require scrolling are not included in the PDF export.
Given your scenario, simply increasing the page height isn't ideal because the number of rows varies based on the selected filters. You would either end up with truncated data or large amounts of unused whitespace.
For requirements where the full table must be exported regardless of the number of rows, the recommended approach is typically a Paginated Report. Paginated Reports are designed for exactly this use case and will automatically flow table data across multiple pages when exported to PDF, ensuring all rows are included without requiring scrollbars.
If moving to Paginated Reports isn't an option, the alternatives are generally limited to:
- Exporting the underlying data to Excel/CSV instead of PDF.
- Redesigning the report to reduce or eliminate scrolling.
- Using a dedicated printable report page specifically for export purposes.
So in short, if the requirement is"export all rows to PDF and automatically span multiple pages", I would strongly recommend a Paginated Report. Standard Power BI report exports don't currently support automatic pagination of scrollable visuals during PDF export.
If my answer helped you solve the problem, please consider accepting it as the solution and help other members to use the same solution in same/similar situations.
5 Replies
Hi Dynizju,
Unfortunately, I don't believe there is a native way for Power BI report exports to automatically split a scrollable visual across multiple PDF pages. The same has been answered in another post - PDF export do not show full table
What you're seeing is expected behaviour. When exporting a standard Power BI report to PDF, only the visible portion of a scrollable visual is captured. Any rows that require scrolling are not included in the PDF export.
Given your scenario, simply increasing the page height isn't ideal because the number of rows varies based on the selected filters. You would either end up with truncated data or large amounts of unused whitespace.
For requirements where the full table must be exported regardless of the number of rows, the recommended approach is typically a Paginated Report. Paginated Reports are designed for exactly this use case and will automatically flow table data across multiple pages when exported to PDF, ensuring all rows are included without requiring scrollbars.
If moving to Paginated Reports isn't an option, the alternatives are generally limited to:
- Exporting the underlying data to Excel/CSV instead of PDF.
- Redesigning the report to reduce or eliminate scrolling.
- Using a dedicated printable report page specifically for export purposes.
So in short, if the requirement is"export all rows to PDF and automatically span multiple pages", I would strongly recommend a Paginated Report. Standard Power BI report exports don't currently support automatic pagination of scrollable visuals during PDF export.
If my answer helped you solve the problem, please consider accepting it as the solution and help other members to use the same solution in same/similar situations.
Unfortunately, this isn't supported by the standard Power BI PDF export.
When exporting a report to PDF, Power BI exports the report exactly as it is rendered on the report canvas. For table and matrix visuals, only the visible portion of the visual is captured—content that requires scrolling is not automatically paginated or included in additional PDF pages.
Current limitations
❌ No automatic pagination of table or matrix visuals during PDF export.
❌ No option to split a long table across multiple PDF pages.
❌ Report page size cannot dynamically adjust based on the amount of data.
Possible workarounds
1. Use Paginated Reports (Recommended)
If your requirement is to export tables that may span multiple pages, Power BI Paginated Reports are the best solution. They are designed for:Automatic page breaks
Multi-page tables
Dynamic row counts
Print-ready PDF, Excel, and Word exports
This is the recommended approach for operational or printable reports.
2. Export the underlying data
If users primarily need the complete dataset rather than a formatted PDF, they can use:Export data (CSV or Excel)
Analyze in Excel (if enabled)
This ensures all rows are available without being limited by the visual's scroll area.
3. Redesign the report
If staying with interactive Power BI reports, consider:Using drillthrough pages.
Applying additional filters or slicers to reduce the number of visible rows.
Splitting the report into multiple pages based on business categories.
This won't create automatic PDF pagination but can make exports more manageable.
Recommendation
For reports where the number of rows varies significantly and complete PDF output is a requirement, Power BI Paginated Reports are the intended solution. They provide automatic pagination and are purpose-built for scenarios that standard Power BI reports don't support.
For more information:
Paginated Reports in Power BI: https://learn.microsoft.com/power-bi/paginated-reports/paginated-reports-report-builder-power-bi
Export Power BI reports to PDF: https://learn.microsoft.com/power-bi/collaborate-share/end-user-pdf
💡 Helpful? Give a Kudos 👍 — keep the community growing.
✅ Solved your issue? Mark this as the Accepted Solution ✔️
Best regards, Prince Singh | Data Science & Microsoft Fabric Enthusiast
Hi Dynizju
If your requirement is Export all table rows to PDF, with automatic page breaks, regardless of row count then the best approach is to use a Paginated Report.
Best approaches
1) Use a native Power BI table or matrix visual
If the goal is exportable tabular data, this is usually the best option.
Why it helps:
- Native tables/matrices are much better supported in export
- They can span multiple pages in PDF more predictably than HTML visuals
- You can use formatting, conditional formatting, row padding, and column sizing to improve appearance
Limitations:
- Still not as flexible as custom HTML
- Very long tables can still be awkward, but export behavior is much better
2) Move the table to a paginated report
If you need a true printable document that automatically flows across pages, this is the best-fit solution.
Use Power BI Paginated Reports (Report Builder / SSRS-style reports):
- Designed for invoices, statements, lists, and long tables
- Supports automatic page breaks
- Repeats headers across pages
- Handles variable-length data much better
- Exports to PDF cleanly
This is the closest match to what you want.
3) Use a drill-through or export-only detail report
If the main report is interactive and the detailed table is large, create:
- a summary Power BI report page for viewing, and
- a detail/paginated report for export
That keeps the interactive report clean while giving users a printable output when needed.
4) Split the content yourself before export
If you must stay with the HTML visual, the workaround is to pre-split the data into chunks and display them as separate sections/visuals.
For example:
- Page 1: rows 1–20
- Page 2: rows 21–40
- etc.
But this is usually awkward in Power BI because:
- the split logic must be driven by the data
- it adds complexity
- it still won’t behave like true pagination unless you manage the layout carefully
Hi Dynizju,
Thank you for reaching out to Microsoft Fabric Community.
Thank you garvitgupta96, Prince0011 and powerbidev123 for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user's for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
