Features

Multi-Platform Markdown Converter is a free in-browser cross-platform Markdown format-interop tool for technical bloggers, knowledge-management users, self-media operators, and indie developers. Paste a Markdown document (or rich text copied directly from Platform A) written on any source platform, then one-click convert it to the native format / platform-specific Markdown dialect of Platform B. Coverage spans 18+ major Chinese-internet content platforms: WeChat Official Accounts (WOA), Zhihu, Juejin, CSDN, Yuque, Notion, Obsidian, Feishu Docs, GitBook, GitHub README, Hexo, Hugo, Jekyll, Xiaohongshu, Jike, WordPress, Medium, Confluence. Supports bidirectional conversion, batch processing, auto image migration to target-platform image beds, TOC auto-generation, and platform-differentiated compatibility for 60+ syntax elements including internal/external links, footnotes, task lists, math formulas, code-block highlighting, tables, blockquotes, cards, and Callouts. It solves the single biggest cross-platform publishing pain point: 'the same draft posted to 8 sites takes 8 separate formatting passes.'

When You Need This

Common pain points this tool solves

1. A tech-blog operator publishes the same 8000-character Go Generics deep-dive to 7 platforms weekly (WOA, Zhihu, Juejin, CSDN, Yuque, GitHub, Medium). Previously each platform required 20–30 min of manual formatting after pasting (mainly code-block highlighting, image paths, math, TOC, footnotes). Now they paste the source Markdown, pick 'Obsidian' as source, tick 7 targets → one-click batch-export of 7 platform-native-format files. Paste each into the corresponding backend and it's final layout. Total time drops from 3 hours to 3 minutes
2. A knowledge-management user exported 200 Markdown articles from 3 years of personal Yuque knowledge base and wants to fully migrate them into a local Obsidian vault. The blocker: Yuque 'cards / callouts / inline formulas / anchor links / platform-specific attachment syntax' aren't recognized by Obsidian. They run Converter with source=Yuque target=Obsidian, batch-import 200 .md files locally — 98% of syntax elements migrate perfectly (including Yuque cards → Obsidian callout grammar mapping, Yuque inline $…$ → Obsidian native MathJax mapping). Zero articles arrived with mangled structure
3. An indie dev just finished a 40-page open-source project doc locally (Hugo-flavored Markdown + shortcodes) and needs to sync it to GitBook + Feishu Docs for internal team reading. Previously GitBook and Feishu used completely different math renderers, code-block titles, alert-block and hint-block syntax — every sync required changes in 3 places. Running Converter twice as 'Hugo → GitBook' and 'Hugo → Feishu Docs' maps even Hugo-specific {{< hint warning >}} blocks into GitBook's {% hint style='warning' %} on one side and Feishu-native 'Warning' Callout blocks on the other. Saves an hour of manual syntax-fixing per doc sync.

How to Use

Step-by-step instructions

