本文へ移動
cccskills
無料GitHub で公開

kling-ai

Write and improve prompts for Kling AI video generation, and pick the right Kling model for the job. Covers image-to-video, text-to-video, multi-shot storyboards, talking avatars from one photo plus audio, motion transfer, video editing of an existing clip, Element Reference for character consistency, Voice Control and voice cloning, native audio and dialogue, first/last frame control, credit and API costs, and troubleshooting failed generations.

インストール方法を見る

含まれるファイル(4)

  • SKILL.md30.6 KB
  • evals/evals.json4.6 KB
  • references/pricing.md8.5 KB
  • references/prompt-templates.md11.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Kling AI Video Generation

Source-of-truth for the facts in this skill: the official Kling release notes at kling.ai/release-note and the API pricing page at kling.ai/dev/pricing. Verified 2026-08-04. When numbers, durations, credit costs, or language lists matter for a deliverable, verify them there before quoting.

Scope: this skill covers Kling's video models. Kling also ships image models (the IMAGE 3.0 series, IMAGE O1, Image Series Mode, 2K/4K image output) - those are out of scope here; for still images use the nano-banana skill or check Kling's release notes directly.

Platform Access

Primary interface: app.klingai.com/global (or kling.ai/app)

Alternative platforms with Kling integration: Higgsfield, Pollo.ai, Fal.ai, Media.io, Artlist, Vidful.ai, Scenario, BasedLabs, LetzAI, PiAPI, kie.ai


Quick Start: Animate an Image in 60 Seconds

  1. Go to app.klingai.com/global - AI Videos - Image to Video
  2. Select VIDEO 3.0 (or VIDEO 3.0 Turbo if the shot has dialogue or you are generating a batch, or VIDEO 3.0 Omni if you have reference images / video elements to anchor identity)
  3. Upload your image
  4. Write a short motion prompt - describe only what moves, not the whole scene:
    Subtle breeze moves through hair. Eyes blink naturally. Camera static.
    
  5. Set duration: 5s for loops/social, 10-15s for narrative (3.0 supports up to 15s)
  6. Set output: 1080p Standard for drafts; switch to native 4K only for finals (4K costs ~30 credits/sec)

That's it. For model selection, advanced prompting, avatars, and multi-shot workflows - read on.


Model Lineup (as of August 2026)

ModelBest ForResolutionAudioMax DurationReleased
VIDEO 3.0Cinematic storytelling, multi-shot, native audio, multilingual dialogueup to 4KYes (5 langs)15s2026-01-31
VIDEO 3.0 TurboSame job as 3.0 but faster and cheaper per second; strongest audio-visual sync and lip-sync720p / 1080p (no 4K)Yes, always on15s2026-06-17
VIDEO 3.0 OmniVIDEO 3.0 capabilities + video element reference + element voice control + video editingup to 4KYes (5 langs)15s2026-01-31 (editing upgraded 2026-06-17)
VIDEO 3.0 Motion ControlMotion transfer with high facial consistency, including occlusions and multi-angle1080pOptional30s2026-03-04
Avatar 2.0Talking avatars from 1 image + 1 audio file, up to 5 minutes1080p / 48fpsLip-sync to provided audio5 min2025-12-04
Kling 2.6Older Native Audio pipeline (EN+ZH), good fast/budget option1080pEN + ZH10s2025-12-03
Kling 2.5 TurboFastest, simplest scenes, draft work1080pNo10searlier

Important clarification on the 3.0 Series: "Kling 3.0" is a series name, not a single model. It contains VIDEO 3.0 (upgrade path from VIDEO 2.6), VIDEO 3.0 Turbo (the efficiency variant, added 2026-06-17) and VIDEO 3.0 Omni (upgrade path from the older VIDEO O1). All share the unified multimodal training framework; Omni adds video element reference, element voice control and video editing. Third-party reviews sometimes merge them into one - the official release notes do not.

What VIDEO 3.0 Turbo actually changes (2026-06-17)

