Skip to main content

Model comparisons

VEED Dubbing vs Video Translator

Only VEED Dubbing returns audio in the same file as the video. Compare VEED Dubbing and Video Translator tier by tier: prices, request fields and limits.

VEED Dubbing

VEED Dubbing turns the speech in a clip into one of 86 languages, voices it in a clone of each speaker and redraws the mouths so the lips follow the new lines. Billed per second of the source clip.

View model details →View sample outputs →

Video Translator

Video Translator transcribes the speech in a clip, translates it into one of 28 languages and voices it again, optionally in each speaker's own cloned voice, returning the same picture with the new audio and a matching subtitle file. Billed per started minute of the source clip.

View model details →View sample outputs →

Compare

The short answer

Start with the input you have, the result you want and your budget. These are the differences that affect that choice.

  • These tools produce different results. Choose the operation you need first; a lower price does not make one a substitute for the other.

These tools produce different results. Choose the operation you need first; a lower price does not make one a substitute for the other.

Current price

Price at the same setting

A start price answers a different question than the one you have. These are the tiers both models publish, matched setting for setting, in US dollars per billed unit with no conversion step in between.

These two bill on different tiers, so there is no row to line up. Each one's own published tiers are listed here instead.

VEED Dubbing: $0.144 / output seconds

Video Translator: $0.005 / output seconds

About this comparison

Controls and limits

Every row here is read from the JSON Schema the endpoint validates against, so it matches what the API will really accept rather than a feature list written by hand.

Swipe horizontally to compare all fields.

VEED Dubbing vs Video Translator
Controls and limitsVEED DubbingVideo Translator
Supported tasksvideo-translatevideo-translate
Audio outputYesNo
ExecutionSubmit, then poll or take the callbackSubmit, then poll or take the callback
Request timeout180 minutes180 minutes
AvailabilityLiveLive

Do low-filter models allow every request?

Content policy, side by side

Two separate facts sit behind these labels. The first is what we do, which is nothing: no platform content filter, and no maturity flag to set on a request. The second is what each model does on its own, and that is the only part that varies between these two.

VEED Dubbing

Uncensored

This model declares no content filter. SpicyAPI forwards the request without adding a platform content scan; legal and consent duties remain with the customer.

Use these content labels to shortlist models, then open each model page for available examples and content-test details.

The label never changes your obligations. Age, consent, real-person likeness and the law where you operate stay with you, and SpicyAPI does not inspect each request.

Can I swap the model ID without changing the request body?

Request body, field by field

The task lifecycle is shared; the body is not. Each endpoint publishes its own JSON Schema and the API validates against that, so this is the list to reconcile before a switch.

  • 3 fields appear in both request bodies under the same names. source_language, target_language, video_url
  • Only VEED Dubbing accepts: keyterms.
  • Only Video Translator accepts: clone_voice, glossary, keep_background_audio, speaker_count.
  • VEED Dubbing requires target_language, video_url.
  • Video Translator requires video_url.
  • Both reject unknown fields outright, so a parameter left over from the other model comes back as a validation error instead of being quietly ignored.

How to choose

How to choose

Audio output

VEED Dubbing returns a soundtrack in the same file as the picture; the other returns picture only, so audio has to be added afterwards.

Compare

Moving from one to the other

The model identifiers are veed/dubbing/video-translate and spicyapi/video-translator-v1/video-translate, and both go in the same field of the same request.

Both run the same way: submit the task, then poll it or take the callback. Queueing and retry logic carry over unchanged.

Both use the same submit-and-track flow, but their required inputs may differ. Check each model page before switching.

One key, one balance, one set of spend caps. Both bill to the same account in US dollars, and the per-key daily, monthly and lifetime limits apply to whichever one you call.

Questions developers ask

Which is cheaper, VEED Dubbing or Video Translator?

Which is cheaper, VEED Dubbing or Video Translator?

These tools produce different results. Choose the operation you need first; a lower price does not make one a substitute for the other. Prices may change; check the estimate shown for your actual settings before submitting.

How long can a single request run?

VEED Dubbing allows 180 minutes per task and Video Translator allows 180. Those are ceilings rather than typical times — most requests finish far sooner — but they are what your own client timeout has to survive.

Prices and capabilities shown here come from the current public model catalogue. Check each model page for its latest inputs and examples.

Related comparisons