Frequently asked questions
Short answers to the questions teams ask before and after they start with transglot.
Before you start
It keeps your product's text translated. You bring source strings in from a repository, a file or a content platform; Glossa drafts the translations; automatic checks and your reviewers catch what needs a person; and the finished languages go back out through your build, a pull request, the CDN or the content platform. See How transglot works.
Yes. The Free plan includes one workspace, one project and a monthly allowance of AI translation, plus a one-time grant of welcome words. The paid plans are Starter, Team, Business and Enterprise. See pricing for current allowances and prices.
Starter or above. The CLI, the GitHub Action, the API, the CDN, the glossary and the integrations all start on Starter. Quality mode, AI quality review and self-heal start on Team. Single sign-on and SCIM are on Enterprise. See Plan requirements.
Yes. When you connect the CLI from a Free account, the browser offers a free trial of the Starter plan to the account's owners and billing members. Stripe asks for a card and nothing is charged that day. See the Quickstart.
Yes. Projects with an OSI-approved licence and a public repository can apply for the open source plan, which is reviewed by hand. See Open source plan.
Glossa, the transglot translation engine. Glossa Flux is the fast default model; Glossa Deep is the higher-quality model you get with Quality mode on Team and above. See AI translation.
No. transglot does not train any models on your content. The AI services it uses process your content under commercial terms, for translation only. See the Trust Center.
Exact-match reuse draws on an anonymised, shared pool as well as your own workspace's history. You can turn that off per project with the Translation memory setting; the project then neither reads from nor adds to the pool. Similar-match suggestions only ever come from your own workspace. See Translation memory.
Twenty, including JSON (flat and nested), YAML, XLIFF 1.2 and 2.0, gettext PO, Android XML, Apple strings, stringsdict and string catalogs, Flutter ARB, Laravel PHP and JSON, Java properties, .NET resx, Markdown, CSV and Excel. See File formats.
Yes. You can bring your keys and translations across from Lokalise, Phrase, Crowdin, Transifex, Weblate or POEditor with a read-only token. Your existing translations arrive as human-authored. See Import from another tool.
Only to connect your codebase. Uploading files, migrating from another tool and connecting a content platform need no code. See Do I need a developer to set transglot up?
Yes. Invite them with the Translator or Reviewer role, limit them to the projects and languages they work on, and hand them languages as assignments with a due date. See Onboard a vendor or freelancer.
Yes. Turn off Auto-translate for the project and nothing is translated until someone starts a run; your team can write every translation in the editor. See AI translation settings.
Yes, with SAML 2.0 and OpenID Connect identity providers, plus SCIM provisioning, on the Enterprise plan. See Set up single sign-on.
Once you are using transglot
No. A translation you have edited or reviewed is never overwritten by AI. Glossa only writes into strings that are empty or still a Glossa draft. See Translation states.
In source words, once for each target language they are translated into. Reused translations and anything your team writes by hand do not count. See Words and usage.
Your plan includes an allowance of AI translation each month. Usage is measured against that allowance, and what happens when you exceed it depends on whether usage-based billing is turned on for your account. With it off, translation stops until the next cycle or until you upgrade; with it on, translation continues up to the spend cap you set. See Usage-based billing.
A person flagged it, a quality check found a problem, or confidence routing sent it to review. See Why was my translation flagged for review?
Pull them into your build with the CLI or the GitHub Action, merge the pull request a connected repository opens, or publish them to the CDN and read them at runtime with an SDK. See The CDN and The runtime SDKs.
Editing and publishing are separate. Publish the language again, or run the build that pulls translations. See My translations are not reaching my app.
Yes. Screenshots show where a string appears, and on Starter and above the in-context editor lets reviewers edit translations on your running app. See The screenshot library and In-context editor.
Yes. A project's Export settings page builds one archive of the languages and formats you choose: files for your app in any supported format, or a bilingual sheet for a person to work on. The CLI's pull writes the languages named in your transglot.json to files.
Can't find your question? See Get help.