Why the route matters
On-image product text can be translated without leaving the desktop, or with text or images sent to a third party. The wrong route creates either unnecessary uploads or unexpected quality and billing outcomes. This guide summarises the three paths so you can choose before you queue a batch.
1. Local engine
OCR and translation run on the installed computer. No product account is required for the local engine. A one-time purchase unlocks unlimited local translations and free updates. First launch may download or install a local runtime, so keep a network connection available during setup.
Choose local when catalogue images should stay on-device by default, or when you are processing privacy-sensitive sets. See local image translation.
2. Your API (DeepL or Google)
You may configure your own DeepL or Google translation API. In that case, recognised text is sent to that provider. Images are not sent to Imagoo cloud AI on this path, but text still leaves the device. Treat this as a separate policy decision from on-device local translation.
3. Cloud AI
Optional high-quality cloud AI sends images to the product cloud workflow. Sign-in is required, and each cloud translation deducts points. The unlimited local license does not cover cloud AI jobs.
Use cloud when upload is allowed and the cloud model is appropriate for the artwork. Details: cloud image translation.
Quick decision checklist
- Images must stay on this device → local engine.
- Text may leave the device via your own API key → DeepL or Google.
- Image upload and per-image points are acceptable → cloud AI.
- Packaging-heavy shots may still need an editor pass after any route.
For the full data-handling matrix, read local and cloud data handling.
FAQ
Frequently asked questions
Does the local engine upload product images?
No. Local OCR and translation run on the installed Windows or macOS device. First-run setup may still need a network connection to download the local runtime.
When should I use cloud AI instead of local?
Use cloud AI when image upload is allowed and you want the optional high-quality cloud workflow. It requires sign-in and deducts points per image. It does not use the unlimited local license.
Is configuring DeepL or Google the same as cloud AI?
No. Your own DeepL or Google key sends recognised text to that provider. Product cloud AI sends image data to the product cloud and bills in points.