Markdown Translator: Translate .md and README Files Without Breaking the Format

The only Markdown translator that preserves your headings, code blocks, tables, and lists — exactly as they are — across 10+ languages.

Preserves # headings Keeps ``` code blocks Retains tables 10+ languages 100% free
Load README sampleLoad docs sampleLoad table sample
Source Markdown
1 lines
0 characters0 words
Translated Output
1 lines

Paste Markdown on the left and click Translate →

0 characters0 words

How to translate a Markdown file

Three steps, no signup.

1

Paste your Markdown

Paste the contents of your .md or README.md file into the left pane, or load one of the samples.
2

Choose the languages

Pick the source and the target language: English, Spanish, French, German, Japanese, Chinese, Portuguese, Arabic, Russian or Hindi.
3

Translate and copy

Press Translate. Headings, code blocks, tables and links keep their syntax, only the text is translated. Copy the result or download it as a .md file.

Example: a README from English to Spanish

The structure stays the same, only the readable text changes. The wording of a real translation may differ.

Source Markdown (English)
# My Awesome Project

Install the tool and run it:

```bash
npm install -g mytool
```

See the [docs](https://example.com).
Translated Markdown (Spanish)
# Mi increíble proyecto

Instala la herramienta y ejecútala:

```bash
npm install -g mytool
```

Consulta la [documentación](https://example.com).

Limits

  • The translation is made by an AI model. Check technical terms and product names before you publish the result.
  • Code blocks and link addresses are never translated, only the readable text is.
  • You paste text, one document at a time. A very long document is easier to translate section by section.

Why use a structure-preserving Markdown translator?

Most translation tools destroy Markdown syntax. This one doesn't — it parses the document structure first, translates only human-readable text, then reconstructs the file.

#

Headings stay headings.

Every #, ##, and ### is preserved exactly — only the text inside is translated, never the syntax.

{ }

Code blocks untouched.

Content inside ``` fences is never passed to the translation engine — your code stays exactly as written.

|

Tables remain intact.

Table separators, alignment markers, and column structure are fully preserved across all languages.

→

Links and references preserved.

Hyperlink syntax [text](url) is parsed carefully — the URL is never translated, only the display text.

Translate documentation, READMEs & technical docs

From a single README to a full documentation site — pick the workflow that fits how you publish.

README.md files

Translate open-source README files to reach a global audience of developers without breaking any Markdown formatting.

Documentation sites

Localize entire documentation sites written in Markdown or MDX without reformatting every file manually after translation.

Blog posts & articles

Translate blog posts written in Markdown for Jekyll, Hugo, Gatsby, Astro, or any static site generator that uses .md files.

Multilingual content pipelines

Add a translation step to content pipelines that doesn't require post-processing, reformatting, or manual cleanup of broken Markdown.

Frequently Asked Questions

Yes — that's exactly what Markdown Translator is built for. We parse .md files line-by-line and translate only the text content while preserving all structural syntax: headings, code fences, tables, blockquotes, and lists. The output is valid Markdown in the target language.

We currently support English, Spanish, French, German, Japanese, Chinese, Portuguese, Arabic, Russian, and Hindi. More languages are being added regularly. If you need a specific language, please reach out.

No. Content inside triple-backtick code fences (```) is never sent to the translation engine. Your code, commands, and variable names stay exactly as they are.

Yes, completely free with no account or signup required. Simply paste your Markdown, choose your languages, and click Translate.

Absolutely. README.md files are one of the most common use cases. Paste your README, choose the target language, and get a translated version that renders correctly on GitHub, GitLab, or any Markdown renderer.

Paste the README.md, set From to Japanese and To to English, and press Translate. Any pair of the supported languages works the same way, and the result renders correctly on GitHub.

The translation is made by an AI model, so check technical terms before you publish. Code blocks and link addresses are never translated. A very long document is easier to translate section by section.

markdown translatortranslate .md filemarkdown localizationtranslate README.mdpreserve markdown formattingtechnical documentation translationMDX translatortranslate Hugo sitetranslate Gatsby markdowntranslate Astro contentmultilingual markdowntranslate Jekyll postsopen source README translationi18n markdown