# How to localize online courses for international students

> A practical plan for taking a finished course to new languages, covering what to translate, in what order, and how to keep quality up across dozens of lessons.

Guide · Published 2026-10-22
Canonical page: https://dubtitle.com/guides/how-to-localize-online-courses-for-international-students/

Most course creators discover international students by accident. Someone from Brazil emails to say how much they got out of lesson four, despite struggling with the English. A few more messages follow. Then you look at your sales dashboard and notice a slice of revenue from countries you never targeted.

Those students are telling you something. If they're willing to push through a course in their second language, a version in their first could reach many more like them. This guide is about how to build that version without turning it into a second full-time job.

<figure class="guide-figure">
<img src="/guides/figures/course-plan.webp" alt="Seven steps for localizing an online course: choose languages, triage lessons, prepare the course, dub, review with a native speaker, handle surrounding materials, then measure and expand." width="1600" height="900" loading="lazy" decoding="async" />
<figcaption>The plan at a glance. Each step is covered below.</figcaption>
</figure>

## Localization is more than translation

It helps to name the layers, because course creators often think only about the voice.

**Spoken content.** The lectures, demos and walkthroughs. This is the bulk of the work and the part that dubbing solves.

**On-screen text.** Slides, diagrams, code comments, lower thirds, UI screenshots.

**Supporting materials.** Worksheets, transcripts, quizzes, certificates, downloadable templates.

**Platform and packaging.** The course title, description, sales page, emails and support.

**Examples and references.** The dollar amounts, the cultural references, the sports analogies. These work fine in your home market and sometimes confuse people elsewhere.

You don't have to do all five at once. Most successful localizations start with the spoken content and the packaging, then work outward.

## Choose languages with evidence, not enthusiasm

It's tempting to pick the biggest languages. Resist. Start with data you already have.

- **Where do your current students live?** Look at enrolment by country, and refund and completion rates by country.
- **Who is asking?** Emails, comments and support tickets in other languages are a signal.
- **Where does your subject have demand?** A coding course, a nursing course and a real-estate course each have different geographies.
- **What can you support?** If you translate into Portuguese, someone needs to answer Portuguese questions, or at least you need a plan for it.

Pick one or two languages first. A well-supported second language beats six half-supported ones.

Also be specific about the variant. Brazilian Portuguese and European Portuguese are different markets, and Latin American Spanish isn't Spanish from Spain. If your audience is mostly in one place, say so when you choose.

## Triage your lessons

You don't have to localize every lesson on day one, and you may not want to. A sensible order:

1. **The free preview and the first module.** This is what people judge before and right after buying.
2. **Lessons with the highest completion and the best feedback.** Your best material earns the translation effort.
3. **Everything else, in order.** Once the first modules prove out, translate the rest.

Alternatively, translate the whole course at once if the cost is low enough that deciding is more work than doing it. With AI dubbing, it often is.

## Prepare the course for translation

Some of the best work happens before you translate a word.

**Fix the source.** If a lecture has an error or an outdated section, correct it now. Fixing it in every language later is far more work.

**Clean the audio.** Remove noise and level the volume. Bad audio produces bad transcripts, which produce bad translations.

**Reduce spoken references to the screen.** "As you can see here, in this blue box" works only if the viewer sees what you mean. Clear verbal signposting helps in any language.

**Write down your terms.** Every course has its own vocabulary: framework names, technique names, brand terms, abbreviations. Decide for each one whether to translate it, keep it in English, or use a local equivalent. This list becomes your glossary, and it's the single most valuable asset in the project.

## Dub the lessons

For the voice, you have a few choices.

**Hire human voice actors.** Highest ceiling, highest cost, slowest. It's rarely practical for a library of lessons.

**Use a generic synthetic narrator.** Fast and cheap, but students lose the instructor's personality, and with it a lot of the reason they enrolled.

