Markdown docs translator
Translate Markdown and MDX docs, with code and links left alone
Upload .md or .mdx files, or your whole docs folder as a .zip, choose a language, and get the same folder back translated. Code blocks, inline code, link and image addresses, front matter keys, MDX imports and components stay exactly as written; headings, paragraphs, lists, tables, image alt text and front matter titles and descriptions are translated. The first part is free with no sign-up; a whole docs folder, up to 1,000,000 characters, is $5 as one payment. A chatbot can translate a README, but a docs site of fifty files tends to come back with translated code, broken links and changed front matter.
- Up to 40 paragraphs free in full; larger jobs start with a free first part
- Whole job $5: a docs folder (.zip) or up to 50 files, up to 1,000,000 characters
- Code blocks, inline code, URLs, front matter keys and MDX components never translated
- Same folder structure back as a .zip; images and config files copied as they are
- Works with Docusaurus, MkDocs, Hugo, Astro, VitePress, Next.js and GitHub READMEs
- 81 languages, glossary and product names to keep
What you get back
A single file comes back renamed for the language (README.md becomes README.de.md). A folder comes back as a .zip with the same paths under a folder named for the language, for example docs-de/, ready to copy into i18n/de or your site's locale folder. Before you download, every block of text is shown on screen with its Markdown, next to the original, and you can edit it.
- Headings keep their anchors, such as {#install}; lists keep their markers and indentation; tables keep their pipes and alignment rows.
- Links: the link text is translated, the address and title stay; reference definitions such as [docs]: https://… are untouched.
- Front matter: title, description, summary, sidebar_label and similar text fields are translated; slugs, dates, tags, ids and every other key stay as written.
- MDX: import and export lines, JSX component lines and {expressions} are copied as they are.
Translating docs with a chatbot, and with this tool
Chat assistants translate a single README well most of the time. A documentation site is many files, full of syntax that must not change and that nothing checks when an assistant rewrites it.
| Your situation | A chatbot | This tool |
|---|---|---|
| One short README | Usually translates it well | Translates it and keeps the Markdown exact |
| A docs folder of 60 files | One file at a time, by hand; long files get cut short | The whole .zip in one job, same paths back |
| Code blocks and inline code | Sometimes translates comments, variable names or commands | Never sent for translation; copied byte for byte |
| Links and images | Can translate or rewrite paths and anchors | Addresses are hidden from the model and put back unchanged |
| Front matter | May translate keys such as slug or id | Only text fields like title and description are translated |
| MDX components | May rewrite JSX or props | Import, export and component lines are left as written |
How to translate a Markdown docs folder
-
1
Upload files or a .zip and choose a language
Drop .md, .mdx or .markdown files, or zip your docs folder and drop the .zip. Choose the language; list product names and terms to keep.
-
2
Check the first part free
The first blocks of text appear on screen next to the original. Edit any of them. No account is needed.
-
3
Unlock and download
Unlock the whole job for $5 and download the translated folder as a .zip, plus a warnings list if anything needs a look.
Why docs trip up general AI assistants
Markdown mixes prose with things that are not prose: code, commands, paths, anchors, YAML keys and, in MDX, JavaScript. An assistant that rewrites the whole file has to copy all of that perfectly while translating the words around it, file after file, and nothing tells you when a command was translated or a link path was changed.
This tool reads each file line by line, skips code blocks, MDX import lines and component lines entirely, and replaces inline code, link addresses, image paths and {expressions} with short markers before anything goes to the model. Only headings, paragraphs, list items, table cells, alt text and front matter text fields are translated, in blocks with the file name as context, and every marker must come back. The file is rebuilt from the original lines.
What people translate
- Docusaurus, VitePress, MkDocs, Hugo and Astro documentation sites
- GitHub READMEs, CONTRIBUTING guides and wikis exported as Markdown
- Obsidian or Notion notes exported to Markdown
- Blog posts and knowledge bases kept as .md files
- Course material and books written in Markdown
Limits worth knowing
Only text fields in front matter are translated (title, description, summary, excerpt, sidebar_label and similar); multi-line YAML values and lists are left as they are. Raw HTML blocks are translated with their tags kept. Comments inside code are never translated, by design. Files other than Markdown in a .zip are copied unchanged.
One payment covers up to 1,000,000 characters of text, about 300 pages, in a .zip or up to 50 files; Unlimited covers up to 2,000,000 characters. Review the result before publishing, especially product terms; the glossary helps keep them consistent.
By language and situation
Translate a Docusaurus docs folder
Zip your docs folder, upload it, and get back the same files translated, ready to drop into i18n/<locale>/docu...
Read more →Translate a README to Chinese
Upload README.md, or the whole docs folder as a .zip, and get it back in Simplified or Traditional Chinese wit...
Read more →Translate MDX files
Upload .mdx files or a zipped content folder and get them back translated, with every import and export line,...
Read more →What it costs
Small jobs, first part
Free
Up to 40 paragraphs free in full, download included. Larger jobs show their first part free, no account.
Whole job
$5
One payment for a docs folder or up to 50 files, up to 1,000,000 characters. No subscription.
Unlimited
$19 / week
Every tool on the site, with jobs of up to 2,000,000 characters.
Questions and answers
Can ChatGPT translate Markdown files without breaking them?
For one short file it usually can. Across a docs folder it is slow, long files get cut short, and nothing checks that code, links and front matter keys survived. This tool never sends code or addresses for translation and rebuilds every file from your original.
Are code blocks translated?
No. Fenced code blocks, inline code and indented code are copied exactly, including the comments inside them.
Does it work with MDX?
Yes. Import and export lines, lines that are only JSX components and {expressions} are left as they are; the prose between them is translated.
What happens to front matter?
Text fields such as title, description, summary and sidebar_label are translated. Keys, slugs, dates, tags, ids and other values stay as written.
Can I upload a whole folder?
Yes. Zip the folder and upload the .zip. The result comes back as a .zip with the same paths under a folder named for the language; images and other files are copied unchanged.
How much can I translate for $5?
Up to 1,000,000 characters of text, about 300 pages, in one job: a .zip or up to 50 files of up to 100 MB. Code and front matter keys do not count.
Is it free?
The first part of every job is translated free and shown on screen. A job of up to 40 paragraphs is free in full, download included. Larger jobs are $5, paid once.
Are my files private?
Only you can open your job. The text is sent to an AI model provider only to translate it and is not used for training. Jobs uploaded without an account are deleted after 7 days, and you can delete a job at any time.
Updated October 25, 2026 · APPFACT STUDIO LTD