Self-hosting vs. EU-hosted file converters

TL;DR

If you convert files daily as part of a pipeline you control, run it locally. If you convert files occasionally and want it to "just work" without installing software, use an EU-hosted converter.

The honest answer is "use both, for different jobs."

Why self-hosting is usually correct for power users

The conversion tools that most online converters use under the hood are already free and open-source:

• LibreOffice headless — handles Office documents, PDF, ODF
• pandoc — handles Markdown, HTML, LaTeX, ePub, DocBook
• ffmpeg — every audio and video conversion ever
• ImageMagick — every image format
• Calibre — eBook formats
• 7-zip / GNU tar — archive formats

The online converters wrap these with a UI, file management, a download URL, and a billing layer. For someone who's comfortable on the command line, removing the wrapper means:

• No upload — files never leave your machine
• No retention concerns — you control storage
• No daily caps — limited only by your CPU
• No price — these tools are free and have been free for 20+ years

If your conversion is part of a recurring workflow (CI pipeline, batch script, automated data ingestion), always self-host.

Where online converters earn their place

Self-hosting falls apart in three scenarios:

1. You're not on your usual machine

You're on a friend's laptop, a public computer, a shared office machine, or a phone. Installing tools isn't an option. An online converter is the right call — the question is which one.

2. The conversion needs a heavy or proprietary engine

Some conversions are genuinely hard to self-host:

• PDF to Word with formatting preserved — needs a real word processor engine
• HEIC to JPG — needs Apple's image SDK or a compatible open-source decoder, which is fiddly to install
• Some CAD format conversions — need vendor SDKs

For these, an online converter with the right engines pre-installed is faster than DIY.

3. You need an HTTP API as glue

If you're building software that occasionally needs to convert a user-uploaded file, don't ship LibreOffice with your app. The dependency surface is enormous, the licensing is a separate consideration, and your users probably don't want to host conversion infrastructure inside your product.

A simple HTTP API (one POST, one signed URL back) is the right shape here.

The middle ground

You can also self-host on your own server — install LibreOffice + pandoc + ffmpeg on a small VM, expose a minimal API. This is what most online converters actually are.

The trade-off:

• Pro: full control, full privacy, no per-conversion cost
• Con: you're now operating a conversion service. Scaling, security patching, format coverage, dependency upgrades, queue management. Real work.

A €20/month VM with the right tools can handle thousands of conversions a day, so for volume use cases this is cost-effective. But "the right tools" is a non-trivial setup.

Where bulkconvert fits

We don't try to replace local tooling for power users. If you have LibreOffice installed and you're converting your own DOCX to PDF, just run it locally — it's faster and more private.

bulkconvert is the right tool when:

• You don't want to install software to do a one-off conversion
• You're sharing a converter link with a non-technical colleague
• You're embedding conversion in a product and don't want to operate the infrastructure
• You want the conversion to be EU-hosted by a service that explicitly says it doesn't read file contents

For everything else, install pandoc.