File Formats and Export Settings for Dubbing

A wrong export setting forces you to re-run the job. The video plays fine in your timeline, but when you upload it to DubLab, the audio stutters, the sync drifts, or the dubbing engine simply rejects it. You re-export, try again, and now you have wasted processing time on the same video twice.

Export settings matter because dubbing engines read the file format strictly. A codec mismatch, a misaligned sample rate, or a bitrate that is too low all land you back at the export step. The right settings work the first time, every time.

Video Codec: H.264 is the safe choice

Use H.264 (also called AVC or MPEG-4 Part 10). It is the most widely supported, produces files that play on every device, and dubbing engines expect it. H.264 has been the industry standard since 2003, and nearly every device from smartphones to set-top boxes decodes it without a hitch.

Avoid these:

• H.265/HEVC: Produces smaller files at the same quality, which sounds ideal. But not all systems decode it smoothly, and some dubbing engines have compatibility issues. If your editor defaults to HEVC because of your hardware, explicitly switch to H.264 for export.
• ProRes or DNxHD: These are intermediate codecs designed for editing and archival. They preserve maximum quality during the editing process, but they are wasteful for upload. A ProRes file is 5 to 10 times larger than H.264 for the same duration.
• VP9 or VP8: WebM format. These are open-source codecs favored by browsers, but dubbing engines do not commonly support them.

If your editing software defaults to something other than H.264, do not assume it will work. Explicitly set it to H.264 before you export. This is not a suggestion; it is the step that prevents a credit waste.

Bitrate: Start at 8-12 Mbps for 1080p

Bitrate is the amount of data flowing per second. Think of it as the fidelity knob. Too low, and the video looks blocky or soft. Too high, and you are paying for pixels no one will see. Dubbing engines can process low-bitrate video, but quality loss compounds during re-encoding.

For 1080p video, use this as your target:

• 8 Mbps: Minimum acceptable. Works for talking heads and screen recordings where motion is minimal and detail is not critical.
• 10-12 Mbps: Standard. Most YouTube creators shoot this range. It is the sweet spot between file size and perceived quality.
• 16+ Mbps: Over-specified for upload to DubLab. Larger file, no real gain in the output, and it only slows your upload.

For 4K video:

• Start at 25-30 Mbps. Never go below 25; the resolution demands it.

A common workflow is to export at a higher bitrate (50+ Mbps) for your editing archive, where you preserve every ounce of detail for future tweaks. Then, when you are satisfied with the cut and ready to dub, export a final version at the bitrate above for upload to DubLab. This protects quality during editing without ballooning the file you are sending.

To calculate bitrate, think about duration. A 10-minute 1080p video at 10 Mbps will be roughly 750 MB. At 8 Mbps, it shrinks to 600 MB. The 150 MB difference in file size is real and affects upload time, but the quality difference is almost imperceptible to the human eye.

Audio: Sample rate matters more than you think

Audio sample rate is the number of audio snapshots per second. Video and audio must have sample rates that either match or are harmonious (one is a multiple of the other). Mismatched rates cause drift and sync problems that compound over a long video.

Use this standard for video:

• 48 kHz: The professional video standard worldwide. Use this for all video work. If your video editing software defaults to this, you are already correct.
• 44.1 kHz: Common in music production and CD-quality audio. It works with video, but it is not ideal. If you are pulling in audio from a podcast recorded at 44.1 kHz, you will need to resample it to 48 kHz before adding it to your video timeline.
• 96 kHz: Overkill for dubbing work. Larger file, no perceptible benefit, and adds processing overhead.

If you are merging audio from multiple sources, always resample the outliers to 48 kHz first. A media player might not notice a 44.1 kHz track embedded in a 48 kHz video, but a dubbing engine will detect the mismatch and either reject the file or attempt re-encoding (which costs time and quality).

Audio bitrate (separate from sample rate) describes how much data the audio stream uses per second:

• 128 kbps: Acceptable for mono voice or podcasts. Adequate but not generous.
• 192-256 kbps: Standard for stereo dialogue and music. Most video creators use 192 kbps as a baseline.
• 320 kbps: Overkill. Do not exceed this. The human ear cannot distinguish it from 256 kbps in typical playback scenarios.

For a video with dialogue and background music, 256 kbps is a safe choice. For a screencast with just voiceover, 128-192 kbps is fine.

Container format: MP4 is the baseline

The container is the wrapper that holds the video and audio streams together. Think of it as the envelope. Use MP4 (file extension .mp4). It is the industry default for a reason: wide support, reliable, and predictable.

Other options and why to avoid them:

