Power BI paginated reports
Paginated reports cover the print-and-export scenarios that interactive Power BI reports don't — invoices, statements, fixed-layout reporting.
Paginated reports in Power BI cover the report category that interactive Power BI reports don't handle well: pixel-precise, fixed-layout, multi-page reports suitable for printing or exporting to PDF. Invoices, statements, regulatory filings, multi-page financial reports, formal exports — paginated is where they live.
Paginated vs interactive
Power BI's flagship product is interactive dashboards — drill, filter, slicer, visual exploration. That's fundamentally different from paginated:
- Interactive reports — slice and dice in the browser, exploratory, no fixed pagination.
- Paginated reports — every record gets its own page (or pages), with strict layout control, perfect for print or PDF export.
A monthly invoice with a fixed header, line items table, and totals footer for each customer is a paginated report. A sales dashboard exploring trends across regions is an interactive report.
Origins and tooling
Paginated reports are the successor to SQL Server Reporting Services (SSRS) reports. The file format (.rdl) is the same; SSRS .rdl files can be deployed to Power BI's paginated report service largely unchanged.
Authoring is done in Power BI Report Builder — a free Windows desktop tool, distinct from Power BI Desktop. Report Builder is designed for fixed-layout report authoring with bands (header, body, footer), tables, charts, sub-reports, and an expression language for dynamic content.
When paginated is the right tool
- Invoices and statements — one per customer, generated on demand or in batch.
- Multi-page financial reports — balance sheets, P&Ls with controlled layout.
- Regulatory filings — fixed-format reports for compliance.
- Letter/email generation — mail-merge-style document creation.
- Long detailed exports — multi-page reports with thousands of records, paginated for navigation.
- Print scenarios — where the report must look right on paper.
For these, paginated is the only good option; trying to do them in interactive Power BI is awkward at best.
When interactive is the right tool
- Dashboards — KPIs, trends, drill-down.
- Exploratory analysis — slicers, filters, what-ifs.
- Mobile consumption — interactive responds to mobile; paginated assumes paper-shaped output.
Most Power BI consumers spend their time in interactive reports. Paginated covers the specific scenarios interactive doesn't fit.
Licensing
Paginated reports require:
- Power BI Premium capacity, Premium Per User (PPU), or Microsoft Fabric capacity for consumption.
- Power BI Report Builder (free Windows app) for authoring.
Not available in standard Power BI Pro consumption — a sometimes-surprising licensing constraint.
Deployment
Authored .rdl files are uploaded to Power BI workspaces (same as PBIX files). Permissions, sharing, and pipelines work the same as interactive reports.
For organisations migrating from SSRS to Power BI, paginated reports are the bridge — your existing SSRS .rdl portfolio largely runs as-is in Power BI's paginated service.
Operational realities
- Performance — paginated reports executing against large queries can be slow; design for set-based queries and avoid row-by-row processing.
- Subscriptions — paginated reports can be subscribed to for scheduled email delivery as PDF / Excel / Word.
- API automation — Power BI REST APIs let you trigger paginated report rendering programmatically; great for bulk PDF generation.
For Microsoft 365 customers with reporting needs that exceed interactive Power BI's scope, paginated reports are a mature, capable option for the print-and-export half of the business intelligence problem.