How to Let Testers Test Your Paid App for Free

If your app is paid, closed testing has a problem built into it. Google's documentation is blunt about this:

"Testers must purchase paid apps when participating in open or closed tests. For internal tests, testers can install paid apps for free."

So you need 12 people to buy your unreleased app in order to test it. Nobody is going to do that, and you cannot use the internal track instead because internal testing does not count toward the 12-tester requirement.

Why the "just make it free" trick is a trap

Google's pricing documentation says it in two lines:

• You can change your app from paid to free.
• Once your app has been offered for free, the app can't be changed to paid.

There is no track-scoped pricing either. The closed testing setup page states that "changes to your app's pricing affect all versions across all tracks." You cannot make it free just for the closed test. Making it free makes it free, everywhere, permanently.

The reason Google does this is sensible once you know it: it stops users who downloaded a free app from being charged on a later update or failing a licence check.

Option 1: Run a $0 sale

This is the officially sanctioned version of what people are trying to do with the free-then-paid trick, and it is far less well known than it should be.

Google's sales feature lets you set a promotional price, and setting that price to zero is explicitly supported. The documentation is unusually direct about the distinction that matters:

"A $0 sale is temporary and is not the same as permanently offering your app for free. Creating a $0 sale does not impact your ability to charge for the app in the future."

The rules

To set one up: Monetize with Play, then Products, then App pricing, then the Sales tab. Create a sale, choose a fixed price, and set the value to 0.

Your app will not appear on paid Top Charts while the sale runs, and $0 sales do not count as purchases, so your finance reports will show zero buyers for the period.

Google also states that "to create or edit a sale, your app must be published," and does not define whether a closed-track-only app satisfies that. Check it in your console before you build a schedule around it.

Option 2: Promo codes

Play Console lets you generate codes that give someone a paid app for free. No billing integration is needed for paid-app codes. The Play Store handles redemption entirely.

The quota

You get 500 promo codes per quarter, per app, shared across all non-subscription promotions. That is a single pool covering paid-app codes and one-time-product codes together, not 500 of each. Unused codes do not roll over.

For a paid app you need one-time-use codes. The multi-use "custom codes" are subscriptions-only, so there is no single code you can hand to all 12 testers. Each one gets their own.

Where to find it: Monetize with Play, then Promo codes, then Create promo code. Name the promotion, set start and end dates, pick the type, enter how many codes you need, set status to On, and create. A CSV downloads a few seconds later.

Testers redeem in the Play Store app under Redeem Code, or you can send them a prefilled link in the form play.google.com/redeem?code=THEIRCODE.

The honest caveat

Google has never documented whether a promo code is redeemable for a paid app whose only active track is closed testing. Every guide asserting it works, including the ones ranking above this page, is asserting, not citing. There is at least one developer report of codes being rejected in exactly this scenario, apparently resolved by waiting several hours.

Also worth knowing: redeeming a code is a purchase action, not an opt-in action. Google's rules state that "each tester needs to opt in using the link" and must both be in your tester list and actively opt in. So the sequence for your testers is opt in via your testing link first, then redeem the code, not one or the other.

Option 3: Ship free with in-app purchases

The structural fix rather than a workaround, and the one Google itself points developers toward.

Publish the app free, put the paid functionality behind an in-app product or subscription, and use licence testing so your testers can exercise purchase flows without being charged. That is under Settings, then License testing, configured at the developer account level rather than per app.

Note the scope limit carefully: licence testing covers in-app billing only. There is no documented statement that licence testers can download a paid app for free. The two things get conflated constantly and they are not the same.

This is the only option here with no timing constraints, no per-tester code distribution, no quota, and no undocumented behaviour. The trade-off is that it forecloses the paid-upfront model. If you have not published yet, that is a genuine architectural decision worth making deliberately rather than by accident.

What about the internal testing track?

Internal testing does solve the payment problem, because testers install paid apps for free there. It just does not solve the problem you actually have, because internal testing does not count toward the 12-tester requirement.

Worse, it actively works against you. Google's documentation states that users who opt into an internal test "aren't eligible for open and closed testing, even if included as testers on those tracks." So a tester you gave free internal access to is now blocked from your closed test until they explicitly opt out of internal.

You cannot run internal for free access and have those same people count toward your 12. They are in one bucket or the other.

Which one to pick

What Closed Test Pro testers see

Worth mentioning if you list a paid app in a reciprocal community: testers will hit the paywall like anyone else. In Closed Test Pro they can report it, which sends you an automated message flagging that your app is paid and cannot be installed, along with the fix. After three such reports your listing is temporarily pulled so other developers are not wasting daily tests on an app they cannot open.

Sort the pricing out before you list, not after.

Frequently asked questions

Related guides

• Complete beginners guide to Google Play closed testing
• Fix "Item not found" when testers cannot install
• Closed testing vs open testing