1. Prepare source images
Group images by source language and destination market. A batch that mixes unrelated languages forces extra review later. Keep the originals available so output can be compared before publication.
Local input includes JPG, PNG, WebP, and BMP; cloud input is JPG, PNG, and WebP only. If a file is in another desktop-supported local format, keep it on the local route instead of cloud.
2. Choose a translation route
Use the local engine when work should stay on the device. The local engine does not require product sign-in. Configure DeepL or Google only if you accept sending text to that provider. Use cloud translation only when image upload and per-image points are acceptable.
Packaging-heavy shots may need the cloud option to skip packaging text, plus a later editor pass. Privacy-sensitive sets should stay on the local engine. Read local and cloud data handling before you switch routes.
3. Create the batch
In the Batch area, add images, select OCR and target languages, and choose an output location. Where available, outputs can be saved with a translated suffix beside the originals, overwrite the source files, or land in a selected folder.
Confirm the OCR language matches the text actually printed on the images. The local engine offers 14 OCR sources and 18 targets. Details: supported languages and formats.
4. Review the visual result
Do not treat automated output as final artwork. Open images that need corrections, adjust text and styling in the editor, and check that important packaging information remains appropriate for the target market.
Pay extra attention to small type, badges, and legal or ingredients copy. See edit translated images.
5. Export and publish
Export approved images as PNG, JPEG, or WebP. Keep the project and exported file with the relevant catalogue record. Uploading into a storefront or DAM happens outside this app.
Checklist before you publish
- Originals are still available for comparison.
- The translation route matches the data policy for this set.
- OCR and target languages match the market.
- Output location will not silently overwrite files you still need.
- Images with packaging or claims were opened in the editor.
- Exports are PNG, JPEG, or WebP as required by the destination.
FAQ
Frequently asked questions
Which formats can I add to a local batch?
Local image selection includes JPG, PNG, WebP, and BMP, plus additional formats supported by the desktop workflow. Cloud input is JPG, PNG, and WebP only.
How do I avoid uploading images?
Use the local engine. Configure DeepL or Google only if you accept sending text to that provider. Use cloud translation only when image upload and per-image points are acceptable.
Where should outputs go?
Where available, save with a translated suffix beside the originals, overwrite, or write to a selected folder. Keep the project with the catalogue record.