RTF to DOC Converter
This turns a Rich Text Format file into a Word 97-2003 .doc binary using LibreOffice on our servers. If you simply need something Word can open, DOCX is the better target; .doc is for systems that check the extension.
Download Started!
How would you rate your experience with MiConvert?
When RTF to DOC makes sense
Both formats are Microsoft's and both are old. RTF is a text-based interchange format readable by almost anything, while .doc is the binary compound-file format Word used from 97 through 2003. Converting between them is a sideways move, not an upgrade, so the honest reason to do it is a receiving system that insists on .doc: an old document management workflow, an e-filing portal that validates extensions, a template or macro that opens files by name, or a machine still running Office 2003.
The conversion happens on our servers. A worker runs LibreOffice 7.4 headless and exports through its "MS Word 97" filter, which writes a real binary .doc stream rather than a renamed text file. LibreOffice reads the RTF control words into its Writer model first, so what reaches the .doc is Writer's interpretation of your document. Text, paragraph and character formatting, fonts, colors, lists and tables normally come across; we have not tested every construct on this route, so check images, headers, footers and footnotes in the output yourself.
Be clear about what a format change cannot do. Converting to .doc does not add tracked changes, comments, macros, mail-merge fields or an automatic table of contents; the document only contains what the RTF already contained. Older RTF constructs without a Writer equivalent are approximated, and fonts are named rather than packaged, so a computer missing a font substitutes one. If no system is forcing your hand, convert the same RTF to DOCX instead: it compresses images, is what Microsoft 365, Google Docs and Pages expect, and avoids the compatibility-mode banner Word shows for a 97-2003 file. Our RTF to DOCX page uses the same LibreOffice engine with the modern OOXML filter.
Converting an RTF file to DOC
- Confirm which .doc the recipient wants. If they just said "Word file", send DOCX. If their software or upload form rejects anything but .doc, continue here.
- Verify the input: the file should begin with {\rtf1 and carry the .rtf extension, which is the only Rich Text extension accepted at upload. Re-saving once from WordPad, Word or LibreOffice repairs most odd RTF output.
- Upload the file on this page. Guests can send 10 files of up to 50 MB per request; a free account raises the per-file ceiling to 100 MB.
- Leave the target set to DOC and run the conversion. Rich Text documents under a megabyte typically take a couple of seconds once the upload has landed.
- Download the .doc and open it in Word or LibreOffice to check pagination, tables and images, since DOC and RTF do not lay out text identically.
- Keep the original RTF. It remains the more portable copy if the .doc ever needs to be re-made.
What you get
- LibreOffice 7.4's MS Word 97 export filter, producing a genuine binary .doc that Word 97 through Microsoft 365 all open.
- Text styling, paragraph layout, lists and tables as interpreted by LibreOffice's RTF reader; images, headers, footers and footnotes are untested on this pair, so verify them in the result.
- One .doc per input file, with no settings to choose; LibreOffice re-flows the document as it writes the Word 97 stream, so pagination can shift.
- Multiple files per request: 10 for guests and free accounts, 25 on Plus, 50 on Pro.
- No software to install and no account needed for guest-sized files; conversion runs server-side over HTTPS.
- Uploads removed the moment the job ends, with the finished .doc available on a random download link for about four hours.
RTF to DOC questions
Should I pick DOC or DOCX?
Choose .doc only when something downstream requires it: Word 97-2003, an old plugin, or a portal that rejects other extensions. Everywhere else choose DOCX, which is ZIP-compressed, far better supported by Google Docs and Pages, and does not open in Word's compatibility mode.
Does converting to DOC give me track changes, comments or macros?
No. Conversion changes the container, not the content. Tracked changes, comments, macros and automatic tables of contents are things you add afterwards in Word; an RTF that never had them produces a .doc that does not either.
Is my formatting preserved exactly?
Text, fonts, sizes, colors, alignment, lists and tables come across. Exact pagination can shift, because LibreOffice re-flows the document when it writes the Word 97 stream, and uncommon RTF control words are approximated. Images, headers, footers and footnotes are not verified on this pair, so open the file and check anything with a strict layout.
Can I convert several RTF files in one go?
Yes, up to 10 files in a single request as a guest or free user, 25 on Plus and 50 on Pro. Each output is downloaded individually; there is no zip-everything button. For bulk archives, soffice --headless --convert-to doc in a loop does the same job locally.
How do I get an RTF into Google Docs instead?
Google Drive imports .rtf directly, so no conversion is needed for that route.
The conversion failed with a message about the document not opening. What now?
LibreOffice could not parse the file. The usual causes are an incomplete upload, a corrupt RTF, or a file with the .rtf extension that is really something else. Re-save it from the original application and retry. Very long or non-Latin file names can also break the output name, so shorten the name first.
Can you convert a password-protected file?
No. RTF has no standard encryption, but if the file is really a protected Word document renamed to .rtf, you will get either a clear "This document is password-protected" message or, for Word 97-2003 encryption, the generic "could not be opened" error. Save an unprotected copy in the original application and upload that.
How long do you keep my documents?
The uploaded RTF is deleted as soon as the conversion job ends. The resulting .doc can be downloaded for roughly four hours from a 64-character random link, after which it is deleted automatically. We do log file names, sizes, formats and outcomes, and signed-in accounts keep a conversion history entry.