Episode Paywall Strategy: How Many Free Episodes?

Micro drama paywall strategy starts with an uncomfortable fact: no number of free episodes is correct for every app. The right window depends on your titles, your audience and your costs, so treat the lock position as a hypothesis, test it, and read revenue per new viewer rather than any single rate. This guide gives you the reasoning, a worked comparison and a test plan.

The model assumed here is the one a micro drama app like ReelShort uses: a few opening episodes play free, the lock appears at a cliffhanger, and the viewer unlocks the next episode with coins, a pass or a rewarded ad. All figures in the worked examples are invented round numbers to show the arithmetic. They are not benchmarks from any app.

What a free window does

A free window has one job: to make the viewer care about the story before you ask for anything. A viewer who has watched four episodes knows the characters, has a theory about the secret and wants the next scene. Asking for payment at that point is a small request. Asking at the first minute is a request from a stranger.

The window also costs you money. Every free episode a viewer watches uses bandwidth and storage, and for a licensed title it may count against a revenue share or minimum guarantee. So the question is not "how generous can we be" but "how few free episodes get most viewers invested". Too short and viewers hit the lock before they care, so they leave. Too long and you give the whole story to people who were never going to pay, while the viewers who would have paid have already had their fill.

A coin asks for the next few minutes of a story the viewer already wants to finish. A subscription asks about next month. That difference is why the lock position matters more in this category than in a monthly-subscription video app.

Placing the first lock

Tie the lock to a story beat, not only to a count. Read the first episodes of each title and mark three points: where the premise is clear, where the first reversal lands, and the first cliffhanger that makes a viewer lean in. The lock belongs at or just after that cliffhanger. If a title's first strong hook is in episode six, a flat window of four episodes locks it before the hook and wastes the best sales moment.

In our platform the free window is a setting that you can move without touching code, and each episode carries its own lock and coin price. That means you can start with a single window across the shelf and later adjust individual titles whose hooks land earlier or later.

A test plan in place of a number

Run three variants of the free window across comparable groups of new viewers, long enough that each group produces a meaningful number of purchases. For example: a short window, a medium window and a long window. Do not call the winner by a single measure. The next section shows why.

Two rules keep the test clean. Change only the free window while the test runs, so prices, packs and rewards stay fixed. And run each variant across the same weekdays, because viewing habits shift between weekdays and weekends. Because the platform's free window is one setting, the simplest test is sequential: one window for a week, then the next, with the dates logged.

Why compare revenue per 1,000 new viewers

A longer free window moves two numbers in opposite directions. Fewer viewers reach the lock, because some drift away during the free run. But those who reach it are more invested, so a bigger share pays. Looking at only one of these misleads you. Combine them.

The example below uses invented figures for 1,000 new viewers. Assume a paying viewer spends 8.00 on average over the life of the series.

In this invented example the medium window wins on revenue, even though the long window has the highest payment rate at the lock and the short window has the most viewers reaching it. A team that read only the payment rate would pick the long window and lose money.

Then add costs. A longer free run means more free episodes streamed per viewer. If a viewer in the 8-episode variant watches on average three more free episodes than one in the 3-episode variant, multiply that by your cost per view to see whether the extra revenue covers it. Your hosting, bandwidth and any title-level fees are yours to supply; the point is to include them in the comparison rather than to guess.

Offering a choice at the lock: coin unlock, VIP or ad

A lock with one option loses everyone that option does not suit. A lock with three routes serves three kinds of viewer, and you do not have to guess which kind you have.

• Coins suit the impulse viewer three episodes into a story late at night. The decision is small and arrives at a moment of high interest.
• A VIP pass suits the heavy watcher who dislikes counting coins and would rather pay once for a window.
• A rewarded ad suits the viewer who will never pay but is still worth something to you, through ad income and through the word of mouth a happy free viewer brings.

In our platform a viewer sees coins, a rewarded ad and a VIP pass side by side at the lock, and each route writes the same unlock record, so an episode unlocked on the web is already unlocked in the store app. The ad route is capped per title per day and resets at midnight. Keep that cap tight at launch. A viewer who would have bought a pack may watch an ad instead, and you want to see ad income and coin income as separate lines before you loosen it. On the web the ad route is a simulated preview, and rewarded ads earn only through the store app. The detail of running that route is in rewarded ads for free episodes.

For an outside reference point, the ReelShort listing on the US App Store says, as of October 2026, that the app is free to use with content that can be unlocked through optional ads and rewarded tasks, and it lists a subscription described as valid for 7 days. Free, pass and ad routes therefore sit together in the category.

Do not offer routes you cannot support. If the store build is not live yet, the ad option on the web does nothing for revenue, and a pass you have not mapped to a store product cannot be sold in the iOS app. State plainly in your plan which routes work on which client at launch.

