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+ OTT platforms powered by Flicknexs
Quick answer: 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
The viewer site, sign-in, plan pages, catalog rows and player controls carry translated labels in five languages: English, French, Italian, Arabic and Polish. The viewer selects one, and every label the platform owns renders in it. This layer is the platform's work, not yours. What it does not translate is your content: title names, descriptions and category labels you typed into the admin appear exactly as you typed them, in whichever language you wrote.
Layer two: subtitles drawn over the picture
On each video or episode record, the admin uploads one WebVTT subtitle file per language, tagged from the shared language catalog. When the viewer starts playback, the player lists those tracks in a caption selector and draws the chosen one over the picture. Nothing about the video stream changes when the viewer switches language. This layer is your work per title, and it is the layer that most cheaply widens who can watch a given film.
Layer three: the audio the viewer hears
Every title is transcoded with a single AAC audio track, the one in the file you uploaded. The admin records the language of that audio as catalog metadata so the title can be labeled and filtered by spoken language. There is no in-player audio switch. If you hold a dubbed version, you publish it as its own title with its own audio language tag, and viewers choose between the two titles rather than between tracks inside one.
How the three layers combine for one viewer
A Polish-speaking viewer can set the interface to Polish, open an Italian-language film, and read Polish captions while hearing the original Italian audio. If you also hold a Polish dub, that is a second title, which you would typically label with the audio language in its name. The viewer's interface choice does not select captions or audio for them; each layer is chosen separately, which keeps the rules simple and predictable.
Where the language catalog sits
The catalog of languages in the admin serves layer two. Each entry has a label the viewer sees in the caption selector. It is not tied to the five interface languages: you can caption in Japanese even though the interface does not ship in Japanese, and you can skip captioning in Arabic even though the interface does. Treat it as the list of caption languages your catalog offers, and keep it to one clean entry per language.
What travels to the device apps
The subtitle track list and the audio language tag are stored with the title, so the web player and the Android, iOS, Android TV and Fire TV apps included in your plan read the same data, and add-on TV apps do too. The interface language setting is a viewer preference applied where the app supports that language. The practical upshot is one language setup per title, not one per platform.
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
A title plays one audio track, the AAC track produced from the file you uploaded. The player has no audio language menu, and the transcoder does not multiplex several audio tracks into one stream. A dubbed version is a separate title with its own audio language tag. This is the single most important limit on this page: plan dubbing as additional titles, not as tracks.
Interface languages are fixed at five
The viewer interface is available in English, French, Italian, Arabic and Polish. Adding a sixth interface language is not an admin setting; it is a request to the team, and it is not part of the plan pricing. Captions are not limited this way, so a catalog can serve a language through subtitles even where the interface does not ship in it.
Your metadata is not translated
Title names, synopses, category labels and any text you enter in the admin appear in the language you wrote them, regardless of the interface language the viewer chose. There is no per-language field for a title description. If your audience spans two reading languages, decide on a house style, such as bilingual titles, and apply it consistently in the admin.
No automatic translation or captioning
The AI transcription job returns text, detected language, duration and timed segments as metadata for search and summaries. It does not produce a WebVTT track and does not translate an existing track into another language. Subtitle files come from your translators or vendors, and the platform stores and serves them. Budget per title and per language accordingly.
Language does not restrict access
Tagging a title as Italian-language or captioning it in Polish has no effect on who can play it. Access is governed by plans, per-title prices and, where you enable it, geo-fencing by country. If a language version is licensed only for one territory, the country list on that title is what enforces the rights, and the geo-fencing page covers how to set it.
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.
Consider a church network with congregations that worship in English, French and Polish, which records a weekly service in each language plus a shared teaching series recorded in English. The network wants each congregation to feel at home on the platform and wants the teaching series to reach all three groups. Reading the three layers, the plan writes itself: the interface will be promoted in English, French and Polish, all of which Flicknexs ships; the teaching series will be captioned in French and Polish; and the weekly services, being separate recordings, are simply separate titles tagged by audio language.
In the admin, the team creates three caption language entries, tags each weekly service with its audio language and files it in a category per congregation. For the teaching series, each episode is uploaded once with English audio, and French and Polish WebVTT files are added as the volunteer translators finish them. The series goes live with English captions on every episode and the other two languages filling in week by week, which the episode-level upload allows without holding the whole season back.
A French-speaking member sets the interface to French, opens the teaching series, and picks French captions over the English audio. The Polish congregation does the same in Polish. When a sermon is later re-recorded with a Polish voice-over, the team publishes it as a new title with Polish as its audio language and a note in the name, rather than expecting an audio switch on the English title. Everything the network sells, a supporter subscription and a per-title conference pass, works the same across all three languages.
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.
The subtitle track list and audio language tag are part of the title record, so the Android, iOS, Android TV and Fire TV apps included by plan and the Roku, Samsung, LG and Apple TV apps sold as add-ons all read the same language data without separate configuration. The interface language a viewer chooses applies where the app supports that language. For the caption layer in particular, the video subtitles page goes into file format, episode-level uploads and where the selector sits on a TV remote, and the video transcoding page explains the single AAC audio track that sets the one-track-per-title rule.
On monetization, language costs nothing extra and restricts nothing. A subscription plan or a pay-per-view price on a title grants every caption track on it. The one decision is how to sell dubbed versions, because each is its own title: you can price the dub identically, bundle both under a subscription, or set a separate pay-per-view price for the dub. The video paywall page covers per-title pricing and rental windows that make any of those work. Where rights differ by territory, pair the language plan with the geo-fencing page, which sets allow and block country lists per title so a dub licensed for one country stays inside it.
Which plan includes multi-language delivery
Standard layers
The five-language viewer interface, per-language subtitle upload and audio language metadata are part of every plan. There is no language add-on and no charge per language or per subtitle track. What a plan changes is which apps your viewers can use in those languages. F1 Standard is the web-only plan, with 300 GB of storage and 20 TB of bandwidth yearly; see our pricing page for current plan and pricing details. F1 Standard includes 300 GB of storage and 20 TB of bandwidth yearly for website streaming; see our pricing page for current plan and pricing details.
Pricing & billing
F2 Super includes 300 GB of storage and 20 TB of bandwidth yearly, and adds native Android and iOS mobile apps; see our pricing page for current plan and pricing details. F3 Premium includes 1 TB of storage and 10 TB of bandwidth monthly, and adds Android TV and Fire TV apps; see our pricing page for current plan and pricing details. F4 Enterprise includes 2 TB of storage and 20 TB of bandwidth monthly and adds dedicated support to everything in F3; Samsung, LG, Roku and Apple TV apps are add-ons on any plan. See our pricing page for current plan and pricing details. TV apps are available as add-ons on any plan, allowing you to expand your reach to more devices; see our pricing page for current plan and pricing details.
Annual savings
Because a dubbed version is a separate title, each dub counts as another video against the storage allowance of your plan, so a heavily dubbed catalog is a storage question rather than a feature question. Plans are flat fees and Flicknexs takes no commission on your revenue; payment-gateway fees are between you and your gateway. See our pricing page for current plan and pricing details. Yearly billing on F1 to F4 costs less per month than monthly billing; see our pricing page for current plan and pricing details.
Conclusion: what to do next
Already on Flicknexs
If you are already on Flicknexs, open five titles and check three things on each: the audio language tag is set, the caption tracks match what you believe you uploaded, and the title name makes clear which language version it is. Then switch your own interface to a second language and browse as a viewer. Ten minutes of this finds the gaps that a spreadsheet never shows.
Choosing a platform
If you are choosing a platform, ask each candidate to state, in writing, which of the three layers it handles and how. Ask specifically whether the player switches audio tracks, because that answer decides your dubbing budget. On Flicknexs the answer is no: one audio track per title, dubs as separate titles, captions per language on each title, interface in five languages. We would rather you plan around that than be surprised by it.
Before a rights call
Read the video subtitles page next for the caption layer in detail, including file format and episode-level uploads. Then read the geo-fencing page, because language reach and territory rights are separate controls that many operators need together. If you are building out the app lineup for a multilingual audience, the Android TV app page shows what the living-room viewer sees.
Frequently Asked Questions
Everything you need to know about multi-language delivery on Flicknexs.
Yes. Every plan includes the viewer interface in five languages, per-language subtitle uploads on each title, and audio language metadata. No plan gates any language feature, and there is no per-language fee. Plans differ in which device apps your viewers get, according to our pricing page, not in language support.
No. Each title plays one AAC audio track, and the player has no audio language menu. A dubbed version is published as its own title with its own audio language tag, and viewers choose between titles. Captions, by contrast, can be switched in the player during playback.
The viewer interface ships in English, French, Italian, Arabic and Polish. The viewer picks one and the site labels render in it. Your own content metadata is shown as you typed it, and caption languages are not limited to these five; you can caption in any language you add to the catalog.
Not from the admin. The five interface languages are built into the platform, and adding another is a request to the team rather than a setting or a plan feature. Subtitles are the practical route to serving an audience whose language the interface does not ship in.
No. The three layers are chosen separately. A viewer can browse in Polish, watch Italian audio and read French captions. The interface setting only changes the platform labels; the caption selector and the choice of title decide what the viewer reads and hears.
No. Title names, synopses and category labels appear exactly as entered in the admin, in whatever language you wrote them, regardless of the viewer interface language. There is no per-language description field, so decide a house style, such as bilingual names, and apply it consistently.
As a separate title. Upload the dubbed file, tag its audio language in the metadata, and give it a name that identifies the language. Attach any caption tracks it needs. Decide whether it shares the original title price or has its own pay-per-view price, as the video paywall page describes.
No. The transcription job returns the spoken text, detected language, duration and timed segments as metadata used for search and summaries. It does not write caption files and does not translate an uploaded track. Translated WebVTT files come from your translators or vendors and are uploaded per language.
No. Language data on a title has no effect on access. Who can play a title is decided by the subscription plan, any per-title price and, where enabled, the geo-fencing country lists. Use those controls, not language tags, when a version is licensed for a single territory.
Yes. Subtitle tracks and audio language tags are stored on the title and read by the Android TV and Fire TV apps included by plan and by the add-on TV apps. The interface language applies where the app supports it. Test the caption selector on a remote, since its position differs from a phone.
There is no feature charge, but each dub is a separate video that counts toward the storage allowance of your plan. According to our pricing page, storage differs by plan, so a catalog with many dubs should be sized against the plan storage line rather than the language feature.
Yes. The caption language catalog is independent of the five interface languages. Add Japanese, for example, to the catalog and upload Japanese WebVTT tracks on any title; the selector will list it even though the surrounding interface renders in one of the five shipped languages.