Skip to content

FAQ

Short answers, with links to the chapter that goes deeper.

Upload one or more source files, pick the source language and the target language(s), and create the project — files are processed and become editable shortly after. See Creating a project.

A file becomes editable once it has finished processing. Each file can be translated into one or more target languages; open it in the editor to translate, and download it from the project hub when it’s done. See The project hub.

Can the platform reuse my previous translations?

Section titled “Can the platform reuse my previous translations?”

Yes — translation memories (TMs) store past translations so identical or similar text can be reused. Exact TM matches and repeated segments can be filled from the memory before machine translation runs. See Translation memories.

Use a glossary: it pins how specific terms should be translated across a project or client. Add term pairs (source term → preferred translation) and edit or remove them as conventions change. See Glossaries.

Which machine translation engines can a project use?

Section titled “Which machine translation engines can a project use?”

Default (recommended, with automatic fallback), On-Prem, Cloud, Google, DeepL, Copy Source (fills targets with the source text unchanged), or None (skips machine translation entirely). See Machine translation & quality.

Working as a team: shared projects, members with roles, and centralized billing. Projects created in the org are shared with the team, and org work is billed at the organization level. See Organizations.