RTF sang PDF

The converter is LibreOffice compiled to WebAssembly, and the engine is about 77 MB compressed. It's downloaded and started the first time you convert in a session; after that, each file takes only a few seconds.

Font styles such as bold and italic, paragraph alignment, lists, tables, and embedded images come through as they would if you exported the file from LibreOffice Writer. Embedded OLE objects, such as inserted spreadsheets, may not render fully.

Only fonts bundled with the engine are available, which covers common Latin, Arabic, and Hebrew faces. Fonts that aren't bundled are replaced with the closest substitute, so line breaks and spacing can shift slightly.

Yes. One file downloads as a PDF with the same base name; several files download together as rtf-converted.zip with one PDF per file, and duplicate names are numbered automatically.

Both use the same LibreOffice engine and produce the same result for RTF. Word to PDF also accepts .doc, .docx, and .odt, so use it when you have a mix of formats in one batch.

RTF written by any standard word processor converts, including files from WordPad, TextEdit, and exports from records systems. Proprietary extensions inside such files may be dropped, but the text and standard formatting still convert.

Those fonts aren't bundled with the browser engine, so text in these scripts may render with a fallback font or as boxes. Latin, Arabic, and Hebrew scripts are covered.

No. The whole LibreOffice engine runs inside your browser tab as WebAssembly. Your file is converted locally, and the only thing downloaded is the engine itself.