Google Play's review process cross-references your Data Safety declaration against the actual URL you list for your privacy policy. If that URL points to a downloaded PDF sitting in a Google Drive folder, the review fails, every time, because there is nothing live for the crawler to check. This is one of six items on the Google Play launch checklist that most developers only discover from a rejection notice: the exact icon sizes Google wants, the adaptive icon's 66x66dp safe zone, the specific words Play Console's screenshot checker will flag, and the AdMob crawl window that leaves app-ads.txt showing as unverified even when the file is correct. Six free WAC tools generate each of these assets the right way the first time.
One Upload, Every Icon Size Google (and Apple) Wants
Android alone wants icons in five legacy sizes: 48, 72, 96, 144, and 192 pixels, covering mdpi through xxxhdpi density buckets. On top of that sits the adaptive icon system, which splits your logo into a foreground layer and a background layer on a 108dp canvas. Only the center 66x66dp of that canvas is guaranteed visible; every launcher (Pixel's circle, Samsung's squircle, some OEMs' rounded square) crops the rest away. An icon designed without that safe zone in mind gets its edges clipped on some percentage of installs, and you find out from a screenshot a user sends you, not from Play Console.
Google Play itself also wants a 512x512, 32-bit PNG with an alpha channel for the store listing, and an optional 1024x500 feature graphic, toggled off by default. If you also plan to ship on iOS, Apple requires a 1024x1024 icon with full opacity: transparent backgrounds get rejected outright, and most exported logo PNGs still carry one unless something flattens it out first.
The App Icon & Asset Generator takes one source image and outputs all of it in a single pass, plus PWA icons (192 and 512px, including a maskable variant) and the three favicon formats browsers still expect: a 32x32 .ico, an .svg, and a 180x180 apple-touch-icon. A safe-zone preview toggle overlays the 66x66dp crop circle on your foreground layer before you download anything, so you catch clipping before Play Console does.
Play Store Screenshots That Pass the Banned-Word Check
A raw device screenshot, cropped straight off your phone, is not what converts browsers into installs. The Screenshot Generator takes that raw screenshot and outputs a phone-framed, background-filled, captioned image sized to exactly what Play Console expects, with no manual resizing or guessing at aspect ratios.
The tool also runs a live checker against Google's actual list of banned promotional terms as you type your captions: words like "#1," "Best," "Top," "Discount," "Sale," "Million Downloads," "Download Now," "Install Now," and "Play Now" all get flagged before you submit anything. These are the words that get a listing rejected, not just flagged with a warning.
Google's own guidance describes the device frame as "highly recommended," not mandatory, so a bare screenshot will technically pass review. But the search-results thumbnail, the small cropped preview Play Store shows before someone taps into your listing, is what a browsing user sees first. A framed, captioned screenshot earns its keep at that first glance, where an unframed one just looks like a random app interface.
A Privacy Policy Google Play Actually Accepts
The Privacy Policy Generator is a short wizard: your identity and business details on one screen, toggles for the data practices you actually use (analytics, Firebase push notifications, AdMob) on the next. It generates a policy that covers GDPR, CCPA, and COPPA language based on which toggles you switch on, rather than a single generic template that claims to cover everything.
Google Play's review cross-references your Data Safety declaration in Play Console against the live URL you submit. A policy pasted into a Google Doc or sitting unlinked in your app's assets folder fails the same way a PDF does: there is no live URL for the crawler to check against your declaration. The policy has to be hosted and reachable at a real link.
Signed-in users can save a hosted link directly from the generator and manage multiple saved policies if they run more than one app, since each app's data practices and package name need their own policy page.
None of this is legal advice, and the generator says so plainly: have the output reviewed by someone qualified before you rely on it for a business handling sensitive data. For the full legal detail on what GDPR, CCPA, and COPPA actually require, WAC's privacy and data handling documentation goes deeper than a generated policy can. For how Play Console's Data Safety section maps to what you declare, the Data Safety and policy compliance documentation covers the mechanics end to end.
app-ads.txt: The File AdMob Takes Two Days to Notice
app-ads.txt is one line of text, but it has to be the exact right line in the exact right place. The app-ads.txt Generator takes a single input, your AdMob publisher ID in the format pub- followed by 16 digits, and outputs the required line: google.com, {publisherId}, DIRECT, f08c47fec0942fa0.
Getting the line right is the easy part. Getting it hosted correctly is where most developers lose a day. The file has to sit at your exact domain root, not a subfolder: https://yourdomain.com/app-ads.txt, nowhere else. The domain also has to match what's registered against your account in AdMob exactly. And once it's live, AdMob does not check it instantly. Its crawler validates the file on a 24 to 48 hour cycle, so a correct file uploaded five minutes ago still shows as unverified if you check right away. For the full mechanics of how AdMob matches sellers and validates ad requests against this file, see WAC's AdMob policy documentation.
Profile Pictures Sized for X, Facebook, LinkedIn, and YouTube
The Social Profile Picture Generator takes one upload and exports four exact sizes in a single download: X (formerly Twitter) at 400x400, Facebook Page at 720x720, LinkedIn Company at 300x300, and YouTube Channel at 800x800. Each platform has its own required dimensions, and getting them wrong means a stretched or off-center logo on your launch day profile.
All four platforms display these images circle-cropped in practice, even though the file you upload and export is square. A live circle-crop preview shows exactly what gets clipped at the edges, which catches logos with text or details close to the corners before you publish them to four platforms at once instead of after.
A QR Code Card for the Table, the Poster, and the Receipt
Not every install starts online. A restaurant table tent, a storefront window poster, a printed receipt: these are places a QR code still does real work, and a bare black-and-white QR square looks like an afterthought next to your branding everywhere else.
The QR Download Card Generator builds a full marketing card instead: your logo, app name, a headline line of text, and a background you choose, with a live preview you can test-scan before you print anything.
The QR code itself always sits on its own white quiet-zone card, regardless of what background color or gradient you pick for the rest of the design. That white margin around the code is not decorative; an insufficient quiet zone is one of the most common, specific reasons a DIY QR graphic scans fine on a laptop screen and fails once it's printed and someone points a phone at it under bad lighting.
The Rest of the Google Play Launch Checklist: Submitting Your App
These six tools produce the assets: icons at every required size, screenshots that won't get bounced for banned words, a privacy policy Play's review can actually verify, a correctly hosted app-ads.txt line, and the social and print assets that make launch day work as marketing. What they don't do is walk you through Play Console itself, the actual upload screens, the full spec cross-check against what Google's review expects, or the specific reasons a submission that looks fine gets bounced back anyway. That's a longer, more mechanical process than a tools roundup can cover honestly, and WAC's own documentation already handles it in detail. For the actual Play Console walkthrough, from creating the listing through uploading your signed AAB and choosing a release track, see the full Play Console submission walkthrough.
Generate the assets here first. Then follow that guide for the part where you actually hit publish.
Build your Android app free, then use these tools to launch it →