Can You Delete or Pause a Closed Testing Track?
Closed testing tracks can’t simply be deleted in Play Console, but they can be paused. What pausing does to testers, and why not to pause mid-requirement.
Short answer
You generally can’t delete a closed testing track, but Play Console lets you pause a track, which stops it serving releases to testers. Don’t pause during your 14-day requirement: Google counts testers opted in continuously to a closed test, and pausing undermines that. To fix a bad build, upload a new release to the same track instead.
What you can do with a track
- Pause the track. Testers stop receiving releases from it. Apps already installed stay installed.
- Remove testers by editing the email list or Google Group on the track.
- Replace a release by uploading a new version to the same track.
- Leave it running. After production access, many developers keep the closed track for future betas.
Play Console labels change, so look for Manage track and the pause option on the track’s page. Check Google’s current help if you can’t see it.
Why not to pause mid-test
The requirement is 12 testers opted in continuously for at least 14 days. Pausing interrupts the test. Even if opt-ins technically survive, you’re creating a gap that’s hard to explain in your production access answers. Leave it running until you’ve applied and been approved.
Situations and what to do instead
| Situation | Instead of pausing |
|---|---|
| You shipped a crashing build | Upload a fixed build with a higher version code to the same track |
| Wrong tester list attached | Edit the Testers tab and add the right list. Don’t remove the old one until the new testers have opted in |
| You want to start over with a new app | Create a new app. Package names can’t change (see package names) |
| Test finished and you’re approved | Keep the track for betas, or pause it if you don’t need it |
After approval
Keeping a closed track is cheap and useful. See should you keep your closed test running after launch.
Frequently asked questions
Does pausing remove the app from testers’ phones?
No. Apps already installed stay installed. Testers just stop receiving releases from that track.
Can I resume a paused track?
Yes, tracks can be resumed. Testers will then receive releases from it again.
Sources and how we keep this accurate
- Play Console Help: Set up an open, closed, or internal test
- Play Console Help: App testing requirements for new personal developer accounts
Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start freeKeep reading
Should You Keep Your Closed Test Running After Launch?
Does Updating Your App Reset the 14-Day Closed Test?
How to Promote a Closed Test Release to Production
Closed Test Release Stuck “In Review”: What to Do
Lost Your Upload Key? How Play App Signing Saves You
Your Closed Test Release Was Rejected: What It Means
Browse all answers, or see the quick answers, guides and comparisons.