How to build a branded report theme in Data Studio

There is no such thing as a saved brand theme in Data Studio. You build one in Theme and layout › Customise, and it can look exactly right, but you can’t export it, import it, or apply it to the report you build next week. The only thing that carries a theme to another report is a copy of the report it lives in.

So this post does two things, step by step:

• builds the theme in Edit theme, in the order that saves rework, with screenshots of each part of the panel;
• turns it into something reusable: one master report per brand, with a swatch page, copied for every new client report.

The screenshots are mine, captured in Data Studio in 2026. The worked example is Harbour & Fern, the fictional garden and home retailer from my ebooks, whose brand is a harbour navy, a fern green and a terracotta accent on a warm sand.

What Google says about Data Studio theme reuse

Three sentences from Google’s documentation on themes govern everything else in this post. Each one closes a door people spend hours trying to walk through.

“Custom themes aren’t shared across reports. To reuse a custom theme in another report, make a copy of the report with the custom theme.”

“You can have one custom theme at a time. Modifying an existing theme creates a new custom theme, overwriting any previous custom theme.”

“Themes apply to the entire report. It’s not possible to apply different themes on separate pages of a report.”

So: no theme file, one custom theme slot, and editing that slot destroys what was in it. The limit is per report, not per account: I checked in the product, and two reports each held their own custom theme. That’s the only reason any of this is workable. The only object that carries a theme from one report to another is a report. Everything below is built on that.

What a Data Studio theme actually controls

“Theme” gets used loosely, so it’s worth knowing where the boundaries sit before you build one.

Two things a theme does not control. Layout isn’t theme: canvas size, grid, display mode and the report-level position live in the Layout tab next door, and travel only because the whole report is copied. My layout and grid guide covers them. And anything styled by hand leaves the theme. Google says that when you style a component individually, it’s “no longer part of the report theme”. Text boxes are the extreme case: “Changing themes doesn’t override any custom styles you’ve applied to text boxes.”

Building a Data Studio theme, step by step

Follow the steps in this order. It isn’t the panel’s own order, so each step names the group to scroll to. Several settings cascade, so doing them out of order means setting the same colour twice. Keep a page of real charts open behind the panel: they repaint as you go.

Step 1: start from the closest preset

1. In the editor toolbar, click Theme and layout, and stay on the Theme tab.
2. Scroll the presets. The report behind repaints under each one.
3. Click the one whose structure is nearest the brand: light or dark, flat or carded. Harbour & Fern starts from a light preset.

Data Studio ships nineteen themes: Default, Edge, Constellation, Groovy, Insight, Ocean, Harvest, Eucalyptus, Pop!, Fog, Lagoon, Executive, Woodsy, Royalty, Sienna, Material, Muted, Simple and Simple Dark, plus whatever you’ve extracted from an image. Google names three of them as dark themes in its layout documentation: Constellation, Lagoon and Simple Dark. Starting from Default every time means setting things a preset would have got right; for a dark brand, start from one of those three, as my dark themes post explains.

Step 2: open Edit theme

1. With the preset applied, click Customise at the top of the Theme tab (Customize in a US-English interface).
2. The Edit theme panel opens with Primary styles at the top. Each change creates your one custom theme for this report.

Step 3: the chart palette and Colour by

The palette holds twenty series colours, and Data Studio assigns them in order. Set the first four on purpose; a chart needing more than four distinguishable series has a problem colour won’t fix.

1. Scroll to Data styles.
2. Click a swatch in Chart palette and paste the hex code from the brand guide. Repeat for slots one to four.
3. Set Colour by to Dimension values, so a channel keeps its colour whatever its rank.
4. Click Manage dimension value colours, then Add a value for each channel that appears on more than one page.

