Numbers, Dates and Currency in Dubbed Scripts

When you dub a video into a new language, most people focus on the script translation and voice quality. What often gets overlooked is how numbers, dates, and currency appear on screen and in the audio. A viewer in Germany reads "10/12/2024" completely differently than one in the US, and speaking a price in the wrong currency format breaks immersion fast.

The challenge is that these formats are deeply tied to locale, not just language. French speakers in Belgium, Canada, and France each have their own preferences. And when your video has on-screen graphics or overlay text, the mismatch between spoken and written form stands out immediately.

Number Formatting Across Locales

The decimal separator and thousands separator vary widely. In the US, one thousand dollars is written as 1,000.99. In Germany, France, and most of Europe, it is 1.000,99. In India, the grouping itself is different: 1,00,000 for one hundred thousand. Even within Europe, smaller differences matter: some locales use a space as thousands separator instead of a comma or period.

When your script mentions a price, profit, or statistic, you need to:

1. Decide whether to show it on screen, speak it, or both
2. Write it in the target locale's format
3. Ensure your voice talent speaks the number correctly for that region

If you are dubbing a business video that says "We reached $1,500,000 in revenue," the graphic should read "1.500.000 EUR" in Germany and "1,500,000 CAD$" in Canada. The spoken version must also match: in French, large numbers are often grouped differently when spoken aloud. A French speaker says "un million cinq cent mille," which flows naturally but does not read as "1,500,000" in the literal sense.

Locales and Their Number Formats

Here is a quick reference for major locales:

This table matters because a misplaced decimal or thousands separator shifts meaning instantly. If your German dub shows "1.234,56" but your talent says "one point two three four," the viewer catches the error and trusts the dub less.

Date Formats and Spoken Dates

Date confusion is frequent and costly. The US writes month-day-year (12/31/2024), while most of the world uses day-month-year (31/12/2024). If your video says "the launch is December 31st" and overlays a date graphic, that graphic must match the locale's convention.

More importantly, the way dates are spoken differs too. Americans say "December thirty-first" or "twelve thirty-one," while British speakers say "the thirty-first of December." Germans say "einunddreißigster Dezember" (day-first). Always record your dubbing talent speaking the date naturally for their market, not as a direct translation of how it was spoken in the original.

When a video shows relative dates like "in 3 weeks" or "since January," check whether the translation needs adjustment. A deadline that makes sense in one market might create confusion in another, and your dub should feel natural to the viewer, not translated-by-numbers.

Date Format Examples

A common failure point: showing "01/15/2024" in a German video where the viewer will read it as the 1st of March, not January 15th. Your on-screen text must match the locale's expectation, and your talent must speak it in the natural form for their region.

Handling Ambiguous Dates

If your original uses a format that could be misread (like "01/02/2024" which could mean January 2nd or February 1st), clarify it in your dub. Instead of relying on the graphic alone, have your talent say "January second" or "the second of January" clearly. This removes doubt. In the dubbed version, the graphic should then show either "01/02/2024" (if using US format) or "02/01/2024" (if using most other locales), and it should match what was spoken.

Currency: Code, Symbol, and Conversion

Currency presentation has three common forms: symbol ($, EUR, GBP), code (US$, 150 EUR), or spoken name. Your choice depends on the target audience and whether the amount appears on screen.

Many creators make the mistake of keeping the original currency without thinking. If you dub a product demo video from US dollars into Japanese, it often makes sense to quote prices in yen, not dollars, so viewers see prices that feel real to them. But if you are dubbing a financial training video, you might keep the original currency and simply voice it clearly: "That is 50 euros, or roughly 55 US dollars at today's rate."

The on-screen text matters most. If you overlay "$50" but your talent says "fifty euros," you have created jarring noise. Sync them exactly. If you cannot change the graphic, adjust the script to match the graphic. Do not assume your viewer will mentally convert.

Currency Decision Framework

Ask these questions in order:

1. Is this product or service sold in the target locale? If yes, use the local currency. If no, keep the original but explain the rate.
2. Is the price an incidental detail or the main point? If incidental, you can use the original currency. If the main point (a sales video, a pricing discussion), use local currency.
3. Will the viewer look up a conversion? If they will (luxury items, international services), use the original. If they will not (everyday products), use local.
4. Does the original video show on-screen price tags or overlays? If yes, you must convert both the graphic and the audio. If no, you have flexibility.

Currency Format Examples

Avoid mixing formats in a single video. If your graphic shows "$50" but later shows "EUR 100," pick one style and stick with it.

Spoken Versus Written Forms

Numbers in video live in two channels: audio and visual. They must agree, or the viewer feels the production is sloppy.

This is especially important for percentages, phone numbers, large numbers, and decimals. For percentages, decide if you will say "15%" or "fifteen percent" and commit to one. If your graphic shows "15%," but your talent says "one five," viewers will check the graphic and find a mismatch.

Phone numbers are particularly tricky. English speakers usually say digits individually: "Call five-five-five, one-two-three-four" (555-1234). But German speakers often group them: "Fünfundfünfzig, einunddreißig, vierundvierzig" (55-31-44 for a seven-digit number). Check the talent's market convention, then ensure your script directs them to speak that way.

Large numbers need care. If your graphic shows "2M," does your talent say "two million" or "two em"? If "2 million," does it sound like "two million" or like they are reading the abbreviation? Test this with actual voice talent before finalizing, because the difference is audible.

