RTF to PDF converts Rich Text Format (.rtf) documents into fixed, portable PDF files. The two formats sit on opposite ends of a design decision Microsoft made deliberately when it published the RTF specification back in 1987: RTF describes a document as a stream of plain-text control words rather than a fixed layout. A bold run looks like \b bold text\b0, a font size is written as \fs24 (half-points, so 24 means 12pt), centered alignment is \qc, and each of these sits inside groups delimited by curly braces that scope which formatting applies to which run of text. Nothing in that stream specifies where a page break falls or exactly how wide a line will render — that is left entirely to whichever application opens the file, using whatever fonts happen to be installed on that particular machine. This was the point: RTF was built so a document formatted in one word processor, on one operating system, could travel to a completely different word processor on a different machine and still come out bold where it should be bold, without both ends needing to speak the same proprietary binary format. Open the same .rtf letter in WordPad on one PC and in Word on a Mac and you can get slightly different pagination and even different substituted fonts, because RTF was never meant to guarantee an identical rendering — only a faithful one, wherever it lands.
PDF exists to solve exactly the problem RTF leaves open. Instead of describing content and leaving rendering decisions to whatever opens the file, a PDF freezes exact glyph positions, embeds or references the fonts it needs, and fixes the page dimensions once and for all at the moment of creation. A PDF looks the same on a phone screen, a laptop, and a sheet of paper coming out of a printer in another country next year. Converting an RTF file to PDF is therefore not a reformat so much as a one-way commitment: you are trading RTF's ability to reflow and adapt to whatever opens it for PDF's guarantee that it will never need to adapt again, because the layout is now permanent.
This tool reads the RTF control-word stream directly rather than routing it through a hidden copy of Word. The parser walks through the brace-delimited groups, recognizes formatting control words like \b, \i, \ul, \fs, and \qc, skips non-printing destination groups such as \fonttbl and \colortbl that only define lookup tables rather than visible content, and decodes hex-escaped characters written as \'e9 for accented letters and other characters outside plain ASCII. Bold runs, italic runs, underlines, font sizes, and paragraph alignment are then reconstructed as flowed text and laid out on a fixed PDF canvas using pdf-lib, with word-wrap and page breaks calculated once, at conversion time, based on the page size and font you choose. From that moment on, the pagination is locked — the resulting PDF prints and displays identically no matter what device, operating system, or PDF viewer opens it next.
Because the whole pipeline — reading the RTF bytes, tokenizing the control words, and rendering the PDF — runs inside your browser using pdf-lib, the document itself is never transmitted anywhere. That matters for the kind of content that still shows up in RTF form: legal templates and form letters saved years ago in WordPad, correspondence exported from old case-management or billing systems that only know how to output RTF, and cross-platform documents from an era when RTF was the safest common denominator between Windows and Mac office software.
Once you have the PDF, Merge PDF can combine it with related documents, and Compress PDF keeps it small for email.
