Docs
Getting started with Lexique
Set up a first project, add locales, import files, review coverage, and export translation bundles.
Docs
Import JSON and YAML translation files
Supported file shapes, locale handling, domains, tags, and import safety notes.
Docs
Import translations from GitHub and GitLab
Repository connection, selected-file import, OAuth privacy boundaries, and onboarding flow.
Docs
Export translations for CI/CD
Export formats, API-token sync, CI examples, and payment-required behavior after trial expiration.
Docs
API sync and agent access
Bearer token authentication, scopes, pull and push endpoints, OpenAPI, and MCP wrapper guidance.
Docs
Trial, Pro, and payment-required behavior
The trial starts on first project creation/import and Pro keeps product activity available after expiration.
Guide
A practical translation key workflow
Naming, context, tags, coverage, and review patterns for translation keys.
Guide
GitHub and GitLab workflow for app translations
A repository-first i18n workflow from import to review to export.
Guide
Shipping translations through CI/CD
A CI/CD pattern for pulling translation bundles and preventing missing-copy regressions.
Guide
Replacing translation spreadsheets
How to move from spreadsheet review to a source-of-truth translation-key workspace.
Compare
Lexique vs spreadsheets
Spreadsheets are flexible, but Lexique keeps translation keys, context, coverage, and exports in one workflow.
Compare
Lexique vs Lokalise
Lokalise is broad localization management. Lexique focuses on a calm, table-first workflow for translation keys close to code.
Compare
Lexique vs Phrase
Phrase covers larger localization operations. Lexique keeps the first workflow narrow: import files, edit keys, track coverage, and export clean bundles.
Compare
Lexique vs Crowdin
Crowdin is mature localization infrastructure. Lexique focuses on a table-first product-copy workspace for teams that want less process overhead.
Release notes
Changelog
Track public beta updates and integration milestones.