When a batch is the right unit of work
A batch is useful when several images share a source language and a destination market. Instead of repeating OCR and target settings on every file, you add the set once, choose the translation route, and watch the queue until items finish.
Keep originals available so you can compare output before publication. Group images that should stay together so review stays manageable after the queue completes.
Local, API, or cloud batches
Batch jobs can use the local engine, an optional DeepL or Google API you configure, or optional cloud translation. Local batches do not require sign-in. Cloud batches require an account and deduct points per image.
| Batch route | Typical reason to choose it |
|---|---|
| Local engine | Keep OCR and translation on this device after the one-time license. |
| Your DeepL or Google API | You already have a provider account and accept sending text there. |
| Cloud AI | You want the product’s cloud high-quality models and accept image upload plus points. |
Batch workflow
- Add the images to translate. Local selection includes JPG, PNG, WebP, and BMP; cloud batches accept JPG, PNG, and WebP only.
- Select OCR and target languages for the job.
- Choose to overwrite originals, save alongside them with a translated suffix, or use another output folder where available.
- Start the queue and monitor task progress in the batch list.
- Review finished files and open individual work in the editor when layout or copy needs a change.
After the queue finishes
Automated output is a draft. Open images that contain claims, small type, or packaging details and refine them before they reach a storefront. Export approved files as PNG, JPEG, or WebP.
FAQ
Frequently asked questions
Can a batch run entirely on the local engine?
Yes. Local batches do not require sign-in. You can also send a batch through an optional DeepL or Google API you configure, or through optional cloud translation.
Where are translated files saved?
Where available, you can overwrite originals, save alongside them with a translated suffix, or write to another output folder.
Do cloud batches use the one-time local license?
No. Cloud batches require an account and deduct points per image. The one-time purchase covers unlimited local translations, not cloud AI.
Should every batch file go live without review?
No. Open individual results when wording, layout, or packaging text needs a visual check, then export PNG, JPEG, or WebP.
