Yes — heading levels in the DOC convert to the matching number of `#` characters, and bulleted / numbered / nested lists convert to `-` and `1.` markers with correct indentation. The Markdown preserves the document outline so the structure is immediately readable as plain text.
The Markdown uses ATX-style `#` headings by default — the modern, widely-supported convention that works in every Markdown flavor and scales to all six heading levels. Setext (underlined) headings only support two levels, so ATX is the safer, more portable choice.
Yes — uploaded DOC files are processed in isolated workers and deleted within minutes. We never read, store, or share the contents. See /privacy/.
为什么我的Markdown有误差 HTML 标记混在一起?
+
Markdown can't express every feature a rich document has (colored text, complex tables, text boxes), so the converter falls back to inline HTML for those fragments rather than dropping them — Markdown allows embedded HTML. If you want pure Markdown, simplify the formatting in the DOC first, or enable the "strip HTML fallback" option.
DOC 到Markdown 处理代码块吗?
+
Yes — monospaced / pre-formatted text in the DOC becomes a fenced ```code block``` in the Markdown, preserving whitespace and, where detectable, the language hint for syntax highlighting. This is essential when converting technical documents and tutorials to Markdown.
