How translation works
On this page
1. Find the text#
ResilientLang reads your pages and splits them into strings. A string is a piece of text such as a sentence, a heading or a button label. Text with bold or links inside it stays together as one string, so translators see the whole sentence. The tags inside it are replaced by numbered markers. See Tags and placeholders.
2. Give each string a key#
Each string gets a key. The key is made from the text itself. The same text always gets the same key. If you change the wording on your site, the new wording is a new string with a new key. It needs a new translation.
3. Translate#
A translation engine translates every string that has no translation yet. The translations are stored per language. A translation that a person wrote or reviewed is never replaced by a machine run.
The product also keeps a translation memory. It can reuse an earlier translation of identical text. Sharing memory between accounts is off by default. The owner approved that on 2026-10-28.
4. Check and edit#
You read and correct the translations in the dashboard. See Edit in the dashboard. The glossary keeps brand names and key terms as you want them. See Glossary.
5. Publish#
Publishing builds a bundle. The bundle holds one small file for each language, plus a manifest that lists them and carries a signature. Files go to your own site and to two CDNs. See Publish changes.
6. The visitor's browser does the rest#
A small script, the loader, runs in the visitor's browser. It fetches the manifest, checks the signature, fetches the language file, checks its checksum and replaces the text on the page. It keeps watching, so text that appears later is translated too.
If a string has no translation, the visitor sees your original text. A missing translation never causes an error.
Why this keeps working#
After step 5 nothing in the visitor's path calls our servers. Read If our servers are down.