Skip to main content

Requesting a custom batch project

Planning a high-volume batch dub? Learn what to include in your project brief, volume, languages and content type, so we can quote pricing and timeline fast.

If you have a larger volume of videos to dub at once the fastest way to get an accurate quote and timeline is to send us a complete project brief upfront. This article shows what to include so we can scope your batch in one round instead of going back and forth.

To start a batch project, book a discovery call at go.dubly.ai/book or write to support with the details below.

Note: Prefer to run the batch yourself? Every Dubly account can use the public API — see Dub multiple videos at once (batch processing).

What to send us

Copy the template at the bottom of this article and fill in what you know. The more complete it is, the faster we can confirm pricing, timeline, and whether anything in your batch needs special handling.

1. Volume & runtime

  • Total number of videos

  • Total runtime in minutes (sum across all videos)

  • Average length per video, plus the longest one

  • One-off batch or recurring (e.g. weekly/monthly)

2. Languages

  • Source language(s) — the language(s) spoken in the originals

  • Target language(s) — every language you need each video dubbed into

  • If different videos need different target sets, say so (e.g. "all 50 → ES + FR; subset of 10 also → JA")

3. Content type

  • Talking-head, interview, screen recording, marketing, course, podcast video, etc.

  • Number of speakers per video (single speaker vs. multi-speaker)

  • Whether lip-sync is required for any/all of them

  • Whether you want custom / cloned voices (and whether you already have voice samples)

4. Source files

  • Format: we accept mp4 and mov, up to 5 GB per file

  • Where they live (Google Drive, Dropbox, S3, YouTube URLs, etc.)

  • Whether we'll get all files at once or in waves

5. Brand & quality requirements

  • Any reference if you already created a translation style in your profile that we should consider in the batch

6. Timeline & delivery

  • Required delivery date (and whether it's hard or flexible)

7. Contact & billing

  • Primary point of contact (name + email)

  • Company name and billing entity, if different

  • Whether this should run on your existing workspace or a new one

8. Per-video spreadsheet

We need one row per video, mapping each video to its dub settings — plus the videos themselves. Which columns that sheet needs depends on whether your videos are YouTube links or your own files.

The full column list, with both cases side by side, is in Dub multiple videos at once (batch processing). Prepare your sheet as described there and send it along with this brief.

The short version:

  • YouTube links — one yt_link column per row, nothing to upload. The videos have to be public or unlisted.

  • Your own files — one folder containing every video, plus a video_key column holding the exact filename for that row. No spaces, umlauts, special characters, or periods except before the extension.

  • Both cases need source_language and target_languages per row. title, speaker_count, custom_voice_id and project_id are optional.

9. API token

We create the dubs inside your account and bill them to your credits, so we need an API token from your workspace:

  • Settings → API → Generate new token, give it a name.

  • Copy it immediately — it is shown only once.

  • Send it to us in the support chat or by email.

Treat it like a password. Once the batch has been delivered, revoke it in the same tab.

What happens next

  1. We confirm we have everything we need (or ask one round of clarifying questions)

  2. You get a quote, timeline, and a delivery plan

  3. Once approved, we set up your workspace, ingest the files, and process the batch

  4. You review and approve via your normal Dubly project view

Related Articles
Did this answer your question?