The files you need to publish your app on Google Play
Google Play will not accept a plain APK from a new app. You need an Android App Bundle — and five other things nobody tells you about. We make all of them, minutes after you pay. You upload from your own account, and it stays entirely yours.
Every Play Store file, made for you
You built the app. These are the six things Google Play wants before it will take it — each one a place where first submissions get refused.
The Android App Bundle (AAB) Google Play requires
Since 2021 Google Play has refused APK uploads for new apps — it only accepts the Android App Bundle. It is the single most common reason a first upload is rejected, and it is the file we build for you.
Your own signing key, kept safe
Every Android app is signed with a key, and if you lose it you can never update your app again — Google cannot recover it for you. We generate a key for your app alone, never shared with anyone else, and send you the file and its password. We keep a copy so we can re-send it if you ever lose yours, and you can ask us to delete that copy at any time.
Every graphic at exactly the right size
Your 512×512 store icon and 1024×500 feature graphic, made from your app’s own icon and brand colour. Google rejects the wrong dimensions without explaining which one was wrong. Screenshots are the one thing you take yourself — Google requires them to show the real app, and a made-up one can get a listing refused. Install the APK, open it, press two buttons. Two minutes.
A privacy policy at a real web address
Google will not publish an app without one, at a working public link. We write yours from your app and host it for you, so you have a URL to paste in.
Every answer for Google’s forms
The content rating questionnaire and the Data Safety form, answered for your app. You paste them in — no guessing at questions about data you did not know your app collects.
A step-by-step guide, written for you
Which button, in which order, in your own Play Console — plus what to do if Google comes back with a question. Sent to you by email so you can follow it at your own pace.
What a refused submission actually costs
Not the fee. The weeks.
A refusal costs another full review
Google’s review usually takes up to 7 days (never guaranteed). A refused app does not get a faster second look — you fix it, resubmit, and wait the same cycle again. Two or three rounds is a month gone.
The things that get apps refused are the dull ones
The AAB format Play now requires, a 1024×500 feature graphic, a 512×512 icon, the content rating questionnaire, the Data Safety form. Any one of them can bounce a submission on its own.
A new developer account has a 14-day test in front of it
New personal accounts must run a closed test with 12 testers, unbroken for 14 days, before Google will consider the app for public release.
Lose your signing key and the app is gone
If you sign your own app and then lose the key, you can never publish an update to it — not a bug fix, not a new version. Google cannot recover it. You would have to start again under a new listing and lose every install and review.
One price, set for your country
One-time. No subscription. Nothing recurring to cancel. Your exact price is shown in full before you pay.
One payment, every file included
Your app is checked for Play-readiness instantly, before you can even pay — apps we can already see Google would refuse are not offered this at all. Paying unlocks your app immediately; download it unbranded right away, and your Play Store files arrive by email within minutes.
Get your Play Store files →You upload it. We make sure you have everything to upload.
The parts that are ours, and the parts that are yours — plainly, before you pay:
You upload it yourself from your own Google Play account, so the submission — and Google’s decision — is yours. Nobody can honestly guarantee approval, and we will not pretend otherwise. What we can do is remove the ordinary reasons apps get refused: the wrong file format, missing graphics, no privacy policy, an unanswered Data Safety form.
Google charges every developer a one-time US$25 registration fee. You pay it to Google, not to us, and the account is created in your name. It is the same $25 whether you register as an individual or as a business.
Every app goes through Google’s review before it appears on the Play Store. Google says this usually takes seven days or less, though it can occasionally take longer.
This is the part most people are not told about, so here it is in full. If you register a brand-new personal developer account, Google requires at least 12 testers opted in continuously for 14 days before you may even apply for production access. Someone who drops out on day twelve does not count, and the count must be back at twelve before you can apply. They must be twelve real people with their own Google accounts — making twelve accounts yourself breaks Google’s rules and can cost you the developer account entirely.
A business account is not subject to this rule at all. Google’s requirement covers personal accounts only. If you have a registered business, register the business account instead and the 12 testers never apply. It needs a free D-U-N-S business number, which takes up to 30 days to obtain — still less work than finding twelve people and holding them for a fortnight. Our guide covers both routes.
One app: the bundle, the signing key, the privacy policy page, the graphics, the form answers and the guide. Rebuild the same app as often as you like. A different app is a separate purchase. Future Google rule changes are not included — we will tell you when they land.
We do not need access to your account at all. You receive files and instructions; everything you do happens in your own Play Console, signed in as yourself.
Before you can pay, we check your app automatically for the things that usually get a website-based app refused, and apps that would clearly fail are not offered this at all. That catches the common problems; it cannot predict every decision Google makes. You must own the website or have permission to use it, and the app has to be genuinely useful on a phone.
Everything is generated automatically the moment your payment goes through, and emailed to you. There is no waiting on us.
How you publish your app to Google Play
Five steps. We do the fiddly two; the rest is you, in your own account.
Build your app free
Use the free builder as usual — paste your website URL, get your Android app.
Your app qualifies instantly
We check Play-readiness automatically before offering the Pack — sites that only wrap a social channel, which Google refuses, are not sold this and are pointed to our custom-work team instead.
Pay once, priced for your country
One payment, priced for where you are and shown in full before you pay. Your app unlocks at the same time — download it unbranded right away.
Your files arrive within minutes
The Android App Bundle, your signing key, your privacy policy link, the graphics and the answers to Google’s forms — generated automatically and emailed to you.
You upload it, and Google reviews
Follow the guide in your own Play Console: create the app, upload the bundle, paste the answers, submit. Google’s review is usually seven days or less. Stuck at any point? Write to us.
Frequently asked questions
Straight answers about what you get and what you still have to do.
Why can't I upload my APK to Google Play myself?
Does this guarantee my app will be approved?
Is the Play Store Pack a subscription?
Do I need a Google Play developer account?
How long does it take?
Your Play Store files, in one payment
The bundle, the signing key, the privacy policy, the graphics, the form answers and the guide — ready within minutes. Your app unlocks at the same time.
Would rather we did the uploading for you? Write to us and we will tell you what that involves.