Convert DOC to RTF: Move a Legacy Word Binary File Into Rich Text
Learn how a Word 97-2003 record file becomes editable RTF, what simple formatting carries over, and where old layouts and objects need checking.
- Add a file Choose or drop it here
- Pick the format Change it whenever needed
- Download the result After conversion completes
DOC begins as a Word binary record file; RTF becomes an editable text interchange file
A legacy .doc is the Word binary format used by Word 97, 2000, 2002, and 2003. Microsoft’s [MS-DOC] specification describes it as records and structures for text, tables, fields, pictures, embedded XML, and other document content. It begins with a File Information Block, the master record through which an application finds other document data. An .rtf file has a different design. Rich Text Format 1.9.1 uses readable text plus control words and groups to describe character formatting, paragraph formatting, fonts, pictures, and related content. DOC-to-RTF is a translation between two editable document models, not a filename change.
RTF is useful when a legacy document’s text and basic formatting must be edited in a broad range of word processors, or when an older workflow explicitly requests RTF. Microsoft describes RTF as an export format that compatible programs can read and interpret. The main advantage is not that it magically modernizes every old document feature; it is that a simpler, text-centered representation can be easier to exchange. Preserve the original DOC until the output has been checked. The old binary document is the visual and structural reference if the RTF exposes a missing object, altered list, unexpected line wrap, or changed page break.
The conversion follows binary links, then writes RTF text, groups, and control words
A converter must interpret DOC records through the references rooted in the File Information Block. It has to locate text, character properties, paragraph properties, tables, pictures, fields, and other objects, then decide which can be represented by RTF controls. Basic paragraphs, bold or italic text, ordinary lists, and many simple tables have direct rich-text counterparts. The hard cases are not visible merely from an extension: an old document may use floating objects, field codes, unusual numbering, embedded objects, or legacy fonts. These can be flattened, simplified, or treated differently by the receiving RTF editor.
RTF does not retain the DOC record graph. It writes a new text document with formatting instructions. That makes it unsuitable as a byte-for-byte preservation copy, but useful as an editable recovery or interchange copy. A picture might be embedded as an image representation, while an OLE object may lose its original editing behavior. A field can appear as its displayed result rather than remain a live old-Word function. Test whether each visible feature must remain editable, or whether a fixed visual fallback is sufficient. This decision saves time: it is better to deliberately replace a complex legacy object with a checked image than to assume it will remain a fully functioning object after conversion.
What RTF makes easier and what a legacy document can lose on the way
- Editable basic prose: ordinary DOC paragraphs and character styling can become text that many word processors can revise.
- Simpler interchange: RTF carries document content and formatting without preserving the DOC binary record layout.
- Useful recovery copy: it can provide editable text when a legacy DOC needs migration into a newer workflow.
- Changed pages: the target editor recalculates wrapping, tables, and page breaks using its own fonts and layout behavior.
- Reduced object behavior: complex fields, OLE objects, floating drawings, and old controls may flatten or lose editability.
- Possible character surprises: legacy fonts and encoding choices can cause symbols or multilingual text to display differently.
The last item deserves careful review. Microsoft notes that text encoding standards tell Word and other programs how to represent text so it is readable, and its legacy Word support history includes old Unicode concerns. A document that looked correct only because a particular symbol font was installed can display boxes or different glyphs elsewhere. Open the RTF in the actual receiving program and inspect names, legal symbols, non-Latin script, punctuation, and every special character. A plain-looking word may hide a wrong character that becomes costly only after the legacy file has been retired.
Word desktop, browser editing, and other word processors have different roles
Current desktop Word can open legacy DOC files in Compatibility Mode and can save a document as RTF. Microsoft says Word for the web displays Word 97-2003 DOC files but creates a new DOCX copy for browser editing; it cannot save the original DOC format in the browser. Its browser support guidance also lists RTF among formats Word for the web cannot open in that environment. These details matter for a migration: use a desktop word processor to create and test the RTF, not a browser-only workflow that may view the DOC yet fail to handle the target.
Other word processors can often open RTF, but opening success is not evidence of page-identical results. Fonts, table measurement, image anchoring, and field handling can differ. Compare the DOC and RTF in a desktop editor at the same zoom, then test the output in the receiving application. Check the first and last pages, all tables, every header and footer, and pages using a special font. If exact page appearance is required, keep a PDF reference as well as the editable RTF. The PDF settles visual questions while the RTF remains the editable exchange copy.
Microsoft’s saving-format guidance identifies the legacy DOC target as compatible with Word 97-2003 on Windows and Word 98-2004 on Mac, while describing RTF as a format other applications can read and interpret. That does not mean every old Mac or Windows Word release renders every rich-text feature the same way. Test the converted RTF in the actual required program, particularly when the handoff includes images, footnotes, tables, or non-English text.
Failure causes that matter in real legacy-document migration
If an RTF opens with unfamiliar symbols or boxes, investigate font availability and character encoding before changing extensions. Replace a document-only symbol font with Unicode text or a shared font in the source where possible, then export again. If a table shifts, use real table widths and cell properties rather than spaces; a different editor can calculate a legacy layout differently. If a picture or embedded object vanishes, determine whether it was a simple image, a floating drawing, or an object requiring an old application. Reinsert a critical picture or create a static substitute deliberately after checking the original DOC.
If the old DOC will not open, make a copy before repair. Microsoft’s guidance for damaged Word documents separates recovering content from preserving formatting. Recovery can provide readable text but may lose original page layout, objects, and styles. If only content can be recovered, create a clean RTF with basic paragraphs and rebuild required structure rather than claiming a damaged DOC has been preserved. An RTF conversion is not a security bypass either: verify an unknown document through normal safety procedures before opening it in an editor or using repair tools.
One less obvious failure is an old file with a .doc label that is not really a Word binary document. Migration reports describe folders containing files with DOC extensions that were actually text or RTF. Use Word’s file-format confirmation or a trusted detector before mass conversion. A converter cannot faithfully translate the binary DOC structure if the source never had one.
DOC-to-RTF checks that locate the expensive problems first
| Legacy DOC item | RTF consequence | Check |
|---|---|---|
| File Information Block links | Binary data must be interpreted before conversion | Use a real DOC reader, never a filename rename. |
| Plain paragraphs and emphasis | Usually editable rich text | Edit a sentence and preserve basic styling. |
| Symbol or legacy font | May show wrong characters elsewhere | Inspect special characters on the delivery system. |
| Complex field or OLE object | May flatten or lose behavior | Test object editing, not only its appearance. |
| Visual table layout | May reflow in target editor | Check widths, borders, and page breaks. |
| Damaged binary source | Text recovery can lose formatting | Recover on a copy and rebuild a clean RTF. |
Questions before converting an old Word file to RTF
Can a DOC file simply be renamed to RTF?
No. DOC is a Word binary record format and RTF uses text control words. A genuine converter must rewrite the content.
Will all DOC objects stay editable?
No. Basic text converts best. Complex fields, embedded objects, and drawing behavior need individual checks or a static fallback.
Why do symbols look wrong after conversion?
A legacy symbol font or encoding may not exist in the receiving editor. Inspect special characters and replace them with shared Unicode text where possible.
Can Word for the web make the RTF?
Use a desktop editor. Word for the web displays DOC but converts browser editing to DOCX and does not support RTF there.
What should be kept after migration?
Keep the original DOC, a verified RTF working copy, and a PDF reference if the old page layout has to be checked later.