Power BI Paginated Reports are designed for formatted, multi-page output — invoices, statements, regulatory filings, and any report where precise layout control matters. This guide covers when to use them, how they differ from standard Power BI reports, and the licensing requirements.
Power BI Paginated Reports are designed for formatted, multi-page output that renders predictably across printers, PDF exports, and email attachments. Unlike standard Power BI reports where visuals resize fluidly to fill the viewport, paginated reports have a fixed page size, precise control over every element's position and dimensions, and page break logic that controls how content flows across pages.
If you need a report that looks the same on screen as it does when printed, paginated reports are the right tool. If you need interactive exploration and fluid dashboards, standard Power BI reports are the right tool.
What paginated reports are for
**Regulated and formal documents**: Tax statements, financial reports filed with regulators, legal notices, compliance audit reports. These require exact formatting that does not change based on screen size.
**Operational documents**: Invoices, purchase orders, shipping labels, work orders. Pixel-perfect layout, often with conditional formatting (e.g., overdue invoices highlighted in red).
**Multi-page analytical reports**: A 50-page detailed drill-down report with a table of contents, page numbers, and consistent headers. Standard Power BI is not designed for multi-page content; paginated reports handle it natively.
**High-volume parameterised reports**: A paginated report can be parameterised (by customer ID, date range, region) and delivered to thousands of recipients via subscriptions — each subscription renders the report with the recipient's parameter values. This is the RDL/SSRS subscription model carried forward into Power BI.
How they differ from standard Power BI reports
**Layout model**: Standard Power BI reports use a canvas layout where visuals are sized relative to the viewport. Paginated reports use an absolute layout — every element has a precise X/Y position and fixed width/height, measured in inches or centimetres.
**Data model**: Standard reports use the Power BI semantic model (DAX measures, import/DirectQuery). Paginated reports connect directly to a data source — a SQL query, a stored procedure, a dataset in the Power BI service, or an Analysis Services model — and the report's tablix, chart, and other data regions bind to the query results. DAX is not the query language; parameterised SQL or MDX is.
**Rendering formats**: Paginated reports export to PDF, Word, Excel, CSV, XML, TIFF, and MHTML with high fidelity. Standard Power BI reports export to PDF (screenshot-based, lower fidelity) and PowerPoint.
**Interactivity**: Paginated reports support basic interactivity — parameter selection, toggleable drilldowns, hyperlinks — but not the rich filter-by-click, cross-filtering, and animation of standard reports. They are designed for reading, not exploration.
Licensing requirements
Paginated reports require one of:
- Power BI Premium Per User (PPU)
- Power BI Premium capacity (P SKU)
- Microsoft Fabric capacity
Standard Power BI Pro licences cannot publish or view paginated reports. This is one of the most common surprises for organisations first encountering paginated reports — the licensing is more expensive than Pro.
Building paginated reports
Paginated reports are authored in Power BI Report Builder (a free Windows desktop application, not Power BI Desktop). The Report Builder uses the same RDL (Report Definition Language) format as SQL Server Reporting Services (SSRS) — if you have SSRS experience, paginated reports will feel familiar.
The primary report data regions:
- **Tablix**: A flexible table/matrix structure for tabular data. Supports row groups, column groups, headers, footers, and subtotals. The workhorse of most paginated reports.
- **Chart**: Standard chart types (bar, line, pie, scatter) as fixed-layout visuals.
- **Image**: Embedded or referenced image elements.
- **Subreport**: Embeds another paginated report as a region within the parent report.
Parameters are defined in Report Builder and appear as filter controls when the report is viewed. Multiple parameters can be cascaded — selecting a value in one parameter filters the available values in another.
Migrating from SSRS
If your organisation runs SQL Server Reporting Services, Power BI paginated reports are the migration path. The RDL format is compatible — SSRS reports can be uploaded directly to Power BI Premium/Fabric workspaces with minor modifications. Connection strings need updating from SSRS data source format to Power BI service data source format.
Microsoft provides the RDL Migration Tool to automate the compatibility conversion step.
When to use paginated vs standard reports
**Use paginated reports when**: The output is printed, emailed as an attachment, submitted as a formal document, or requires exact pixel layout regardless of screen size.
**Use standard Power BI reports when**: The primary use case is interactive exploration, dashboard monitoring, or screen-based consumption where fluid responsive layout is preferred.
For the broader Power BI context, see power bi deployment guide. Our Tableau consulting practice covers Power BI alongside Tableau — book a scoping call to discuss your formatted reporting requirements.
A former Microsoft data architect audits your data foundation, identifies your top priorities, and sends you a written plan. Free. No pitch.
Book a Call →