How is this different from the AI Video API?

The AI Video API generates new videos from scripts and inputs. The Lip Sync API takes existing video + new audio and re-animates the mouth to match. Different use case, different endpoint. Both are in the same private preview.

What input formats does it accept?

MP4 / MOV for video at 720p, 1080p or 4K (24–60 fps). Audio in MP3, WAV, M4A, or AAC. The video must have a clearly visible face occupying at least a third of the frame; very wide shots aren't suitable for accurate sync.

How fast is a typical job?

Lip-sync on a 30-second clip typically renders in 30–60 seconds. Longer videos scale linearly. The API is async-first — submit, get a job ID, receive a webhook when complete.

What languages are supported?

The model is phoneme-driven and works across most languages. English, Spanish, Portuguese, French, German, Italian, Hindi, Mandarin, Japanese, Korean, Arabic are all production-ready. Tonal languages including Mandarin and Vietnamese are supported.

NewStudio 2.0 — Talking Actors at 1080p

Seamless Localization with Lip Sync API
for Developers

Advanced API for video localization.
Perfect for multilingual content at scale.

Generate Your Ad

Continue with Google

Talking Actors 650+ AI Avatars Lip Sync Voice Cloning Text-to-Speech Product Videos Shorts Generator AI UGC Generator Talking Actors 650+ AI Avatars Lip Sync Voice Cloning Text-to-Speech Product Videos Shorts Generator AI UGC Generator

Batch Generation 35-Language Dubbing Background Remover Auto Captions Character Replace B-Roll Generator Hooks & Gestures Voice Library Batch Generation 35-Language Dubbing Background Remover Auto Captions Character Replace B-Roll Generator Hooks & Gestures Voice Library

Ad Video Generator Facebook Ad Generator TikTok Ad Generator AI Ads Video API Lip Sync API Affiliate Tools Content Generator Ad Video Generator Facebook Ad Generator TikTok Ad Generator AI Ads Video API Lip Sync API Affiliate Tools Content Generator

The Lip Sync API exposes AdLit's lip-sync engine as a standalone endpoint, separate from the full UGC generation pipeline. Useful for platforms that already have video content and need to localize, dub or post-correct it programmatically — translation services, dubbing platforms, content-localization SaaS. Currently in private preview alongside the AI Video API; the same waitlist gates access.

The reality

Why this is hard today

Building lip-sync in-house is research-grade

Phoneme alignment, mouth-shape modeling and frame-rate-stable rendering are PhD-level problems. Most teams that try to build this in-house abandon the project after a quarter.

Generic dubbing breaks lip-sync

Most dubbing services replace the audio but not the visuals. Viewers notice the mismatch within 5 seconds and engagement falls. True lip-sync is what makes localized video feel native.

Latency matters for streaming workflows

If your platform processes incoming video and pushes localized versions back to users, the API needs predictable latency. Cobbling together OSS models gives you tail-latency horror stories.

What you can ship

Built for these workflows

Translation service: video output

Offer your translation customers a 'video-with-lip-sync' tier alongside text translation. Charge accordingly. The Lip Sync API does the heavy lifting.

Content localization SaaS

Build a workflow that takes a customer's English video, generates 10 localized voiceovers, and renders 10 lip-synced versions ready to ship to their YouTube/social/CTV channels in each market.

Dubbing pipeline modernization

Replace the legacy 'voice-over only' dubbing tier of your platform with true lip-sync dubbing. Customers pay more for the quality lift; you ship it without building the model yourselves.