• MOV: Works fine, common on Apple hardware. No advantage for upload to DubLab.
• MKV: Powerful and flexible, but not all servers handle it reliably. Avoid for upload.
• AVI or older formats: Do not use. Dubbing engines may outright reject them.
• WebM: Open-source, supported in browsers, but not in dubbing workflows.

If your software prompts you for a container, pick MP4 without hesitation and move on.

Frame rate: 24p, 25p, or 30p

Frame rate (fps) is usually locked during filming or recording, not during export. Export at whatever frame rate the source is. Do not convert or resample unless there is a specific reason, such as retiming content for a different region's broadcast standard (European TV is 25p, North American is 30p, film is 24p).

When in doubt, match the source:

• 23.976 fps (24p): Film standard, used in cinema and cinema-style productions.
• 25 fps: European TV standard. Common in Europe, Asia, and Australia.
• 29.97 fps (30p): North American TV standard, and the default in many American video editors.
• 60 fps: Common for sports, fast motion, or gaming content.

If you filmed at 30p, export at 30p. If you filmed at 24p, export at 24p. Resampling introduces artifacts and is almost never necessary. The dubbing engine will accept any of these standard rates without complaint.

Failure modes: What goes wrong and how to fix it

Sometimes you upload a video and DubLab rejects it, stutters during processing, or produces sync drift in the output. Here are the most common culprits:

Symptom: "File format not supported" error The dubbing engine does not recognize the codec or container. Check that your file is H.264 in an MP4 container. Open the file in a media player to verify it plays. Then re-export with those settings and try again. If the error persists, use a tool like MediaInfo (free, cross-platform) to inspect the actual file codec. The export settings may have been ignored by your software.

Symptom: Audio stutters or sounds choppy Usually a sample rate mismatch. If you mixed audio from a podcast (44.1 kHz) with video edited at 48 kHz, the streams are not in sync. Resample the audio to 48 kHz before re-exporting. Most editors have a "Resample" option in the audio track context menu. Use it, then re-export.

Symptom: Sync drift that increases over time This creeping delay between video and audio almost always stems from mismatched sample rates or frame rate conversion during export. Check your audio sample rate and frame rate; make sure they are standard (48 kHz audio, 24p/25p/30p video) and consistent throughout your project. If you converted frame rate during export, undo that step and export at the native frame rate instead.

Symptom: File rejected with "bitrate too low" message Your video bitrate is below the engine's minimum (5 Mbps). Re-export at 8-12 Mbps for 1080p or 25-30 Mbps for 4K. If your editor shows a bitrate but the error persists, the bitrate you set may not have been applied. Check the export log or use MediaInfo to verify the actual bitrate of the output file.

Symptom: Video plays fine locally but hangs during DubLab processing The file plays locally because your media player is forgiving about codec edge cases, but the dubbing engine is stricter. Re-export with strict H.264, verify with a media player on a different device (or try a web-based player like VLC in a browser), and upload again. Also check file size; if the file is under 10 MB for a 10-minute video, bitrate is probably too low.

Before you upload: A pre-flight check

Do this once per project, before you upload to DubLab:

1. Export the file to your chosen settings.
2. Play it in two different media players (e.g., VLC and your OS default player). It should play smoothly in both.
3. Check file size. A 10-minute 1080p video at 10 Mbps should be roughly 750 MB. If yours is much smaller, bitrate was too low. If it is much larger, bitrate was too high (and upload will be slow).
4. Use MediaInfo (free download) to inspect the file properties. Open the file in MediaInfo and verify: video codec is AVC (H.264), video bitrate is in your target range, audio codec is AAC or PCM, audio sample rate is 48000 Hz. Write these down.
5. Upload and run a short test job (even just the first 30 seconds if DubLab supports it). If it processes cleanly, your settings are correct. If it fails, refer to the failure modes section above.

This five-minute pre-flight check prevents export-related errors.

Export settings for different editing software

Most editing software ships with presets that handle this for you. Use these as starting points. After exporting with a preset, always do a sanity check on the file properties before uploading.

Adobe Premiere Pro: Use the "YouTube 1080p HD" preset or "H.264 Match Source". Then adjust bitrate to 10 Mbps and audio bitrate to 256 kbps if the preset defaults to something lower. In the Export Settings dialog, check the Audio tab and confirm sample rate is 48 kHz. Premiere often defaults to 44.1 kHz; manually change this before exporting.

DaVinci Resolve: Under Delivery, choose "YouTube 1080p" or manually set these: codec to H.264, audio sample rate to 48 kHz, video bitrate to 10 Mbps, container to MP4. DaVinci Resolve is particularly good about pre-filling the right values, but always double-check the audio sample rate.