Decimals trip up many teams. French voice talent instinctively says "virgule" (comma) when they see a decimal point because in French, the decimal separator is a comma. If your graphic shows "2.5 kg" but the speaker says "deux virgule cinq," viewers will look at the screen and see "2.5" not "2,5," and will be confused. Either retrain the talent to say "point" (which sounds odd in French), or change the graphic to "2,5 kg" and have them say "deux virgule cinq" naturally.

Audio-Visual Sync Test

Record your dub, then run this test before final export:

1. Mute the video and read only the visible numbers, recording what you see
2. Unmute the video, listen with closed eyes, and record what you hear
3. Compare the two lists character by character

Any mismatch means re-recording or re-editing. This single test catches most locale errors.

Common Mistakes and How to Fix Them

Mistake 1: Leaving English-format dates and numbers in the target language script. A German viewer reads "12/31/2024" as December 31st, but sees "31/12/2024" in their mind first. If your script says "Let's meet on 12/31/2024" in a German dub, they will stumble. Fix: Convert all dates to the locale format in both script and graphics before recording.

Mistake 2: Speaking a number differently than it appears on screen. If your graphic says "3,5 billion" but your talent says "three point five billion," the mismatch is audible and visible. Fix: Test with real voice talent, not assumptions. Provide a reference sheet with exact phonetic spellings of how to say each number.

Mistake 3: Ignoring currency conversion when it matters. If the original says "$100" and you dub into German without converting, German audiences must mentally convert to EUR. This breaks the flow and makes them distrust pricing. Fix: Use DubLab or similar tools to strip and replace on-screen text, then adjust the script. If that is not possible, have your talent voice both currencies: "That is $100, or roughly 95 euros."

Mistake 4: Forgetting to brief voice talent on number pronunciation. Many talent spend their whole career speaking numbers the way they learned, not how the locale expects. If a German speaker has only ever said "Punkt" for a decimal separator, they will default to it even if the script says "Komma." Fix: Provide a style guide with audio examples, not just text. If possible, record a short reference video showing the talent exactly how to pronounce each number.

Mistake 5: Using automatic machine translation for numbers. Translation APIs sometimes mangle decimal separators, especially in technical or financial content. A number might come out "1.234,56" when your locale needs "1 234,56." Fix: Always export numbers to a separate review step. Do not trust automation. Have a human check every price, date, and figure before recording.

Mistake 6: Not checking time zones in relative dates. If your original says "This offer expires in 24 hours" and shows a specific time, that time might be wrong for the target locale's time zone. Fix: Calculate the deadline in the target locale's time zone, then voice it clearly if it changes.

Workflow: From Script to Finished Audio

Before you record your dub, follow this exact sequence:

Step 1: Extract All Numbers, Dates, and Currency

Go through the original script and create a list of every number, date, and currency figure. Include on-screen graphics, overlays, and subtitles. Do not rely on memory.

Step 2: Decide the Target Locale and Format Each Figure

For each item, decide: Does this need to be converted to the target locale's currency or date format? If yes, convert it. Write down both the visual format (how it will appear on screen) and the spoken form (how talent will pronounce it).

Step 3: Update Graphics and Subtitles

If your video has on-screen text, update it to show the target locale's format. Do not skip this step. If you cannot edit the graphics, note it clearly for the talent so they know to voice it differently than the graphic shows.

Step 4: Create a Reference Sheet for Voice Talent

Write a one-page guide showing each number, date, and currency in both formats, with phonetic pronunciation if helpful. Example:

Price: Show "$100" on screen, voice: "one hundred dollars"
Locale version: Show "95 EUR" on screen, voice: "ninety-five euros"
Date: Show "12/25/2024" on screen, voice: "December twenty-fifth, twenty twenty-four"
Phone: Show "555-1234" on screen, voice: "call five-five-five, one-two-three-four"

Step 5: Record and Verify

During recording, have the talent read a few numbers out loud before the official take so you can confirm the pronunciation matches your expectation. After recording, run the audio-visual sync test described above.

Step 6: Final Review

Watch the finished dub with both sound on and graphics visible. Does every number match? Does every date? Does every price? If not, re-cut the audio or update the graphics.

What to Do Next

1. Audit your current dubbed videos. Pick one and run the audio-visual sync test. Note any mismatches between spoken and written numbers, dates, or currency.

2. Create a locale reference sheet for your target markets. Document the date format, number format, and currency standard for each locale you dub into. Keep it in a shared doc your team can access.

3. Brief your voice talent in advance. Before booking a recording session, send them examples of how to pronounce numbers, dates, and prices for their locale. Ask them to confirm they are comfortable with the style you want.

4. Implement a number-check step in your workflow. Before final export, assign one person to verify every number, date, and price appears in the correct format on screen and is spoken correctly in the audio. This single step removes most errors.

5. Use a tool that supports locale formatting. If you are dubbing at scale, DubLab can help automate some of this work, though you still need to verify the output. Tools that strip and replace on-screen text in the target language make it easier to keep graphics and audio in sync.

Numbers and currency are small details, but they carry weight. A viewer who sees the date in the wrong format, or hears a price that does not match the screen, instantly feels the dub is rough. Getting these details right lifts the entire production and builds confidence in your brand.

---

🚀 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