Series order means slot one colours whatever happens to be first, so “Organic” changes colour the moment another channel outranks it. Dimension values pins the colour to the value. For a client report you almost always want the second. Choosing the palette itself is a separate argument, and the accessibility half of it matters more than the brand half. Chapter 20 of my ebook, Data Storytelling in Data Studio, covers the emphasis half: greying everything except the series that matters, and keeping each channel the same colour on every page.

Step 4: the “Others” colour

1. Below the palette, find Chart styling defaults.
2. Set ‘Others’ colour to a neutral grey from the brand.

It’s the colour of the “Others” slice on any chart with Group the rest as “Others” turned on. Leave it at the preset’s colour and an otherwise branded chart gets a stranger in it. The same group holds Text contrast and Bar border colour.

Step 5: fonts, one family

1. Back at the top, in Primary styles, set Primary font family. Google applies it to text boxes, data labels, legend labels and control labels.
2. Set Primary font colour, and check it clears 4.5:1 on the background.
3. Leave Textbox styles › Font family at (auto), which inherits the primary, unless headings really need a second face.

The theme sets a family, never a size, so the type scale is yours to hold: Paste style only is how.

Step 6: backgrounds, flat or carded

1. In Primary styles, set Report background colour: the page.
2. In Component background and border, set the card: Background, Border colour, Border radius (0 to 20 px), Border weight and Border shadow.
3. For flat, use radius 0, weight None, no shadow. For carded, use a small radius, a 1 px border in a very light neutral, and no shadow on charts.

Flat suits a dense executive page, where borders would add a dozen more lines. Carded suits a page of four or five components with room around them. Border shadow set to show for controls only is a sensible middle: the filters look clickable and the charts don’t.

Step 7: positive and negative change

1. Find Positive and negative change style.
2. Set Positive change colour and Negative change colour to a pair that isn’t the brand’s accent.

Google says these colours are used for gauge, scorecard and waterfall charts. If the brand red is also the bad-number red, every brand element starts to read as bad news. Fix it here once rather than on each chart.

Step 8: accent styles and page navigation

1. In Accent styles, set the Accent font family, Accent font colour and Accent background colour: table headers, filter and date range control headers, and Apply buttons.
2. In Textbox styles, set the link and visited-link colours.
3. At the bottom, in Page navigation style, set the font, the font colour, the background and the Active font colour for the open page.

These two are the most often skipped. Skip them and the report looks branded until someone clicks a filter.

Harbour & Fern’s theme, step by step

Extract theme from image in Data Studio, and what it’s for

Data Studio can build themes from the colours in an image:

1. Either right-click an image already on the canvas and choose Extract theme from image, or use the button of the same name at the bottom of the Theme tab and upload an image or give its web address.
2. Data Studio offers several themes generated from the image. Pick one and click Apply.
3. Then open Customise and check the accent styles and every colour’s contrast by hand.

It saves typing four hex codes, and it isn’t brand matching. It samples the colours present in the image, not the ones your brand guidelines specify: a logo that’s mostly white on a coloured field gives you a palette built from the field. Nothing in it considers contrast either.

Why a report looks half-themed, and how to hand a component back

Component-level styling beats the theme, and it survives a new theme being applied. So a report worked on by two people usually has a scattering of charts carrying styles that no longer match anything. The way back is one component at a time:

1. Select the chart.
2. Open its Style tab.
3. At the bottom of the panel, click Reset to report theme.

One catch, from Google’s documentation: resetting won’t clear custom colours set in the dimension value colour map, which is held separately. If you’re rebranding an inherited report, budget for this: it’s the unglamorous half of the job, and usually where the hours go.

Making a Data Studio theme reusable: the master report

Since a theme can only travel inside a report, the asset you maintain is a report. Build one master per brand: the theme applied and finished, the canvas and grid set, a logo placeholder, a title text box, a date range control and a footer. Nothing bound to a client’s live data, because the moment it is, you’re maintaining a report rather than a shell.

