Multi-language video streaming platform: interface, subtitles, audio
Multi-language video streaming platform explained: an interface in five languages, subtitles per language on every title, and audio language as metadata.
Flicknexs handles multi-language delivery by offering the viewer site in English, French, Italian, Arabic and Polish, attaching per-language WebVTT subtitle tracks to every video and episode, and recording the audio language of each title as catalog metadata with one audio track per title.
Trusted by industry leaders
50+ streaming companies powered by Flicknexs
A multi-language video streaming platform serves viewers in more than one language across three separate layers: the interface they navigate, the subtitles drawn over the picture, and the audio they hear. Flicknexs ships the viewer interface in five languages, stores subtitle tracks per language on each title, and tags audio language as catalog metadata.
Flicknexs provides multi-language video as part of its white-label OTT platform. Flicknexs handles multi-language delivery by offering the viewer site in English, French, Italian, Arabic and Polish, attaching per-language WebVTT subtitle tracks to every video and episode, and recording the audio language of each title as catalog metadata with one audio track per title.
Why "multi-language" means three different things
When a buyer asks whether a platform is multi-language, they usually have one of three questions in mind and rarely say which. Can my viewers use the menus in their own language? Can they read captions in their own language? Can they hear the film in their own language? Those are separate systems with separate costs. The interface is software translation done once by the platform. Subtitles are a text file per title per language that the operator supplies. Audio is a second recording of the title, which is the expensive one. Conflating them leads to disappointed launches.
Flicknexs is explicit about which layer lives where. The viewer interface ships in five languages and the viewer picks one. Subtitles are uploaded per title and per language and selected in the player. Audio language is recorded as metadata on the title so the catalog can label and filter it, and each title carries one audio track; a dubbed version is published as its own title with its own language tag. That last point is the one most operators need to hear before they plan a catalog, and this page states it plainly rather than burying it.
The mechanism the player uses for captions is the HTML track element, documented in the MDN Web Docs reference for the track element, which is how a browser attaches timed text in WebVTT to a video. Understanding that element explains most of what follows: captions are files beside the video, not part of the stream, and so they are cheap to add and cheap to change. Audio has no equivalent side file on Flicknexs, which is why dubbing means a new title. The sections below cover each layer, setup order, limits, a worked example and a launch checklist.
How multi-language delivery works on Flicknexs
Each row below belongs to one of the three layers: interface, subtitles or audio. Keep the layer in mind when reading, because the admin controls for each are in different places.
Interface in five languages
The viewer site and player chrome are available in English, French, Italian, Arabic and Polish.
Viewer language choice
A viewer picks an interface language and the site renders its labels in that language.
Subtitles per language
Each video and episode holds one WebVTT subtitle file per language from the admin catalog.
Language catalog
A shared list of languages tags every subtitle upload and labels the caption selector.
Audio language metadata
Each title carries an audio language tag in its catalog record for labeling and filtering.
One audio track per title
A title plays a single AAC audio track; a dubbed version is published as a separate title.
Same tracks on every app
Subtitle lists and language tags are part of the title data every app reads.
Works with geo-fencing
Per-title country lists decide who can play a title, independent of its languages.
Source: Flicknexs platform documentation and architecture specification, 2026-09-03.
The mechanics: interface, subtitles and audio, one layer at a time
The cleanest way to understand a multi-language catalog on Flicknexs is to follow one viewer through the three layers, from the first screen they see to the sound that comes out of the speaker.
Layer one: the interface the viewer navigates
Layer two: subtitles drawn over the picture
Layer three: the audio the viewer hears
How the three layers combine for one viewer
Where the language catalog sits
What travels to the device apps
How to set up a multi-language catalog in the Flicknexs admin
Setup follows the three layers in a specific order: decide the caption languages, prepare the audio versions, then attach tracks and tags to each title. Rushing the first step makes every later step messier.
- 1
Decide which interface languages you will promote
The interface ships in English, French, Italian, Arabic and Polish. Choose which of those your marketing will point viewers to, and make sure your own metadata, meaning titles, descriptions and category names, is written in the language your primary audience reads. The platform translates its labels; it does not translate the text you type into a title record.
- 2
Create the caption language catalog
In the admin language settings, add one entry per language you will caption in, with the label viewers should see in the selector. This list is independent of the five interface languages. Decide now whether variants such as a hearing-impaired track get their own entries. Renaming later updates every track; deleting later strands them, so name carefully once.
- 3
Tag the audio language on every title
Open each video and episode and set its audio language in the catalog metadata. This is what lets the catalog label a film as Italian-language or filter a row by spoken language. For titles you hold in more than one dub, create a separate title per audio version, tag each with its own language, and consider adding the language to the title name for clarity.
- 4
Upload WebVTT subtitle tracks per title and language
On each video or episode record, choose a language from the catalog, upload the WebVTT file and save, repeating per language. Keep cue timing checked against the file uploaded for transcoding. Episodes are captioned individually, so a series can go live with the languages that are ready and gain the rest as translations arrive.
- 5
Test one title through all three layers on two apps
As a viewer, switch the interface to a second language, open a title, confirm the caption selector lists every uploaded language and that the audio language label matches what you hear. Do this on the web player and on one device app. Then check that the dubbed version, if any, appears as its own title with the right tag.
Limits and tradeoffs: what multi-language on Flicknexs does not do
Each layer has a boundary. Knowing them before you plan a catalog saves the awkward conversation where a dubbing budget was spent on the assumption of an in-player audio switch that does not exist.
No audio switching inside the player
Interface languages are fixed at five
Your metadata is not translated
No automatic translation or captioning
Language does not restrict access
A worked example: a church network serving three congregational languages
A fictional operator makes the three layers concrete. The steps are what a real network of this shape would do on Flicknexs; the name and figures are invented.
Launch checklist for a multi-language catalog
Walk this list once per language before you announce a launch in that language. Most items take minutes and catch the mismatches viewers notice first.
- Your primary audience reads one of the five interface languages, or you have accepted that the interface will not be in their language.
- Title names, descriptions and category labels are written in the language your viewers read, since the platform does not translate them.
- The caption language catalog has exactly one entry per language, with the viewer-facing label agreed by the whole team.
- Every title carries an audio language tag that matches what the viewer will actually hear when playback starts.
- Dubbed versions are published as separate titles, each tagged with its own audio language and named so viewers can tell them apart.
- Every WebVTT track was timed against the file uploaded for transcoding and starts with the line WEBVTT.
- One title was tested through all three layers as a viewer, on the web player and on one device app from your plan.
- Nobody on the team expects the AI transcription job to produce caption files or translations, and the caption budget reflects that.
- Titles licensed for one territory have their country lists set on the geo-fencing side, separately from any language tag.
- Marketing copy promises interface, captions and audio in the languages you actually configured, and no more.
How multi-language delivery fits with the device apps and with monetization
Language data is stored on the title and read by every app, which keeps the device side simple. The revenue side needs one decision about how dubbed titles are sold.