The catalogue problem this app addresses
Cross-border listings reuse photography across languages. On-image text — headlines, callouts, badges, and packaging — has to change with the market while the underlying shot stays the same. Doing that file by file in a general design tool does not scale when a category has dozens of SKUs.
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 product-image localisation
| Step | Use in Imagoo |
|---|---|
| Prepare a catalogue slice | Group images 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. Cloud jobs can skip packaging text when that option is needed. |
| Publish | Export PNG, JPEG, or WebP images, then place those files in your storefront or campaign pipeline. |
What this page does not claim
The product does not replace listing copy, marketplace compliance review, or a connection into a specific CMS. Translation output is not guaranteed to be commercially final artwork. Use human review for claims, ingredients, and legal marks.
For privacy-sensitive work, review local and cloud data handling before you enable API or cloud routes.
FAQ
Frequently asked questions
What does this workflow cover?
It covers preparing a product-image set, translating with local, API, or cloud routes, reviewing visuals, and exporting PNG, JPEG, or WebP for a storefront or campaign.
Can packaging text stay in the source language?
Cloud translation includes an option to leave packaging text untranslated when that fits the image. Local review in the editor is still the place to confirm what should remain visible.
Does Imagoo connect to a store CMS?
This desktop workflow exports image files. Upload or assignment in a storefront, DAM, or CMS happens in those systems.
Which route should a privacy-sensitive catalogue use?
Use the local engine so OCR and translation run on the installed device. Review local and cloud data handling before enabling API or cloud routes.