Google Play Console submission history keeps one year

Google Play Console submission history is now visible for one year

Google Play Console now displays submission records for up to one year, starting May 1, 2026. The record is tied to each submission, not to the app as a whole, and it shows what was sent, when Google received it, how it was submitted, and what state it is in.

The part people miss is scope. Submission history is not a full release diary, and it is not the same thing as Play History in the consumer app. It is a publishing log inside Play Console, built so you can trace a submission, confirm what changed, and reference a submission ID when you talk to support.

Google says the change applies from May 1, 2026, and that it will maintain up to one year of history from that point forward. That means older submissions can age out of the view, so teams that need longer retention should keep their own release notes, changelog records, or ticket references outside the console.

The useful detail is that Google breaks one submission into the changes that were included in it. If you bundle a store listing edit, a production artifact, and a policy response into one send, the activity page is the place to check what actually went in together. That helps when a reviewer asks what changed or when your own team needs to reconstruct a release.

The thing that goes wrong in practice is assuming the page is a permanent audit archive. It is not. One year is enough for most release troubleshooting, but it is not enough for long-lived compliance tracking, contract disputes, or postmortems that run past a year. For those cases, save your own records the day you submit.

If you are using Play Console for a launch that gets revised several times, submission history is the fastest way to answer questions like: which version was sent, whether it came from the console or the Publishing API, and whether Google still marks it in review, ready to publish, or published. That saves time when a later change obscures the first one.

This also matters when a release gets split across workflows. A team might prepare the release in Play Console, then another tool or person submits the final group of changes. The submission activity page records the source, so support can see whether the submission originated from the console interface or the Publishing API.

For app teams that are still clearing Google Play’s testing gates, this is only a tracking feature. It does not replace the closed testing requirement for newer personal developer accounts, and it does not change the internal testing limit or the 14 day closed test rule. Internal testing still goes up to 100 testers, and closed testing still needs the continuous opt in period before production access.

That distinction matters because people often treat every Play Console page as if it can help them qualify for production. Submission history cannot do that. It can show what you submitted and when, but it cannot substitute for test participation, tester continuity, or the evidence Google asks for in the production access flow.

A practical workflow is simple. Submit the release, note the submission ID, copy the timestamp, and keep the release notes in your own tracker. If Google later asks what changed, or if a teammate needs to find the exact package that was reviewed, the console history gets you back to the right submission faster.

If you are also coordinating testers, use this page only as a timeline, not as proof that testing happened. Google’s closed testing requirement for newer personal accounts is based on opted in testers over time, and if a tester opts out and later returns, the 14 day count restarts. That is separate from submission history, even though both sit inside Play Console.

For teams that want a public-facing place to organize testers, releases, and jobs around real app shipping work, DevConnect keeps that collaboration separate from Play Console and stays free to use. A platform like https://devconnectplatform.com can help with coordination, but the evidence for submission history still lives in Google Play Console itself.

The inconvenient truth is that this new one year window helps only if your process is already disciplined. If you submit often, reuse release names, or let notes live only in chat, the console log will still be hard to interpret later. The record exists, but the meaning of each record depends on the notes and artifacts you saved alongside it.

For debugging, the best habit is to treat each submission like a support case. Save the date, the submission ID, the version code, and the reason for the change. When a review stalls or a release needs to be rolled back, that bundle tells you more than memory does, and it is still useful after the console’s one year limit passes.

FAQ

Does this show every change I made in Play Console It shows the changes that were included in each submission group. It is a submission log, so it is most useful for tracking what was sent for review, not every click a user made in the console.

Can I use submission history to prove I completed closed testing No. Submission history records publishing activity, while closed testing compliance depends on tester opt in and the 14 day continuous requirement for the accounts that need it. Those are separate checks.

What disappears after one year Google says it will maintain up to one year of history from May 1, 2026 onward. That means records older than that can fall out of the visible history, so teams should keep their own archive if they need longer retention.

Where do I find the submission ID On the submission activity page in Play Console. Google says the page provides a submission ID you can reference when seeking support.

Is internal testing part of this history Internal testing has its own track and tester limits. Submission history can help you track the release you sent, but it does not change the rules for internal testing, which still allows up to 100 testers.