The store-asset problem this app addresses
App and game teams ship the same visual frames across languages. Store screenshots, feature callouts, promo banners, and event art carry headlines and CTAs that must change with the market while composition stays consistent. Hand-editing each file does not scale when a release covers several locales at once.
Imagoo Image Translator Unlimited keeps translation, review, and export on Windows and macOS. Teams can run the local engine for device-based work, optionally attach a DeepL or Google API, or use cloud translation when image upload and points are acceptable.
One workflow for store and promo assets
| Step | Use in Imagoo |
|---|---|
| Prepare a locale slice | Group screenshots and banners by source language and destination market. Keep originals. Local input includes JPG, PNG, WebP, and BMP. |
| Choose a translation route | Local engine for on-device work, an optional DeepL or Google API, or cloud translation when appropriate. |
| Translate in a batch | Add the set, set OCR and targets, and choose overwrite, suffix-beside-original, or another folder. |
| Review visuals | Open individual results to refine text, style, colours, and layout so longer strings still fit the frame. |
| Ship to stores | Export PNG, JPEG, or WebP images, then place those files in your store console or release pipeline. |
What this page does not claim
The product does not replace store listing copy, age ratings, or a connection into App Store Connect, Google Play Console, or a game engine. Translation output is not guaranteed to be storefront-final artwork. Use human review for claims, pricing, and legal marks.
For privacy-sensitive pre-release work, review local and cloud data handling before you enable API or cloud routes.
FAQ
Frequently asked questions
Does Imagoo connect to App Store Connect or Google Play Console?
No. The desktop workflow exports PNG, JPEG, or WebP files. Upload and listing assignment happen in the store consoles or your release tooling.
Can it translate live in-game UI or embedded fonts?
This product works on image files — screenshots, banners, and promotional art. Runtime UI strings, font packs, and engine localisation are outside the scope of this workflow.
Which route should pre-release assets use?
Use the local engine so OCR and translation stay on the installed device. Review local and cloud data handling before enabling API or cloud routes for confidential builds.
What does visual review cover?
After translation, open results to refine text, style, colours, and layout so longer locales still fit screenshot and banner frames.