Per the official release note, Turbo is positioned as "the right balance between efficiency and quality" - not a downgrade:

  • Quality held, not cut - consistent performance in visual quality, motion dynamics and prompt adherence; it "accurately follows multi-shot storyboard logic, ensuring smooth continuity and a unified visual style across scenes."
  • Best-in-family audio-visual sync - "highly accurate alignment between audio and visuals, with smooth and natural lip sync", and it "maintains stable synchronization even in longer videos." The release note names the use cases: talking-head content, voice-driven storytelling, character-based formats.
  • Faster and cheaper at scale - explicitly aimed at "reducing the overall cost of scaled creation." Confirmed on the API price list: 1080p with native audio at 1.0 Unit/s vs. 1.2 Units/s for VIDEO 3.0 with audio.
  • No 4K tier. The API price list has no 4K column for Turbo. If the deliverable is 4K, use VIDEO 3.0 or Omni.
  • Native audio is always on for Turbo in the price list (there is no audio-off row), so budget accordingly.

Practical rule: if the shot is a person talking, or you are generating many clips of a series, start on Turbo. If it is a 4K hero shot, use VIDEO 3.0. If identity must hold across shots from a reference video, use Omni.

Model Selection Guide

Choose VIDEO 3.0 when:

  • Text-to-video or image-to-video from prompts/images you already have
  • Need multi-shot sequences (3.0 introduced multi-shot - 2.6 did not have it)
  • Want native multilingual audio (Chinese, English, Japanese, Korean, Spanish) with dialects/accents
  • Need start-frame + element reference, or multi-character coreference (3+ characters)
  • Working up to 15s, flexible duration
  • Default choice for prompt-driven work

Choose VIDEO 3.0 Turbo when:

  • The subject is talking - dialogue, presenter, voice-over-driven narrative (best lip-sync and A/V sync in the family)
  • You are generating a batch: a series of clips, many variants, or a full storyboard where per-second cost compounds
  • You want 3.0-class quality and multi-shot continuity without paying the 4K-capable tiers
  • Not when you need 4K output - Turbo has no 4K tier

Choose VIDEO 3.0 Omni when:

  • Have a reference video (not just images) to anchor character/scene
  • You want to edit an existing video rather than generate from scratch (see Video Editing below)
  • Want to add voice to specific elements (Element Voice Control)
  • Need the strongest cross-shot consistency for commercial work
  • Same other capabilities as VIDEO 3.0 (text-to-video, image-to-video, native audio, multi-shot, 15s)

Choose VIDEO 3.0 Motion Control when:

  • Have a reference action video and want to transfer the motion to your character
  • Need high facial consistency across angles/emotions/occlusions
  • Need up to 30s of motion-controlled output (vs. 15s on regular 3.0)
  • Built on 2.6 Motion Control, now with facial element binding

