Translate MDX files, with imports, components and expressions left exactly as written
Upload .mdx files or a zipped content folder and get them back translated, with every import and export line, every component line and every {expression} exactly as you wrote it. Headings, paragraphs, lists, tables and front matter text fields are translated. The first part is free without an account; up to 1,000,000 characters of text is $5.
- import and export statements copied as written
- Lines that are only components, such as <Callout type="info">, kept
- {expressions} inside a paragraph protected and put back
- Front matter title and description translated; other keys kept
- Works for Next.js, Astro, Nextra, Gatsby and Docusaurus content folders
MDX is code with prose inside
An MDX file compiles. One translated variable name, a quote added to a prop or a changed import path stops the build, and a chat assistant rewriting the whole file has many chances to make one of those changes. This tool does not let the model touch the code at all.
Import and export lines and lines made only of component tags are skipped. Inside a paragraph, inline code, links, image paths and {expressions} are swapped for markers before translation and restored afterwards; the model must return every marker. Components that wrap prose, such as a callout around a paragraph, have their tags kept and the paragraph inside translated.
What to check
- Props that hold visible text, such as title="Install" on a component, stay in the source language; translate those by hand
- Strings inside JavaScript expressions are not translated
- Run the build once after copying the files
- Look at the warnings file for any paragraph kept in the original
Folder in, folder out
Upload a .zip of your content folder and you get a .zip with the same paths under a folder named for the language, for example content-de/. Images, JSON and other files in the .zip are copied unchanged, so the folder is complete. Single files come back renamed, such as index.de.mdx.
How the tool works, what it costs and how your files are handled is on the Translate Markdown Docs page; prices for every tool are on the pricing page.
Last updated
Questions and answers
Are component props translated?
No. Props are part of the code and stay as written; translate visible prop text by hand if your components use it.
What about .md files in the same folder?
They are translated too. .md, .mdx and .markdown files are all handled in one job.
How big can the job be?
Up to 1,000,000 characters of text for $5, in a .zip or up to 50 files.
Is it free to try?
The first part is translated and shown free. A job of up to 40 paragraphs is free in full.