Add a swatch page: one page showing every theme property on a component. Change one colour and it shows you every place it just landed. Chapter 6 of my free ebook, The Marketer’s Guide to Dashboard Design, on building a branded theme you can reuse, draws the swatch page in full: seven components, each making one theme property visible. Run them on a small sample sheet, not client data:

That’s about ten minutes once per agency: build it in the first master, then copy it into each new one. I also write the four type sizes from my type scale on it, so the next person to add a chart can match them.

In Data Studio: start a new report from the master

1. Open the master in view mode and choose ⋮ › Make a copy at the top right.
2. For each of the master’s data sources, choose the one the new report should use, then confirm the copy.
3. Rename the copy straight away, so nobody mistakes it for the master.
4. If you track report usage, open File › Report settings and add the Google Analytics measurement ID again. Google is explicit that copying “does NOT copy the Google Analytics measurement ID”.

A copy inherits the pages, charts, controls, style settings, text, shapes and images, and not the data sources, which you choose as you copy. What else does and doesn’t survive is in copying and reusing a Data Studio template.

The one-custom-theme trap, written out

You build a report for a client with an orange brand. Months later the same report needs to serve a second brand, blue. Someone opens Theme and layout, changes the palette, and it looks right. The orange theme is now gone: not stored under another name, not in a menu, gone.

The habit that prevents it costs nothing: one master report per brand, and the master’s theme is never edited in place. For an agency, that looks like this:

• One Drive folder per brand, not per client: a client with two brands needs two themes.
• One report in it called “— MASTER (do not edit)”.
• Every new report started as a copy of it.
• When a brand changes, copy the master first, change the copy, and rename the old one with the year.

Why what you’ve built is a template, not a theme

The master is, in Data Studio’s own terms, close to a template. Google’s documentation: “A template is a special kind of report, created by appending /preview to the report’s URL”; anyone opening it copies it before they can change it. So neither a theme nor a template is a file. A theme is a set of styles that can’t leave its report; a template is a report you invite people to copy. In daily use they collapse into each other: reusing a theme means copying its report. Keep public templates apart from masters, though: a public template needs a sample data source that works for a stranger. I’ve set the two side by side in report templates versus report themes.

A branding checklist for a new client report

• Copy the brand master; don’t start from a blank report
• Replace the logo placeholder, keeping the aspect ratio
• Check the swatch page renders the way you expect before adding any charts
• Confirm accent styles: open a filter control and look at a table header
• Confirm the “Others” colour on a chart with a row limit
• Confirm positive and negative change colours on a scorecard
• Confirm navigation colours by opening the page menu
• Add the measurement ID in Report settings, if you track usage
• Check any inherited text boxes, which will have ignored the theme
• Never edit the master’s theme in place

Frequently asked questions

Can I save a custom theme in Data Studio and reuse it?

Not as a theme. Google’s documentation states that custom themes aren’t shared across reports, and that to reuse one you make a copy of the report carrying it. The working method is to keep a blank branded master report per brand and copy it for each new client report.

How many custom themes can a Data Studio report have?

One. Google states that you can have one custom theme at a time, and that modifying an existing theme creates a new one, overwriting the previous. The limit is per report, so different reports can each hold their own custom theme, which is why one master report per brand works.

Why does my report still show the old colours after changing the theme?

Two likely causes. Component-level styling beats the theme and survives a theme change, so charts styled by hand keep their old look until you select them and use Style › Reset to report theme. And text boxes keep any custom styles: Google says changing themes doesn’t override them.

How many themes does Data Studio have?

Nineteen presets in the Theme tab, from Default to Simple Dark, including the three Google names as dark themes (Constellation, Lagoon and Simple Dark), plus any you extract from an image. Each report can also hold one custom theme.

Where to go next on report design

• Dashboard design principles for readable reports
• How to choose a dashboard colour palette in Data Studio
• Data Studio fonts and type sizes
• Report templates versus report themes
• How to copy and reuse a Data Studio template
• Dark themes in Data Studio, and what they cost