TXT to Word
.txt / .rtf to .docx · Chinese displays properly · the result is ready to edit and format
为什么这个工具要上传文件？
本站其它工具都在你的浏览器里本地处理、文件不出本机；但把纯文本写成一份真正可编辑的 .docx需要文档排版引擎（生成符合 Office 规范的 OOXML 包、按段落写入样式，并带上中文字体信息），浏览器里能做到的程度有限，因此它是本站少数需要上传的工具之一。 上传的文件只用于这一次转换：不写入数据库、不留存在服务器（转换完成立即删除）、不上传到任何第三方、不会被任何人看到。 若文件敏感到「连转换服务都不能经手」，可在本地用 Word / WPS 打开 txt 后「另存为 .docx」完成。
把 .txt / .rtf 文件拖到这里，或点击选择
支持纯文本 .txt 与富文本 .rtf；单文件不超过 20MB
提示：常见文本几秒完成，长文档或 .rtf 最长约一分半钟。转换期间文件只在内存与临时目录里流转，结束后立即删除。
TXT 转 Word 的常见用法与效果边界
最常用的三种场景。一是把纯文本草稿变成能在 Word / WPS 里继续排版的正式文档（加标题样式、插入表格与页眉页脚）；二是把日志、导出数据、聊天记录整理成便于批注与存档的 Word 文件；三是把老系统导出的 .txt / .rtf 资料统一转成 .docx，方便同事继续编辑。
转出来的 Word 长什么样。原文的换行与空行会按段落保留，中文正常显示（服务端带 Noto CJK 字体信息）。但 .txt 本身没有任何版式：字体、字号、缩进、加粗这些信息在纯文本里并不存在，所以转出来的文档用的是 Word 默认正文样式，也不会自动把第一行识别成"标题 1"——需要你自己套用样式。段落之间的空行会保留为空白段落，便于后续统一调整。
.rtf 会保留基本格式。加粗、斜体、下划线、字号、颜色这类字符级格式会带进 .docx；但 RTF 里的页面设置（纸张、页边距）不保证逐项还原。要严格套用固定版式，建议直接在 Word 里打开 .rtf 另存为 .docx。
本页不做的事。不把图片、扫描件、照片里的文字变成 Word——那需要 OCR（文字识别），本页只处理"本来就是文字"的 .txt / .rtf；也不做 Markdown 解析（井号、星号这类标记会按普通字符原样保留）。
Privacy note:文件仅用于这一次转换——不写入数据库、不留存服务器（转换完成立即删除）、不上传到任何第三方。单文件上限 20MB，超出会在上传前直接拦下。
FAQ
Yes, it uploads - but only for this one conversion. Turning plain text into a spec-compliant .docx that Word / WPS can edit normally requires the server-side document engine to build the OOXML structure and write paragraph styles (achieving the same compatibility in the browser is high-risk, especially for Chinese and legacy-encoded files). So these tools go through the server-side document engine (the same channel as our Word / Excel / PPT to PDF). Uploaded files are used only for the conversion: deleted the moment conversion finishes, not written to any database, not retained, not used for anything else, never sent to any third party. Every other tool on the site (images, local PDF processing, text, QR codes and so on) still runs entirely in your browser - those files never leave your machine.
A .txt is plain text: it carries no font, size or indentation information, so the output uses Word's default body style - line breaks and blank lines survive as paragraphs, but there are no heading styles and none of the original indentation or colors (that information never existed). Afterwards you can apply Heading 1 / Body Text and so on in Word / WPS, add headers, footers and tables - that is exactly the workflow this tool is for: get an editable document first, then do the layout. A .rtf is rich text: bold, italics, underline, sizes and colors - character-level formatting - is carried into the .docx.
Both are supported. Input may be .txt (plain text) or .rtf (rich text); output is always .docx. As for encoding, the server auto-detects UTF-8 and GB18030 (the 'ANSI' Chinese saved by old Windows Notepad), so legacy files do not need saving as UTF-8 first. One caveat: rarer encodings (Big5, Shift-JIS) may fail to be detected - run them through our mojibake repair tool to convert to UTF-8 first. Also, this page does not handle text inside images or scans - that would need OCR.
20MB per file; above it the page says so before upload (no request is sent, no data is wasted). Conversion usually takes seconds; a long document can run to about ninety seconds. When the server is busy you get a 'too many requests' message - wait a moment and retry. Common failures and their messages: unsupported format or direction (400), file over 20MB (413), conversion quota used up (429), corrupt file (502), conversion timeout, usually an oversized document (504), service temporarily unavailable (503). A failed conversion never modifies your original file - retrying is just clicking Start again.