Which reference inputs do current video-generation vendor docs accept for keeping a character or subject the same across separate generations, and what limits and failure cases do they state?
Corrected 2026-10-24 - see CUR-0618-02; the original statements below are kept for history and are superseded where the correction says so. Vendor docs read on 2026-10-22 offer three different mechanisms, not one: (a) reference images that condition a generation (Google Veo 3.1: up to 3 images of a person, character or product, and 8 s output only; Runway's hosted third-party models: e.g. up to 7 for Kling O3, 10 images plus 5 videos plus 5 audio for WAN 3.0), (b) first/last or multi-position keyframes (Luma Ray 3.2: 1-64 keyframes, exclusive with start/end frame), and (c) a reusable character asset (OpenAI Sora, non-human only, name must be in the prompt; the Sora API was shut down on 2026-09-24). None of the pages read publishes a measurement of cross-shot identity; Runway's own Gen-4 / Gen-4.5 image-to-video entries list only a single prompt image in the docs read. Vendor statements are claims; Kling's docs could not be read.
Structured fields
{
"citations": [
{
"url": "https://ai.google.dev/gemini-api/docs/veo.md.txt",
"note": "candidate evidence excerpts"
},
{
"url": "https://ai.google.dev/gemini-api/docs/video.md.txt",
"note": "candidate evidence excerpts"
},
{
"url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/video/generate-videos-from-references",
"note": "candidate evidence excerpts"
},
{
"url": "https://ai.google.dev/gemini-api/docs/omni.md.txt",
"note": "candidate evidence excerpts"
},
{
"url": "https://docs.dev.runwayml.com/assets/inputs/",
"note": "candidate evidence excerpts"
},
{
"url": "https://docs.dev.runwayml.com/recipes/reference-media/",
"note": "candidate evidence excerpts"
},
{
"url": "https://docs.dev.runwayml.com/recipes/multi-shot-video/",
"note": "candidate evidence excerpts"
},
{
"url": "https://developers.openai.com/api/docs/guides/video-generation.md",
"note": "candidate evidence excerpts"
},
{
"url": "https://docs.agents.lumalabs.ai/guides/videos/generation/index.md",
"note": "candidate evidence excerpts"
}
]
}Evidence claims
- [sourced_fact] Vendor docs read on 2026-10-22 offer three different mechanisms, not one: (a) reference images that condition a generation (Google Veo 3.1: up to 3 images of a person, character or product, and 8 s output only; Runway's hosted third-party models: e.g. up to 7 for Kling O3, 10 images plus 5 videos plus 5 audio for WAN 3.0), (b) first/last or multi-position keyframes (Luma Ray 3.2: 1-64 keyframes, exclusive with start/end frame), and (c) a reusable character asset (OpenAI Sora, non-human only, name must be in the prompt; the Sora API was shut down on 2026-09-24). None of the pages read publishes a measurement of cross-shot identity; Runway's own Gen-4 / Gen-4.5 image-to-video entries list only a single prompt image in the docs read. Vendor statements are claims; Kling's docs could not be read. · locator: candidate evidence excerpts source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |
Linked records
- cites → https://ai.google.dev/gemini-api/docs/omni.md.txt
- cites → https://ai.google.dev/gemini-api/docs/veo.md.txt
- cites → https://ai.google.dev/gemini-api/docs/video.md.txt
- cites → https://developers.openai.com/api/docs/guides/video-generation.md
- cites → https://docs.agents.lumalabs.ai/guides/videos/generation/index.md
- cites → https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/video/generate-videos-from-references
- cites → https://docs.dev.runwayml.com/assets/inputs
- cites → https://docs.dev.runwayml.com/recipes/multi-shot-video
- cites → https://docs.dev.runwayml.com/recipes/reference-media