AI Glot websiteOpen AI Glot
File formatsZIP
File formats

Translate ZIP archives

Send a ZIP of up to 200 files of one format, 20 MB in total, and get the whole set back translated with the same folder layout and file names. Example instructions included.

A ZIP archive (.zip, up to 20 MB and 200 files) lets you translate a whole folder in one job. AI Glot unpacks it, translates every file with the same instruction and the same glossary, and rebuilds the archive with the same directories and file names.

What is translated, and what is left alone

TranslatedLeft as it was
Every translatable file inside, with one set of rulesThe folder tree and every file name
Subfolders, with their paths preservedSystem files such as .DS_Store, which are left out

What you can ask

An instruction for an archive is an instruction for the format inside it. The examples are the ones from the format guides.

A season of subtitles

One glossary of names and terms for every episode.

Translate all the subtitle files into French in a natural, spoken tone.

A docs folder

Markdown files with their layout rebuilt.

Translate all the Markdown files into German. Leave code blocks, inline code and URLs alone.

A locale folder

Resource files translated together so the set stays in step.

Translate all the files into Spanish. Keep placeholders such as %s and %d unchanged and keep every key as it is.

An album of lyrics

One glossary for names and refrains.

Translate all the lyric files into Italian. Keep every time tag and keep each line short enough to sing.

Good to know

  • One format per archive. The files must share the same format and structure, for example the same columns or the same keys, because the whole batch is planned as one shape. A mixed archive is refused.
  • Limits. Up to 200 files and 20 MB in total, with no ZIP nested inside. An archive is also judged on how many values its files add up to: a translation well under 20 MB can still be refused if the files hold too many values. Split it into smaller archives if that happens.
  • Languages. Whether the job takes one language or several follows the format inside. Subtitles, Markdown and most localization files take one language per upload.
  • A file that cannot be read fails the job loudly instead of being skipped.
  • What comes back. A ZIP with the same folder structure and file names, each file translated. Nothing is renamed.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search AI Glot Docs documentation and read it in full, instead of answering from memory.

https://ai-glot.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://ai-glot.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.