VIP versus pay-per-episode

These two routes sell different things and interact with each other, so decide how before launch.

The interaction is where mistakes happen. Suppose the mid coin pack gives a viewer enough for about 36 episodes. If a seven-day pass costs a similar amount and lets them watch anything for a week, heavy watchers will choose the pass every time, and your coin sales come only from light viewers. That may be right, since a heavy watcher on a pass is a recurring customer, but you should choose it on purpose. Work out the pass price against what a heavy viewer would spend in coins in that week, and set it so that the pass is clearly better for heavy use and clearly worse for casual use.

A short validity window sells to impulse buyers, and a longer one sells to loyal viewers. Our platform builds VIP plans by validity window, each with its own order history; confirm with us how each plan maps to a store product for the app builds. For coin ladders and the economics of packs, see how to price coins in a micro drama app.

Unlock decided when the episode is requested

How the platform decides who can watch matters for how you change the paywall later. In our platform, every request for an episode is checked against four facts: whether the episode is locked, whether its number falls inside the free window, whether the viewer holds an active VIP window, and whether an unlock record already exists. Coins, a rewarded ad and auto-unlock each write that same record.

Three consequences follow.

• A rule change applies to existing titles at once. Move the free window from five to four and every title follows, with nothing to re-import. This is a strength for testing and a hazard for carelessness. Change the setting during a quiet hour, and log it.
• People who paid keep what they paid for. Existing records stay attached to the viewer and the episode, so a re-cut or a reorder does not take away access. Reordering episodes renumbers and relocks them, so check the lock line after any reorder.
• Every client agrees. Because one record is read by the web app, the store app and the console, a viewer who unlocks an episode on one device sees it unlocked on the other. Test that path before you launch: unlock an episode on the web, then play it in the app.

If you build this yourself, the shared rule is the part to get right early, because three clients that each decide access in their own way produce disputes you cannot explain. The full list of what ships in the wallet and lock layer is on the ReelShort clone features page.

Reading the data

Once the lock is live, read the same few things every week. The console reports revenue by series and by episode, and by ledger code, which covers most of this.

1. Drop-off at the lock. Of the viewers who see the lock screen, how many leave without any action? A very high rate suggests the lock is too early, the price unclear or the options weak.
2. Unlock rate by episode. A lock that works on episode six and fails on episode nine tells you where the story's pull is strong, and where to put a higher price.
3. Route mix. Which share chooses coins, a pass and an ad? If nearly everyone picks the ad, your coin price may be too high or the ad cap too loose.
4. Return after the first purchase. Do buyers come back the next day? A viewer who returns is worth more than one who bought once.
5. Revenue per 1,000 new viewers. The summary measure, as in the table above, once each week.
6. Series-level differences. Compare titles. If one series sells far more than the rest at the same lock position, study why before you apply its pattern to the others.

Keep a dated log of every change to the free window, the prices and the route options. Without it you cannot tell whether a change in results came from your edit, from a new title or from a marketing push.

Keep the lock fair

A paywall that tricks viewers raises short-term sales and long-term refunds, bad reviews and store trouble. Keep it fair.

• Show the coin price and the viewer's balance on the lock screen before they confirm.
• Show all available routes, including the free one, in a clear order. Do not hide the ad option.
• Explain a pass in one line: how long it lasts, what it covers, and whether it renews. Apple's guidelines ask for clear disclosure of duration, content access and downstream charges before a subscription purchase.
• Do not move the lock after a viewer has started a series without telling them, and do not charge for an episode they already own.
• Offer a way to see purchase history. In our platform you can inspect any wallet and its history, which also lets support answer a dispute.

Store policy shapes the details. Both stores treat virtual currency and passes as digital goods that generally use their own billing, with exceptions that vary by region and change over time. Read the current rules on Apple's App Review Guidelines and Google's Payments policy, and see Apple and Google billing for drama coins. Rules on consumer disclosure differ by country, and this guide is not legal advice. Ask a consumer-law or payments adviser in your market.

What to decide before launch

Decide four things. First, read the opening episodes of your first titles and mark each one's first strong hook. Second, pick three free-window variants to test and write down how you will compare them: revenue per 1,000 new viewers, with costs. Third, choose which routes appear at the lock on day one and confirm each works on each client. Fourth, set the log: who changes settings, when, and where it is written down.

If you are still working out the whole launch, how to start a micro drama app covers the order of work. If you want these lock, pass and ad settings ready to configure, a white-label ReelShort clone comes with them in the platform, and the ReelShort clone business model page lays out how the three routes earn. Episode length also shapes where a cliffhanger can fall; see micro drama episode length.