What It Actually Costs to Publish an App on Google Play in 2026

Search results will tell you it costs $25 to publish on Google Play. That is the registration fee. Here is what a first launch actually costs, including the parts nobody budgets for.

The fixed, unavoidable cost

• Google Play developer registration — US$25, one time, not annual. One account publishes unlimited apps.
• That is genuinely the only mandatory fee Google charges to publish a free app.

The costs that depend on your app

• Google's service fee on in-app purchases and subscriptions — 15% on the first $1M of annual earnings, 30% above that, with lower rates for qualifying subscriptions. Free apps with no in-app purchases pay nothing.
• A domain and hosting for your privacy policy — roughly $10–20 a year, and you do need a public URL.
• Backend and infrastructure, if your app has a server. Free tiers cover most early-stage apps.
• A D-U-N-S number for organisation accounts — free, but allow days to weeks for issuance.

The costs first-time publishers do not see coming

These are where real launch budgets go, and none of them appear in the $25 figure.

• Store assets — icon, feature graphic and screenshots. Designers charge anywhere from $50 to several hundred. Free browser tools cover this if you can write a decent caption.
• A test device or two. Emulators miss real-world rendering, performance and OEM behaviour.
• Closed testing — for personal accounts, finding 12 testers who stay opted in for 14 days. This is the stage that costs weeks, not rupees, and it is where most launches stall.
• Re-review cycles. Every rejection costs days. Two or three rejections is common on a first submission and can push a launch out by a fortnight.

A realistic total for a solo developer

Assuming a free app with no backend: $25 registration, about $15 for a domain, and your own time on assets. Under $50 in cash.

The real cost is calendar time. Three to four weeks from account creation to a live listing on a personal account is normal, and most of it is waiting — verification, the closed testing window, then two review queues.

Where paying actually saves money

Spending is worthwhile where it removes calendar time rather than effort. The clearest case is the testing requirement: recruiting 12 people who reliably stay opted in for 14 straight days is the single most common reason a launch slips by a month, because one drop-out on day nine restarts the count.

That is what CloseTesting does — verified manual testers who stay opted in for the full window, so the stage with the most variance becomes the one you can actually schedule around.

Budget in weeks, not rupees. On Google Play, time is the expensive resource.