Transcription used to be the chore you did after the video was finished, usually because a client asked for a subtitle file at the last minute. Today it sits much earlier in the process. Social feeds autoplay without sound, search engines index caption text, and accessibility rules in several regions treat missing captions as a legal defect rather than a polish item. If your team publishes video across more than one language, transcription is no longer an afterthought — it is part of the publishing pipeline.
This guide is a practical workflow for teams producing video for social platforms and websites in multiple languages. It covers how to choose a caption path, how to run a repeatable pipeline, what actually drives accuracy, how to plan turnaround, and how to keep accessibility compliance from becoming an emergency. Instead of ranking specific vendors, it focuses on the decisions that determine whether your captions are usable six months from now.
Why transcription moved into the core workflow
Three forces pushed transcription from post-production convenience to default infrastructure.
First, viewing behavior. A large share of social video is watched with sound off, at least for the first few seconds. Captions are often the only thing that keeps a viewer in the first ten seconds, which is where most drop-off happens. A video with clean captions can be understood in silence; a video without them is a series of unexplained visuals.
Second, discoverability. Caption text is machine-readable. It feeds search indexing, recommendation systems, and internal content archives. Teams that caption consistently build a text corpus they can search, repurpose into articles, and use to train their own glossaries. Teams that do not end up with a video library nobody can query.
Third, compliance. Accessibility expectations have hardened. In the European Union, public sector and many publicly funded bodies work against EN 301 549, which references WCAG success criteria for media. In North America, ADA-related litigation and Section 508 requirements for federal procurement set similar expectations. Comparable rules and guidance exist in Canada, the United Kingdom, Australia, Japan, and Brazil, and they differ in detail rather than in direction. The trend line is consistent: captions for prerecorded video are expected, not optional.
None of this means every clip needs a broadcast-grade subtitle file. It means you need a deliberate process that scales with the stakes of each piece of content.
Decide what deliverable you actually need
Most transcription problems start with a mismatch between the file you produce and the job it has to do. Before choosing any tool, agree on the deliverable.
| Deliverable | Typical use | Notes |
|---|---|---|
| Raw transcript | Internal notes, repurposing, search | Can be unformatted, speaker labels optional |
| Edited transcript | Articles, show notes, quotes | Needs human review for names and numbers |
| Caption file (SRT, VTT) | Platform upload, website player | Needs timing, line breaks, reading speed control |
| Burned-in subtitles | Social video with no player controls | Inflexible; language variants require re-render |
| Translated caption set | Multi-language distribution | Built from a locked source caption file, never from raw ASR |
Two distinctions matter more than people expect. The first is transcript versus caption: a transcript is read, a caption is read at playback speed with a limited window. A sentence that reads fine on a page can be unreadable as a two-line caption. The second is verbatim versus edited. Verbatim captions preserve every filler word; edited captions clean up false starts and repetitions. For accessibility purposes, edited captions are usually acceptable for prerecorded content as long as meaning is preserved, but live content generally needs near-verbatim output.
Decide these two questions upfront, and half the tool-selection debate disappears.
A seven-step transcription workflow that scales
The following pipeline works for a single editor and for a distributed team with several language owners. The key is that each step has a clear owner and a gate.
Step 1 — Inventory and triage
List every video asset with four attributes: language, duration, content type, and stakes. Stakes is the important one. A regulatory explainer for a public-facing program has different requirements than a five-second teaser. Build three tiers:
- Tier A: regulated or high-visibility content — full human review, speaker labels, translated caption sets, archived source files.
- Tier B: marketing and product content — machine pass plus human review of names, numbers, and terminology.
- Tier C: episodic social content — machine pass plus spot check, with a shared glossary enforced automatically.
Triage prevents the two most common failure modes: over-processing throwaway clips and under-processing content that ends up in a legal review.
Step 2 — Language detection and code-switching
Automatic language detection fails predictably in three situations: heavy accents, music-heavy intros, and code-switching, where a speaker moves between two languages inside one sentence. If your content regularly mixes languages, do not rely on detection. Tag the asset manually and, where possible, split the pipeline so each language gets its own model pass and its own reviewer.
For code-switched content, a practical approach is to transcribe the dominant language first, then have a bilingual reviewer fill the second language. Punctuation and capitalization rules differ between languages, and a single pass often produces inconsistent results.
Step 3 — Machine pass
Run the audio through your chosen speech recognition engine, ideally at the highest sample rate you have. Do not use the compressed export that was uploaded to the platform if a cleaner master exists; compression artifacts measurably hurt accuracy. Output should include word-level timestamps if the tool supports it, because word timing makes later caption formatting far easier.
At this stage, do not fix anything. The machine pass is a draft. Its job is to get you to roughly 90 percent accuracy quickly so that human attention goes to the hard 10 percent.
Step 4 — Human review
Quality review has a priority order. Fix these first, because they cause the most damage when wrong:
- Names of people, companies, and products
- Numbers, dates, currency, and units
- Technical and legal terminology
- Negative constructions and anything that flips meaning
- Speaker labels
The review pass is also where you capture glossary additions. Every correction that will recur should go into a shared term list so the next machine pass gets it right without human effort.
Step 5 — Caption formatting and timing
Formatting rules should be written down once and applied to every file. A workable starting point:
- Maximum two lines per caption
- Roughly 32 to 42 characters per line for Latin scripts, fewer for languages with longer average word length
- Minimum caption duration around 1 second, maximum around 6 seconds
- Reading speed under about 20 characters per second for general audiences, lower for children's or highly technical content
- Break lines at natural phrase boundaries, not at arbitrary character counts
- Keep speaker identification consistent and unobtrusive
Languages expand differently. A German or Spanish caption of the same content is typically longer than the English source, while Chinese and Japanese are usually shorter in character count but need different line-breaking rules. Build the formatting step per language rather than assuming one set of limits fits all.
Step 6 — Translation and localization variants
Translate from a locked, reviewed source caption file — never from raw machine output. Translate captions as captions, meaning the translator needs to respect reading speed and line limits, not just produce an accurate sentence. Budget for a review pass by a native speaker who understands the product, because idioms and formal or informal address patterns cause more audience friction than minor terminology slips.
For right-to-left languages, verify rendering in the actual player, including punctuation placement and any embedded Latin brand names. For CJK languages, confirm that your player handles line breaking correctly instead of breaking mid-word visually.
Step 7 — Publish, verify, and archive
After upload, watch the video with captions enabled on at least one mobile device and one desktop browser. Check synchronization drift, truncated lines, and caption overlap. Then archive the source caption file, the translated variants, and the glossary version used. Versioning sounds bureaucratic until the first time someone asks for a corrected version of a two-year-old video.
What actually drives accuracy
Word error rate is the standard accuracy metric, and it is easy to misread. A 10 percent word error rate does not mean one in ten words is unreadable; it means the transcript needs a review pass, and edits will cluster around proper nouns and domain vocabulary.
What moves accuracy in practice:
- Audio quality. A lapel microphone beats a room microphone more than any model upgrade.
- Overlapping speech. Panel discussions and interviews with crosstalk are the hardest case for any engine.
- Domain vocabulary. Medical, legal, and engineering content needs a custom term list or accuracy collapses on exactly the words that matter most.
- Accents and dialect. Model quality varies widely by language and region. Always test with audio that resembles your actual speakers, not a clean studio sample.
- Code-switching. Expect a measurable drop and plan bilingual review.
- Numeric formatting. Telephone numbers, prices, and dates need explicit rules, because a plausible-looking wrong number is worse than a visibly uncertain one.
- Diarization. Speaker separation quality matters for interviews and training content. Poor diarization creates caption files that are technically accurate and practically unusable.
A reasonable expectation for a mature workflow: machine output at 85 to 92 percent accuracy, and a finished caption file at effectively full accuracy after review for tier A and B content.
Planning turnaround and throughput
Speed benchmarks from tool demos rarely match production reality. A transcription engine may return a draft in less than real time, but the finished deliverable includes review, formatting, and verification. Practical planning numbers for a team new to the workflow:
- Machine pass: often 0.1x to 0.5x of video duration
- Human review and formatting: 2x to 6x of video duration for complex content, less for clean monologue
- Translation and localized review: 2x to 4x of video duration per language, depending on how much the target language expands
That means a ten-minute interview can consume several hours of combined effort before it is publishable in three languages. Plan capacity by language, not by total minutes, because your bottleneck will almost always be the one reviewer who covers an under-resourced language.
Two structural choices speed things up. Batch by language so a reviewer stays in one linguistic context. And treat glossary maintenance as continuous work rather than a quarterly cleanup, because glossary quality compounds: every term you add saves review time on every future asset.
Multilingual quality checks that catch most failures
Build a checklist that runs before every publish. The items below catch the majority of real-world defects.
- Spot-check the first 30 seconds, a mid-point, and the final 30 seconds for drift
- Verify every proper noun against the glossary
- Confirm numbers, dates, and currency formats follow the target locale
- Check that on-screen text matches spoken captions where they overlap
- Confirm formal versus informal address is consistent throughout
- Review caption line breaks visually, not just in a text editor
- Test one caption file on a small screen; line lengths that look fine on desktop often overflow on mobile
- Confirm the language tag on the file or platform setting is correct, since a wrong tag suppresses the correct caption track for viewers
If a video includes music, decide once whether to caption lyrics, describe music, or stay silent. Inconsistent handling across a series looks careless.
Accessibility compliance as a design constraint
Accessibility is easier when it is designed in rather than audited later. The WCAG media success criteria give a useful framework regardless of your jurisdiction: captions for prerecorded content, a transcript or media alternative, audio description where visual information is essential and not conveyed in the audio, and live captions where live content is published. Regional frameworks — EN 301 549 in the European Union, Section 508 and ADA-related obligations in the United States, and equivalents in Canada, the United Kingdom, Australia, Japan, and Brazil — mostly point at the same underlying practices with different enforcement.
Practical implications for a video team:
- Keep a transcript page alongside embedded video so search engines and assistive technology both have a text version
- Ensure caption styling has sufficient contrast against the video; default white text with a hard shadow or a semi-opaque background box usually works
- Do not rely on color alone to convey meaning in on-screen graphics
- Provide audio description or an equivalent descriptive track for content where visuals carry essential information
- Keep captions available for archived content, not just new uploads; remediation projects get expensive fast
Documenting your process matters as much as the output. A short internal standard that states your caption tiers, review rules, and file formats will answer most compliance questions without a scramble.
Choosing tools without getting locked in
Tool selection should follow the workflow, not the other way around. Evaluate candidates against a short list of criteria tied to your actual constraints.
| Criterion | Why it matters |
|---|---|
| Language coverage and quality per language | Regional accuracy varies more than vendor marketing suggests |
| Export formats | SRT, VTT, and editor-native formats reduce manual conversion |
| Word-level timestamps | Makes caption timing adjustments dramatically faster |
| Glossary or custom vocabulary support | The single highest-leverage feature for recurring content |
| Speaker diarization | Required for interviews, panels, and training material |
| Collaboration and versioning | Multi-reviewer workflows fail without it |
| Data handling and retention | Relevant for unreleased product or regulated content |
| API or batch processing | Needed once volume passes the manual threshold |
| Offline capability | Useful for confidential material or unreliable connectivity |
In practice, teams end up with a hybrid: a general speech recognition engine for drafts, a subtitle editor for timing and formatting (Subtitle Edit and Aegisub are common choices), and an editor-integrated caption panel in tools like Premiere Pro, DaVinci Resolve, or CapCut for simple projects. Specialist services make sense for tier A content where human review is mandatory and turnaround is tight. Test two or three options against the same hard three-minute clip in your least-supported language, then compare finished files rather than demo output.
Compare plans directly against the vendor's own published terms, and factor in review labor. The cheapest draft is rarely the cheapest finished caption file.
Common mistakes to avoid
- Treating automatic captions as a finished deliverable rather than a draft
- Translating before the source caption file is locked, which forces a full redo
- Ignoring reading speed and producing technically accurate but unreadable captions
- Using one formatting standard across languages with very different expansion rates
- Failing to version caption files alongside video masters
- Skipping mobile testing, where most line-length problems surface
- Leaving glossary maintenance to whoever remembers, so accuracy never improves
- Forgetting that archived content also needs captions when it is republished
Most of these are process problems, not technology problems. That is good news, because process problems are cheaper to fix.
FAQ
How accurate are automatic captions, realistically?
For clean audio in a well-supported language, expect 85 to 92 percent accuracy on the draft. That is good enough to accelerate review and not good enough to publish unreviewed for anything regulated or brand-critical.
Do I need a transcript if I already have captions?
Yes, for most teams. A transcript page improves discoverability, supports assistive technology, and gives you reusable text for articles and posts. It is also easier to search than a caption file.
Should I burn subtitles into the video?
Only when the player offers no caption controls, such as some social placements. Burned-in subtitles lock the language and require a re-render for every variant, so prefer sidecar files wherever possible.
How do I handle videos with two or three languages?
Tag the asset manually, run separate machine passes per language, and route each to a reviewer fluent in that language. Do not ask one reviewer to validate a code-switched transcript in an unfamiliar language.
What is the minimum viable quality standard?
Meaning preserved, names and numbers correct, captions synchronized within a fraction of a second, reading speed comfortable, and a transcript available. Everything above that is polish that matters more for regulated content.
How often should we revisit our tooling?
Once a year, or whenever a language owner reports recurring pain. Speech recognition improves quickly, but switching costs are real, so change tools when a specific criterion — glossary support, diarization, a language you cannot cover — is unmet.
A pre-publish checklist worth keeping
Before anything goes live, confirm: the source caption file is reviewed and locked; names, numbers, and terminology match the glossary; line lengths and reading speed pass a mobile check; language tags are correct; translated variants were built from the locked source; the transcript page exists for long-form content; and both the video master and caption files are archived with version numbers.
Run that checklist consistently and transcription stops being a recurring crisis. It becomes what it should be: a quiet, predictable part of how your team publishes video to a multilingual audience.
Where to improve next
If your pipeline is stable, the next gains come from three places. Build a domain glossary and keep it under version control. Standardize caption formatting per language instead of per editor. And measure something — even a simple sample audit of a few files per month — so you can tell whether accuracy is improving or quietly slipping. Teams that measure transcription quality tend to fix problems while they are still cheap, which is the entire point of treating it as a workflow rather than a last-minute task.
