There was a time when moving a formatted document between computers was an uncertain business. A file created by one word processor might be meaningless to another, even when both programs ran on the same machine. Rich Text Format was Microsoft’s answer to part of that problem.
Introduced in the 1980s, RTF was intended as an interchange format. It could describe ordinary document features—fonts, bold and italic text, paragraph alignment, margins, and later much more—without depending entirely on the private working format of one program. Microsoft published specifications, and developers on several operating systems added importers and exporters. For many users, saving a copy as .rtf became a practical way to send a styled document to someone using different software.
What is inside an RTF file?
RTF represents a document as text mixed with control words. Braces create groups, backslashes introduce instructions, and tables near the beginning can define fonts or colors used later. Open a small RTF file in a plain-text editor and parts of the prose may be recognizable among the markup. A large file, especially one containing images, quickly becomes less approachable.
This structure gave applications room to ignore instructions they did not support and continue reading what they understood. That was valuable, but it did not guarantee an identical page everywhere. A missing font might be substituted. One application might support a particular table feature while another did not. Even a successful exchange could alter line wrapping or pagination.
The middle ground
RTF occupies a useful position between plain text and a word processor’s full native format. Unlike TXT, it can preserve common styling. Unlike many older binary formats, it can be examined and generated as a tagged character stream. For years it was a sensible lowest common denominator for resumés, school work, correspondence, and documents that needed modest formatting rather than exact reproduction.
Its importance has diminished. Modern office formats are widely supported, PDF is used when final appearance matters, and collaborative editors often avoid file exchange until export. RTF nevertheless remains in archives, email attachments, and the save dialogs of current applications. Old formats rarely vanish at the moment a newer one arrives.
Choosing between RTF and TXT
The decision should follow the document. Choose rich text when bold type, lists, and paragraph treatment carry meaning and recipients have compatible software. Choose plain text when the content must be transparent to simple tools or processed as data. Merely changing the extension does not perform a conversion; software has to read one structure and deliberately write the other.
TextEdit.cc exports TXT and makes no claim to preserve formatting pasted from a word processor. That limitation is intentional. A narrow, verifiable export is preferable to an RTF conversion that only appears to work until an important document is opened elsewhere.
Format note: Rich Text Format was developed by Microsoft. Product and format names are used here for historical identification.