A One-Page Localization SOP for Every Upload

What a localization SOP is for

Once you translate more than the occasional video, the work stops being creative and becomes routine: export the right audio, run the translation, check names, upload files, fill in metadata. Routine work goes wrong in boring ways. A step gets skipped when you are tired, a new editor does it differently, a subtitle file goes to the wrong language version.

A standard operating procedure fixes that by writing the routine down. It is not a strategy document; which languages to add and why belongs elsewhere. It is the page you open every time a video is ready, follow from top to bottom and tick off.

One page is the right size. If the procedure needs more, the extra detail usually belongs in linked reference notes, such as a term list or a style guide, rather than in the steps themselves.

The parts of a one-page template

Every SOP for translating uploads needs the same blocks. Use this as the skeleton:

Purpose

One sentence: which videos this covers and what a finished result looks like.

Trigger

The exact event that starts the procedure.

Inputs

The files and information that must exist before step 1.

Steps

Numbered actions, each starting with a verb, each with an owner.

Checks

Pass or fail tests at the points where errors are cheap to fix.

Outputs

The files produced, with their names and where they are stored.

Publish

Where each language version goes and what must be filled in.

Owner and date

Who maintains the page and when it was last changed.

Keep the language plain and the steps concrete. Write "Export dialogue-only WAV from the final timeline, full length" rather than "prepare audio".

Define the trigger and inputs

The trigger answers the question "when does this start?" Good triggers are events you cannot miss: the English master is approved, the video is scheduled, the editor drops the export into the shared folder. Vague triggers like "after publishing" let translation slide by weeks.

Then list the inputs that must be ready before anyone starts:

• The final master and a dialogue-only audio stem from the locked edit.
• A music-and-effects stem, if you dub from the dialogue stem and want the cleanest remix of the original music under the new voice. Dubs made from the full master keep the original background automatically.
• The target languages for this video, which may differ from video to video.
• The current term list: names, brands and phrases with agreed translations or kept in the original.
• The English title, description and any pinned comment text.

If an input is missing, the SOP should say what to do: wait, or proceed with subtitles only, for example. That one line prevents the most common improvisation.

Write the steps with owners

Even on a one-person channel, give every step an owner. When you hire help later, you only change names, not the procedure. A typical set of steps:

1. Export the dialogue stem from the locked timeline, full length from the first frame. Owner: editor.
2. Run transcription and check the source transcript for names and numbers. Owner: creator.
3. Run translation for each target language: a dub where the format suits it, subtitles otherwise. Owner: creator or assistant.
4. Download every output, rename it to the house convention and file it in the language folder. Owner: whoever ran the job.
5. Search each translated transcript for every entry on the term list and fix or flag mismatches. Owner: reviewer for that language.
6. If the dub was made from the dialogue stem, remix the dubbed audio with the music-and-effects stem; otherwise check the kept background. Export the language version. Owner: editor.
7. Translate the title, description and chapters. Owner: reviewer for that language.
8. Run the publish checklist below. Owner: channel manager.
9. Log the version in the tracker: date, languages, reviewer, anything changed. Owner: channel manager.

Choosing between subtitles and a dub per format is a decision you make once and record in the SOP, not every time; subtitles versus dubbing lays out the trade-offs. If several people review each language, the hand-offs and approval rounds deserve their own page; see a review workflow for teams rather than packing it into this one.

Checks that catch problems early

Checks are the part of an SOP that pays for itself. Put them where a mistake is still cheap:

• Before translation: the audio file is the full length of the final edit and has no stray tracks or test tones.
• After transcription: names, product terms and numbers in the source transcript are correct. Errors here carry into every language.
• After translation: every term-list entry appears in its agreed form. Numbers, prices and dates match the original.
• After the remix or background check: watch the whole language version at normal speed. Listen for lines that sound rushed, clipped words, music that drowns speech and faint traces of the original voice.
• Before publishing: the right subtitle file is attached to the right version, and links in the description point to pages in that language where they exist.

For dubbed versions, a fuller list of what to listen for is in the AI dubbing quality checklist. Copy only the items that have caught real problems for you; a check nobody performs is worse than no check, because it creates false confidence.

File names and storage

Write the naming rule into the SOP with one real example per file type, so nobody has to guess. Name each file with date, short slug, file type and language tag, for example 2026-10-02_lens-guide_subs_pt-BR.srt, and keep all files for a language in one folder inside the video's folder. The full folder system is described in video asset management for creators; the SOP only needs to point to it.

Publish steps

Publishing is where versions get mixed up, so list it as its own block. For each language version:

• Upload or attach the right file: a separate video, an extra audio track, or a subtitle file, depending on the platform.
• Paste the translated title, description, chapters and tags.
• Set the language fields the platform offers for the video, audio and subtitles.
• Use the localized thumbnail if you make one.
• Check that end screens, cards and links still make sense in that language.
• Schedule or publish, then open the public page and play the first minute.

The metadata step has its own detail; translating titles and descriptions covers it.

Example: a weekly cooking channel

Mistakes, limits and keeping it current

The most common SOP failures:

• Writing the ideal process instead of the real one. Start from what you actually do, then improve it.
• Burying decisions inside steps. Language choices, voice choices and per-format rules go in a short decisions section at the top.
• Too many checks. Each one should have a reason you can name.
• No owner for the document. Without one, the page drifts out of date within a few months.
• Treating it as permanent. Tools, platforms and your formats change.

An SOP cannot replace judgment. It will not tell you that a joke does not land in Portuguese or that a sponsor read needs a different approach in another market. It also assumes a stable format; a one-off documentary or a livestream may need its own variant rather than forcing the standard steps.

Keep it current with a simple rule: whenever someone does a step differently and it works better, they update the page and the date in the same session. Review the whole page every quarter or after any tool change, and delete steps that no longer happen.

Where mydubly sits in the SOP

In a template like the one above, mydubly covers steps 2 and 3, and produces the files for step 4. You choose a video or audio file from your device, up to 2 hours long; the spoken language is detected automatically. A transcript job returns a plain transcript, a timestamped transcript, and SRT and VTT subtitles, optionally with a translated transcript. A dubbing job returns translated audio (the new voice mixed over the original background, with the original speech removed), a translated video with that audio, target-language subtitles that follow the dubbed lines, and transcripts in both languages.

A few facts belong in the SOP itself. Each job produces one subtitle language, so plan one job per language. Leaving or closing the page cancels the job, so the person running it keeps the tab open until downloads are done. Results are deleted within 30 minutes of a job finishing, so step 4 happens immediately. mydubly has no glossary import, batch mode, API or review tool, so the term check, approvals and tracking stay in your own documents. Prices for the procedure are easy to state: transcripts cost 1 credit per minute with a 5-credit minimum, dubs 50 credits per minute with a 2-minute minimum.

Next step

Open a blank document, write the trigger and the nine steps above in your own words, and follow it for your next upload in the video translator. Fix the page as you go; after three videos it will describe your real process, and it will be ready to hand to someone else.