RTF stores formatted text and document controls in a portable text-based syntax.
Markdown stores lightweight text markup for headings, lists, links, and code.
Pandoc preserves supported document structure but does not reproduce every application-specific layout feature.
Macros, scripts, tracked changes, and external resources are not executed during conversion.
RTF stores formatted text for word processors, while Markdown uses plain-text markers for headings, lists, emphasis, links, and other document structure. This converter sends the RTF file to the private document worker, where Pandoc translates supported structure into an editable Markdown file.
The formats do not represent every feature in the same way. Fonts, page geometry, headers, footers, text boxes, and complex layouts may be simplified or omitted. The conversion preserves representable content and structure, not the exact visual appearance of the source document.
Open the downloaded Markdown in the editor or publishing system where it will be used. Check heading levels, nested lists, tables, links, images, line breaks, and escaped characters. A valid Markdown file can still need editorial cleanup when the RTF relied on visual spacing instead of document structure.
Keep the original RTF until the converted text has been reviewed. The worker validates the input and generated output, but it cannot decide whether a simplified table, missing layout detail, or changed line break matches the intended reading order.
This conversion uses Pandoc's deterministic format reader and writer. It does not expose layout controls that the selected pair cannot honor.
One document is processed per request. The input limit is 50 MB.
The web application validates the file before forwarding it to a private worker. The worker validates the signature again, processes the file inside a unique temporary directory, validates the output, and removes the job directory in a guaranteed cleanup path. Files are not written to the database or retained for analytics.
When you import from a URL, the application fetches only a validated public HTTP or HTTPS address, checks the downloaded file in memory, and applies the same worker cleanup rules. The URL, filename, and file contents are not sent to analytics.