Yes — heading levels in the PDF 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.
我的 PDF 表格在 Markdown 中的代表性如何?
+
表格转换为 GitHub-Flavered Markdown 管道表 ( col col col 和 `-'分隔符行), 使 GitHub、 GitLab 和大多数静态站点生成器正确。 超过 Markdown 简单网格的非常宽的或合并的单元格表格会简化, 因为 Markdown 没有合并的单元格语法 。
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.
PDF 到Markdown 是否保存链接和脚注?
+
超链接变成内线 `[text](url)'链接,当 PDF 标记真实脚注时,它们转换为`[%1] 的参考式脚注,使支持扩展的平台上正确。
Yes — uploaded PDF 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 PDF first, or enable the "strip HTML fallback" option.
PDF 到Markdown 处理代码块吗?
+
Yes — monospaced / pre-formatted text in the PDF 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.