Dashboard

Image and video presets

Save a reusable look, test it and bind it to the agents and workflows that need it.

Before you begin

You need a business workspace and owner or dashboard editor access. Presets separate the scene from its reusable visual or motion direction. Agents see the name and when-to-use line; generation applies the saved recipe without exposing it to the agent.

Create an image preset

  1. Open Studio → Image presets.
  2. Choose New preset.
  3. Choose Blank preset.
  4. Enter Name and When to use in your workspace's language.
  5. Describe the desired medium, lighting, colours, materials and mood.
  6. Add persistent reference images from Workspace or upload them on the preset form.
  7. Choose the platform default model or pin an enabled image model.
  8. Set the default aspect ratio and lock it if every run must use that ratio.
  9. Save the preset.

Write a positive description rather than negative instructions. Keep the recipe concise; beyond about 1,500 characters, the style field warns that models may summarize it.

An image preset using the platform default follows future default changes. A pinned model stays fixed.

Its catalog shows supported resolution, reference limits, privacy facts and estimated Sparks. Run references count toward the same model limit.

Create a video preset

  1. Open Studio → Video presets.
  2. Choose New video preset.
  3. Choose Blank video preset.
  4. Enter Name and When to use.
  5. Write camera, motion, pacing and sound direction in Prompt.
  6. Choose the model and supported duration, resolution, ratio, audio and frame rate.
  7. Add persistent reference images if the model supports them.
  8. Save the preset.

Video presets start with the platform default, then pin the saved model. Frames and references follow current capabilities. Ask the Assistant for model-specific help; review its English prompt before saving.

Test before binding

  1. Open the preset's page.
  2. Enter a scene prompt in its test panel.
  3. Check the resolved image prompt, when testing an image preset.
  4. Select supported output settings and run inputs.
  5. Review the estimated Sparks.
  6. Generate a test.

Resolved image prompts cost nothing to preview. Tests offer one to four separately charged variants and up to three run-only references within the model’s remaining allowance.

Higher resolutions can cost more. Results save in the preset’s Studio folder.

Bind to an agent or workflow

  1. Open the agent's Connections canvas.
  2. Open the presets drawer's image or video section.
  3. Connect the presets it should use.
  4. Select a default when connecting several image presets.
  5. Enable the image-preset requirement if off-brand output must fail.

Without image bindings, the agent can generate preset-less. One preset applies automatically; several let it choose by when-to-use lines, falling back to the default. A required but unresolved preset fails generation.

No preset bound

Generates with no preset at all

One preset bound

Everything comes out in that look, with no choice to make

Several bound

It picks by reading each preset’s when-to-use line

What an agent generates depends entirely on what you bind to it.

In a workflow, select the preset inside the image step. Workflow image bindings also govern delegated agent steps; different steps can use different looks.

Rule — Connecting an agent's first video preset gives it the generateVideo tool; disconnecting the last removes it. Agent video always requires a bound preset. Account-attributed generation bills the shared pool.

Archive and restore

  1. Find the preset in Image presets or Video presets.
  2. Choose Archive from its actions menu to retire it.
  3. Enable Show archived to find retired presets.
  4. Choose Restore from the menu to reactivate one.

Presets are archived, not permanently deleted. Existing results retain their original recipe and folder name.

Archiving is refused if it would leave a target requiring an image preset without an active one. Archiving keeps bindings. Restoring reactivates those retained bindings; connections you removed need to be added again.