← All Kits · Tableau Kit

Tableau Dashboard Sizing: Fixed, Automatic or Range, and Why It Matters

Michael Nocito · Updated August 2026 · Every number on this page was worked before it was published

You build the dashboard, it looks right, you publish it, and somebody opens it on a laptop with a smaller screen. Now the title wraps, a filter has slid over a chart, and the bottom view is cut off. Every one of those is the size setting.

What you do: choose Fixed size, pick dimensions that match where it will actually be read, and lay out with tiled containers rather than floating pieces.

The short version. Fixed size is the only setting where what you see is what they see.

The three settings

Automatic sounds like the responsive option and behaves like the unpredictable one. Tableau stretches the containers but does not rewrap the design: text does not resize, so a dashboard that is legible at 1400 pixels wide has cramped labels at 1000, and floating objects keep their coordinates while everything around them moves.

Choosing the dimensions

Ask where it will actually be read before choosing. Most dashboards are read on a laptop in a browser, which is a smaller usable area than the screen resolution suggests once the browser bar and any portal navigation are taken off.

Device layouts

Device Preview, in the toolbar, adds Desktop, Tablet and Phone layouts to one dashboard. Each layout keeps its own arrangement while sharing the same sheets, so a phone version can stack views vertically and drop the ones that will not read small, without touching the desktop version.

1. Build and finish the desktop layout first.
2. Device Preview, choose Phone, then Add Phone Layout.
3. Set it to Custom rather than Default, and rearrange: one column, biggest number at the top.
4. Remove views that need width, such as a wide table or a scatter with many labels.
5. Check the filters. A multi-select list that works with a mouse is painful on a phone; a single-select dropdown is better.

Tableau picks the layout by the screen size of the device opening it, so the phone version appears automatically for phone-sized screens.

Tiled and floating

Tiled objects sit inside containers and move together when anything resizes. Floating objects hold absolute coordinates and do not. A dashboard built entirely from floating objects looks fastest to assemble and is the one that breaks on somebody else's screen.

Use horizontal and vertical containers as the skeleton, then float only where you genuinely need overlap, such as a label on top of a chart. Select All in Container, then Distribute Contents Evenly, does most of the tidying people do by dragging.

The checks before publishing

1. Preview at the size you chose, not at your monitor size.
2. Open the published version in a browser with the portal navigation visible, which is what the audience sees.
3. Check the bottom of the dashboard is reachable without a scroll that nobody will make.
4. Test one phone layout if any part of the audience is mobile.
5. Ask one colleague on a different screen to send you a screenshot. Thirty seconds, and it catches everything above.

How to apply this to your own work

1. Open your most used dashboard and check whether it is on Automatic. If so, switch to Fixed and see what moves.
2. Find out what screen your main audience uses, and size for that rather than for yours.
3. Replace floating objects with containers in the areas that shift.
4. Move the headline number above the fold at your chosen height.
5. Add a phone layout for anything people open away from a desk.

The one habit to keep

Look at the dashboard on a screen that is not yours before you call it finished. It is the only test that catches sizing problems, and it takes one message to a colleague.

Do you know the screen size of the person who opens your dashboard most often?