An HTML file is mostly not words. Tags, classes, scripts and styles surround a few sentences, and a translation has to change only those sentences.
This guide is for the files you can hand over: a landing page, an email template, a help centre export, the built pages of a static site.
Is this the right tool?
AI Glot translates files and returns files. It does not sit in front of your website, and it does not publish. If you want a live site translated automatically, a website translation tool fits better, and our comparison of website translation software covers them.
If you have the HTML in a file and want a translated file back, keep reading.
Which option should you use?
| Good for | Where it stops | |
|---|---|---|
| AI Glot | Many pages, several languages, a glossary that must hold, pages you update | Not needed for a single paragraph |
| DeepL | One page. It takes HTML files up to 5 MB | One file at a time, no plan to read first, and a glossary that swaps terms without understanding why they are fixed |
| ChatGPT, Claude or another assistant | A short snippet | The markup counts toward what you paste, so a page uses more of your usage limit than its words alone. Each answer needs a check for changed tags or attributes |
| A website translation tool | A live site that translates itself | It lives in front of your site, so it suits a different job than a file you control |
| A freelancer or an agency | The landing page that sells | Slow, priced per word, and you still prepare the files |
Have a person read the page that sells. Run the help articles and email templates through an engine.
Why AI Glot fits an HTML file
- It reads what a visitor reads. Paragraphs, headings, lists, table cells, alt text, titles and the meta description.
- The markup comes back as written. Only the text between the tags is rewritten.
- A link or a bold word stays attached to the right words in the target language.
- One glossary for every page, including the ones you translate next month.
- A plan before any spend.
The path of one file
- 1UploadA .html file, or a ZIPUp to 8 MB each
- 2Say what you needOne plain sentenceFree
- 3Read the planText found, languages, costFree
- 4ApproveThe only step that spendsSpends credits
- 5DownloadTranslated HTMLSame markup
What is read, and what is not
- Paragraphs, headings, lists and table cells
- Page title and meta description
- Alt text, placeholders and aria labels
- Text inside links and bold words
- Tags, classes and attributes
- Scripts, styles and code blocks
- Anything marked translate="no" or notranslate
- Links, hreflang and canonical URLs
Three things to check
Text inside scripts. A message that lives in a JavaScript string, or structured data in a script tag, is never read. Look for visible text that your page builds in the browser.
Your language links. The lang attribute is updated for you. Links, hreflang and canonical URLs are not, so point them at the translated page.
Length. Translations are often longer than English, so look at buttons and headlines in a browser.
How to do it, step by step
1. Try a file for free. The HTML translator needs no account and takes files up to 2 MB and 5,000 words.
2. Upload the file or a ZIP of the pages in the app.
3. Say what a visitor should read, in one sentence.
Translate this page into Spanish.
Translate the visible text, the alt text and the meta description.The sentence decides what is translated across the whole file. A rule about wording, such as “keep the product name in English” or “use the informal register”, goes into the second box at approval, because it is applied to each piece of text as it is written.
4. Add a glossary for product names, slogans and the words you always say one way. How to build one.
5. Read the plan and choose a quality level.
Lite gives about three times more words per credit and is faster: right for a help centre or an internal page. Standard is for the page that sells. One credit is one word in Standard.
6. Approve and download.
One page, several languages
The file names are an example. An HTML file declares one language, so each language is its own file.
Three ways to run it
In the app suits a landing page or an email template.
With your AI agent: connect AI Glot as an MCP server. The agent can upload the pages, write the plan, update your glossary and download the result.
With the API or the command line: for a help centre that exports on a schedule, or a build step that translates new pages. See the API documentation.
Check the result
Open the translated page in a browser and scroll it once. Check a button, a table and the page title in the tab. Then check the lang attribute and your hreflang tags. Keep the original until someone who reads the language has looked at the page.
Pricing lists what a larger volume costs, and a free account comes with credits to run a real file.
The limits quoted here are the ones in force when this was written: 8 MB per HTML file, 200 files and 20 MB per ZIP, and 2 MB and 5,000 words in the free tool. DeepL’s limit comes from its own documentation. File names in the diagrams are examples. Your plan shows the real figures for your own files, and it is free to read.