> 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/using-a-rendered-template.md).

# Using a rendered template

A saved template is delivered like any other asset in your library: it has a link, and opening that link produces an image. Nothing is generated in advance and stored - the image is produced when it is asked for, which is why one template can serve every size and every value you need.

### What changes the output

| Input                       | Effect                                                                                            |
| --------------------------- | ------------------------------------------------------------------------------------------------- |
| The layout                  | Which output size renders. Without one, the default layout is used                                |
| The layout color            | The canvas background                                                                             |
| Each variable's value       | The text, colors and pictures that are left open. Anything not supplied falls back to its default |
| The regional variant        | Which language or market variant the metadata-driven values resolve to                            |
| The source asset's metadata | The live value behind any [asset metadata](/studio/template-builder/variables.md) variable        |

The last one is the reason to prefer metadata over typed values wherever the data already exists: correct the product description in the DAM and every image built on it is correct from the next render onward, with no template to reopen.

### Getting a link

1. Open **Manage variations** for the template, or the template's **Variations** tab in the DAM.
2. Hover the variation you want.
3. Use **Copy link** for the image link, or **Open** to check it in a new tab. **Download** saves the rendered file.

The link is a normal image URL. Paste it wherever an image is expected - a campaign brief, a CMS field, a message to an agency.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FDccLg0oVySpmD6huRI3G%2F31-rendered-variation-in-browser.png?alt=media&amp;token=60ff6747-2836-40b6-a12c-210c4496cad1" alt=""><figcaption></figcaption></figure>

### Keeping outputs consistent

Save a variation for anything you will reuse. A variation records the layout, the values and the regional selection, so the same link keeps producing the same image, and anyone can see how it was made instead of reconstructing it.

For a set of related outputs - one per size, per market or per product - save one variation each and keep them under the template. They stay together on the [manage variations](/studio/template-builder/variations.md) page.

### For developers

Everything above has a programmatic equivalent, documented in the Headless DAM section rather than here:

* [The render URL](/developers-headless/studio/template-builder/render-url.md) - every parameter a link can carry, and how to build one yourself.
* [Getting started](/developers-headless/studio/template-builder/getting-started.md) - embedding the builder in another application, so your own users edit templates without leaving it.
* [Custom metadata](/developers-headless/studio/template-builder/custom-metadata.md) - supplying variable values from an external system.

### Where to go next

* [Variations](/studio/template-builder/variations.md)
* [Managing your templates](/studio/template-builder/managing-your-templates.md)