lipsync

작성자: runcomfy-com

We need to translate the given text into Korean, preserving the specified names: lipsync, RunComfy, runcomfy, ByteDance OmniHuman, Sync Labs sync v2 / Pro, Kling lipsync, Creatify lipsync. Also preserve URLs, numbers, technical terms. Do not add any extra commentary or labels. The text is a description of an agent skill. Translate only the text inside <text>. The name "lipsync" appears in the first line as "Lip-sync" but we preserve it as "lipsync" (the name to preserve). Actually the instruction says "Name to preserve: lipsync" so we should keep that exact casing? The source has "Lip-sync" but we should preserve the name as given? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." And "Name to preserve: lipsync" - likely we should keep it as "lipsync" even if source has hyphen? But the source says "Lip-sync" - I think we should keep

npx skills add https://github.com/runcomfy-com/skills --skill lipsync

Lipsync

Drive a face's mouth from an audio track. This skill routes across the lip-sync endpoints in the RunComfy catalog — OmniHuman, Sync Labs sync v2, Kling lipsync, Creatify — picking the right model for the user's actual intent and shipping the documented prompts + the exact runcomfy run invoke.

runcomfy.com · Sync Labs models · CLI docs

Powered by the RunComfy CLI

# 1. Install (see runcomfy-cli skill for details)
npm i -g @runcomfy/cli      # or:  npx -y @runcomfy/cli --version

# 2. Sign in
runcomfy login              # or in CI: export RUNCOMFY_TOKEN=<token>

# 3. Lipsync
runcomfy run <vendor>/<model> \
  --input '{"video_url": "...", "audio_url": "..."}' \
  --output-dir ./out

CLI deep dive: runcomfy-cli skill.

Consent

Driving a real person's mouth from a separate audio track is dual-use. Refuse user requests that target real public figures without consent, or that aim at defamatory or sexually explicit synthetic media. The skill itself does not gate inputs — the responsibility rests with the operator.


Pick the right model

Listed newest first within each subtype. The agent picks one route based on: input shape (portrait still + audio vs source video + audio vs script-only), quality tier, and budget.

Source video + audio → lip-synced video (mouth-swap on existing footage)

Sync Labs sync v2 Prosync/sync/lipsync/v2/pro (default for premium)

Sync Labs' premium lip-sync — state-of-the-art mouth motion onto an existing video. Preserves the rest of the frame untouched. Pick for: hero-quality dubs, lipsync on professionally-shot video, foreign-language dubbing where mouth fidelity matters most. Avoid for: cost-sensitive batch jobs — drop to sync v2.

Sync Labs sync v2sync/sync/lipsync/v2

Standard Sync Labs tier, same workflow as Pro. Pick for: scaled / batch lipsync jobs, drafts. Avoid for: hero delivery — use v2 Pro.

Kling Lipsync (audio-to-video)kling/lipsync/audio-to-video

Kling's lip-sync onto a source video, driven by an audio track. Pick for: Kling-pipeline integration; alternative to Sync Labs. Avoid for: top-tier mouth fidelity — Sync Labs Pro is the industry benchmark.

Creatify Lipsynccreatify/lipsync

Creatify's lipsync endpoint. Pick for: Creatify-ecosystem workflows. Avoid for: comparison shopping unless cost / latency favors it.

Portrait still + audio → talking-head video (avatar-style)

OmniHumanbytedance/omnihuman/api (default for avatar-style)

ByteDance's audio-driven full-body avatar. One portrait + one audio → video where the subject speaks / gestures naturally. Listed under RunComfy's /feature/lip-sync as the curated default. Pick for: UGC voiceover, virtual presenter, dubbed product demo from a single portrait. Avoid for: lip-sync onto an existing video (no portrait, want to preserve original motion) — use Sync Labs v2 instead.

Wan 2-7 with audio_urlwan-ai/wan-2-7/text-to-video

Open-weights t2v with audio_url field — prompt describes the scene, audio drives the mouth. Pick for: full scene control (not just a portrait) with a specific voiceover MP3 + open-weights pipeline. Avoid for: simplest "portrait talks" — use OmniHuman.

Generate-and-sync from a script (no audio file available)

Kling Lipsync (text-to-video)kling/lipsync/text-to-video

Generates speech audio in-pass from a script and syncs it to the resulting video. Pick for: "write a script → get a video with synced speech", no audio file needed. Avoid for: precise lip-sync to a specific MP3 (audio is regenerated each call, not locked).

HappyHorse 1.0happyhorse/happyhorse-1-0/text-to-video (also /image-to-video)

