Launch a free, ad-supported streaming app like Tubi
How to launch a streaming app like Tubi on Flicknexs: free titles with your own ad tags, server-side ads on channels, the real monthly cost and the limits.
Flicknexs runs a free, ad-supported catalog with your own ad tags, server-side ad insertion on linear channels, and the option to add paid plans later, all under your brand and with no commission on your revenue.
Trusted by industry leaders
50+ OTT platforms powered by Flicknexs
Quick answer: A streaming app like Tubi gives viewers a large library for free and earns from ads served inside the player. Flicknexs supports that model with free access rules per title, ad tags in the player, server-side ad insertion on linear channels, and web, phone and television apps by plan, with paid plans available whenever you add a tier.
Flicknexs provides streaming app like tubi as part of its white-label OTT platform. Flicknexs runs a free, ad-supported catalog with your own ad tags, server-side ad insertion on linear channels, and the option to add paid plans later, all under your brand and with no commission on your revenue.
Why a streaming app like Tubi is an ad business wearing a video app
Can you start your own free streaming service? Yes, and it is one of the simpler models to build because there is no checkout to design at launch. Choose a platform with the player, the apps and the ad hooks already in place, load your library and mark titles free; that is how you build the app. The cost is a flat monthly fee rather than a share of ad revenue. 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.
The Tubi model works because the ad break replaces the paywall. A viewer arrives from search or from a store listing, presses play without a card, and the pre-roll and mid-roll pay for the minutes watched. That only holds if three things are true at once: the library is broad enough that people find something, the ad breaks are delivered reliably on every screen, and the ad demand is real, which means an ad server or a supply partner is filling those breaks with paying campaigns. The platform supplies the first two; you supply the third.
Flicknexs is not affiliated with Tubi; the name describes the product category viewers recognize. Two external references frame this page. Tubi's own public site shows the viewer-side expectation: browse by genre, press play, watch with ad breaks, no card required. The IAB Tech Lab VAST specification defines the ad tag format that ad servers hand to a video player, and it is the format the Flicknexs player and the server-side ad insertion on linear channels expect. If you have not chosen an ad server yet, read the VAST specification first, because every ad partner you talk to will assume you know it.
What Tubi does, and how Flicknexs gives you the same
The left column is what a viewer notices on an ad-supported app. The middle column is where that behavior comes from in the Flicknexs admin, and the right column is why it changes the revenue.
Free viewing without a card
A per-title access rule of free, with free-preview minutes for visitors, so no checkout stands between viewer and play.
Ads inside the player
Ad tags from your ad server attached in player settings, played as pre-roll and in-stream breaks on free titles.
Ads on linear channels
Server-side ad insertion on cloud playout channels, stitched into the stream rather than played by the client.
A browsable library
Categories, genres, series with seasons, search, and per-title posters and descriptions managed in the admin.
Viewer accounts and lists
Optional accounts with continue watching, watch later and a wishlist, kept across web and apps.
Territory control
Geo-fencing platform-wide and per title, enforced at playback from an IP country lookup.
A paid tier later
You can add subscription plans and pay-per-view at any time through 96 gateway integrations.
Apps on every screen
Web, Android and iOS by plan, Android TV and Fire TV on F3, other television apps as add-ons.
Source: Flicknexs platform documentation and architecture specification, 2026-09-03.
What makes the Tubi model work, translated into platform requirements
A free app is not a paid app with the price set to zero. Its economics push five specific requirements onto the platform, and each is listed here with the Flicknexs answer.
Zero friction between arrival and play
Every step between a search result and the first frame costs viewers, and on a free app there is no revenue to justify any of them. Flicknexs lets a title carry a free access rule so a visitor can press play without a checkout, and free-preview minutes let you open the first part of a title to anyone while keeping the rest behind an account. Keep the account prompt for lists and continue watching, not for the first play.
Reliable ad breaks on every screen
An ad break that fails to play is a minute of viewing you gave away. Flicknexs takes the ad tag from your ad server in player settings and plays it on free titles on web, in the phone apps and in the television apps. On linear channels built in cloud playout, ads are inserted server-side into the stream itself, which is the method that holds up on smart televisions and in browsers with ad blockers.
A library that is broad and easy to browse
An ad-supported library earns on watch time, so breadth and discovery matter more than exclusivity. The Flicknexs admin organizes titles into categories and genres, groups episodic content into series with seasons, and gives every title a poster, a description and a language tag that feed search. Viewers who cannot find something in two screens leave, and on a free app they leave without a refund request, which means you never hear about it.
Territory rights that hold
Ad-supported licenses are usually cheaper than subscription licenses precisely because they are narrow, often limited to one or two countries. Flicknexs geo-fencing runs platform-wide and per title, looks up the viewer country from the request IP, and refuses playback outside the allowed list. The per-title lists let a library with mixed territory deals coexist in one app without a separate build per country.
A path to a paid tier
Most free services eventually add a paid, ad-free option or a premium shelf. On Flicknexs that is a plan created in the admin and a change to the access rules on the titles you move behind it; the free titles keep their ad tags and the new plan sells through the gateway you connect. Nothing about the app, the catalog or the viewer accounts has to change.
Reporting you can show an advertiser
Advertisers buy watch time and completion, and they ask for proof. Flicknexs analytics records player sessions with watch time and completion rate, device and platform breakdown, and content-level reports, all in the admin and in warehouse tables you can export. Ad impressions and fill are reported by your ad server, so the two reports together are what you take to a sales conversation.
Setup: how to launch a Tubi-style app in the Flicknexs admin
Five steps in the order that avoids rework. Do them with a dozen titles and a test ad tag before the full library arrives.
- 1
Upload the library and mark titles free
Add films as videos and shows as series with seasons and episodes. On each title set the access rule to free, add free-preview minutes if you want playback to start before any account prompt, and fill in the poster, description, category and language. Add the age-restriction flag where it applies so kids mode can hide the title later.
- 2
Connect the ad server tags
Get a VAST ad tag from your ad server or supply partner and paste it into the player settings in the admin. Play a free title on the website and in a phone app and confirm a pre-roll appears. Use a test tag from your ad partner first; a live tag with no demand behind it will show an empty break, which looks like a bug to a viewer.
- 3
Build a linear channel with server-side ads
Open Cloud Playout, create a channel from titles in the library, and switch on server-side ad insertion with the same ad tag or a channel-specific one. A single always-on channel gives casual viewers something to land on and gives you a stream where the ad break is stitched into the video rather than played by the device.
- 4
Set the territory rules
Open Geo-fencing and choose an allow list of the countries your ad-supported licenses cover. Add per-title lists on titles whose rights differ from the platform default. Test from a blocked country with a VPN and read the refusal message a viewer will see; make it plain, because free viewers will not email support, they will leave a one-star review.
- 5
Publish the apps and switch on accounts
Submit the Android and iOS apps from the app builder with your icon, name and store listing. Turn on viewer accounts so continue watching, watch later and the wishlist work, but keep first play free. On F3 and above submit the Android TV and Fire TV apps, since television inventory is where ad-supported viewing earns most per hour.
What a platform like Tubi has that Flicknexs does not give you
Plainly stated so you plan for it. None of these are hidden in the fine print; they are simply outside what a platform vendor does.
The ad demand and the sales team
Tubi fills its breaks through its own sales organization and programmatic partners. Flicknexs plays the tags you supply and stitches ads server-side into channels, but it does not sell inventory, bring advertisers or guarantee fill. You need an ad server or a supply partner before launch, and their reporting, not the Flicknexs admin, is where impression and revenue numbers live.
A studio-scale licensed library
A free app lives on breadth, and Tubi's breadth is the product of years of licensing. Flicknexs holds and delivers whatever you have the rights to; it does not source content, and there is no built-in marketplace of licensable titles. Budget for acquisition as a separate line from the platform fee.
A large-scale recommendation engine
Tubi's home screen is shaped by viewing behavior at a scale a new service does not have. Flicknexs gives you categories, genres, search, continue watching and the lists a viewer builds, and it records the watch data you would need to shape the home page by hand. Do not promise personalized rows on launch day.
Premium formats and offline viewing
Dolby audio, 4K output and downloading for offline viewing are not in the Flicknexs platform code. The transcoding ladder defaults to 720p, 480p and 360p and can be raised to 1440p on request, with a single AAC audio track. For an ad-supported library of catalog titles this is rarely a problem, but say it in your licensing conversations.
A worked example: a film distributor turning a back catalog into a free app
Consider an independent film distributor with rights to about six hundred older features and documentaries in two countries, most of which earn nothing on the shelf. The team wants a free app with ads, on phones first and on televisions once the library proves itself, and it wants the option to add a paid ad-free plan for the titles it acquires in future. Nobody on the staff writes software; one person manages the catalog and one runs sales and marketing.
The catalog manager uploads the features as videos with posters, descriptions and genres, marks every title free, and flags the titles that need an age restriction. Geo-fencing is set to an allow list of the two licensed countries. A supply partner provides a VAST tag for player settings, and cloud playout runs one documentary channel with server-side ad insertion so the home screen has something live. 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.
Six months in, the watch-time reports show the television share climbing, so the distributor moves to F3 for Android TV and Fire TV and creates a paid plan for a shelf of newer acquisitions, sold through Stripe on the web and through store billing inside the apps at the store's published fee. 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. The free titles keep their tags, the paid shelf has none, and the same accounts work across both.
Pre-launch checklist for a Tubi-style app
A free app gets no second chance from a viewer who hit a broken ad break. Check every line on a real device before the store listing goes live.
- Every title has a free access rule or a deliberate reason not to, and none is left with an unassigned rule.
- The VAST tag from your ad partner plays a pre-roll on web, on an Android phone and on an iPhone, with sound.
- Server-side ad insertion on the linear channel shows a stitched break on a smart television, not a frozen frame.
- The ad partner's test campaign shows impressions in their dashboard that match session counts in Flicknexs analytics.
- The geo-fencing allow list matches the countries in every license, and a VPN test from outside returns the refusal message.
- Posters, descriptions, genres and language tags are filled on every title so search and category pages are not half empty.
- Age-restricted titles carry the flag, and a kids profile cannot reach them through search or a category page.
- Continue watching and watch later work after sign-in on web and in the phone apps for the same account.
- Store listings for Android and iOS are submitted with screenshots from the real library and the free-with-ads description.
- The bandwidth allowance on your plan has been compared against expected watch hours, according to our pricing page.
Devices and monetization for a Tubi-style app
Ad-supported viewing earns most per hour on the television, so the device path matters more on this model than on a subscription service. The website and the Android and iOS apps come with F2, Android TV and Fire TV with F3, and Roku, Apple TV, Samsung and LG as add-ons on any plan. Each app reads the same catalog, the same free access rules and the same ad tags, and server-side ad insertion on linear channels behaves the same on every screen because the break is in the stream, not in the app.
Monetization starts with ads and can grow. Player ad tags on free titles and server-side insertion on channels are the first revenue line, reported by your ad partner. A paid plan is the second, sold through any of the 96 gateway integrations on the web and through Apple and Google billing inside the phone apps at the store's published fee. Pay-per-view on a single premiere is a third line that needs no plan at all. The revenue reports in the admin cover subscriptions and pay-per-view by month; ad revenue stays in the ad server.
If the linear channel side interests you more than the on-demand library, the page on launching a FAST TV platform like Pluto TV covers channels, schedules and server-side ads in depth. If you expect to combine ads with a strong paid tier from the start, the page on launching a streaming platform like Hulu lays out that mixed model. The video paywall page explains the access rules both of them rely on.
Which plan includes a Tubi-style app
Standard layers
Ad tags, server-side ad insertion on channels, free access rules, geo-fencing, viewer accounts and analytics are part of every plan, so the plan choice for a Tubi-style app is about which apps you ship and how much bandwidth free viewing will consume. 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. 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.
Pricing & billing
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. Because ad-supported watch hours are long and free viewers are many, the bandwidth allowance is the figure to compare between plans, and our pricing page lists it for each.
Annual savings
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. Ad revenue is collected by your ad partner and is never touched by Flicknexs, so the platform fee is the only cost on the platform side.
Conclusion: what to do next
Already on Flicknexs
If you are already a Flicknexs customer, take five titles you own outright, mark them free, paste a test VAST tag into player settings and watch a pre-roll play on a phone. Then build one channel in cloud playout with server-side ad insertion and watch it on a television app. Those two tests, done in an afternoon, tell you whether the ad-supported model fits your library before you change any live title.
Choosing a platform
If you are choosing a platform, arrive at the trial with a test ad tag from the ad partner you intend to use. Fill, reporting and break behavior are what decide whether a free app earns, and the only way to judge them is to see a real tag play through the platform player on the devices your audience uses. Do not evaluate the player with a placeholder.
Before a rights call
Read the companion pages next. The FAST TV page covers linear channels and server-side ads in detail, the Hulu page covers combining ads with subscriptions, and the geo-fencing page explains the territory rules an ad-supported license depends on. The video analytics page shows the watch-time reports you will put in front of advertisers.
Frequently Asked Questions
Everything you need to know about a Tubi-style app on Flicknexs.
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. A website-only launch is possible on a lower plan, television apps arrive on F3, and no commission is taken on your revenue, according to our pricing page.
Through ads you sell or source. You attach a VAST tag from your ad server or supply partner in player settings, and free titles play its pre-roll and in-stream breaks; linear channels from cloud playout insert ads server-side. The ad partner reports impressions and pays you directly; Flicknexs takes no share.
Yes. Create a plan in the admin, connect one of the 96 gateway integrations, and change the access rule on the titles you move behind it. Free titles keep their ad tags, the paid titles carry none, and existing viewer accounts continue to work. No app resubmission is needed for the change.
Not to press play. A title with a free access rule plays without a checkout, and free-preview minutes can open the first part of any title to visitors. Accounts add continue watching, watch later and the wishlist, so most operators prompt for one after the first play rather than before it.
Any ad server or supply partner that issues a VAST ad tag. Flicknexs does not sell inventory or bring demand; it plays the tag you supply in the player and, on linear channels, inserts ads server-side. Test with a partner-issued test tag before launch so an empty break never reaches a viewer.
Yes, on linear channels built in cloud playout. The ad is stitched into the stream before it reaches the device, so Android TV, Fire TV and the add-on television apps show the break without any client-side ad logic, and browser ad blockers do not remove it. On-demand titles use the player ad tag instead.
You configure it. Flicknexs supplies the admin, the player, the app builder and the ad hooks; you upload titles, mark them free, paste your ad tag, set territory rules and submit the apps with your icon and listing. The one thing to bring from outside is an ad partner with real demand.
Yes, within your licenses. Geo-fencing runs platform-wide and per title from an IP country lookup, so a library with mixed territory rights can live in one app with an allow list per title. Rules are platform-level, not per device, so the same refusal applies on web and in every app.
Flicknexs analytics gives you player sessions with watch time and completion rate, content-level reports and a device and platform breakdown, in the admin and in warehouse tables. Impression, fill and revenue figures come from your ad server. Together they are the pack an advertiser expects.
No. The transcoding ladder defaults to 720p, 480p and 360p and can be raised to 1440p on request, audio is a single AAC track, and there is no download for offline viewing. Catalog titles on an ad-supported app rarely need more, but say so in licensing conversations.
Yes. The web-only plan runs the free catalog, ad tags, geo-fencing and analytics on your domain, and the phone apps arrive when you move to F2. Many operators launch on the web to prove fill rates with their ad partner before paying for the app plans.
According to our pricing page footnote, plans allow up to 50 cloud playout channels. Most ad-supported apps start with one or two always-on channels built from library titles, with server-side ad insertion on each, and add more once the watch-time reports justify the bandwidth.