Try for free
Learn/Guides/Localize store and CRM

How to localize store and CRM creatives into 10+ languages with AI

Written by Avia Shavit, Product Lead, Genie Labs

Workflow · 4 prompts · Last updated Oct 26, 2026

MODEL A MODEL B
1Compare image models
Aa EN あ JA ع AR Я RU
2Multi-language localization
1:1 9:16 16:9
3Resize for every platform

To localize a store screenshot, CRM pop-up or event banner without reopening the design, chain five steps: test which model renders your scripts, make fast drafts in every language, fix length before generating finals, run the finals with your approved translations, then resize each language for every placement. The art stays the one you approved. Only the text changes.

Key takeaways
Drafts and finals are different jobs. Machine translation for review, approved copy for anything players see.
Fix length before you generate. German and Russian run long; decide per asset whether text shrinks or boxes grow.
Test non-Latin scripts first. Arabic, Hebrew and CJK vary most between models.
Keep a do-not-translate list: the game's name, feature names, currency names.
In Genie, the language list, the do-not-translate terms and the format list save as skills, so every launch runs the same way.

How do you localize a creative, step by step?

1

Step 1: Test your hardest scripts first

Before a full run, take one creative and test it in your trickiest languages, usually Arabic, Japanese or Korean, on two or three models with Compare image models. Text rendering varies a lot between models. Pick the one that gets your scripts right and use it for the whole run.

PromptCompare image models →
2

Step 2: Make drafts in every language

Run the many-languages version of Multi-language localization with your full language list. This is for review: product, marketing and regional teams see every market's version in one pass and flag layout problems early.

Aa あ ع Я
PromptMulti-language localization →
3

Step 3: Fix length before finals

Ask Genie's agent which translated strings run longer than the original and whether shorter alternatives exist. Then decide per asset: should the text fit the existing space, or should buttons, banners and text boxes expand so the full translation fits? Send shortened copy back to your localization team for approval.

Every market live on the same day. Try Genie
4

Step 4: Run finals with approved copy

Run the own-translation version of Multi-language localization once per language, pasting the approved translation exactly. Flag any text that must stay unchanged. If copy changes come back late from legal or a regional team, use Text editing to swap just that text without regenerating.

Aa あ ع Я
PromptMulti-language localization →
5

Step 5: Resize every language for every placement

Run Resize for every platform on each final with your format list: store screenshot sizes, pop-up, banner, push image. Name what must stay: logo, CTA, price.

PromptResize for every platform →

The run at a glance

StepPromptPurposeShip it?
1Compare image modelsPick the model for your scriptsNo, it's a test
2Multi-language localization (many languages)Review every marketNo, drafts
3Agent length checkFit or expand, per assetNo, a decision
4Multi-language localization (approved copy)Final assetsYes
5Resize for every platformEvery placementYes

What goes wrong most often?

Brand names get translated. Keep a do-not-translate list in a skill and include it every time.
Right-to-left layouts break. Arabic and Hebrew may need the layout mirrored, not just the text. Check those assets by eye.
Fonts change between languages. Ask to keep the font family and weight, and review CJK separately since many fonts don't cover it.
Drafts ship by accident. Name files by stage, draft or final, so machine translation never goes live.
The honest read: this doesn't replace your localization team or native review. It removes the design queue between their approved copy and a shipped asset.

Where does Genie fit?

Localization is where one system pays off most: the same approved image, the same language list, the same do-not-translate terms and the same formats, saved as skills and reused for every launch and every LiveOps event. Every market goes live the same day instead of waiting in the design queue.

FAQ

Drafts can cover your full list in one request. For finals, run one language per request with its approved copy.

Keep reading

All guides →
Every offer,onbrand.
Offer artWorkflow · 6 prompts

How to create and test in-game offer art with AI

A workflow for offer pop-ups and store packs: currency in the art, a clear pack ladder, rarity tiers, color and copy variants, and every placement.

Test it,thenchoose.
Choose an AI image modelWorkflow · 6 prompts

How to choose the right AI image model for your game art

A test protocol for picking an AI image or video model per asset type: check what's available, test on your real prompt, judge against your style guide, save the winner.

Same game,newseason.
Seasonal event artWorkflow · 6 prompts

How to reskin your mobile game for a seasonal event with AI

A LiveOps workflow for Halloween, winter or any event: reskin plan, costumes, lighting, event icons and the launch post, chained in one consistent look.

Localize your next launch.

One approved creative in. Every market's version out.

Try GenieBook a demo
Learn/Guides/{{ g.crumb }}

{{ g.h1a }} {{ g.h1b }}

Written by {{ g.author }}

{{ metaLine }}

{{ g.intro }}

Key takeaways
{{ k }}

{{ pre.h2 }}

{{ b }}

{{ b.n }}{{ b.k }}{{ b.v }}

{{ g.stepsH2 }}

{{ s.n }}

{{ s.title }}

{{ x.text }}{{ x.text }}{{ x.text }}

{{ c }}
{{ x.text }}{{ x.text }}{{ x.text }}

Why first{{ s.why }}

Prompt{{ pc.name }} →
{{ g.cta.a }} {{ g.cta.b }} Try Genie

{{ g.glanceH2 }}

{{ c }}
{{ r.n }}{{ r.p }}{{ c }}

{{ g.wrong.h2 }}

{{ g.wrong.intro }}

{{ x.text }}{{ x.text }}{{ x.text }}
{{ g.wrong.honest }}

Where does Genie fit?

{{ g.genie }}

FAQ

{{ x.text }}{{ x.text }}{{ x.text }}

{{ g.closing.a }} {{ g.closing.b }}

{{ g.closing.line }}