Translate Markdown Documentation with Perfect Formatting
Keep your documentation, blog posts, and content perfectly formatted across all languages with Lingo.dev's intelligent Markdown translation system.
Perfect for Content-Rich Projects
Ideal for translating:
- Technical documentation
- Blog articles and tutorials
- README files and project wikis
- Product guides and manuals
- Knowledge bases
TIP
Need to translate JSX-enhanced Markdown? Check our dedicated MDX documentation.
Quick Setup
Configure your project in three simple steps:
- Create an
i18n.json
configuration file - Define your source and target languages
- Point to your Markdown files using the
[locale]
placeholder
{
"version": 1,
"locale": {
"source": "en",
"targets": ["es", "fr", "de"]
},
"buckets": {
"markdown": {
"include": ["docs/[locale]/*.md"]
}
}
}
This configuration:
- Sets English as your source language
- Targets Spanish, French, and German translations
- Organizes files in language-specific folders (e.g.,
docs/en/
,docs/es/
)
Find Supported Languages
Discover all available language options:
# View source language options
npx lingo.dev@latest show locale sources
# View target language options
npx lingo.dev@latest show locale targets
One Command Translation
Translate all your Markdown files with a single command:
npx lingo.dev@latest i18n
This automatically:
- Processes your source Markdown files
- Identifies new or modified content
- Translates only what's changed
- Creates or updates target language files with identical structure
Smart Markdown Handling
Structure Preservation
Lingo.dev maintains all Markdown formatting elements:
- Headings: All heading levels (
#
,##
, etc.) - Formatting: Bold, italic, code blocks, tables
- Lists: Ordered and unordered lists with proper nesting
- Code: Fenced code blocks with language specification
- Blockquotes: Nested quote formatting
Special Elements
YAML Front Matter
---
title: Getting Started
description: Learn how to use our product
---
# Welcome to Our Product
This guide will help you get started...
Front matter is intelligently processed - content is translated while preserving the YAML structure.
Links and Images
[Visit our website](https://example.com)

Links maintain their URLs while only translating the link text. For images, only the alt text is translated.
Why Technical Writers Choose Markdown Translation
- Format Integrity: Your document structure remains perfectly intact
- Context-Aware: AI understands technical terminology in context
- Incremental Updates: Only translates what's changed - ideal for documentation that evolves over time
- Workflow Integration: Fits seamlessly into documentation-as-code practices
- Multi-Format Support: Works alongside other file types in the same project
By integrating Lingo.dev into your documentation workflow, you maintain consistent, high-quality content across all languages with minimal effort - whether you're documenting an open-source project, creating technical guides, or managing a multilingual knowledge base.