Kling 3.0 Omni belongs to the reference-led branch of the 3.0 family.
Reference is more than a thumbnail
The vendor guide describes multiple reference types, including images, referenced subjects and a recorded video used to establish a subject. It contrasts those capabilities with the older O1 product, which it lists at a maximum of ten seconds rather than the Omni generation limit of 15 seconds. Model documentation is therefore essential when a production template will be reused across months.
Construct an authorized subject
Begin with a subject card and the permission record for the performer, product or scene. Choose clean reference angles that describe the same design instead of unrelated photographic styles. A front-facing portrait and an oblique view can help the prompt express an intended identity, but vendor promotional language about persistence does not prove that a distinctive mole, earring or shirt stripe will survive every shot. For continuity-critical assets, keep an independent frame-by-frame review.
The reference-video and native-audio trade-off
The official 3.0 API specification expressly notes a mutually exclusive relationship between reference-video input and native audio generation for `kling-v3-omni` at that documented revision. Do not build a workflow that silently sets both and assumes the service will reconcile them. One pathway prioritizes motion or subject evidence and adds approved sound later. The other prioritizes native sound and a separately allowed visual control. Production should log the selected pathway as structured metadata.
Shot construction and review
Imagine a 10-second museum presenter introducing an artifact across two angles. Provide approved outfit and room references, script a single thought, and select an audio strategy before generation. Review the generated turn of the head, eye-line, continuity of the object, language intelligibility and any unexpected resemblance. For a recurring presenter, retain stable project-specific frames, not just prompts. Keep a human reviewer empowered to reject an attractive but visually inconsistent take.
What the specification does not prove
Reference quantity, request size, plan limits, region and per-second cost must be resolved against the current endpoint and tenant agreement. The public guide is evidence of a capability family, not evidence that it is enabled in every account. API changelog entries can also move or rename parameters. Record the exact `model_name`, endpoint revision and output metadata. Confirm rights to the source actor and upload, and never repurpose one person’s recorded gestures or voice without permission.
Relevant alternatives and trade-offs
Ordinary Kling 3.0 may be simpler for text-driven multishot. For deterministic lip sync after editing, a specialized approved dubbing stage can be easier to audit than regenerating an entire scene.