Data Studio’s theme sets a font family. It does not set a font size. That one gap is why reports drift — every chart title ends up at whatever size the person building it happened to leave it, and nothing in the theme pulls them back into line.
So type in Data Studio is a discipline rather than a setting. Here’s the font list, what the theme does and doesn’t govern, the four-tier scale worth holding yourself to, and the two panels where all of it actually gets set.
The thirty-three fonts Data Studio offers
The picker is alphabetical and runs to roughly thirty-three faces, each name rendered in its own face so you can judge it without applying it.

They fall into four groups, and only two of the groups are useful for a report.

The web-safe set — Arial, Calibri, Cambria, Courier New, Georgia, Times New Roman, Trebuchet, Verdana. Dull, and completely reliable. Reach for Verdana if a report is going to be read at small sizes on old monitors; it was drawn for exactly that.
Google’s UI faces — Roboto, Roboto Condensed, Open Sans, Lato, Montserrat. These are what most well-built reports use. Roboto Condensed in particular earns its place because it fits more axis label into less width, which is the single most common space problem in a marketing dashboard.
The workhorses — Lora, Raleway, Quicksand, Oswald, Ubuntu, Ubuntu Mono, Orbitron and a few others. Some genuinely useful: Ubuntu Mono for anything where digits should line up in columns.
The display faces — Bangers, Bubblegum Sans, Chewy, Comic Sans MS, Coming Soon, Eater, Indie Flower, Permanent Marker, Pop. These exist and they are not for client reports.
Can you use a custom font in Data Studio?
Not in the report’s own type. There’s no font upload, and no way to point the theme at a Google Font that isn’t on the list.
The workarounds people reach for are worth knowing so you can rule them out quickly. A community visualisation can render its own type, which covers a chart but not the report. An image of text is sharp and unsearchable and breaks at any other size. And the “import Google Fonts” advice that circulates applies to Looker, the enterprise BI platform, not to Data Studio — which is a recurring confusion worth checking before acting on any tutorial that promises it.
For brand work, the practical answer is to pick the closest available face and put the real brand typeface in the logo, which is an image anyway.
What a Data Studio theme governs about type, and what it doesn’t
The font family lives in Theme and layout → THEME → Customise → Primary styles, in a field called Primary font family.

That family applies broadly — text boxes, data labels, legend labels, control labels. What it doesn’t carry is size. There is no default-font-size setting in Theme and layout, which is a long-standing gap rather than something hidden in a submenu.
Scroll the same panel further and there’s a second font field, in Textbox styles, which defaults to (auto) — meaning “inherit the primary”.

Two consequences worth planning around.
Sizes are per component. Every chart title, axis, label and text box carries its own. Which means a report is only as consistent as the person building it, and a report built by two people usually isn’t.
Text boxes ignore theme changes entirely. Google is explicit that changing themes doesn’t override custom styles applied to text boxes. So hand-styled headings survive a rebrand — and are the reason a rebranded report still has one page that looks like the old one. If you’ve hand-styled a heading, note it somewhere, because the next theme change won’t reach it.
Paste style only: the nearest thing to a type system
The tool that closes the size gap is Paste style only, and it’s worth learning as a habit rather than a rescue.
- Style one chart title exactly as you want it — size, weight, colour, alignment.
- Select that chart and copy it (⌘C / Ctrl+C).
- Select the chart you want to match — or several at once, with Shift.
- Arrange → Paste special → Paste style only.
The target keeps its own data and takes the source’s appearance. On a twelve-chart report that’s about ninety seconds and it removes the most visible symptom of a report built in a hurry. It’s also the repair for a report you inherited: style one chart properly, then push it outwards.
A four-tier type scale for a Data Studio report
Since the theme won’t hold a scale for you, hold one yourself. Four tiers is enough for any report, and writing them down means a second person can match them.