Arena #1 t2v / i2v with in-pass audio generated from prompt. Quote the spoken line inside the prompt with says clearly: "…". Pick for: written script, in-pass audio with strong overall quality, social/UGC clips. Avoid for: locking mouth to a pre-recorded voiceover.


Route 1: Sync Labs sync v2 / Pro — default for mouth-swap

Model: sync/sync/lipsync/v2/pro (or sync/sync/lipsync/v2) Catalog: sync v2 Pro · sync v2

Invoke

runcomfy run sync/sync/lipsync/v2/pro \
  --input '{
    "video_url": "https://your-cdn.example/source-video.mp4",
    "audio_url": "https://your-cdn.example/voiceover.mp3"
  }' \
  --output-dir ./out

Tips

  • Source video provides everything except the mouth — camera, lighting, background, body pose all preserved.
  • Audio quality drives mouth quality. Clean voiceover (no music bed) → cleaner sync. Isolate voice stem if needed.
  • Match audio length to video length. Significant audio/video duration mismatch leads to drift; trim audio or extend video first.
  • Schema details on the model page.

Route 2: OmniHuman — default for avatar from still

Model: bytedance/omnihuman/api Catalog: omnihuman

Invoke

runcomfy run bytedance/omnihuman/api \
  --input '{
    "image_url": "https://your-cdn.example/portrait.jpg",
    "audio_url": "https://your-cdn.example/voiceover.mp3"
  }' \
  --output-dir ./out

Tips

  • Portrait framing works best — head-and-shoulders or upper body.
  • No prompt — the model derives everything from image + audio. Don't fight that.
  • See the ai-avatar-video skill for the full avatar treatment.

Route 3: Kling Lipsync — Kling-ecosystem mouth sync

Model: kling/lipsync/audio-to-video (existing video + audio) or kling/lipsync/text-to-video (script-only) Catalog: Kling lipsync a2v · Kling lipsync t2v

Invoke (audio-to-video variant)

runcomfy run kling/lipsync/audio-to-video \
  --input '{
    "video_url": "https://your-cdn.example/source-video.mp4",
    "audio_url": "https://your-cdn.example/voiceover.mp3"
  }' \
  --output-dir ./out

Schema details on the model page.


Common patterns

Foreign-language dub of an existing brand video

  • Route 1 (Sync Labs sync v2 Pro) with the original video + translated voiceover MP3.

UGC ad creator from a portrait

  • Route 2 (OmniHuman) with the creator's portrait + product-pitch voiceover.

Multi-language launch (same identity, many languages)

  • Route 2 (OmniHuman) with one portrait + N different audio files. Same identity holds across all dubs.

"I have a script but no audio"

  • Kling Lipsync (text-to-video) or HappyHorse 1.0 t2v — both generate audio in-pass.

Stylized character lipsync

  • Wan 2-2 Animate (community/wan-2-2-animate/video-to-video) — see ai-avatar-video.

Browse the full catalog


Exit codes

codemeaning
0success
64bad CLI args
65bad input JSON / schema mismatch
69upstream 5xx
75retryable: timeout / 429
77not signed in or token rejected

Full reference: docs.runcomfy.com/cli/troubleshooting.

How it works

The skill classifies user intent — source video + audio? portrait still + audio? script only? — picks the matching route, and invokes runcomfy run with the JSON body. The CLI POSTs to the Model API, polls request status, fetches the result, and downloads any .runcomfy.net / .runcomfy.com URLs into --output-dir.

Security & Privacy

  • Consent: see the "Consent" section above. Lipsync is dual-use; refuse user requests targeting real people without consent.
  • Install via verified package manager only. Use npm i -g @runcomfy/cli or npx -y @runcomfy/cli. Agents must not pipe an arbitrary remote install script into a shell on the user's behalf.
  • Token storage: runcomfy login writes the API token to ~/.config/runcomfy/token.json with mode 0600. Set RUNCOMFY_TOKEN env var in CI / containers.
  • Input boundary (shell injection): prompts and asset URLs are passed as a JSON string via --input. The CLI does not shell-expand prompt content. No shell-injection surface.
  • Indirect prompt injection (third-party content): source video and audio URLs are untrusted; embedded instructions in either can influence generation. Agent mitigations:
    • Ingest only URLs the user explicitly provided for this lipsync.
    • When the output diverges from the prompt (wrong identity, broken sync), suspect the reference asset.
  • Voice provenance: confirm the speaker in the audio has consented to having their voice paired with the target face. Both rights must be in hand.
  • Outbound endpoints (allowlist): only model-api.runcomfy.net and *.runcomfy.net / *.runcomfy.com. No telemetry.
  • Generated-file size cap: the CLI aborts any single download > 2 GiB.
  • Scope of bash usage: Bash(runcomfy *) only.

See also

