Convert DOC to RTF
A .doc file is an opaque binary from the pre-2007 era, and that opacity is its problem: it can hold macros, it cannot be inspected without Word, and a damaged one gives up nothing. RTF holds the same formatting as readable text. Converting is how a document leaves a format nobody wants to keep depending on.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeDrop your DOC file here, or click to browse
Up to 50 MB. Deleted automatically after 30 minutes.
What it does
- Formatting survives as readable RTF control words
- Macros are not carried across, because RTF has no macro storage
- The result can be inspected, searched and diffed as plain text
How to use DOC to RTF
- 1
Upload the .doc
Any legacy binary Word document. Files produced by very old software convert as well as recent ones.
- 2
Formatting is rewritten as text
Bold, headings, lists, tables and colors are re-emitted as RTF control words. Nothing about the appearance is discarded in the process.
- 3
Inspect the result if you want to
Open the RTF in a text editor. Being able to see what is in a document is the main reason to make this trip.
How it works
The binary document is opened and its content is re-emitted as RTF. Where a .doc stores a formatting run as structured bytes in a compound file, RTF states it as a control word inside plain text: a switch for bold, a token for a font size, a marker for a table row.
The conversion is a re-encoding of the same document model, not a rendering, so the result stays editable and the formatting stays attached to the text it belongs to.
The case for leaving .doc behind
The old binary format is difficult to inspect, difficult to repair, and historically the carrier of choice for macro-borne malware, which is why so many mail systems treat it with suspicion. Anything that reduces how many .doc files an organization depends on is usually worth doing.
RTF is one of two sensible exits. It is text, so it can be searched, diffed in version control and read by scripts. The other exit is .docx, which is smaller and better supported by modern software.
Choosing between RTF and DOCX
Choose DOCX if the documents will keep being edited in a current word processor: it is smaller, more capable and the format everything expects today.
Choose RTF if the documents are going into a system that must read them without a document library, if they will be archived somewhere that prefers text, or if you specifically want the macro storage to disappear along the way.
What to check afterwards
Tables and anything that floated. These are the constructs where a very old document is most likely to have used a Word feature with no exact RTF equivalent, and they are worth looking at once before the original is retired.
A format built to be read by anything
RTF is plain text with markup, which is the whole point of it. Open one in a text
editor and the content is legible between the control words — a property .doc,
as a binary, does not have.
That makes it the interchange format of last resort. Word processors going back
decades read it, as do legal document systems, older content management tools and
a good deal of institutional software that was written before .docx existed.
It costs size — an RTF is typically larger than the .doc it came from, because
nothing is compressed — and complex layout can simplify. Both are acceptable when
the alternative is a file the other end cannot open at all.
Examples
An old contract leaving a binary archive
Bigger and far more durable. The clauses can now be searched, diffed against a later revision, and read by software that has no idea what a .doc is.
A template that carried a macro
RTF has nowhere to store a macro, so it does not survive. That is often the point: the conversion is a way to keep a document and drop the executable content inside it.
Frequently asked questions
Does converting to RTF remove macros?
Yes, as a consequence of the format rather than as a security feature. RTF has no macro storage, so a macro project attached to a .doc has nowhere to go and is not written to the output. This is a genuinely useful property when an old template needs to be kept but its executable content does not, though it should not be treated as sanitization for a file you already suspect.
Why is the RTF bigger than the .doc?
Because RTF spells everything out. A binary format encodes a formatting change in a few bytes; RTF writes a control word for it, in text. Any embedded image is stored as hexadecimal, which roughly doubles its size. A document that was two hundred kilobytes as a .doc becoming three or four hundred as RTF is normal, and the extra bytes buy inspectability.
Will the formatting look the same?
Very close. Character formatting, paragraph styles, lists, tables and colors have direct RTF equivalents and come across faithfully. The differences that do appear are usually in features from later Word versions that RTF never gained, and in complex floating layouts. Open the result once in the application that will be reading it before you rely on it.