Skip to main content
Blog
google-play

google will write your play store listing in every language now. the screenshots are still on you.

At I/O, Google Play added Gemini-powered listing localization — upload a CSV, get every language. Here's the part it doesn't translate.

Carlton Aikins3 min read

the most useful thing google play shipped at i/o this week, for a one-person shop, wasn't a model or an agent. it was a csv importer. and i mean that as a compliment.

what they announced#

buried in the "scaling your business with less complexity" section of tuesday's play post: gemini now does the heavy lifting of localizing your store content. you upload a structured file — a csv or a google sheet — and play console pre-populates your listing across languages "for your review." subscription benefits get auto-translated too. separately, when you click a keyword recommendation on your grow page, gemini spins up a brand-new custom store listing tuned to that keyword, deployable in one click.

if you've ever copy-pasted your description into google translate forty times to half-localize a listing you never finished, you know exactly how much manual misery this deletes. localization was the thing every indie dev says they'll "get to." the text barrier is basically gone now. good.

the part nobody localizes for you#

here's the catch, and it's the same catch every "ai does it for you" feature carries: the easy 80% is the part that was never the problem.

a play store listing isn't just words. gemini will translate your description and your subscription perks. it will not localize your screenshots — and the screenshots are where conversion actually happens. the caption text baked into the image stays in english. the in-app UI in the screenshot stays in english. the currency in your pricing shot stays in dollars. a japanese user looking at a localized paragraph sitting on top of five english screenshots doesn't read "global app." they read "lazy port."

and "for your review" is doing a lot of quiet work in google's sentence. machine-translated copy is still your copy, legally and policy-wise. an overclaim that would get one english listing flagged is now an overclaim in thirty languages. the data safety form doesn't translate itself either. neither does a content rating that shifts by region.

the stora angle#

this is exactly the half stora was built for. point it at your repo and it renders localized screenshots across every play device size and every locale you care about — captions, frames, and the in-app strings, not just the listing paragraph above them. it generates the listing copy per market, and runs a compliance pass that catches the screenshot-to-claim mismatches before google's reviewers (now partly AI) do.

gemini handles the paragraph. the picture is still the thing that gets the install.

the call#

google just removed the copy-paste tax on going multilingual, and that's genuinely great — take the win, upload the sheet. just don't mistake "my listing is now in 40 languages" for "my app is localized." the words are the floor. the screenshots are the product. that work is still yours, and honestly, it's the fun part.