For the complete documentation index, see llms.txt. This page is also available as Markdown.

Models

Every image and video model the visualizer exposes, with one-line guidance on when to reach for each.

The visualizer is a model aggregator: under the hood, every Generate Image and Generate Video click routes to one of several diffusion models from external providers. The dropdown is the working set, refreshed as providers ship new versions and as some get retired.

This page is the working reference. Pick a model based on what your shot needs; the table below has one-line guidance per model.

Image models

Model
Provider
When to reach for it

Flux Pro Kontext

Black Forest Labs

Photoreal stills with strong material rendering. Metallic, glass, and complex surfaces hold up well. Reference-image-conditioned and disciplined about it.

Flux2 Pro

Black Forest Labs

Next-generation Flux. Cleaner subjects, finer detail, better at rendering text in the image when text matters.

Nano Banana Pro

Google

The cinematic workhorse. Strongest with image references, especially for character consistency across shots. Default reach for hero shots when you have reference imagery.

Nano Banana 2

Google

Sharper than Pro on certain stylized treatments. Picky about prompts; rewards specificity.

GPT Image 2

OpenAI

OpenAI's image model in the working set. Different stylistic register from the Flux and Nano Banana families; useful as an alternative when the others flatten the subject.

Seedream 5 Pro

ByteDance

Holds composition harder than anything else in the working set. Reach for it when the shot you framed has to survive the render intact, and when detail named in the description needs to outrank the reference images on everything except identity.

Video models

Model
Provider
When to reach for it

Veo 3.1

Google

Wide latitude, slow generation. Best for atmospheric long-take shots where motion is naturalistic and you have time to wait.

Veo 3.1 Fast

Google

Faster Veo at lower fidelity. Iteration-tier for atmospheric shots.

Kling 2.5 Turbo

Kuaishou

Fast iteration. Use when you're cycling through compositions and want feedback in seconds.

Kling 2.6 Pro

Kuaishou

Action-shot strong. Reach for it on motion-heavy shots.

Kling 3 Standard

Kuaishou

Latest Kling family standard tier.

Kling 3 Pro

Kuaishou

Latest Kling family pro tier.

Kling 3 (4K)

Kuaishou

The 4K tier of the Kling 3 family, on its own endpoint. Reach for it when the deliverable needs 4K out of the visualizer rather than an upscale afterwards.

Kling o3 Pro

Kuaishou

Available for both image-to-video and video-to-video. Takes up to eight reference images named in the prompt. Reach for it when a video shot has to honor specific reference imagery.

Omni Flash

Google

Available for both image-to-video and video-to-video, with generated audio and an optional end frame on the image-to-video path. Takes up to eight reference images. Video-to-video sources are capped at 10 seconds.

Luma Ray 3.14

Luma

Available for both image-to-video and video-to-video. Honors authored 3D structure strictly, so it is the reach when your shot has animated meshes, splined cameras, or specific motion the model should follow rather than reinterpret. Video-to-video sources are capped at 18 seconds.

Luma Ray 3.2

Luma

Video-to-video model. Takes an existing video as input and reskins or extends it while respecting the source motion. Higher fidelity; use when output quality matters more than cost. Video-to-video sources are capped at 18 seconds.

Runway Gen 4.5

Runway

Alternative video model. Different tonal register than Kling and Veo; useful for stylistic variation.

Seedance 2.0

ByteDance

Available for both image-to-video and video-to-video. Motion-strong with first-and-last-frame support and up to seven reference images. Strong for photorealistic, faithful output – a good reach for technical or aerospace work where the render needs to stay true to the source.

Tuning Luma for technical and aerospace work. Luma exposes a creativity control. Set it to Adhere with the strength low when faithfulness to the source geometry matters – it keeps the render true to what you built. Reimagine gives the model far more license and will invent elements that aren't in your scene, so keep it away from technical work. For faithful output, Seedance 2.0 is also a strong choice.

Some models run on both paths, some only on one. Ray 3.14, Omni Flash, Kling o3 Pro and Seedance 2.0 each appear for image-to-video and for video-to-video. Ray 3.2 is video-to-video only. Video-to-video takes an existing clip as the source input rather than generating from the scene, so use it to restyle, extend, or relight footage you already have. The mode and strength control (Adhere → Reimagine) behaves the same on either path: low Adhere keeps the motion faithful to the source; Reimagine lets the model depart significantly from it.

Which AI model should I use?

Direct answers per common job:

If your shot is
Reach for
Why

Brand-true product hero with reference imagery

Nano Banana Pro

Strongest reference-image conditioning. Holds character and product across shots.

Photoreal still with complex materials (glass, metal, fabric)

Flux Pro Kontext

Best surface fidelity. Disciplined about reference images.

In-image text rendering matters (signage, packaging)

Flux2 Pro

Cleanest text generation in the working set.

Stylized illustration or graphic look

Nano Banana 2

Sharper on stylized treatments. Reward specificity in the prompt.

