Use case 14 · Localisation
Translate a whole project, article by article, structure intact.
Machine translation is easy. Keeping the heading levels, bullet lists, tables and links in place while you do it is not. output.md translates Markdown as Markdown, so the translated file has the same shape as the original — ready to publish, not ready to reformat.
Free account, 10 markdown + 10 AI credits included. No credit card needed.
Today
- Pasting paragraphs into a translator and rebuilding the formatting by hand.
- Tables and lists that fall apart in translation.
- No clean way to keep source and translation side by side.
With output.md
- A translated .md with identical structure to the source.
- Headings, links and tables exactly where they were.
- One project per language, exportable as a ZIP.
Step by step
How it works, in 5 steps.
-
01
Import the source content
You do
Sitemap mode for a site, bulk mode for a list of pages, or upload the Word and PDF files.
You get
Clean source Markdown — the best possible input for a translation.
-
02
Fix the source first
You do
Correct typos and awkward sentences in the editor before translating.
You get
Every language downstream inherits the fix.
TipTranslating a clean source once beats correcting five translations later.
-
03
Translate
You do
Run the Translation transform on each article and pick the target language.
You get
A translated version stored next to the original, structure intact.
-
04
Review side by side
You do
Open source and translation together; adjust terminology and tone in the editor.
You get
A version a native speaker signed off on, not a raw machine draft.
-
05
Export by language
You do
Download the project ZIP.
You get
A folder of translated .md files ready for your CMS, static site or docs tool.
Why it works
What you get out of it.
Structure survives
Headings stay headings, tables stay tables, links stay links. Formatting is not the translator’s problem any more.
Source and target together
Each translation lives with its original, so review and updates are straightforward.
Scales with the site
Five pages or five hundred: the workflow is the same, the queue does the counting.
What it costs
1 markdown credit per source article, 1 AI credit per translation.
Forty pages into one new language = 40 markdown + 40 AI credits — the Workspace pack with credits left for edits.
Packs are one-time top-ups — no subscription. See all packs.
Questions
Before you start.
Which languages are supported?
Any language the AI model handles well, which covers all major European and Asian languages. You choose the target language per transform.
Can I add a glossary or tone instructions?
Fix terminology in the source and review the translation in the editor. For brand-specific vocabulary, a quick find-and-replace after translation is the most reliable approach.
Does it translate the text inside tables and links?
Table cells and link labels are translated; link URLs are left untouched so nothing breaks.
Try it on your own material.
Paste a link or upload a file, and see the Markdown before you decide anything else.