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
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
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
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.
Video models
Veo 3.1
Wide latitude, slow generation. Best for atmospheric long-take shots where motion is naturalistic and you have time to wait.
Veo 3.1 Fast
Faster Veo at lower fidelity. Iteration-tier for atmospheric shots.
Kling 2.0 Master
Kuaishou
Legacy master tier. Still supported; useful when consistency with previously rendered shots matters.
Kling 2.1 Standard
Kuaishou
The everyday Kling. General-purpose, balanced cost vs quality.
Kling 2.1 Pro
Kuaishou
Standard pro-tier video generation. Earlier-generation; Kling 2.6 Pro is the default action-shot reach today.
Kling 2.1 Master
Kuaishou
Higher fidelity than Standard or Pro at the cost of generation time.
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.
Luma Ray 3
Luma
Honors authored 3D structure most strictly. Reach for it when your shot has animated meshes, splined cameras, or specific motion the model needs to follow rather than reinterpret.
Runway Gen 4.5
Runway
Alternative video model. Different tonal register than Kling and Veo; useful for stylistic variation.
Seedance 2.0
ByteDance
Motion-strong model with first-and-last-frame support. Useful when the brief calls for fluid action and you want to hand the model two anchor frames.
Which AI model should I use?
Direct answers per common job:
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
Honors keyframed and splined motion most strictly.
First-and-last-frame video interpolation
Veo 3.1, Kling 2.6 Pro or later, or Seedance 2.0
These three model families currently support end frames. See First and last frame.
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.
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. Pick the closest-named successor (Kling 2.6 Pro replacing Kling 2.6, for instance) and re-render to confirm the look survives.
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.
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.
Watch
Provider documentation
Each provider has its own deeper docs for what their models can and cannot do at the system-prompt level:
Black Forest Labs Flux: bfl.ai
Google Veo: aistudio.google.com/models/veo-3
Kuaishou Kling: kling.ai
Luma Ray: lumalabs.ai/ray
Runway: runwayml.com
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.
Related
Last updated
Was this helpful?