Practical guide

How to translate subtitles from your video

Start with what you actually have: a video with speech, or an existing subtitle file. This guide follows the video workflow in ClipLocale. If the input is already SRT, follow the SRT file guide instead; re-transcribing a video is a different task from translating existing cues.

Open the example workspace

1. Choose a short, representative input

Open the workspace and select the local video. Read its duration and any media-support error before starting recognition. Choose a section that includes the speakers and vocabulary you care about. A quiet introduction alone may not reveal the errors in the rest of an interview or lesson.

Selecting the video is local. When you click Generate, Google sign-in is required. The normal Google popup keeps your selected video in the original workspace. If your browser blocks the popup, the explicit same-page fallback explains that you must select the video again on return; media is not saved to survive navigation. The prepared example remains available without an account.

2. Set the spoken and target languages

Select English, Chinese, Spanish, or Japanese as needed, or leave the spoken language on Auto. The target choice is the language of the translated text, not a request to replace the video audio. ClipLocale creates subtitles and does not dub the video.

Choose languages before processing. Once chunks have started, changing the language can produce inconsistent results, so review the whole intended direction first. A video that switches languages repeatedly needs careful manual review; a single language selector is not a promise of reliable multilingual speaker identification.

3. Confirm the processing range

The service checks account balance before sending audio. Each account has one 300-second trial. If the video exceeds the available seconds, you can review and explicitly confirm an affordable prefix. The retained result covers that prefix, not the entire clip.

Audio is extracted and sent in bounded chunks. Wait for the full selected range to finish before treating the subtitles as complete. A partial result after an error can be useful, but an already translated first chunk does not prove that the ending has been processed. Cancelling the client request is also separate from confirming a billing release.

4. Review original text, meaning, and timing in that order

Listen while viewing the original captions. Correct missing words, proper names, and speech-recognition mistakes before relying on the translation. Then compare the translated lines with the speaker’s meaning, especially instructions, negation, numbers, and references such as “this” or “that”.

Click a cue on the timeline to inspect its start and end. Captions should appear while the relevant words are spoken and clear during genuine gaps. Avoid dragging all captions earlier to fix one bad cue. Check a cue near the beginning, another in the middle, and one near the end to detect drift.

  1. Read the original line while listening to the matching audio.
  2. Compare the translation for meaning rather than word count.
  3. Play through the cue boundary and any silence after it.
  4. Check that an edited line is still readable in the available time.

5. Export the right subtitle variant

Use translated-only content for viewers who need the target language. Use bilingual content for learners or reviewers who want to compare lines, and original content when a separate translator will take over. SRT works as a common interchange file; VTT is useful for compatible web players. Player support and styling vary.

Download before closing the tab. Reopen the subtitle file with the same video in the intended player or editor and inspect the last cue. Confirm that the chosen export mode contains the text you expect and that the file is encoded correctly. The download creates a subtitle file; embedding captions into video pixels is a separate export in a video editor.