One vocabulary, every article
Feature and menu names hold their translation across the whole knowledge base and across every future update.
Supported formats:.html.json.csv
Translate your help center without losing the product vocabulary
Export your articles and describe how your product should be talked about. Every language comes back with the same terms, headings and links.
Drop your HTML file here
Up to 10 MB, five files a day. Nothing to install, no account.
Built for support teams covering several languages
The single most expensive support mistake is an article telling someone to click a button that is named differently in their language. Your glossary pins every UI term, so the instructions match the screen.
Formatting and links preserved
Headings, lists, inline links and embedded markup come back in place, so an article does not need reformatting after import.
Only what changed
Re-run an export after editing ten articles and ask for existing translations to be kept. The rest of the knowledge base is left alone.
Whole knowledge bases at once
Hundreds of articles in a single job instead of one ticket per article for an agency.
From article export to localized help center in 3 steps
Hundreds of articles under one glossary, so support answers the same way in every language.
Export your articles
CSV or Excel from Zendesk, Intercom, HelpScout or Freshdesk, JSON from a headless setup, or a Notion export. Article IDs and URLs ride along untouched.
Upload an export →product-catalog.csvwebsite-content.xlsxmobile-app.xliffcourse-subtitles.zip
Fix the product vocabulary
Feature names, UI labels the customer will see on screen, the terms that must match your app exactly. Saved once to your glossary and applied to every article.
Write your instructions →How to translate this file?
Translate into German and Spanish. Keep product names in English, use our glossary, and make the copy sound natural for e-commerce.
Glossary applied
Translation planReadyUpdated
LanguagesEN → DE, ES
Scope742 cells
Volume8,490 words
Existing translationsKeep unchanged
Start translation
Refine your instructions
Import the localized articles
Same structure, same identifiers, same internal links. Ready to publish in each locale of your help center.
Export result →fr-FR
de-DE
es-ES
ja-JP
website-content_localized.xlsx
Help center translation FAQ
Which help desk exports work?
CSV and Excel from Zendesk, Intercom, HelpScout, Freshdesk and Front, JSON from headless or API-based setups, and Notion or Confluence exports. HTML inside article bodies is preserved.
How do I make sure UI names match the app?
Put them in a workspace glossary. Every article then uses the exact label your product shows in that language. That is the difference between an article that helps and one that creates a ticket.
Will links and formatting survive?
Yes. Inline markup, links, headings and lists are treated as structure and returned unchanged, with the words around them translated.
Can I update only the articles I have edited?
Yes. Ask AI Glot to keep existing translations and it fills only what is empty, so your reviewed articles are never rewritten.
Is AI translation good enough for support content?
For coverage, yes, and it is far better than leaving customers with English-only articles. For anything touching billing, legal or safety, have a native speaker review the output before publishing.
How many articles can I translate at once?
A full knowledge base of several hundred articles runs as one job, with progress you can watch.