**Use AI dubbing with voice cloning.** The translated lesson sounds like you, in another language. That continuity matters when students are paying for a person's expertise.

Dubtitle takes the third route. You upload your lesson videos, choose the languages, and it produces dubbed versions that keep your voice, pacing and emotion. Most videos finish in 2 to 10 minutes.

## Review with a native speaker

This is the step that separates a course students trust from one they put up with.

You don't need a professional translator for every lesson. A good, practical approach:

- **Review the first two or three lessons carefully** with a native speaker who knows the subject. Their corrections will reveal patterns: a term that's consistently wrong, a tone that's too formal.
- **Turn those patterns into glossary entries.** The fix applies to every later lesson automatically instead of being repeated by hand.
- **Spot-check the rest.** Sample a few minutes of each module.
- **Invite students to flag errors.** Make it easy: a feedback link in the lesson notes. Students are often your best reviewers.

In Studio, the reviewer can edit any line in the translated transcript, and only the changed lines are regenerated. A native-speaking reviewer can work through a lesson in a text editor's worth of effort, no audio editing needed.

## Handle on-screen text

This is the part people underestimate. If your slides are full of English text, students see English while hearing their language, which can be jarring.

Options, from least to most effort:

- **Leave it.** Reasonable for code, UI screenshots and product names that are English everywhere.
- **Add subtitles** for the key terms and instructions.
- **Re-export slides** in the target language. Worth doing for conceptual courses where the slides carry the teaching.
- **Replace diagrams** with localized versions.

Decide per course, not per lesson. Consistency matters more than perfection.

## Don't forget everything around the video

A flawless dub inside a course sold through an English-only page converts poorly. At minimum, translate:

- The course title and description
- The sales page and pricing copy
- Lesson titles and module names
- Transcripts or subtitles for each lesson
- Welcome and onboarding emails
- The refund and support information

Support is the one people forget. If a student writes in Portuguese and gets an English reply a week later, the localized course loses much of its value.

## Think about pricing and platforms

Purchasing power differs across countries. Some creators set regional prices, and many platforms support this. It's worth thinking about, though be careful not to undercut your home market.

Check where your course is hosted and whether it supports multiple language versions or separate course listings. Some platforms handle audio tracks within one course, and others need a separate copy.

## Measure, then expand

After launch, watch:

- Enrolment and completion rates in the new language, compared with your English course
- Refund rates
- Support questions about confusing sections
- Reviews that mention language quality

If completion is lower than in English, the usual culprits are translation issues, pacing, or an audience mismatch. Fix them before adding more languages.

## A first-month plan

**Week 1:** Analyse student data, pick one language, write your terminology list.
**Week 2:** Dub the first module and have a native speaker review it.
**Week 3:** Build the glossary from their corrections and dub the rest.
**Week 4:** Translate the sales page and emails, launch to a small audience, collect feedback.

If you'd like to test the process on a real lesson, [start a free trial](https://dubtitle.com/api/signup). Pick the lesson with the most specialist vocabulary. If it holds up there, the rest of the course will too.

## Frequently asked questions

### How do I translate an online course?

Pick target languages using student data, triage lessons by importance, prepare scripts and on-screen text, dub or subtitle the lessons, have a native speaker review them, then localize the materials around the video.

### Should I dub or subtitle my online course?

Dub when students need to watch demos or slides, because reading subtitles splits attention. Subtitle when the speaker’s voice matters or you need the fastest route. Many courses do both.

### How much does it cost to translate an online course?

Cost scales with lesson minutes times languages. AI dubbing is a small fraction of traditional dubbing, so a course that would be unaffordable with studios becomes practical.

### How do I keep course terminology consistent in other languages?

Use a translation glossary for key concepts, tool names and brand terms, and apply it to every lesson so a concept is translated the same way throughout.

### Which languages should I localize my course into first?

Look at where your current students come from, where search interest is growing, and where competitors are thin. Start with one or two languages, measure completion, then expand.
