“Can you make the report mobile-friendly?” is three different requests, and they have three different prices. One is a rebuild. One is a Pro subscription and a list of things Google refuses to convert. One is free and mostly means building differently in the first place.
Nearly every page on this topic collapses them into a single answer. Here’s what each one actually is, what it costs, and how to choose.
Freeform and responsive, side by side
Before the options, the thing worth seeing. This is one report built both ways, opened in the same desktop window.
Two differences worth naming. The freeform report’s scorecards are boxes at fixed coordinates on a fixed 1200 × 900 canvas. The responsive report’s are cells in a full-width band that will stretch and reflow. And the Theme and layout panel is visibly shorter in the responsive version — several settings simply aren’t there, which is the first hint at the cost.
Now the same two reports on a phone.
The freeform pane isn’t broken — it’s doing exactly what it was told, at a third of the size. The scorecards are clipped, the table is a grey smear, and the axis labels have gone. The responsive pane has rearranged itself into one readable column.
If that were the end of the story everyone would build responsive. It isn’t, and the rest of this guide is why.
Why a freeform Data Studio report struggles on a phone
The default report type is freeform, and freeform behaves like a slide: components sit at fixed coordinates on a fixed canvas. That canvas is designed for a desktop screen, and on a phone the whole thing scales down rather than reflowing. Nothing moves; everything just gets smaller.
Which is why a report that’s perfectly readable on a laptop turns into a page of unreadable 6px axis labels on a phone — the layout is doing exactly what you told it to, at a third of the size.
Option one: the responsive report type in Data Studio
Data Studio has a genuinely different report type. Instead of a fixed canvas you build in sections, each holding columns, laid out on an automatic 12-column grid that reflows to the viewer’s screen.
Choosing responsive: the only moment Data Studio offers it
Create a new report and the empty canvas carries two pills — Freeform layout and Responsive layout — with a tooltip describing the second as automatic structuring “with responsive grids that adapt to any screen size”.
Take that screenshot seriously, because it’s a one-time decision dressed up as a toggle. Everything in the next few sections follows from which pill you click here.
Building in sections, and what a section actually is
In a responsive report you don’t place a chart on a canvas — you add a section, then put components in it. Select a section and the properties panel says Group properties, which is the tell: a section is a group, with everything that implies.
That panel is the part nobody covers, and it’s the reason responsive reports can be better structured than freeform ones rather than merely more portable. A section can carry:
- Its own data source — so a “Paid” section runs off Google Ads while the section above it runs off GA4, without setting the source chart by chart.
- Its own filter — one filter applied to a band of four charts, maintained in one place.
- Its own date range dimension — useful when one band needs a different date field from the rest of the page.
- Apply filter controls to page — a toggle deciding whether a control inside the section reaches the whole page or stays local to it.
Where that earns its place in a marketing report: the classic channel-by-channel monthly. One section per channel, each pointing at its own source and filtered to its own campaigns, and adding a fifth channel next quarter is one section rather than nine components with nine filters.
Vertical stacking within a column shipped in late 2025, which changed the one-row-per-section model that most tutorials on responsive reports still teach.
Checking it: View → Preview → Phone
You don’t have to guess, and you shouldn’t. The View menu carries a Preview submenu with Phone, Tablet and Desktop.
Make Phone the last thing you check before sending. It takes four seconds and it catches the section that turned into a two-screen scroll.
That shot also shows the cost concretely: the responsive report’s LAYOUT tab has no Display mode and no Canvas size. There’s no canvas to size, and no fit-to-width to choose, because the grid already decides.
What responsive costs you
Google publishes the list, and it’s long. Eleven things are unsupported in a responsive report: lines and arrows, canvas size configuration, grid settings, snap-to settings, grouping components, making a component report-level, rotating components, sending components forward or backward, the Fit to width and Actual size display modes, report-level component position, and — the one to read twice — two or more users editing the same report simultaneously.
Three of those decide it for most agencies:
No report-level components. That’s your persistent logo, your one date-range control, and your navigation bar — all gone. Everything is per-section, maintained separately. If you’ve built a report the way the layout guide recommends, responsive removes the mechanism that made it maintainable.
No simultaneous editing. Two people cannot have the report open at once. For a solo consultant that’s nothing; for an agency where an account manager tweaks commentary while an analyst fixes a chart, it’s disqualifying. No competitor page I’ve found mentions this.
No migration path. This is the big one, and it has its own section.
Why you can’t convert an existing report to responsive
Google’s documented rule is that you can change from freeform to responsive only “if your report has one or fewer components per page”. Any real report has more, and the product enforces it bluntly. Set Layout mode to Responsive on a built report and you get this.
The dialog’s own words: “You cannot directly change from freeform layout to responsive layout at this time. To use this layout, create a new report in responsive layout mode and copy components from this report into the new one.” So you cannot convert an existing client report. You rebuild it.
The other direction is allowed, and worth knowing before you rely on it as an escape hatch.
Read those two dialogs together and the shape of the decision is clear: the door opens one way, once. Which is why “try responsive and see” is bad advice, and why the choice belongs at the start of a build rather than at the end of one.
Is responsive still in preview?
Worth being precise, because the answer is genuinely ambiguous and I’ve seen it stated confidently in both directions.
Google’s documentation navigation still lists the page as “Create a responsive report (Preview)“. The page itself carries no preview banner and reads as ordinary documentation. The feature has been shipping improvements for well over a year.
So: it works, it’s documented, it’s being developed — and Google hasn’t taken the Preview label off the menu. What I’d tell a client is that it’s stable enough to build on and not yet something to describe as a guaranteed long-term surface. I would not tell them it’s generally available, because Google hasn’t said so.
Option two: the mobile app’s “mobile friendly view”
A completely separate mechanism, and one that requires nothing from you. The Looker mobile app can render a report in what Google calls a mobile friendly view — an automatic reflow — rather than the original web view. Navigation becomes a bottom sheet reached by tapping the report name.
It needs Data Studio Pro, and it publishes its own refusals. Google lists what it will not convert:
“Reports that include lines (such as line, arrow, elbow, or curved). Reports that have mind map or flow chart-like arrangements. These are not converted in order to preserve the order and layout of charts and elements. Reports that include overlapping non-image items.”
Read that as a design brief rather than a limitation. A single decorative arrow anywhere in your report disqualifies it from automatic conversion. So does one chart overlapping another by two pixels — which happens constantly in freeform layouts built by dragging, and which snapping to a grid prevents almost for free.
The useful thing here is that those same three properties are what make a report awkward on a phone generally. Google’s refusal list is, in effect, a checklist for the third option.
Option three: build the freeform Data Studio report better
For most agency reports this is the right answer, because most client reports are read on a laptop and merely opened on a phone — someone checking a number between meetings rather than doing analysis.
Four decisions cover it:
Fewer, taller pages. A phone scrolls comfortably and pans badly. A tall page with one column of stacked components reads far better than a wide one, and it’s the single biggest change available. Set it in Theme and layout → LAYOUT → Canvas size → Custom, with a narrower width and a taller height than the preset.
No lines, arrows or overlap. Google’s refusal list again. These are the same things that break the automatic conversion, and they break human reading on a small screen for the same reasons.
Bigger type than feels necessary. Data Studio’s 12px default is small on a desktop and unreadable on a phone. Chart titles and scorecard labels are where it matters, and the type guide has the scale worth holding to.
Put the answer first. If the report’s top-left component answers the question, a phone reader gets what they came for without scrolling. That’s just the executive summary page argument applied to a small screen.
Your navigation bar will not survive the move to responsive
Worth its own section because the two posts that would tell you are never the same post.
A custom navigation bar is, by construction, a report-level component — that’s what makes it appear on every page and stay maintainable. Responsive reports have no report-level components. So if you’ve built a branded nav bar and you switch to responsive, the bar cannot come with you in any form.
You’re left with the built-in navigation, which is no bad thing — it’s better than most hand-built bars and it highlights the current page. But it’s a constraint that arrives before the design decisions, not after, and the navigation guide is worth reading in that light.
How to choose between the three
Build responsive if the report is genuinely read on phones — a field team, a client who works from their phone, a report embedded in a mobile app. Accept the rebuild and the co-editing loss, and design in sections from the start rather than converting.
Rely on the app if you have Pro, your readers use it, and your reports contain no lines, arrows or overlapping components. Check one report against the refusal list before promising anything.
Build freeform carefully in every other case, which is most of them. Fewer, taller pages; no decorative lines; larger type; the answer at the top.
What I’d avoid is the middle path where someone converts one report to responsive, discovers the co-editing limit a week later, and converts it back — because as those two dialogs show, going back is a one-way door of its own.
Frequently asked questions
Does Data Studio have responsive reports?
Yes, as a separate report type built from sections on an automatic 12-column grid, with a Phone, Tablet and Desktop preview under the View menu. Google’s documentation navigation still lists the page under a Preview label, though the page itself carries no preview banner.
Can I convert my existing report to a responsive one?
No. Setting Layout mode to Responsive on a built report returns a dialog saying you cannot directly change from freeform to responsive, and telling you to create a new report in responsive mode and copy components into it. That’s a rebuild rather than a conversion.
Why won’t the Looker mobile app show my report in mobile friendly view?
Google publishes the three reasons it refuses to convert a report: it contains lines, arrows, elbow or curved connectors; it has a mind map or flow-chart-like arrangement; or it contains overlapping non-image items. A single decorative arrow is enough.