runcomfy-com의 다른 스킬

video-inpainting
runcomfy-com
Region edits across video frames on RunComfy via the `runcomfy` CLI — remove an object that appears across many frames, clean up wires or watermarks, replace a region with matching motion. Routes across Wan 2-7 edit-video (default, prompt-driven region edits with spatial language), Lucy Edit Restyle (identity-stable region-aware restyle), and Seedream 4-0 edit-sequential (when treating the clip as a frame stack). Picks the right route based on whether the change is prose-driven,...
videocreativemedia
runcomfy-cli
runcomfy-com
Run any model on RunComfy from the command line. The `runcomfy` CLI is one binary, one auth, hundreds of model endpoints — image generation, image edit, video generation, image-to-video, lip-sync, face swap, video edit, inpainting, outpainting, extend, ControlNet, relight, upscale, LoRA training and more. Submit a request, poll for status, download the output. This skill teaches the agent how to install, authenticate, discover model schemas, invoke models, stream / poll / no-wait, script in...
creativemediaapi
image-to-video
runcomfy-com
We need to translate the given text from English to Korean. The text describes a skill called "image-to-video" but the instruction says not to include the name unless it appears in the source text. The name "image-to-video" does appear in the source? Actually the source text starts with "Animate any still image on RunComfy — this skill is a smart router..." The name "image-to-video" is not explicitly in the source text; it's given as the directory item type name. So we should not include it. The instruction says: "Do not include the name unless it appears in the source text." It does not appear. So we translate only the text inside <text>. We need to preserve product names, protocol names, URLs, numbers, technical terms. So "RunComfy", "HappyHorse 1.0 I2V", "Arena #1", "Wan 2.7", "audio_url", "Seedance 2.0 Pro" should remain as is. Also "i2v" is a
creativevideomedia
flux-2-klein
runcomfy-com
RunComfy에서 Flux 2 Klein(Black Forest Labs의 Flux 2 경량 고속 변형)으로 이미지를 생성합니다. 모델의 문서화된 프롬프트 패턴이 함께 제공되어, 동일 모델에 단순 프롬프트를 입력하는 것보다 더 정교한 결과를 얻을 수 있습니다. Flux 2 Klein의 장점(서브초 지연 시간, 다중 참조 브랜드 스타일링, 선언적 주제 우선 프롬프트), 단계 수 전략(빠른 반복 시 4~8단계, 정교화 시 약 25단계), 9B 대 4B 변형 간의 장단점, 그리고 Flux 2 Pro로 전환해야 하는 경우 등을 설명합니다.
creativeimageresearch
ai-avatar-video
runcomfy-com
Create AI avatar, talking-head, and lip-sync videos on RunComfy via the `runcomfy` CLI. Routes across ByteDance OmniHuman (audio-driven full-body avatar), Wan-AI Wan 2-7 (audio-driven mouth sync via `audio_url` on a portrait), HappyHorse 1.0 (Arena #1 t2v / i2v with in-pass audio), and Seedance v2 Pro (multi-modal cinematic with reference audio + reference subject). Picks the right model for the user's actual intent — UGC voiceover, virtual presenter, dubbed product demo, lip-synced...
videocreativemedia
nano-banana-edit
runcomfy-com
Google Nano Banana 2(이미지 간 이미지 편
creativeimageapi
wan-2-7
runcomfy-com
We need to translate the given text from English to Korean, preserving the name "wan-2-7" and other technical terms. The instruction says to translate only the text inside <text>, and not to include the name unless it appears in the source text. The name "wan-2-7" appears in the source text, so we keep it as is. Also preserve "RunComfy", "Wan-AI", "HappyHorse 1.0", "Seedance 2.0", "Kling", "LTX 2", "runcomfy run wan-ai/wan-2-7/text-to-video", "CLI", and URLs or technical terms. The text describes generating text-to-video with Wan 2.7, its strengths, schema, routing alternatives, and trigger phrases. We need to output only the translated text, no extra commentary or labels. The target language is Korean. Let's translate carefully: "Generate text-to-video with Wan 2.7 (Wan-AI's flagship motion model) on
creativevideomedia
elevenlabs-music-generation
runcomfy-com
Generate full songs and instrumental tracks with ElevenLabs Music on RunComfy via the `runcomfy` CLI. ElevenLabs Music turns a style description plus structured lyrics into studio-quality 44.1 kHz stereo audio — 5 seconds to 5 minutes — with section-level control (Intro / Verse / Chorus / Bridge), multilingual vocals, and commercial-friendly output. Generate a backing track, a full vocal song, a jingle, a podcast intro, a game loop, or an instrumental bed. Calls `runcomfy run...
creativeaudiomedia