Sync Labs pricing per second, and a Sume dry_run cost preview
Sync Labs bills per second on top of a $5, $19 or $49 plan, and lists sync-3 at $0.107 to $0.133 per second. On Sume, preview a paid call with dry_run first.

Sync Labs is usage-based: you pay a monthly plan fee plus a rate per second of video, $0.05 per second on Hobbyist and Creator and $0.0475 on Growth. Its sync-3 page separately lists $0.107 to $0.133 per second at 25 fps. Sume's way to know a cost before spending is dry_run=true on a paid MCP tool, which returns an admission and cost preview without submitting the job.
Sync figures are as written on its pricing and sync-3 pages; Sume facts from MCP tools and gates, read 2026-10-01.
How is Sync Labs priced?
| Plan | Per month | Per second |
|---|---|---|
| Hobbyist | $5 | $0.05 |
| Creator | $19 | $0.05 |
| Growth | $49 | $0.0475 |
| Scale | $249 | $0.04 |
How do I check a cost on Sume before paying?
Write and paid MCP tools require an idempotency_key. Add dry_run=true to get an admission and cost preview only; the docs say not to submit the job from that call. They also suggest generation_admission_preview before expensive bursts, and max_spend_usd, enforced only when you provide it, as a cap.
What if the balance is too low?
A generation submit fails with 402 insufficient_credits before provider work starts. The price itself depends on the model and options: for avatar video, quality accepts standard, plus (default) or max, so preview each tier you plan to use. Per-clip numbers for avatar video are in avatar video pricing per minute.
Does a dry run work like the Hedra and Replicate estimates?
It plays the same role as a price check ahead of a paid call; see Hedra's estimate endpoint vs Sume dry_run for that comparison.
Sources
Related posts
More in Pricing
- Synthesia auto top-up vs Sume: manual dashboard top-ups
Synthesia now offers automatic credit top-ups. Sume top-ups are a manual Stripe-backed dashboard action; a low balance fails at submit, not mid-job.
- Video render priced per minute: 61 seconds bills two minutes
Sume Timeline bills per ceil(output minute), so a 61-second render counts as 2 minutes. A worked rounding table for 59, 60 and 61 seconds.
- Render cost estimate before export: Timeline plan is unbilled
POST /v1/timeline-1.0/plan returns billable_minutes and an estimated cost without creating a job or reserving credits. What it cannot predict.
- Vidu off-peak mode: 48 hours for half price, and Sume's cheap tiers
Vidu's off-peak mode generates within 48 hours at half price. Sume has no Vidu model and no off-peak flag; the cheap path is a low-resolution tier.
Written by Sume