> For the complete documentation index, see [llms.txt](https://docs.scaleflex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scaleflex.com/studio/template-builder/regional-settings.md).

# Regional settings

If your project defines regional variants - languages, currencies, or anything else set up in your [metadata configuration](/digital-asset-management-dam/settings/metadata/metadata-configuration.md) - a template that reads metadata can render one design per variant. The same banner then comes out in English with pounds and in French with euros, from one template.

This is the same mechanism the DAM uses in [Regional settings](/digital-asset-management-dam/library/assets/asset-details-window/asset-actions/regional-settings.md) on an asset, applied while a template renders.

#### What makes a template localized

Nothing beyond a variable that reads localized metadata. If a text placeholder uses the **Asset metadata** source and the field it points at belongs to a regional-variants group, the template is localized and the control becomes active.

There is no separate setting to switch on. See [Variables](/studio/template-builder/variables.md) for how to bind a variable to a metadata field.

#### Choosing a variant while designing

The **Regional settings** control sits in the editor header, marked with a globe. Open it and you get one entry per group your project defines - languages and currency are the usual pair, though a project can name and group its variants however it likes. Pick one variant per group and the canvas re-renders with those values.

Use it to check the design, not just the wording: translations change length, and a headline that fits in English may need a smaller size or a taller box in German.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FZ96SIq23mbRc7PjBW1g7%2F24-regional-settings-dropdown.png?alt=media&amp;token=6a205803-0dc0-4fdf-88fd-a1d81d22d658" alt=""><figcaption></figcaption></figure>

The control is always visible, so its absence never leaves you guessing. When the template has nothing to localize it appears grayed out with a tooltip explaining why. Groups that offer only one variant are left out, since there is nothing to choose.

#### Choosing a variant for a variation

The same control appears in the variation builder. Choosing a variant there updates the preview and the metadata-driven fields, and the choice is stored with the variation when you save it - so a variation is a specific language and currency, not just a set of values.

That is how you produce a set of localized outputs: one variation per market, each with its own regional selection, all from one template.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FU8EoPWJa421QsVjYGwuK%2F25-variation-regional-settings.png?alt=media&amp;token=ab597fae-8b02-47a6-b31b-1993dd05d040" alt=""><figcaption></figcaption></figure>

#### When a variant has no value

A localized metadata field holds one value per variant. The variable renders the value for the variant you selected, and nothing else: if that field has no value for the selected variant, or your selection covers none of the groups it belongs to, the variable falls back to its default value rather than borrowing another variant's text.

That is worth knowing when a design looks right in one language and shows placeholder wording in another - the gap is in the asset's metadata, not in the template.

#### What changes and what does not

Regional settings change the *values* pulled from metadata. They do not change the design: layouts, layers, fonts and positions are the same for every variant. Anything typed directly into a text layer is also unaffected, because there is no metadata behind it to localize.

{% hint style="info" %}
If a variant renders text that no longer fits, adjust the layer's **Shrink to fit** or **Word wrap** rather than the text itself. See [Text layers](/studio/template-builder/building-a-template/text-layers.md).
{% endhint %}

#### Where to go next

* [Variables](/studio/template-builder/variables.md) to bind values to metadata.
* [Variations](/studio/template-builder/variations.md) to save one output per market.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scaleflex.com/studio/template-builder/regional-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.