What an incremental import does
A source file can change on every software release. A reliable localization process compares imported keys against the existing project rather than replacing the entire translation catalogue. LangKit previews new, changed and unchanged keys, and keeps keys that are absent from an individual upload.
A safer review cycle
When source text changes, existing translations remain visible but their approvals can be reset for review. Translators can see what needs attention instead of starting over. A comparison checksum prevents a stale preview from being applied after concurrent edits.
Use it with CI/CD
Developer clients can preview and apply batches using project-scoped API tokens. Confirm the reported differences before applying them. For large pipelines, use a stable idempotency identifier when creating machine-translation jobs.
Common questions
Does an import remove keys not present in the file?
No. Missing keys in a partial file are preserved.
Will unchanged translations be rewritten?
No. Unchanged values are skipped by the incremental import flow.
Before relying on this in production
Confirm support for your resource syntax and test exported translations in your application. Documentation describes supported workflows, not a guarantee of lossless conversion for every specialized format.