Where each tier earns its place in a marketing report:
- 34px page title — once per page, and it should name the question the page answers, not the data source. “Where did organic traffic come from?” beats “GA4 Acquisition”.
- 22px section heading — the label on a band of three or four related charts. This is the tier most reports skip entirely, and skipping it is why a page of eight charts reads as eight unrelated things.
- 15px chart title — every chart, no exceptions, and phrased as a finding where you can.
- 12px body — axis labels, table text, the note under a chart. Nothing important lives here.
The reason to keep it to four is the same reason size decides reading order: a page with seven type sizes has no hierarchy, because nothing is clearly more important than anything else.
The pixel size at which WCAG contrast rules change
A detail that connects type to accessibility, and which I haven’t seen stated anywhere in this space.
WCAG requires 4.5:1 contrast for normal text and relaxes to 3:1 for large text. But it defines large text in points — 18pt, or 14pt bold — while Data Studio sets type in pixels. At the standard 96dpi that works out to 24px, or about 20px bold.
Which means the relief starts much higher than people assume. Your 15px chart titles are not large text. Neither is anything at Data Studio’s 12px default. Almost everything in a typical report owes the full 4.5:1, and a mid-grey label on a white card frequently doesn’t clear it. The colour palette guide goes into the rest of the contrast requirements, including the one that governs chart series.
Practical legibility in a Data Studio dashboard
Five things that matter more than which face you picked, and two of them are visible enough to draw.

Axis labels are where reports fail first. They’re small, often rotated, and frequently truncated. Fewer categories, or a horizontal bar chart instead of a rotated-label column chart, fixes more than any font choice — and it’s a two-click change in the chart type picker, not a redesign.
Both of those live in one place, and it’s not the theme. Select a chart, open Style, and the X-Axis group carries the axis label’s own font family, size, colour and rotation.

That Rotation (0° to 90°) field defaults to (auto), which means Data Studio decides — and what it decides, when a chart is narrower than its labels need, is to tilt them. Setting it to 0 forces horizontal labels and lets Data Studio truncate instead, which is usually the better failure: a shortened label you can hover to read beats a tilted one nobody reads at all.
Numbers want a tabular face, or at least a consistent one. In a table of figures, digits that vary in width make columns look ragged. Ubuntu Mono solves it outright; Roboto is reasonable. This matters most in a table a client scans down rather than reads across — a top-landing-pages table, say.
Condensed faces buy you width, and cost you at small sizes. Roboto Condensed at 12px in an axis is fine. At 9px it stops being readable faster than the regular cut does.
Two families, maximum. One for headings, one for everything else — and honestly, one is usually enough. The report isn’t a brochure.
Check it at the size it’ll be read. Building at 100% zoom on a 27-inch monitor and shipping to someone reading on a 13-inch laptop is how 10px labels happen. Phone screens compress it further still, and the three options for mobile-friendly Data Studio reports each handle small type differently — responsive layout reflows it, freeform just shrinks it.
A type checklist before a Data Studio report goes out
- One font family, or at most two
- Four sizes, written down somewhere the next person will find them
- Chart titles all the same size — use Paste style only rather than trusting yourself
- Nothing below 12px, and nothing important at 12px
- Every text colour checked against 4.5:1, because almost nothing qualifies as large text
- Axis labels checked at the reader’s screen size, not yours
- Rotated axis labels either shortened or swapped for a horizontal bar chart
- Hand-styled text boxes checked after any theme change, since they ignore it
Frequently asked questions
How many fonts does Data Studio have?
Around thirty-three in the picker, alphabetical and each rendered in its own face, ranging from web-safe faces like Arial and Verdana through Google’s UI set — Roboto, Open Sans, Lato, Montserrat — to display faces such as Bangers and Permanent Marker that have no place in a client report.
Can I use a custom font in Data Studio?
No. There’s no font upload and no way to point the theme at a Google Font outside the list. Advice about importing Google Fonts generally refers to Looker, the enterprise BI platform, rather than Data Studio. Pick the closest available face and carry the real brand typeface in the logo.
How do I set a default font size for a whole report in Data Studio?
You can’t. The theme carries a font family but not a size, so every component holds its own. The practical substitute is to decide a four-tier scale, style one chart title to match it, and push that style outwards with Arrange → Paste special → Paste style only.
Where to go next on report typography
- Dashboard design principles for readable reports
- How to choose a dashboard colour palette in Data Studio
- How to build a branded report theme in Data Studio
- Data Studio layout and grid: building aligned reports
- Mobile-friendly Data Studio reports: the three options
- Data Studio chart types, and how to choose one

