Rudoc

What is Rudoc

Rudoc is a small Rust document converter designed for straightforward format changes without the weight of a full document-processing suite. It was built for users who wanted a much smaller standalone binary than Pandoc for everyday conversion tasks.

The tool supports a limited set of formats: txt, md, html, typ, docx, pdf, pptx, xml, and json. Based on the project notes, the most common use case is converting a Markdown file into HTML. Rudoc is not positioned as a Pandoc replacement, and it does not aim to cover advanced formatting or broad template-based publishing workflows.

A few traits define the app clearly:

• it is written in Rust
• it ships as a single binary
• it has no other runtime dependencies
• it is intended for simple conversion commands

Key features

Rudoc centers on fast, local document translation between a small set of file types.

• Single-binary distribution: the project is built to run without extra runtime dependencies.
• Small footprint: the author specifically built it because existing tools felt heavy for the intended use case.
• Format support: it can work with txt, md, html, typ, docx, pdf, pptx, xml, and json.
• Simple command pattern: the expected usage is rudoc input.file output.file.
• Fast basic conversions: the example in the source shows txt→md finishing in 52 ms and md→html in 4 ms.
• PDF behavior: PDF generation can work without Typst, but PDF input conversion needs Typst as a backend.
• Focused scope: the tool is meant for common conversions, not advanced layout preservation.

There are also constraints that matter:

• pptx and other complex formats still have limited compatibility
• advanced formatting is not the goal
• format coverage is intentionally narrower than larger document conversion tools

How to use it

Rudoc follows a very direct command-line workflow. The basic pattern is to pass an input file and an output file, with the target format inferred from the output extension.

1. Install or download the Rust binary for your environment.
2. Open a terminal in the folder that contains the files you want to convert.
3. Run a command in the form rudoc input.file output.file.
4. Check the output file to confirm the conversion result.
5. If you need PDF input conversion, make sure Typst is available as the backend.

A sample workflow from the source material looks like this:

• convert OhPDF_ROADMAP.md.txt to r.md
• then convert r.md to r.html

That makes Rudoc useful for chained document conversion tasks, especially when moving between plain text, Markdown, and HTML. It may also handle office-style and structured formats, but the project notes make clear that compatibility is still limited for some of them.

Who it is for

Rudoc is a good fit for people who want a lightweight document conversion utility instead of a broad publishing toolkit.

• developers who need quick local format conversion
• users who mainly convert Markdown, HTML, and text files
• people who prefer a single executable with no extra runtime setup
• command-line users who value small binary size and simple syntax
• builders who only need basic text conversion from docx or pptx

It is less suitable for users who depend on:

• advanced document styling
• template systems
• filter pipelines
• high-fidelity office document reproduction
• full compatibility across many markup ecosystems

If your workflow is mostly about routine file translation, Rudoc fits that narrower job well. If your work depends on preserving complex layouts, embedded objects, or sophisticated formatting rules, a larger document conversion suite is likely a better match.

What to know before you use it

Rudoc is intentionally limited, and those limits are important before you rely on it in production or in polished publishing workflows.

• It is not a full substitute for Pandoc.
• It supports only a small group of formats.
• It does not aim to preserve advanced formatting.
• Some complex inputs, especially pptx, still have limited compatibility.
• PDF input conversion depends on Typst being available as a backend.
• The project notes mention plans for better error messages and improved compatibility, so behavior may change over time.

For that reason, Rudoc is best used when you need a practical document converter for common jobs, not when you need exhaustive edge-case handling. If your deliverable depends on strict fidelity, official exports from the source application or a more feature-rich converter may be the safer choice. Rudoc is strongest as a lightweight Rust document converter for everyday file-to-file transformations, and it is most appealing when simplicity matters more than breadth.