RTF to PDF
.rtf rich text to PDF · Chinese fonts embedded so nothing is garbled · A4 automatic pagination
为什么这个工具要上传文件？
本站其它工具都在你的浏览器里本地处理、文件不出本机；但 .rtf 是富文本文档，要把它按原样排成 PDF（加粗斜体、字号颜色、项目符号、自动分页），需要一个真正的排版引擎，并且要把中文字体嵌进 PDF 里，这些在浏览器里做不到同等效果，因此它是本站少数需要上传的工具之一。 上传的文件只用于这一次转换：不写入数据库、不留存在服务器（转换完成立即删除）、不上传到任何第三方、不会被任何人看到。 若文件敏感到「连转换服务都不能经手」，可在本地用 Word / WPS 打开这个 .rtf 后「另存为 PDF」。
把 .rtf 文件拖到这里，或点击选择
支持富文本 .rtf；纯文本 .txt 也可以（按段落排版）；单文件不超过 20MB
提示：常见 RTF 几秒完成，内容多的文档最长约一分半钟。转换期间文件只在内存与一次性临时目录里流转，结束后立即删除。
RTF 转 PDF 的常见用法与效果边界
最常用的三种场景。一是把 .rtf 定稿成「谁打开都一样」的 PDF 发出去（合同附件、说明书、报价单）；二是把老工具（很多写作软件、编辑器、旧版 Word）导出的 .rtf 资料统一归档成 PDF；三是打印或投稿前把 RTF 转成 PDF，避免对方缺字体导致排版错乱。
会保留的格式。文字与基本字符格式会保留：加粗、斜体、下划线、字号、字体颜色、段落对齐、项目符号与编号列表、换行与分页符。中文字体由服务器嵌入 PDF，任何设备打开都不会变方块。
会丢的格式（请先看这条再决定用不用）。嵌入对象（OLE 对象、公式编辑器内容）、某些域代码（自动更新的日期与页码域可能变成静态文本或丢失）、文档里引用的自定义字体（服务器没有该字体时会用相近字体替代，字宽与断行可能与原文档有差异）。图片的表现取决于文档本身：简单的内嵌图片通常能保留，复杂的图文混排或引用外部文件的图片可能丢失或错位。若你要的是「版式与原文档完全一致」，请在 Word / WPS 里打开后直接另存为 PDF。
和别的工具怎么选。纯文本 .txt 用「TXT 转 PDF」；Office 文档（.docx / .doc / .pptx / .xlsx）用对应的「Word/PPT/Excel 转 PDF」；本页专门处理 .rtf。三条路都走同一个转换通道，不会因为选错页而更容易失败。
Privacy note:文件仅用于这一次转换——不写入数据库、不留存服务器（转换完成立即删除）、不上传到任何第三方。单文件上限 20MB，超出会在上传前直接拦下。
FAQ
Our other tools all process locally in your browser and the file never leaves your machine; but .rtf is a rich-text document - typesetting it into PDF as-is (bold and italics, font sizes and colors, bullets, automatic pagination) needs a real layout engine, and Chinese fonts have to be embedded into the PDF; the browser cannot achieve the same result, so this tool is one of the upload exceptions. The uploaded file is used only for this one conversion: not written to any database, not retained on the server (deleted the moment conversion finishes), never sent to any third party, never seen by anyone.
What survives is text and basic character formatting: bold, italics, underline, font size, font color, paragraph alignment, bullet and numbered lists, line breaks and page breaks; Chinese fonts are embedded by the server, so no tofu boxes. What is lost is everything beyond RTF's own reach: embedded objects (OLE, equation-editor content), some field codes (auto-updating date and page fields may become static text or vanish), and custom fonts referenced by the document (if the server lacks one, a similar font substitutes and character widths and line breaks may differ from the original). Images depend on the document itself: simple inline images usually survive; complex text-image layouts or images referencing external files may vanish or shift. For pixel-perfect layout, save as PDF directly in Word / WPS.
No tofu boxes. The server has Noto CJK fonts installed and embeds them into the PDF during conversion, so the result opens on any device regardless of whether the reader has Chinese fonts. In the RTF specification non-ASCII characters are normally written as \uXXXX escapes (pure ASCII at the byte level), so standard RTF is immune to file encoding; for text-like input the server also runs one encoding normalization: read as UTF-8 if valid, otherwise converted from GB18030 (the common Chinese encoding of older Windows tools). One honest caveat: if a file was hand-corrupted (escape digits with the wrong width, or a code page declared while the bytes were replaced with another encoding), individual characters may differ from the original document - that is a problem in the source file itself, and re-converting will not change it.
20MB per file - above that the page blocks it before upload (no request is sent). Conversion usually takes a few seconds; a content-heavy document may run to about ninety seconds. When the server is busy you get a 'too many requests' message - wait a moment and retry. Failures are explained in plain words on the page (content does not match the extension, corrupt file, conversion timeout, service temporarily unavailable); your original file is never modified, and retrying is just clicking Start again. If a huge embedded image pushed the RTF over the limit, compress the images or split the document in Word / WPS first, then convert.