Final Cut Pro: Final Cut Pro's native export presets produce ProRes, which is not suitable for DubLab upload. Instead, export using "Master File" and let it create a ProRes file, then use the Compressor application (included with Final Cut Pro) or a third-party tool like HandBrake to transcode that file to H.264, MP4, 10 Mbps. This two-step workflow is cumbersome but unavoidable with Final Cut Pro.

CapCut (mobile or desktop): Export uses H.264 by default at 1080p, which is correct. On mobile, tap Export and select quality "High". On desktop, go to File > Export Project, select resolution as 1080p, and bitrate as "High". Confirm the bitrate target is at least 8 Mbps in the advanced settings.

OBS Studio: If you recorded a stream or presentation using OBS, use File > Export Video. Select output format as MP4, encoder as H.264, and bitrate of 8-10 Mbps for 1080p. OBS records at 48 kHz by default, so audio is correct.

FFmpeg (command-line): For precision control, use:

ffmpeg -i input.mov -c:v libx264 -b:v 10M -c:a aac -b:a 256k -ar 48000 output.mp4

This encodes video to H.264 at 10 Mbps, audio to AAC at 256 kbps with 48 kHz sample rate, in MP4 container.

Common mistakes and corrections

Mistake 1: Exporting ProRes for upload to save time. ProRes is 5 to 10 times larger than H.264 and many dubbing engines do not accept it. Export to H.264 instead. You will save upload time.

Mistake 2: Keeping audio at 44.1 kHz because "it works in my editor". Local playback can mask mismatches. The dubbing engine will notice. Resample to 48 kHz before export.

Mistake 3: Exporting at 30 Mbps because "higher is better". Wrong. Dubbing engines do not extract quality from excessive bitrate. You are just uploading slower. Stick to 8-12 Mbps for 1080p.

Mistake 4: Converting frame rate from 30p to 24p to "match film". Unless you are specifically retiming for cinema distribution, keep the original frame rate. Conversion introduces timing artifacts that confuse the dubbing engine.

Mistake 5: Using a custom export preset without testing first. Test one video all the way through dubbing before applying the same settings to 50 videos. The first one is your proof.

Quick reference table

Save this table. Bookmark it. Print it if you want.

Worked example: A YouTube video workflow

You filmed a 12-minute how-to video at 30p with a Canon camera. You edited it in Premiere Pro, mixed in background music, and now you want to dub it into Spanish.

1. In Premiere Pro, go to File > Export > Media.
2. Choose the "YouTube 1080p HD" preset.
3. In the Video tab, verify codec is H.264 and bitrate is at least 10 Mbps. If it shows 8 Mbps, change to 10.
4. In the Audio tab, check sample rate. If it shows 44.1 kHz, change it to 48 kHz.
5. Export to a file named video_master_spanish.mp4.
6. Upload to DubLab, select Spanish as the target language, and start a job.
7. Once the dub completes, you have a Spanish version of the same 12-minute video, ready to upload.

If the dub job fails, you did not verify the audio sample rate. Go back, re-export with 48 kHz audio, and try again.

Worked example: A podcast-to-video conversion

You have a podcast recorded at 44.1 kHz that you want to dub into multiple languages. Set your project to 48 kHz and export to H.264, MP4, 10 Mbps. The editor will resample the audio on export. If you skip this step, DubLab will reject the file.

What to do next

Follow these five steps to nail your export settings once and for all:

1. Pick your software's "YouTube" or "Web" preset. Most editors have this built in. It pre-fills codec, bitrate, and sample rate to safe defaults.

2. Override only these three fields if needed: Video codec to H.264, video bitrate to 10 Mbps (1080p) or 27 Mbps (4K), and audio sample rate to 48 kHz. Use the table above as your reference.

3. Export a single short test video (even just 30 seconds) to this setting. Do not change anything between exports.

4. Upload the test to DubLab and run a full dub. Watch the progress bar. If it completes without errors and the output sounds in sync, your settings are correct.

5. Use this exact setting for every subsequent export. Create a preset in your editor if possible and name it "DubLab Upload". Consistency prevents accidents.

Once you have passed step 4, you are done configuring. Every video you export with those settings will upload and process cleanly on the first try. Save time and processing by getting export settings right at the start.

---

🚀 Start Dubbing Your Videos Today

DubLab uses AI to translate your videos into 92+ languages in minutes.

📱 Download for iOS

🌐 Try Free at dublab.app