# Custom styles

The preloaded [style presets](/visualize/style-presets.md) cover the common cinematic and illustrative looks. Custom styles are how you go beyond them: upload reference images and write the descriptive prose, save the result as a personal or team-level preset, apply it to any future render with one click.

![Create Style Preset modal with a Name field, an "add prompt notes" action, and a drop zone for reference images with the recommendation "We recommend providing 3-10 reference images" plus Cancel and Create actions](/files/DCDcG5ipjq2OycW5lgBb)

## What it does

Three reasons to build a custom style:

* **The preloaded set doesn't cover the look you want.** A Mobius-influenced 2D illustration; a specific photographer's grade; an anime register that's tuned tighter than the generic anime preset.
* **You're working in a brand's visual language.** The agency's house look, applied across every render, with one click.
* **You're cycling between two custom looks across a project.** A vehicle hero in look A, an environment beat in look B – fast switching across renders with both pinned.

Custom-style prompts work across multiple image models. The current set with explicit custom-style support: Flux Pro Kontext, Flux2 Pro, Nano Banana Pro, Nano Banana 2, and GPT Image 2. The strength of the effect varies model to model.

## How to create a custom style

{% stepper %}
{% step %}

#### Open the Style tab and pick the custom-style flow

The Style tab's picker has **+ New Style** as the first panel. Click it. A modal opens.
{% endstep %}

{% step %}

#### Name the style

The modal opens with a **Name** field at the top. Pick something descriptive ("Mobius ligne claire", "Agency house warm grade") rather than generic. The name is what you'll see in the picker later.
{% endstep %}

{% step %}

#### Upload 3-10 reference images

Drop reference images into the zone or click **Choose file** to browse. The recommended count is 3-10. The system note says "For best results, choose images with clear lighting, consistent subjects, and minimal motion." Stills work better than video frames.
{% endstep %}

{% step %}

#### Add prompt notes

Click **add prompt notes** to attach descriptive prose to the style. A few sentences a cinematographer or illustrator would use: *"Mobius-influenced ligne claire illustration with flat color planes and minimal shading."* The prose is what the model reads on every render; the images anchor it.
{% endstep %}

{% step %}

#### Click Create

The modal's footer has **Cancel** and **Create**. Create saves the style to your library and closes the modal. The new style appears in the Style tab's picker for future renders.
{% endstep %}
{% endstepper %}

## How custom styles flow at render time

```mermaid
flowchart LR
    A[Custom style: prose] --> C[Visualizer Style tab]
    B[Custom style: reference images] --> C
    C --> D[Diffusion model]
    D --> E[Render in your style]
```

The model receives both the prose and the reference images at generation time. The combination produces tighter results than prose alone (which is generic) or images alone (which can be misinterpreted).

## When to reach for it

* **You've used the same custom prose three times in the Style tab.** Save it as a custom style so the next render is one click instead of three minutes of typing.
* **The team needs to share a brand look.** Save at the team level; everyone gets it.
* **You're delivering a campaign.** Pin the campaign's custom style; every render uses it. Brand consistency across hundreds of variations.

When not to reach for it:

* **One-off renders.** If you'll only use this look once, don't bother saving. Edit the Style tab in place.
* **Looks that vary heavily by shot.** If every shot wants different surface treatment, custom styles are overhead. Use the preloaded preset library and the Style tab's edit-in-place workflow.

## Personal vs team styles

Two scopes:

| Scope    | Visible to                            | Use for                                                                     |
| -------- | ------------------------------------- | --------------------------------------------------------------------------- |
| Personal | Just you                              | Your own experiments, looks you're prototyping                              |
| Team     | Everyone in the active team workspace | Brand looks, campaign styles, anything the team needs to apply consistently |

Switching between personal and team workspaces (see [Workspaces](/teams-and-billing/workspaces.md)) swaps which custom-style library is visible. A style saved at the team level only appears when you're in that team's workspace.

## Limits and known issues

* **Reference images are not used by every model.** Most image models honor them; some video models ignore them. Confirm against your target model.
* **Custom styles don't auto-update.** If you tweak the prose or the reference images, existing renders aren't regenerated. The change applies to future renders only.
* **No version history.** A custom style holds its current state; previous versions aren't recoverable. Save copies if you want to fork.
* **No export path.** You can import a custom style into a workspace, but there's no flow to export one out. Moving a style between teams means re-creating it from the original references in the destination workspace.

## Related

* [Style presets](/visualize/style-presets.md)
* [Lighting presets](/visualize/lighting-presets.md)
* [LoRAs](/build/loras.md): for cases that need fine-tuned model bias rather than custom prompt prose.
* [Workspaces](/teams-and-billing/workspaces.md)


---

# Agent Instructions: 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:

```
GET https://help.intangible.ai/visualize/custom-styles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.