Pixverse Transition is Pixverse's first/last-frame video model on Versely. This page is its structured prompting reference: the 9 parameters its schema actually exposes, the first-last-frame 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 Pixverse Transition, the page says so.
What Pixverse Transition 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 |
|---|---|---|
promptreq | Text prompt | string |
first_image_urlreq | First frame | string |
end_image_urlreq | Last frame | string |
aspect_ratio | Aspect ratio | 16:9 · 4:3 · 1:1 · 3:4 · 9:16default: 16:9 |
resolution | Resolution | 360p · 540p · 720p · 1080pdefault: 720p |
duration | Seconds | 5 · 8 · 10default: 5 |
negative_prompt | Exclusions | string |
style | Visual style | anime · 3d_animation · clay · comic · cyberpunk |
generate_audio_switch | Audio | boolean |
Technique that applies here
First/last-frame and transition: describing the in-between motion
- All three models in this family are built around two fixed images, and the prompt is connective tissue between them, not a description of either end. veo-first-last-frame requires both first_frame_url and last_frame_url; Pixverse Transition requires both first_image_url and end_image_url; and the general VEO 3.1 endpoint can do the same job on its kie provider variant by setting generationType=FIRST_AND_LAST_FRAMES_2_VIDEO with imageUrls=[first,last] (exactly two). Describe the transformation, not either endpoint — the images already fix those.
- None of the three schemas in this family expose a transition-type or easing parameter — there's no 'match cut' / 'morph' / 'wipe' enum anywhere (Pixverse Transition's style enum — anime/3d_animation/clay/comic/cyberpunk — is a visual style, not a transition type). The nature of the transition lives entirely in your prose, which makes this the one family block where the prompt text is doing more of the work than any parameter is; be explicit ('dissolves into,' 'match-cuts to,' 'smoothly morphs into') rather than assuming a toggle exists.
- The field names for the two images are not interchangeable across models — veo-first-last-frame uses first_frame_url/last_frame_url, Pixverse Transition uses first_image_url/end_image_url, and VEO 3.1's own kie-provider fold reuses its general imageUrls array plus a generationType flag instead of dedicated fields. Confirm the exact param names for the specific model before wiring the two images in.
Copy-ready templates
Replace the bracketed slots; each template says when it's the right shape.
Over [N] seconds, [SUBJECT] moves from [STATE A] to [STATE B] in one continuous motion, no cuts.
Use when: the family's short fixed-duration enums (VEO's 4s/6s/8s, Pixverse's 5s/8s/10s) — one connective arc sized to the real clip length, not a multi-beat sequence.
[TRANSITION PROMPT TEXT]. Style: [anime / 3d_animation / clay / comic / cyberpunk]. Negative prompt: [ELEMENTS TO EXCLUDE].
Use when: pixverse-transition, which exposes a style enum and a separate negative_prompt field alongside the two required images.
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 Pixverse Transition'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
- Describing either endpoint in detail — the two images already define the start and end state; re-describing 'a red flower in a vase' when the first image already shows exactly that wastes prompt budget instead of directing the change.
- Assuming a first-last-frame variant automatically shares its parent t2v/i2v sibling's duration or aspect enum — it often does (veo-first-last-frame keeps VEO 3.1's up-to-8s cap; Pixverse Transition reuses the standard Pixverse 5s/8s/10s enum), but that's a fact to verify per model in its own schema, not a rule to assume blindly.
- Using the wrong field name for the second image — first_frame_url/last_frame_url (VEO), first_image_url/end_image_url (Pixverse), or the general imageUrls array plus a generationType flag (VEO 3.1's own kie fold) aren't interchangeable; the wrong key name means the second image is silently dropped rather than erroring.
The long-form guide
This page is the structured reference. For the essay treatment — worked examples, failure modes, and narrative — read PixVerse Prompting: Stylized Video That Lands.
Frequently asked questions
Does Pixverse Transition 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 Pixverse Transition support?+
The aspect_ratio parameter is an enum: 16:9, 4:3, 1:1, 3:4, 9:16. Set the parameter — describing the frame shape in prose does nothing on its own.
How long can a Pixverse Transition generation be?+
Duration is a hard enum: 5, 8, 10. Write one continuous beat sized to the window you pick, not a script the model will compress.
How does the Versely agent know Pixverse Transition'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.
Related prompting guides
Generate with Pixverse Transition
Pixverse Transition 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.