Frequently Asked Questions

You change the date. Because nothing is published until the moment arrives, moving a launch forwards or backwards is editing a field rather than unpicking something that has already gone out. That is the practical advantage of scheduling over publishing manually and hoping the plan holds.

Yes. Vodlix lets you preview and customise a new template separately from your live site, which stays untouched until you choose to activate the new one.

Yes. Vodlix custom templates are reversible. If a new look does not perform, you can switch back to the previous template within minutes, so redesign carries no lasting risk.

No. The template your viewers currently see stays exactly in place while you work on an alternative in preview. Nothing changes for viewers until you activate the new template.

Yes. Vodlix lets you adjust colours, layouts and content placement fully in preview, see the template exactly as viewers would, and only then decide whether to activate it.

Reversibility removes the risk that makes redesigns get deferred for years. With Vodlix custom templates, refreshing the look becomes an ordinary decision rather than a quarterly project.

A template is the structure and layout. Themes and colours are the brand values applied within it. You would change a template rarely and colours whenever your branding moves, which is why they are separate screens.

Templates govern the web front end, while the apps have their own presentation with the branding shared between them. What travels across all of them is the brand layer rather than the layout, since a television and a browser cannot use the same structure anyway.

Rarely, but the point is that you can. Services that find changing painful never change, which is how a front end quietly ages for three years and then needs an expensive rebuild all at once.

Viewers spend minutes browsing and hours in the player, so it is the part of a streaming service they remember. A rough player loses subscribers that no amount of content can win back.

Yes. Vodlix dynamic menus are lists you build and reorder in the admin area, with changes going live the moment you save, so a new link never needs a developer ticket or a release.

Vodlix lets you control header, footer and page navigation menus, all built and managed the same way, with drag to reorder and on/off status for every item.

A Vodlix menu item can point to an internal page, an external link or a content list, so a curated collection can be promoted to the top level navigation the week it matters.

Yes. Each Vodlix menu item declares where it belongs, so an item can be web only, TV only or shown everywhere, keeping each screen's navigation appropriate to how it is used.

Yes. Vodlix menu items can be switched off or restricted to specific audiences until you are ready, so you can build navigation for a launch in advance and enable it on the day.

No. Navigation is configuration rather than code, so a change is live when you save it and reaches the web and the apps together.

Browser uploads fail on large batches, need someone present and do not resume after a dropped connection. The Vodlix FTP uploader handles hundreds of large files unattended and resumes interrupted transfers.

The Vodlix FTP uploader is for distributors, post production teams and content operators delivering large launch libraries or back catalogues, using a delivery method they already know.

Yes. Unlike browser uploads, transfers to the Vodlix FTP drop point resume after a connection drop rather than failing near the end, so large files arrive reliably.

Files delivered by FTP enter the same Vodlix transcoding pipeline as every other upload, so they are encoded, packaged and ready to publish with their processing state visible in the CMS.