Requesting a custom batch project

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.

💬 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 delivery)

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 + source folder

To ensure a smooth and efficient ingestion of your content into Dubly, please prepare two things and submit them together:

A folder containing every source video for the batch.
A spreadsheet (Excel or CSV) with one row per video, mapping each video to its dub settings.

For the batch process to work, your spreadsheet must include the following columns:

Column	Notes
`video_key`	Must match your filename exactly, including the extension (e.g. `episode_12.mp4`). Crucially, filenames must not contain spaces, periods (aside from the extension), special characters, or umlauts. This key is how we pair each row to its source file — if it does not match or follows an invalid format, we cannot ingest the video.
`video_url`	Optional — only include this if you're sharing via a direct URL instead of, or in addition to, a folder.
`title`	The dub title as it will appear in your Dubly dashboard.
`source_language`	The language code of the original audio (e.g. `en`, `de`). Can be set per-row if videos in the batch differ.
`target_languages`	Comma-separated language codes for the desired translations (e.g. `de, fr, es`).
`speaker_count`	The number of distinct speakers in the video (e.g. `1` for a single host, `2` for an interview).
`custom_voice_id`	Optional — leave blank to use automatic speaker matching, or paste a specific custom voice ID from your account.
`project_id`	Optional — the specific Dubly project where the dubs should be assigned.

Please be advised that we can only proceed with processing your batch if the data is prepared without errors and strictly follows all the rules above. Mismatched filenames or formatting errors will prevent successful ingestion.

What happens next

We confirm we have everything we need (or ask one round of clarifying questions)
You get a quote, timeline, and a delivery plan
Once approved, we set up your workspace, ingest the files, and process the batch
You review and approve via your normal Dubly project view