Guide section 18 of 31
Responsive Design & Screen Sizes
Power BI should not be designed as if it were a CSS-responsive website. Desktop report pages use a configured canvas and are scaled/fitted in the viewer. Phone use has a separate mobile-optimized layout.
| Topic | Guidance |
|---|---|
| Report canvas | Choose a consistent page size/aspect ratio for the target environment. The recovered guide defaulted to 16:9. |
| Common 16:9 references | 1280×720, 1920×1080, 2560×1440 and 3840×2160 were used as reference choices in the prior guide; choose based on real embed/display target. |
| Page types | Power BI also offers presets such as 4:3, Letter, Tooltip and Custom depending on authoring context. |
| Desktop / embedded | Validate effective browser/embed viewport, surrounding navigation chrome and text readability. |
| Fixed-canvas behavior | Expect scaling/fit-to-width/actual-size behaviors, not automatic arbitrary reflow. |
| Mobile layout | Create a separate phone-optimized composition and select only the important visuals. |
| Mobile ordering | Tell the story top-to-bottom; place highest-priority content first. |
| Mobile density | Avoid side-by-side analytical visuals; cards/KPIs are the main exception. |
| Scrolling | Avoid nested vertical scrolling inside visuals where possible. |
| Responsive slicers | Power BI supports responsive slicers that rearrange/condense based on available space. |
| A4 / PDF | If print precision matters, design/test a dedicated composition or use paginated reporting rather than assuming the interactive page will print optimally. |
Power BI platform fact — current check Microsoft documents a mobile layout view in Desktop and Service, including auto-create, a phone canvas and visual-specific mobile formatting. PDF export converts each report page into a PDF page, so page composition still needs explicit print validation.