Official sources reviewed
| Primary source | What it establishes | Review date |
|---|---|---|
| LibreOffice conversion documentation | Published command-line conversion filter behavior. | 2026-07-22 |
What this decision is actually about
This page is about operational cost more than feature checklists. Teams outgrow LibreOffice headless when concurrency, font drift, or process instability starts leaking into the product.
Evaluation prompts—not a feature scorecard
| Alternative boundary | Confirm the supported input, deployment, and output behavior in the official source above using your current version. |
| Runstamp boundary | Prove one real artifact locally first; local package behavior does not imply hosted access. |
| Delivery decision | Test the native file, recipient handoff, and release check that matter in your product. |
When Runstamp is the better fit
Choose Runstamp when the surrounding stack is already JavaScript and the operational cost of LibreOffice is becoming part of the product problem.
When LibreOffice is the better fit
If you need broader legacy format coverage (ODT, RTF) or the highest possible fidelity for very complex Word documents, LibreOffice still covers more formats.
Cost of choosing Runstamp
Runstamp focuses on DOCX-to-PDF only, not every office format. Teams with broad legacy conversion needs may still need LibreOffice alongside Runstamp.
Evaluate the file your customer receives.
Bring one real payload, its expected file, and the release check you cannot miss. Pro and Platform are self-serve; contact us when the evaluation requires Enterprise terms or architecture review.