Calibre manages and converts ebooks; the separate Ebook Translator plugin adds a translation workflow. If you already maintain a Calibre library, that combination can be useful. It also means there are several things to configure: the plugin, the engine it calls, the language, and the output.
Follow the project's current official English guide. The steps below describe its documented setup, not a claim that this article tested every supported engine.
Know which part does what
Calibre handles the book library and final conversion work. The plugin prepares and sends translation requests using the selected engine. The engine supplies the language output under its own account conditions and data-processing terms.
This distinction prevents two common mistakes. Clicking Calibre's normal Convert books action does not translate a book. And running a plugin on your desktop does not mean the translation is offline. If its engine is a cloud service, your content is sent for processing according to that service's setup.
Keep the original EPUB outside the working process and check that it opens correctly. Broken source navigation or missing chapters make it harder to judge the translated result.
Install and configure a supported engine
The official guide describes installing Ebook Translator from Calibre's plugin list in Preferences, then restarting Calibre. In the plugin settings, choose the engine and supply the credentials it requires. Language support depends on that engine.
For one documented setup, open the plugin’s Settings → Engine panel and select Google (Basic). This engine requires a Google Cloud API key; use the Google Cloud console linked from the plugin guide to manage that credential, and follow Google’s current Cloud Translation setup and billing requirements. Enter the key in the plugin’s engine configuration, then use Test to check the selected connection. Do not use the separate ADC engine option unless you have configured Application Default Credentials.
Check the account type as carefully as the key. A consumer translation subscription and an API account are not necessarily interchangeable. Check the engine provider's current pricing, quotas, and privacy terms before sending a full book. Never include a secret key in a shared screenshot, support post, or exported instructions.
Once configured, use a small approved test to confirm that the connection returns the intended language. This is a connection check, not enough evidence of whole-book quality. If requests fail, read the error for authentication, quota, or service limits before changing unrelated settings.
Choose the translation mode and EPUB output
The documented Advanced Mode supports reviewing translated passages before output; Batch Mode provides a different whole-job workflow. Follow the current guide for the mode you choose, select the target language, and confirm EPUB output and the destination for the generated file.
Avoid changing every customization setting on the first run. Record the engine, language, output choice, and any content-retention option you use. That record is useful if you need to understand a mixed-language result or recreate a successful setup later.
Keep a simple filename convention for the original and new edition. If a library contains several files with the same title and cover, open a known passage to identify the actual language before sending it to a device.
Review both translation and book structure
Start with content that exposes likely errors: dialogue with several speakers, a technical definition, a paragraph containing a negative, and a passage with numbers. Search for recurring names in early and late chapters. Do not judge the entire translation by the opening paragraph.
Then review the EPUB itself:
- Follow several table-of-contents entries, including one near the end.
- Check chapter boundaries for missing or repeated text.
- Inspect illustrations, captions, and one note reference.
- Enlarge the font and try a narrow reader window.
- If retaining original text, check that source and translated passages follow the intended order.
A successful engine call does not prove these structures survived. Conversely, a display problem in one app does not necessarily mean the translation text is missing; compare another reader and the source.
Use an online route when setup is the obstacle
If your aim is simply to read a complete EPUB in another language, configuring keys and engine settings may be more work than you want. PDF Craft's EPUB translator accepts the complete file online. Choose the target language, translation-only or bilingual output, and optional instructions, then download from the completed task.
Its bilingual output places each translation after the original passage. It does not require configuring an external engine in the interface. New users receive trial credits, and translation is charged by usage; see Pricing for current rates.
Choose the plugin when its configuration fits your existing library workflow. Choose a file-based online route when you want fewer setup decisions. The EPUB workflow comparison and whole-ebook guide help separate those choices from the review both routes still need.