Choose Avatar 2.0 when:

  • Need a talking-head video (presenter, explainer, music performance)
  • Have one image of the person and an audio track (recorded or AI-generated)
  • Need duration up to 5 minutes (much longer than VIDEO 3.0's 15s)
  • The face/voice IS the content - camera and scene are secondary

Choose Kling 2.6 when:

  • Need synchronized native audio in English or Chinese with the older pipeline
  • Lower credit budget than 3.0

Choose 2.5 Turbo when:

  • Rapid prototyping, simple 3-4 element scenes, no audio needs

Core Workflows

Image-to-Video

  1. Navigate to AI Videos - Image to Video
  2. Select VIDEO 3.0 (or VIDEO 3.0 Omni for reference-heavy work)
  3. Upload image (min 300x300px, max 10MB, JPG/PNG/WEBP)
  4. Write a motion-focused prompt - describe only what moves (the scene already exists in your image)
  5. Optionally set an end frame to control where motion resolves
  6. Set duration (5s for loops/social, up to 15s for narrative)
  7. Set aspect ratio to match source image
  8. Render at 1080p first to verify; switch to 4K only for final delivery

Text-to-Video

  1. Navigate to AI Videos - Text to Video
  2. Select VIDEO 3.0
  3. Write prompt in this structured order: Scene - Characters - Action - Camera - Audio & Style
  4. Optionally use multi-shot mode to define each shot separately
  5. Set duration (3-15s), aspect ratio, quality
  6. Render at 1080p for review; 4K only for final

Talking Avatar (Avatar 2.0)

The headline feature of Avatar 2.0: one image + one audio file → talking avatar with synchronized expressions, body language, and hand gestures. Up to 5 minutes of continuous output for any scenario (knowledge sharing, song performance, advertising, storytelling).

  1. Navigate to AI Avatar (or via fal.ai / PiAPI / kie.ai API endpoints)
  2. Upload a reference image - good lighting, face clearly visible
  3. Upload an audio track - speech, narration, singing. Recorded or AI-generated (e.g., ElevenLabs)
  4. Optional: short text prompt for tone or framing (e.g., "calm professional presenter, minimal gestures")
  5. Generate

What 2.0 improved over 1.0:

  • Enhanced performance and motion quality - body movements, gestures, expressions, camera angles
  • Stable, clear hand movements (the main fix vs. 1.0's notorious hand artifacts)
  • Up to 5 minutes of continuous output for any scenario

Note on languages: Kling officially lists multilingual support for Avatar 2.0 as English, Japanese, Korean, Chinese. However, the model lip-syncs to whatever audio file you provide - it uses your audio as the reference, not just trained-language detection. Field-tested confirmation: Polish audio (e.g., ElevenLabs-generated) works and produces correct lip-sync. Other non-listed languages will likely work too. Practical guidance: don't tell the user "your language isn't supported" - if they have a good audio file, try it. Worst case the sync is slightly off and a paid generation is wasted; best case (most common) it works perfectly.

When NOT to use Avatar 2.0: When you need full scene control (complex cinematography, environment, camera moves) - use VIDEO 3.0 talking-head workflow instead. Avatar 2.0 is purpose-built for face/voice content with a relatively static framing.

Multi-Shot Storyboard (VIDEO 3.0)

Multi-shot was introduced in the 3.0 generation - VIDEO 2.6 did not support it. Instead of one continuous clip, direct a complete scene sequence in a single generation pass.

Two ways to use it:

  • Implicit multi-shot: Describe a scene in natural prompt language - the model recognizes cinematic structure (shot-reverse-shot, cross-cutting dialogue, voice-over) and adjusts camera angles automatically.
  • Custom multi-shot: Explicitly define each shot with its own subject, action, camera, duration.

Example custom multi-shot prompt structure:

Shot 1 (3s): Wide establishing shot of rain-slicked Tokyo street at night, neon reflections on pavement. Camera: static.
Shot 2 (4s): Medium shot - young woman in red coat emerges from subway exit, looks around. Camera: slow push in.
Shot 3 (3s): Close-up on her face, raindrops on cheek, determined expression. Camera: static.
Shot 4 (5s): She walks toward camera into the crowd. Camera: tracking shot from behind.

Kling Canvas Agent (one-click storyboard)

Launched 2026-01-29 - an AI orchestrator on top of the Kling generation models that automates the storyboard production pipeline:

  • Continuous shot creation - upload an element, get consistent storyboard images and videos across many shots
  • Multi-angle storyboard expansion - from one reference image, generate multiple angles/perspectives
  • Script creation - feed a story outline; Canvas Agent expands it into a structured storyboard script
  • Reverse prompt suggestions - feed it a video or image; it extracts visual style and core elements as a high-quality prompt
  • Batch generation - parallel processing of multiple prompts
  • E-commerce image set - from one product photo, generate Main + Model + Scene images

When the user needs more than a single clip - a complete short film with consistent characters, or a multi-asset deliverable - Canvas Agent is the right starting point.

Video Editing (VIDEO 3.0 Omni)

Upgraded 2026-06-17 (release note). Instead of generating a new clip, you feed Omni an existing video plus reference images and an instruction, and it re-renders the clip with your change applied while keeping the original motion.

Current limits per that release note:

  • Input video 3-15s, output up to 15s (was capped lower before this release)
  • 4K input and 4K output both supported
  • Stronger fidelity to the source: "Editing results stay more faithful to the source material, while creative instructions are executed with greater precision."

Reference syntax. Omni's official examples address inputs by role with @-prefixed handles - @video for the motion/trajectory source, @image for the style or object source:

Use @video as the motion trajectory reference and @image as the rendering style reference.
Keep the original camera angle, main architectural structure, spatial layout,
and the red ball's motion path unchanged.

What edits actually work well (all four patterns below are from Kling's own published examples):

  1. Object swap, motion preserved
    Replace the trophy in the video with the toy figurine shown in the reference image.
    
  2. Background and subject replacement with light matching
    Replace the video background with Image 1 and the subject with Image 2,
    keeping the original motion and positioning unchanged. Ensure the lighting and
    shadows on the subject match the target environment, with a natural,
    non-composited look and no sticker-like artifacts.
    
  3. Targeted colour/attribute change
    Change the character's pupil colour to light blue, and the hair colour to light blue.
    Change the headphones to light brown. Refer to the reference image for the expected result.
    
    Change the colour of the parrot's feathers to match the reference image.
    Keep all other elements of the video unchanged.
    
  4. Full style transfer with trajectory lock - restyle the whole scene while an element keeps its exact original path. This is the hardest edit and where the explicit "unchanged" list earns its keep.

Prompt rules for editing (the pattern visible across every official example):

  • Name the change first, in one clause. One edit intent per generation.
  • Then an explicit unchanged list: camera angle, motion path, spatial layout, positioning, everything else.
  • For anything composited in, add the physical-plausibility clause: "lighting and shadows match the target environment, natural, non-composited look, no sticker-like artifacts." Kling's own example includes it - it is doing work.
  • Point at the reference explicitly (@image, "Image 1", "the reference image") rather than describing the target from memory.

First and Last Frame Control (VIDEO 3.0)

Define exactly where a video starts and ends visually.

  • Start + End frames: Full control over composition and motion arc
  • End frame only: Guide how motion resolves without fixing the start
  • Upload reference images for either or both frames

Use this to create near-seamless loops by matching the end frame composition to the start.

Element Reference (character/scene consistency)

Kling's official mechanism for keeping subjects, items, and scenes consistent across shots is the Element system (sometimes called Element Library or Element Reference). Third-party reviews call this "Character LoRA" - the user-facing feature in Kling is named Element.

How it works (VIDEO 3.0 / Omni):

  1. Open the Element panel
  2. Upload reference image(s) for the subject - multi-image references work, and Omni also accepts a video as an element
  3. Name the element (e.g., @protagonist)
  4. Reference it in prompts via the element chip or the @element_name syntax
  5. Reusable across multiple generations - the Element Library persists

For commercial work where identity must stay locked across many shots, this is the recommended approach.

Voice Control (VIDEO 2.6 / 3.0)

Launched in VIDEO 2.6 on 2025-12-16 as a separate feature from generic Native Audio. Voice Control extracts the timbre from your uploaded audio sample into a reusable Voice Embedding, then binds it to characters via the [Character] @VoiceName syntax.

Key facts (verify before quoting):

  • Upload a 5-30s clean clip (single speaker, neutral emotion, low noise) to train a voice
  • Up to 200 voices in your library
  • Syntax: [Subject] @VoiceName in the prompt - e.g., [Livestream Host] @Sweet Female Voice: "This top is a trending must-have!"
  • Multi-character dialogue: each character can have its own @VoiceName
  • Currently supports Chinese and English only for voice creation/use, with bidirectional Chinese-English cross-language delivery (a voice trained in one can perform in the other)
  • Pricing: +2 credits/sec on top of base video generation

This is what you want when you need a consistent IP voice or brand persona across many videos. For one-off talking-head content with audio you already have, Avatar 2.0 is a different tool entirely.

Motion Control (VIDEO 3.0)

Current Motion Control is the VIDEO 3.0 Motion Control model (launched 2026-03-04), an upgrade over VIDEO 2.6 Motion Control (Dec 2025).

  1. Navigate to Motion Control
  2. Upload reference action video and target character image
  3. Click "Bind Facial Element to Enhance Facial Consistency" below the character image - bind an existing element or create a new one
  4. Optionally upload additional images/short video to enrich multi-angle expression data
  5. Set duration (up to 30s)
  6. Generate

What 3.0 Motion Control adds over 2.6: facial element binding for high facial consistency across angles, emotions, and even occlusions (hands, props in front of face). Element Binding requires the character orientation to match the video orientation.


Language of Prompts

Always write Kling prompts in English, regardless of the language the user is writing in. Kling was trained predominantly on English and Chinese; English prompts produce significantly better and more predictable results than prompts in less-represented languages.

The workflow is:

  • Communicate with the user in their language (Polish, German, French, etc.)
  • Write all Kling prompts in English

If the user writes their prompt in Polish or another language, translate it to English before presenting the final version they should paste into Kling. Explain this briefly if it's not obvious.

Exception: when using Native Audio features (VIDEO 3.0), dialogue text inside [Speaker: Name] "text" syntax should be in the target language. VIDEO 3.0 supports Chinese, English, Japanese, Korean, Spanish with dialects and accents. The surrounding prompt structure should still be in English.

For Avatar 2.0: language is determined by the audio file you upload, not by the prompt. The framing prompt itself stays English.


Prompt Engineering

The Director's Mindset

Kling 3.0 understands cinematic intent. The key shift: stop writing prompts like image captions, start directing like a DoP (Director of Photography). Think of each prompt as a mini-screenplay:

Scene setting - Camera direction - Subject action

Structured Prompt Formula

[Scene/Environment] + [Characters/Subjects] + [Sequential Actions] + [Camera Movement] + [Audio & Style]

VIDEO 3.0 handles sequential actions reliably: "First she looks up, then turns toward the window, finally smiles." Use this for any action that has phases.

Model-Specific Guidance

ModelPrompt LengthMax ElementsKey Pattern
VIDEO 3.0 / 3.0 Omni100-200 words6-7Sequential actions, multi-shot, native audio
VIDEO 3.0 Turbo100-200 words6-7Same as 3.0; lean on dialogue and lip-sync - that is where it wins
VIDEO 3.0 Omni (editing)40-120 words1 edit intentChange clause + explicit unchanged list + @video / @image handles
Avatar 2.020-50 words (framing only)1-2Tone/energy descriptor; audio does the work
2.650-80 words5-7Include audio instructions (EN/ZH)
2.5 Turbo40-60 words3-4Keep it simple

Essential Prompt Rules

  1. Specify camera behavior explicitly - Without it, camera will improvise unpredictably
  2. Add motion endpoints - "then settles back" or "returns to starting position" prevents the stuck-at-99% generation hang
  3. Use spatial language - "left to right", "toward camera", "background depth"
  4. Be hyper-specific about setting - "cyberpunk alleyway at midnight, neon reflections on wet pavement" beats "a street"
  5. One main action per shot - Use multi-shot for complexity, not a single overloaded prompt
  6. Use negative prompts - Explicitly tell the model what to avoid
  7. Validate at 1080p before 4K - 4K is ~30 credits/sec; iterate cheaper first

Keeping Elements Static

All [element] must remain absolutely fixed and unchanged throughout.
[element] stays completely static. No movement on [element].

For critical logos or text: generate without text, add as a post-production overlay.

Loop-Friendly Prompts

Subtle [motion type], gentle oscillation, returns to starting position.
Breathing effect, slow pulse, cyclical movement.

With 3.0: use first/last frame control with matching compositions. Post-process with 0.3-0.5s cross-dissolve.

Resolution Workflow

  • 1080p for iteration - same prompt quality as 4K, fraction of the credits
  • 4K (VIDEO 3.0 series, launched 2026-04-23) for final deliverables - 30 credits/sec, native (not upscaled), preserves reference consistency, lighting, color
  • 30fps for most content; higher framerates available on 3.0 for fast action

Prompt Templates

See references/prompt-templates.md for ready-to-use templates organized by use case (image-to-video, multi-shot, text-to-video, Avatar 2.0, audio).


Common Issues & Solutions

IssueCauseSolution
Generation stuck at 99%Open-ended motionAdd endpoint: "then stops", "returns to start"
Burning credits on bad promptsGoing to 4K too earlyAlways iterate at 1080p first; only render 4K once prompt is locked
Unwanted camera movementNo camera instructionAdd "static camera" or specific movement
Text/elements changingAI interpretationRepeat "fixed", "unchanged", "static" multiple times
Character morphing across shotsIdentity driftUse VIDEO 3.0 Omni with Element Reference (multi-image/video). Rewrite prompt from scratch rather than retrying with same settings.
Artifacts on hands/facesModel limitationSimplify scene, reduce duration, use 4K with 3.0
Avatar 2.0 lip-sync looks offDifficult audio (noise, multi-speaker, distorted)Use a clean single-speaker audio source; check current docs for language support
Avatar 2.0 body too static / too activeNo framing promptAdd a one-line tone/energy descriptor: "calm presenter, minimal gestures" or "energetic performer, full body movement"
Voice Control sounds wrongBad reference audioUse 5-30s clean clip, single speaker, neutral emotion, low background noise
Multi-shot feels disjointedNo shared style anchorDefine visual style once at start, use Element Reference for people/items
Audio desyncMissing speaker attributionUse [Speaker: Name] "dialogue" format, or with Voice Control [Character] @VoiceName. If it persists on a talking shot, switch to VIDEO 3.0 Turbo - stable A/V sync in longer clips is its headline strength
Edited video drifts from the sourceNo unchanged listOn Omni editing, always append the explicit list: camera angle, motion path, spatial layout, positioning. One edit intent per generation
Swapped-in object looks pasted onMissing physical-plausibility clauseAdd "lighting and shadows match the target environment, natural non-composited look, no sticker-like artifacts" (Kling's own example wording)
Editing job rejected or truncatedInput video outside 3-15sTrim the source into range; output caps at 15s
4K request fails on TurboTurbo has no 4K tierUse VIDEO 3.0 or Omni for 4K

Settings Reference

Duration:

  • VIDEO 3.0 / Turbo / Omni: 5-15s (flexible)
  • VIDEO 3.0 Omni video editing: input 3-15s, output up to 15s
  • VIDEO 3.0 Motion Control: up to 30s
  • Avatar 2.0: up to 5 minutes
  • 2.6 / 2.5 Turbo: 5-10s

Aspect Ratios: 16:9 (landscape), 9:16 (vertical/mobile), 1:1 (square)

Quality / Output:

  • Standard mode - for drafts
  • Professional mode - for finals (requires paid plan)
  • Native 4K - VIDEO 3.0 and Omni only (not Turbo), ~30 credits/sec in-app, launched 2026-04-23
  • Omni video editing accepts and returns 4K

Credits & Pricing

Kling bills two different ways and they are easy to confuse:

  • In-app / subscription: credits. What you spend generating in the Kling web app on a Basic/Standard/Pro/Premier/Ultra plan.
  • API: Units. 1 Unit = $0.14 list price, billed per second of output, and the rate depends on model x resolution x whether native audio and video input are on.

See references/pricing.md for the full breakdown of both. Pricing changes frequently - re-check before quoting.

API rate card, per second of video (source, verified 2026-08-04):

Model / configuration720p1080p4K
VIDEO 3.0 Turbo (native audio always on)0.8 U ($0.112)1.0 U ($0.14)n/a
VIDEO 3.0, no native audio0.6 U ($0.084)0.8 U ($0.112)3.0 U ($0.42)
VIDEO 3.0, native audio, no Voice Control0.9 U ($0.126)1.2 U ($0.168)3.0 U ($0.42)
VIDEO 3.0 Omni, no video input, no audio0.6 U ($0.084)0.8 U ($0.112)3.0 U ($0.42)
VIDEO 3.0 Omni, no video input, with audio0.8 U ($0.112)1.0 U ($0.14)3.0 U ($0.42)
VIDEO 3.0 Omni, with video input, no audio0.9 U ($0.126)1.2 U ($0.168)3.0 U ($0.42)
Motion Control0.9 U ($0.126)1.2 U ($0.168)n/a
Avatar0.4 U ($0.056)0.8 U ($0.112)n/a

Three things worth internalising from that table:

  1. 4K is a cliff, not a step - 3.0 U/s regardless of model, i.e. ~2.5-5x the 1080p rate. Iterate at 720p/1080p, render 4K once.
  2. Turbo at 1080p with audio costs the same as Omni with audio and less than VIDEO 3.0 with audio - for talking-head work it is the cheapest 3.0-class option.
  3. Native audio and video input each add cost. If a clip does not need sound, turning audio off saves ~33% at 1080p.

Subscription facts (verified against the official pricing page 2026-05-21, re-verify before quoting):

  • 5 subscription tiers: Basic (free), Standard ($6.99), Pro ($25.99), Premier ($64.99), Ultra ($127.99)
  • Basic/free tier output cannot be used commercially - hard restriction; user must be on Standard+ for commercial use
  • Voice Control is FREE for all paid subscribers (the "+2 credits/sec" rate applies to API / pay-as-you-go use, not subscription)
  • VIDEO O1 Element AI Multi-Shot: 3 daily free uses on every paid plan
  • 4K generation: 30 credits/sec (VIDEO 3.0 series)
  • 720p baseline: ~20 credits per 5s clip

Audio Features

Native Audio (VIDEO 3.0 / Omni)

Languages supported (per official 3.0 release note): Chinese, English, Japanese, Korean, Spanish, with dialects and accents. Multi-character coreference (3+ characters) and per-character voice precision.

Speaker attribution syntax (critical for accurate lip-sync in T2V/I2V workflows):

[Speaker: Character Name] "[dialogue]" in a [tone/emotion] [accent] voice.
Add [sound: footsteps / rain / door closing] when [action occurs].
Background ambient: [environment description].

Native Audio (VIDEO 2.6)

Chinese and English only. Same speaker-attribution syntax.

Voice Control (VIDEO 2.6 / 3.0)

A separate, more advanced feature. See the Voice Control section above. Currently Chinese-English only; +2 credits/sec.

Avatar 2.0

Uses your provided audio directly - no voice cloning or attribution syntax needed. Lip-sync is automatic.


Verification & Sources

When facts in this skill matter for a deliverable (credit pricing, language lists, duration limits), verify against the current Kling state:

Release timeline covered by this skill (newest first, from the official index): 2026-06-17 Kling 3.0 Model Series Upgrade (Turbo + Omni editing) · 2026-04-23 Native 4K · 2026-03-16 Team features + Desktop app · 2026-03-04 VIDEO 3.0 Motion Control · 2026-01-31 Kling 3.0 era (VIDEO 3.0 + Omni) · 2026-01-30 frame extraction + .mov export · 2026-01-29 Canvas Agent · 2025-12-17 VIDEO 2.6 Motion Control · 2025-12-16 Voice Control · 2025-12-04 Avatar 2.0. As of 2026-08-04 the 2026-06-17 entry is the most recent release note published.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

このスキルの問題を報告する