LTX 2 Pro is LTX's image-to-video model on Versely. This page is its structured prompting reference: the 7 parameters its schema actually exposes, the i2v technique that applies to it, copy-ready templates.
Everything here is grounded in the same sources Versely's agent reads — the model's input schema. Where a line is general craft advice rather than a documented fact about LTX 2 Pro, the page says so.
What LTX 2 Pro wants
The exact input surface, from the same schema the Versely agent fetches with get_model_input_schema before every generation.
| Parameter | What it does | Values |
|---|---|---|
image_urlreq | Start frame (jpg/jpeg/png/webp/gif/avif) | string |
promptreq | Text prompt | string |
duration | Seconds (4-12) | integer (min 4, max 12)default: 8 |
aspect_ratio | Aspect ratio (auto infers from image) | auto · 16:9 · 9:16 · 1:1default: auto |
resolution | Output resolution | 1080p · 1440p · 2160pdefault: 1080p |
generate_audio | Generate audio | booleandefault: true |
negative_prompt | Exclusions | string |
- — Schema skeleton — verify enums before strict mode
Technique that applies here
Image-to-video: animating a start frame; motion description relative to the input image; UGC hook pool applies
- Aspect ratio usually isn't a settable parameter in image-to-video mode — it's inherited from your source image. Vidu Q3's runpod schema note is explicit: 'No style/aspect_ratio fields in I2V — aspect ratio is inferred from the input image.' Pixverse 5.6 I2V's note says the same thing: 'I2V infers aspect_ratio from image (no aspect_ratio field).' Wan's i2v schemas (2.7, and the folded Wan 2.5 variants) all omit an aspect_ratio param entirely; two of its provider variants confirm this directly in their own schema notes — kie's says 'inferred from image', replicate's says 'aspect is derived from the input image.' Crop or compose your source image to the aspect you want before you upload it; asking for '16:9 widescreen' in the prompt text does nothing on these schemas.
- The prompt describes motion relative to what the image already shows, not the scene itself. Vidu's own param description for its i2v prompt field is literally 'Text description of the desired motion and action' — contrast a text-to-video prompt, which has to establish the whole scene from nothing. General craft, not a schema fact: name what changes — a hand reaches, a head turns, hair moves in wind — rather than re-describing the subject or setting the photo has already fixed, which just competes with the image for the model's attention instead of directing it.
- Several i2v schemas quietly accept a second, optional 'end' image alongside the required start image — Vidu Q3's fal variant (end_image_url, described as generating a transition), Kling Video V3 Standard Image to Video's fal variant (end_image_url), LTX 2.3 Image to Video Pro (a model folded into the LTX 2 Pro page; end_image_url), and Wan 2.7 Image to Video (last_frame_url). If you supply one, write the prompt as the path between the two states, not as 'what happens next' from a single photo — you're now effectively writing a first-last-frame prompt inside an i2v call.
Copy-ready templates
Replace the bracketed slots; each template says when it's the right shape.
[WHAT MOVES — e.g. 'she turns her head toward camera and smiles'], [SECONDARY MOTION DETAIL — e.g. 'hair drifts in a light breeze']. Camera: [static / slow push-in / slight handheld].
Use when: i2v models whose schema infers aspect ratio from the source image (Vidu, Pixverse, Wan) — crop the source image to your target aspect first, then spend the whole prompt on motion, not framing.
[STATE A DESCRIPTION] transitions into [STATE B DESCRIPTION] as [WHAT CHANGES IN BETWEEN].
Use when: you've supplied both a start image and an optional end/tail image (Vidu's end_image_url, Kling Video V3's end_image_url, LTX 2.3 Image to Video Pro's end_image_url, Wan 2.7's last_frame_url) — describe the whole path, not a single continuation.
How the Versely agent does this automatically
You can use this page by hand, or let the agent apply the same knowledge. Four real mechanisms — no more, no less:
get_model_input_schema— before generating, the agent looks up LTX 2 Pro's exact input fields, required fields, allowed values, defaults, and min/max bounds. The parameter table above is that same surface.- The prompt enhancer's family rules — 12 per-family rewrite rules (this model's family isn't one of the 12, so only general enhancement applies) shape how a rough prompt gets rewritten.
- The per-provider speech guide — for TTS scripts, the agent follows a provider-specific tag scheme — not relevant to this model, but it's why voiceover scripts come out marked up correctly.
expand_movie_scene— in movie flows, brief scene ideas are rewritten into detailed cinematic descriptions before generation.
Mistakes that waste generations
- Asking for a specific aspect ratio in the prompt when the schema doesn't expose an aspect_ratio param — it's silently ignored; on Vidu, Pixverse, and Wan's i2v variants the frame shape comes entirely from the source image you upload.
- Re-describing the subject or scene the source image already shows instead of focusing on the motion — wastes prompt budget and can conflict with the photo (a different outfit or background than what's actually in frame).
- Treating every 'image-to-video' model as the same shape: sending a HeyGen-style voice/talking_style prompt to Vidu, or a plain motion-description prompt to HeyGen, targets a control surface that model doesn't expose.
The long-form guide
This page is the structured reference. For the essay treatment — worked examples, failure modes, and narrative — read LTX 2.3 Prompting Guide: Fast Iteration Patterns.
This guide also covers
These siblings share LTX 2 Pro's prompting-relevant input surface, so their prompting URLs resolve here — tier and pricing differences live on their own model pages:
Frequently asked questions
Does LTX 2 Pro support negative prompts?+
Yes — the schema exposes negative_prompt. Put exclusions there instead of writing "no text, no watermark" into the main prompt.
Which aspect ratios does LTX 2 Pro support?+
The aspect_ratio parameter is an enum: auto, 16:9, 9:16, 1:1. Set the parameter — describing the frame shape in prose does nothing on its own.
How long can a LTX 2 Pro generation be?+
Duration is bounded (min 4, max 12). Write one continuous beat sized to that window rather than a multi-act script.
How does the Versely agent know LTX 2 Pro's parameters?+
Before generating, the agent calls its get_model_input_schema tool, which looks up the exact input fields, required fields, allowed values, defaults, and min/max bounds for the model. Nothing on this page is guessed — it is the same schema surface those tools read.
Does this guide also cover LTX 2 and LTX 2.3 Image to Video Pro?+
Yes. LTX 2, LTX 2.3 Image to Video Pro share the same prompting-relevant input surface as LTX 2 Pro, so their prompting URLs redirect here instead of duplicating this page. Tier and pricing differences live on each model's own /models page.
Related prompting guides
Generate with LTX 2 Pro
LTX 2 Pro is live in Versely — paste a template above, or just describe what you want and let the agent map it onto the schema for you.