Compare your last accepted Android release with the next version. Spot changed permissions, inconsistent declarations, and missing review details — all inside your browser.
✓ No login✓ Local-only processing✓ No paid API
release_comparison.jsonLOCAL
RELEASE DIFF · SAMPLE
versionCode112→113UPDATED
READ_MEDIA_IMAGES—→AddedREVIEW
Reviewer accessProvided→MissingCHECK
SDK inventoryUnknown→UnknownUNKNOWN
◈ Your input stays in this browser
GET STARTED
Choose a real-world scenario
All examples are synthetic, not real developer releases. Try one to see how the tool explains a possible issue and its next steps.
WHAT YOU GET
From changed fields to a useful repair checklist
1. Compare two release snapshots. 2. Review evidence and uncertainty. 3. Export a report you can use before resubmitting.
ⓘ
Independent diagnostic tool. Not affiliated with Google. Results describe user-provided snapshots only; they cannot verify live Play Console state, guarantee compliance, or predict approval.
STEP 01 · INPUT
Compare release snapshots
Use the simple form or advanced JSON editor. Data stays in your browser; no account needed.
Only enter details you have verified. Blanks mean unknown.
Start with version codes and target SDKs. Add permissions or reviewer details if you know them. You can test the sample without any real app data.
Previous accepted release
New or rejected release
Only report SDK collection as verified if you have evidence. Do not enter passwords, reviewer account details or API keys.
Import local JSON snapshot (max 30 KB; file stays in browser)
Previous accepted release
Baseline snapshot
JSON
Values you have actually verified · Missing fields mean unknown
New or rejected release
Candidate snapshot
JSON
Do not paste passwords, private keys or secret tokens
Privacy: the browser processes your snapshots and does not send them to us.
STEP 02 · RESULTS
Evidence-linked report
Load a sample or compare your release snapshots to create a report.
DEMO REPORT — created using synthetic data. Not a real app assessment.
Δ
No report yet
Start with a demo or paste two releases to produce a local audit.
CHANGED FIELDS0Supplied snapshot fields
RULE FINDINGS0Rule checks needing attention
CONFIRMED INPUT ISSUES0Limited to supplied evidence
RISKS / UNKNOWN0Require manual verification
Detected changes
Prioritized checks
ⓘ
Findings rely on your input and a date-stamped rule reference set. Policies can change. Always check official Google documentation and the current Play Console status before taking action.
BETA FEEDBACK
Was this report useful?
Your selection can be counted only if optional anonymous event tracking is enabled and you choose to allow it. Otherwise, copy the feedback text to share yourself. No release snapshots or report content will be collected.
PRIVACY BY DESIGN
Your project stays on your device.
The release comparison remains local to your browser. There is no account, central release database, paid API, or payment integration. The default static upload has no custom event tracking. An optional Worker deployment can collect only allowlisted feature-event names after explicit opt-in. Hosting providers may still record ordinary page requests.
⌁
No remote file uploads
All comparison code runs in JavaScript locally. We do not send the snapshots to an API.
⊘
No credentials
Never paste passwords, API tokens or Play Console credentials. Known secret key names are blocked.
⇩
Portable reports
Exports are built and downloaded in your browser. You decide whether to share them.
◷
Short-lived session
Inputs are kept only in memory. Refreshing clears them; no localStorage is used.
ⓘ
Analytics: Cloudflare Web Analytics, if you enable it separately, measures website visits. Optional product-event tracking uses an Analytics Engine binding and only sends an allowed event name and demo/real category after opt-in. No release content, credentials, report evidence, IP address, or persistent visitor ID is deliberately included in product events. The hosting provider can still observe network request metadata. Events are counted, not used to identify unique users. Opt-in lasts only this page session.