Atmospheric long-take video, naturalistic motion

Veo 3.1

Wide latitude. Slow but the best for ambient mood.

Action-heavy video with motion

Kling 2.6 Pro

Action-shot strong. The chase-and-vehicle workhorse.

Authored 3D motion needs to be honored exactly

Luma Ray 3.14

Honors keyframed and splined motion most strictly.

Composition has to survive the render intact

Seedream 5 Pro

Holds the framing you built harder than the rest of the image working set.

First-and-last-frame video interpolation

Veo 3.1, Kling 2.6 Pro or later, Seedance 2.0, or Omni Flash

These model families support end frames. See First and last frame.

Video shot that has to follow specific reference imagery

Omni Flash, Kling o3 Pro, or Seedance 2.0

These carry reference images into video prompts. See Generate video.

Video with generated audio

Omni Flash or Veo 3.1

Both generate a synchronized audio track. Audio adds cost on top of the render.

4K video straight out of the visualizer

Kling 3 (4K) or Luma Ray 3.14

The two 4K paths in the working set. See Resolution and cost.

Video-to-video (restyle or extend an existing clip)

Luma Ray 3.2, Luma Ray 3.14, Omni Flash, Kling o3 Pro, or Seedance 2.0

Supply a source video; the model reskins or extends it. Ray 3.2 for final quality, Ray 3.14 for iteration.

Fast iteration on a video composition

Kling 2.5 Turbo or Veo 3.1 Fast

Seconds-tier feedback.

Nano Banana Pro vs Flux Pro Kontext

The two most-asked-about image models. Both are reference-image-disciplined; they differ in what they're tuned to honor.

Nano Banana Pro
Flux Pro Kontext

Reference fidelity

Cinematic; consistent across shots

Photographic; consistent within a shot

Material rendering

Strong on warm tones, skin, fabric

Strongest on glass, metal, complex surfaces

Best for

Hero shot with character or product references

Hero shot with material-heavy products

Cost tier

Standard

Standard

Default reach when both fit

Cross-shot consistency wins

Single-shot material accuracy wins

For a campaign that needs multiple shots of the same product, Nano Banana Pro. For a one-shot hero of a watch, Flux Pro Kontext. For both at once, render the multi-shot story on Nano Banana Pro and the watch macro on Flux Pro Kontext.

What to do past the first pass

The answer is always "test against your specific shot". Different models honor different prompt languages differently; what reads cleanly on Nano Banana 2 may flatten on Flux2 Pro and vice versa. Burn 1K iterations comparing before committing video credits.

When models change

The model list churns. Providers ship new versions, sometimes retire older ones, occasionally pull capabilities out of free or lower tiers. The visualizer's dropdown is authoritative for what's currently available; this page tracks the names and the rough heuristics.

If a model you've been using disappears from the dropdown, the most likely reason is the provider deprecated it.

You don't have to hunt for the replacement yourself. When a saved shot points at a model the working set doesn't carry, regeneration routes to a configured successor and an in-app banner names the substitution before the render runs.

The same banner appears when a team admin has restricted the model you picked. Read the banner: the shot you get back came from a different model than the one stored on the shot, so the look can shift. If it matters, pick the successor deliberately and re-render.

Models the visualizer routes away from, and where they land:

Stored on the shot
Regenerates on

Kling 2.0 Master

Kling 3 Pro

Kling 2.1 Standard

Kling 3 Standard

Kling 2.1 Pro

Kling 3 Pro

Kling 2.1 Master

Kling 3 Pro

Luma Ray 3

Luma Ray 3.14

Luma Ray 2

Luma Ray 3.14

Luma Ray 2 Flash

Luma Ray 3.14

Older names you may see in transcripts

Some YouTube tutorials and webinar talks reference earlier model names. The mapping:

  • Kling 2.6 in the older transcripts is now Kling 2.6 Pro.

  • Kling 2.0 and Kling 2.1 in either the Standard, Pro, or Master tier map to the Kling 3 family.

  • Luma Ray 3, Ray 2, and Ray 2 Flash map to Luma Ray 3.14.

  • Seedance 2.0 Motion Guide is the video-to-video path of Seedance 2.0.

  • Flux 1 Depth (referenced in summit talk) is superseded by Flux Pro Kontext for general use.

  • Flex (mentioned in passing) was an older naming; see Flux Pro Kontext or Flux2 Pro for the current Black Forest Labs lineup.

Use the current names everywhere in your work. The older names will still appear in older tutorial videos until the team re-records.

Image model dropdown expanded with provider-grouped options: Black Forest Labs (Flux Pro Realtime, Fast Pro) and Google (Nano Banana Pro, Nano Banana 2)

Watch

Provider documentation

Each provider has its own deeper docs for what their models can and cannot do at the system-prompt level:

Most users won't need the provider docs; the visualizer abstracts away most provider-specific syntax. For specialized model behaviors not exposed in Intangible's UI, the provider docs are the next stop.

Last updated

Was this helpful?