1. Pick one of three modes: ① Single-paste conversion (default, ideal for 1 article → multiple platforms). ② Batch file conversion (upload multiple .md files, for KB migration / batch publishing). ③ Two-way sync mode (source platform edited version A → incrementally sync to target platform without overwriting existing content).
2. Picking the correct SOURCE platform matters enormously. Pick correctly and the converter automatically loads 60+ grammar rules + 'compatibility patches for known traps' for that platform (e.g., WOA table column-width limits, Zhihu rejecting inline HTML, Juejin auto-demoting h1 → h2). Currently 18+ source platforms supported; top 5 most used: Obsidian / Notion / Yuque / GitHub / WeChat Official.
3. TARGET platforms can be multi-selected (batch export). Each target gets its own toggle panel: image handling (keep external links / upload to target OAuth-authorized image bed / base64 inline), math handling ($ delimiter / $$ delimiter / plain-text fallback / image-render), code-block handling (language-tagged / titled / WOA-style line-wrap), TOC (auto-gen / keep original / strip), footnotes (platform-native syntax / end-of-doc bracket citations), alert/callout blocks (platform-native Callout / downgrade to styled blockquote).
4. After conversion each target platform gets its own tab. Left: converted Markdown source (with platform-specific syntax highlighting). Right: real-time preview rendered in target-platform style (e.g., WOA preview matches the WOA backend renderer, Zhihu preview shows Zhihu's native quote + code-block styles). Three buttons at the bottom: 'Copy Markdown', 'Copy Rich Text (paste directly into backend editor)', 'Download .md file'. Batch mode exports a zip archive.

Why Choose Korelyy

What makes us better

1. 18+ platforms × 60+ syntax elements — the differentiated mapping table is the real moat. This is no half-baked 'regex-replace image paths' script. Each platform ships 30–50 independent rules (including pre-degradation for 50 HTML categories WOA rejects, Zhihu anti-spam special-casing for inline HTML, Feishu nested-table width limits, Yuque private-chain image auto-fetch with your login session). All rules were distilled from 2000+ real cross-platform publishing feedbacks; measured conversion success rate is 28 pp higher on average than the open-source Markdown interop scripts you find on GitHub.
2. 100% browser-local + optional OAuth image-bed authorization, zero upload. Batch 200-article KB migrations, company internal confidential tech drafts, private unpublished notes — everything runs in local JS, nothing uploaded to any server. Only when you manually tick 'auto upload to target-platform image bed' does an official platform OAuth window pop up (Aliyun OSS / Tencent COS / GitHub Pages / Qiniu / SM.MS / etc. — 12 mainstream beds + any S3-compatible custom endpoint). Auth tokens live solely in your browser localStorage; our backend never sees them.
3. Two-way intelligent patching = zero information loss. Anyone who's migrated a KB knows the scariest part: 'Source platform has Syntax A, target has no direct equivalent → content silently dropped.' We built lossless degradation mappings for 42 categories of platform-differentiated syntax. Example: Yuque discussion / homework / database-view cards. If the target doesn't support them, they downgrade into a 'blockquote with platform-source attribution + original fields as a Markdown table'. Information integrity is 100% preserved, only presentation degrades — no surprise 30% content vanishings after a KB migration.

Monetize With This Tool

Turn this tool into a side income stream

1. Use this tool to speed up your freelance work and take on more paying clients
2. Create polished content faster for your blog, YouTube channel, or social media and grow your audience
3. Offer this tool's capabilities as a service on Fiverr, Upwork, or to your local business clients

Frequently Asked Questions

1. Is Markdown Converter — 18+ Platforms, Batch in 1 Click free to use?

   Yes. Markdown Converter — 18+ Platforms, Batch in 1 Click is 100% free for core features — no signup, no watermarks, no hidden paywalls on the tools you need day to day.

2. Do I need to sign up to use Markdown Converter — 18+ Platforms, Batch in 1 Click?

   No. Open and use instantly in your browser. Nothing to install, no account required. Your preferences stay on your device.

3. Is my data safe with Markdown Converter — 18+ Platforms, Batch in 1 Click?

   Yes. Markdown Converter — 18+ Platforms, Batch in 1 Click runs locally in your browser whenever technically possible — sensitive inputs are processed on your device, not on our servers. No tracking cookies.

4. Which devices does Markdown Converter — 18+ Platforms, Batch in 1 Click work on?

   Phones, tablets and desktops with any modern browser (Chrome, Safari, Edge, Firefox). Touch-friendly and responsive from 320px to 4K.

5. What is the difference between Markdown on Notion vs Obsidian vs GitHub?

   Notion uses a proprietary Markdown variant with /-commands and inline database properties. Obsidian follows CommonMark closely with wiki-style [[links]]. GitHub uses GitHub Flavored Markdown (GFM) which adds task lists, tables, and strikethrough. Our converter handles all these differences, so you can move content between platforms without broken formatting.

6. Can I convert a full Notion page to GitHub Markdown?

   Yes, paste your Notion-exported or copied Markdown into the converter. It automatically strips Notion-specific syntax like database properties and /-commands, and outputs clean GFM-compatible Markdown ready for GitHub READMEs or issues.

7. Does this tool convert images and links correctly?

   Yes, standard image and link syntax is preserved. Our converter normalizes relative paths where possible and keeps inline image references intact. For platform-specific embed syntax (like Notion embeds), a clean fallback text is generated.