There is no such thing as a saved brand theme in Data Studio. You can build one, and it will look exactly right — but you cannot export it, cannot import it, and cannot apply it to the report you build next week. Every tutorial on branding a Data Studio report skips this, which is why the workflow they teach quietly stops working the moment you have a second client.
This is how to build the theme properly, and then the method that does make it reusable — because there is one, and it isn’t the one you’d guess.
What Google says about Data Studio theme reuse
Three sentences from Google’s documentation on themes govern everything else in this post. They’re worth reading in full, because 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 one-theme limit is scoped to the report rather than to your account — different reports can each hold their own custom theme, which is the only reason any of this is workable.
Read those together and the consequence is specific. The only object that carries a theme from one report to another is a report. Not a file, not a preset, not a saved style. A report. Everything below is built on that.
What a Data Studio theme actually controls
Before building one it’s worth knowing where the boundaries sit, because “theme” gets used loosely and two of the three things people expect it to cover are somewhere else entirely.
| Group | What’s in it | Commonly missed |
|---|---|---|
| Text and background | Font family and colour, report background, component background and border | — |
| Chart palette | The ordered series colours, and the “Others” colour | Yes — the “Others” colour is separate and almost nobody sets it |
| Accent styles | Table headers, filter controls, buttons, links and visited links | Yes — this is why a report looks half-branded |
| Positive / negative change | The up-and-down colours on scorecards | Yes |
| Page navigation | Navigation background, text and selected-item colours | Yes |
And two things a theme does not control, which trip people up constantly:
Layout is not theme. Canvas size, grid, margins and component position live in the LAYOUT tab next door and travel separately. The design principles guide covers what to do with those.
Text boxes ignore you. Google is explicit: “Changing themes doesn’t override any custom styles you’ve applied to text boxes.” If you hand-styled a heading once, it will keep that styling through every theme change you make afterwards — which is the single most common reason a rebranded report still has one stubbornly wrong-coloured title on page four.
Building a Data Studio theme: the order that saves rework
Theme and layout → THEME → Customize. Work top to bottom; several of these cascade, so doing them out of order means setting the same colour twice.
1. Start from the closest preset. Data Studio ships nineteen themes — Default, Edge, Constellation, Groovy, Insight, Ocean, Harvest, Eucalyptus, Pop!, Fog, Lagoon, Executive, Woodsy, Royalty, Sienna, Material, Muted and Simple, plus whatever you’ve extracted from an image. Pick the one whose structure is closest to your brand — light or dark, high or low contrast — and customise from there. Starting from Default every time means setting things the preset would have got right.
2. The chart palette — twenty slots, four decisions. The palette holds twenty series colours, not the three or four that most branding guides imply, and Data Studio assigns them in order. Slot one goes to whatever your first series happens to be.
In practice the first four do nearly all the work, so set those deliberately and let the rest be reasonable; a chart needing more than four distinguishable series has a problem colour won’t fix. Choosing the palette itself is a separate argument, and the accessibility half of it matters more than the brand half.
Directly above the palette is a choice worth understanding before you spend time on the colours: Colour by — Series order or Dimension values. Series order means slot one colours whatever happens to be first, so the colour of “Organic” changes the moment a different channel outranks it. Dimension values pins a colour to a value, so Organic stays the same colour on every chart and in every month. For a client report you almost always want the second, and Manage dimension value colours is where those are set.
3. The “Others” colour. A separate setting, sitting under Chart styling defaults alongside text contrast and bar border colour. It’s the one that shows up on every pie and bar chart with a row limit, and leaving it default puts a grey wedge in an otherwise branded chart.
4. Two fonts, maximum. One for headings, one for everything else. Data Studio’s font list is long and the temptation is real; resist it.
5. Report and component backgrounds. Report background is the page; component background and border are every chart card. These two decide whether the report reads as flat or carded, and it’s worth picking one deliberately rather than inheriting it.
The four settings that decide it are in that second group: Border colour, Border radius, Border weight and Border shadow. Flat is radius 0, weight None, no shadow — charts sitting straight on the page background. Carded is a small radius, a 1px border in a very light neutral, and shadow off. Shadow set to “Show for controls” is a sensible middle: the filters look interactive, the charts don’t.
Where each earns its place: flat suits a dense executive page where the borders would add twelve more lines to an already busy layout. Carded suits a page of four or five components with room around them, and it is what makes a report look designed rather than assembled.
6. Positive and negative change colours. Every scorecard comparison uses these. If your brand red is also your “bad number” red, you have a problem worth solving here rather than on each chart.
7. Accent styles and navigation colours. Last, and the two most-skipped. Accent styles cover table headers, filter controls and buttons; navigation colours cover the page menu. Skip them and the report looks branded until someone clicks a filter.
Extract theme from image in Data Studio, and what it’s actually for
There’s a button in the THEME tab that builds a palette from an image — point it at a logo and it returns several candidate themes. You can also right-click an image already on the canvas and extract from that.
It’s useful, and it’s consistently misrepresented as brand-matching. It isn’t. It samples the colours that are present in the image, which is not the same as the colours your brand guidelines specify — a logo that’s 80% white on a coloured background will give you a palette built from the background. Treat the result as a starting point that has saved you typing four hex codes, then correct it by hand.
The two things it reliably gets wrong are accent styles and contrast. Check both before you move on.
Why a report looks half-themed, and how to hand a component back
Component-level styling beats the theme, always, and it survives you applying a new theme afterwards. So a report that’s been worked on by two people usually has a scattering of charts carrying styles that no longer match anything.
The way back is per-component: select the chart, open the STYLE tab, and at the bottom of the panel click Reset to report theme. One caveat worth knowing, from Google’s docs: resetting a chart to the report theme won’t reset any custom colours you’ve set in the dimension value colour map. Those are held separately and need clearing on their own.
If you’re rebranding an inherited report, budget time for this. It’s the unglamorous half of the job and it’s usually where the hours go.
Making a Data Studio theme reusable: the blank-report method
Now the part that the limits at the top made necessary. Since a theme can only travel inside a report, the asset you maintain is a report.
Build a master. One report per brand, containing no charts. The theme, applied and finished. A logo placeholder, a title text box, a date-range control, a footer. Canvas size and grid set the way you want them. Nothing that refers to a data source, because the moment it does you’re maintaining a report rather than a shell.
Add a swatch page. This is the part that makes the master worth having rather than just correct: one page showing every theme property rendered visibly. When you change one colour, that page shows you the six places it just changed. Without it, you’re checking by memory.
What to put on it, and which theme property each one exposes:
| Put on the page | So you can see |
|---|---|
| A table with six rows | Accent styles — the header row colour |
| A bar chart with six series | Palette slots one to six, in order |
| A pie chart with a row limit of four | The “Others” colour |
| Two scorecards with comparison on, one up and one down | Positive and negative change colours |
| A text box containing a link | Textbox styles, link and visited-link colours |
| One drop-down filter control | Accent styles again, plus component border and shadow |
| A second page, so the menu renders | Page navigation colours |
That’s seven components and about ten minutes, once per agency rather than once per brand — copy the swatch page into each new master.
Duplicate, never modify. New client report? Make a copy of the master and work in the copy. Do not open the master and adjust the theme “just for this one” — that’s the one-theme-at-a-time rule waiting to happen, and the previous theme does not come back.
The mechanics of what does and doesn’t survive that copy are their own subject — data sources in particular behave in a way that catches people out — and I’ve covered them in copying and reusing a Data Studio template.
The one-custom-theme trap, written out
Worth playing forward, because it’s cheap to avoid and expensive to discover.
You build a report for a client with an orange brand. Months later the same report needs to serve a second brand, blue. You open Theme and layout, adjust the palette, and it looks right. The orange theme is now gone — not stored under another name, not recoverable from a menu, gone. If you need it back you rebuild it from the brand guidelines, assuming you still have them.
The habit that prevents it costs nothing: one master report per brand, and the master’s theme is never edited in place. If a brand genuinely changes, duplicate the master, change the copy, and keep the old one until you’re sure.
Why what you’ve built is a template, not a theme
The master report you now maintain is, in Data Studio’s own terms, a template — and that word means something specific here rather than something vague. It’s worth being precise about the difference, because the two get used interchangeably everywhere and they behave completely differently. I’ve pulled that apart in report templates versus report themes.
The short version: a theme is a set of styles that cannot leave the report it lives in. A template is a report you’re inviting someone to copy. Neither is a file, and that’s the thing that makes Data Studio branding feel harder than it should.
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 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
- 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 report per brand and duplicate 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 the one-master-report-per-brand approach 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 Reset to report theme. And text boxes are explicitly exempt — Google says changing themes doesn’t override custom styles applied to text boxes.