Key concepts

Ten terms cover 90% of the product. This page defines them once; every guide builds on them.

A project is one series — it owns the source language, target languages, glossary, team and translation memory. A chapter is one batch of pages (a volume, a season arc, an episode). Pages are the individual images the pipeline processes.

The source language drives OCR hints and vertical-text handling; target languages can be added or removed at any time. Each translation is stored per language, so adding one later only translates what is new — existing languages are untouched.

OCR detects text blocks and reads them. AI correction (optional) fixes misreads before translation. Translation converts each block into every target language, using the glossary, story context and your prompts. Inpainting erases the original text from the artwork. Rendering composes the final page server-side, exactly as the editor shows it.

Stages draw from your plan credits — roughly one credit per page per stage. Bringing your own API key (BYOK) routes translation through your provider and costs zero credits. See Credits & billing in the Reference for the exact accounting.

The glossary locks how names and terms are translated — the pipeline must use it. The translation memory records source→target pairs (machine or human) and reuses them: exact matches auto-fill for free, fuzzy ones are suggested.

Invite teammates to a project with a role, or reuse a whole team across projects. Share links give read-only reviewers access to composed pages with block-anchored comments — no account needed on their side.