Wedding speech subtitles. Share the words with both families.

Make the toast understandable beyond the room

A wedding recording can preserve a speech that some relatives could hear but could not understand. A translated subtitle track lets them follow the speaker’s words while keeping the original voice. Polyglot can create, translate and review timed text locally on an Apple Silicon Mac, then export separate SRT or WebVTT files for a compatible player.

This workflow is for a videographer or family editor preparing permission-cleared speech clips after the event. Start with one complete, final speech clip in a supported spoken language. Decide which relatives need the original-language track and which need a translation. Polyglot does not provide live ceremony interpretation, identify speakers automatically or host a private family gallery.

If your existing editor already produces reviewed language tracks that work in the delivery player, you may not need a separate subtitle tool. The useful job here is the review and handoff: one approved speech, the right language files and a recipient who can actually turn them on.

Agree the clip, language and viewing scope

Confirm permission to process the recording, prepare translations and share the resulting clips with the intended people. A couple’s approval does not by itself establish every speaker’s permission or clear music and other included material. Keep private family delivery separate from permission to use a speech in a public videographer portfolio. Record those decisions outside Polyglot.

Make a small delivery sheet with the exact speech filename and edit revision, spoken language, requested subtitle languages, reviewer and intended audience. Use a project identifier if filenames containing family names would reveal more than needed. Preserve the original recording and earlier approved exports.

Use the final standalone clip as the timing reference, including its opening title or silence. If an editor later moves the toast into a highlight film, its subtitle timestamps do not automatically become highlight-film timestamps. That new edit needs a separate timing and playback check.

Handle language switches before trusting a draft

Check the supported speech-recognition languages before importing. Recognition covers 25 European languages; translation targets are a separate list. A translation option is not evidence that the app can recognize that language from a recording. The app detects the source language automatically, and a speech that switches languages can need additional human work.

For separately delivered speeches, keep a separate project for each final clip and review every spoken passage against playback. Do not assume a greeting or quotation in another language has been understood because the rest of the draft reads well. Ask a speaker or qualified reviewer to resolve it; never fill an unclear phrase from an expected wedding script.

For a mixed-language film, use a human-reviewed, correctly timed SRT or WebVTT source when automatic recognition cannot provide a reliable draft. Polyglot can import and edit that file. Preparing missing cues or assembling separately timed segments may require another subtitle editor. Splitting and recombining a wedding film is not an automatic Polyglot workflow. Hold a language track if you cannot get its meaning checked.

Check relationships, nicknames and the joke

Review the original text first. Give the reviewer the recording and a short, approved reference for names and preferred spellings. Family context can help verify a name, but it must not add facts the speaker never said. A nickname, a term of affection or a reference to “our first home” can be mistranscribed or translated into a different relationship.

For each requested target language, ask someone fluent in both languages to watch the speech while reading the translation. Check who each pronoun refers to, whether a relationship is literal or affectionate, and whether a joke still means what the speaker intended. Avoid explaining the punchline early or turning a playful remark into a factual claim. Keep cultural explanations outside the captions unless they are actually spoken.

The fictional note below illustrates a review question, not a verified translation or a processed wedding recording. The reviewer must use the audio and the relevant languages to choose the final wording.

Fictional speech review
Clip: toast-02-v3.mp4
Source: English
Requested track: Dutch

Heard: “my other brother”
Context: a close friend
Check: affectionate wording,
not a new family relationship

Reviewer: confirm in context
Audience: agreed family group

Approve the recording and subtitles together

Review the final clip with each track from beginning to end. Check the first words after the microphone is handed over, quiet asides, applause that masks speech, the punchline and the final toast. Read translated lines at playback speed. Polyglot preserves source timing during translation; you can adjust a language’s cue timing independently when needed. Cue splitting, merging or special placement needs a suitable finishing editor.

W3C distinguishes translated speech subtitles from captions that also communicate relevant sounds and speaker context. If a relative needs captions to follow without hearing the audio, arrange that human captioning pass too. Automatic speech text alone is not a complete accessibility review.

If a speaker requests removal of a personal anecdote, resolve that in the media edit and obtain a new approved clip. Deleting only its subtitle does not remove the audible information. Recheck all language files after an edit, and keep rejected drafts out of the delivery folder. Polyglot is not a redaction or video-editing tool.

Test the actual family viewing route

Ask the delivery provider which timed-text formats and language tracks it accepts before export. Name each reviewed file with the clip revision and language, then upload or attach it manually using that provider’s process. YouTube’s documentation, for example, supports adding a language and uploading a timed subtitle file. That is a destination example, not a Polyglot integration or a recommendation to upload private recordings there.

Agree the access setting with the people responsible for the recording. YouTube documents that anyone with an unlisted link can share it onward; unlisted therefore does not mean access restricted to named relatives. Check your chosen provider’s current access rules and test with an intended recipient’s view, not only the uploader’s account.

On the phone or player relatives will use, confirm that the right people can open the clip, find the language selector and read the chosen track. Check names with accents, line wrapping, the opening and ending, and any other subtitles already visible in the picture. If the player cannot load sidecar files, use an external finishing workflow to render a captioned video and review that export. Polyglot does not burn subtitles into the picture.

Keep the approved media, subtitle files and delivery sheet together for the agreed retention period. Local processing keeps media and transcript work on your Mac; model downloads, user-controlled updates, optional content-free analytics and Pro licensing have separate network boundaries. Uploading to a family gallery is a separate sharing decision.

Keep exploring.