How to Reinstate a Google Play Console Developer Account Closed Due to Inactivity
Short answer
Yes — an account closed for inactivity can sometimes be reinstated. You appeal through the Play Console general contact form, not from inside Console (you can't log in anyway). Of 8 appeals I have personally handled, 6 accounts were restored. Your chances are best if you had live apps on the account, one of them had 1,000+ installs, and the closure was under 180 days ago.
Google closes Play Console developer accounts that sit unused. If it has happened to you, the email is blunt and the Console is gone — and most of the advice online tells you to just start over with a new account and a new $25 registration fee.
That advice is often wrong, or at least premature. Recently closed accounts do get reinstated. I have helped with these appeals repeatedly, and below are my real numbers, who tends to qualify, the exact form to use, and screenshots of the reinstatement emails Google actually sent.
What are the real chances of getting it back?
Nobody publishes honest numbers on this, so here are mine. These are appeals I have personally worked on for accounts closed due to inactivity — a small sample, and my own cases rather than an industry statistic:
My real numbers on inactivity closures
These are the accounts I have personally helped appeal after closure for inactivity — not an industry average, and not a promise. Your outcome depends on your own reason and Google's decision.
- Appeals filed
- 0
- Accounts restored
- 0
Six out of eight came back. I want to be equally clear about the other two: they did not. This is not a guaranteed process, and anyone telling you otherwise is selling something.
Who has the best chance of reinstatement?
Google does not publish criteria for these decisions. What follows is the pattern I see across the cases I have handled — the accounts that come back tend to share these three things:
You had 1–2 live apps when the account closed
An account with published, working apps on it reads very differently to a review team than an empty one. This is the single factor I see matter most.
At least one app had 1,000+ installs
Real users on a real app make a stronger case for reinstatement — there are people affected by the closure, not just a developer account.
The closure was less than 180 days ago
Recent closures have a noticeably better outcome rate. The further back it goes, the harder the case becomes.
If all three describe your account, an appeal is genuinely worth filing. If none of them do — no live apps, no meaningful installs, and the closure was over a year ago — the honest answer is that your chances are slim, and registering fresh may be the faster route.
How to appeal when you can't access Play Console
This is where most people get stuck. The usual appeal flow lives inside Play Console — and your account is closed, so you cannot reach it. There is a way around that.
Use the Google Play Android Developer general contact form. It works without Console access and reaches the Play Developer Support team directly:
What to write in the appeal
The single thing that decides these cases is your reason for the inactivity. A vague message gets a vague outcome. Be specific and truthful about why the account went unused — illness, a job change, a paused project, a team that moved on. Then state what you intend to do with the account now.
- Your developer account email — the exact one the account was registered under.
- Your package names, if you had apps published.
- A clear, honest reason for the period of inactivity — this carries the most weight.
- What happens next — that you plan to update your apps and keep the account active going forward.
Keep it factual and short. You are writing to a reviewer with a queue, not making a case in court. One clear paragraph explaining the reason beats three pages of frustration.
Proof: real reinstatement emails
Here are three of those reinstatements, as redacted screenshots of the actual emails Google sent — all from googleplay-developer-support@google.com, all for accounts that had been closed due to inactivity, spanning April 2025 to June 2026. Names are blacked out for the developers' privacy. Click any of them to read the full message.
Each one carries the same core sentence: “Good news — we were able to reinstate your developer account.” Note that Google also warns in these emails that a reinstated account can be closed again for inactivity, so publish an update once you are back in.
What to do once your account is back
Reinstatement is not the end of it. Google states plainly in the reinstatement email that the account becomes eligible for inactivity closure again if it goes unused. Two things to do straight away:
- Publish an update. If your apps were removed when the account closed, you will need to send a new update through review to get them live again.
- Keep the account genuinely active. Sign in periodically, keep your account details current, and ship occasional updates rather than letting it go quiet for another year.
The honest caveat
This is not a guaranteed fix.Reinstatement depends on the strength of your reason and on Google's final decision — nobody outside the review team controls that, myself included. Two of my eight cases did not come back.
What I can tell you is that if you match the eligibility points above and your closure is recent, filing this appeal costs you nothing but the time it takes to write it clearly. That is a reasonable trade against paying to register a new account and starting from zero.
Want me to look at your case?
Send me your situation — when the account closed, what apps were on it, and why it went inactive. I'll tell you honestly whether an appeal is worth filing, and help you write it. No charge.
Did this article help you?
Your answer tells other developers whether this is worth their time.