One book is a one-click job. Twenty books is a workflow. When you need to move a whole shelf from one format to another — a Calibre library export, a box of old PDFs, a stack of MOBI files from a retired Kindle — you want batch conversion, not twenty round trips through a single-file form. This guide covers how batch ebook conversion works, where the limits are, and when desktop Calibre still earns its keep.
What Counts as Batch Conversion?
Batch conversion means feeding the converter many files in one pass and getting many outputs back, ideally as a single download. The point is to remove the repetitive click-per-file overhead. Typical triggers:
- Migrating a Calibre library from MOBI to EPUB so it reads on a Kobo
- Turning a folder of scanned PDFs into reflowable EPUB for a phone
- Converting a shelf of EPUB to AZW3 before a move to a modern Kindle
- Freeing a retired Kindle's MOBI books so they open anywhere
Any job with more than a handful of files is a batch job in spirit, even if the tool processes them sequentially behind the scenes.
How Browser Batch Conversion Works
A browser-based batch converter takes your files, processes them (usually two at a time to stay responsive), and packages the results into one ZIP you download at the end. You do not install anything and you do not babysit each file.
On BookConv, the batch converter guide walks through the exact UI: drag in up to 20 files, pick one output format for all of them, and grab a single ZIP when it finishes. That ceiling exists for a reason — see the limits section below.
Practical Limits You Should Know
Batch is convenient, but it is not unlimited:
- File count — keep a batch to a sane size (BookConv caps it at 20 files per run). Beyond that, split into multiple batches.
- Per-file size — very large books (hundreds of images, embedded fonts) take longer and can hit size ceilings; a single heavy PDF can slow the whole batch.
- One format per batch — you pick the target format once for all files. If you need EPUB for some and AZW3 for others, run two batches.
- Same-direction jobs only — a batch converts many files from format A to format B. Mixed source formats are fine; mixed targets are not.
These limits are about keeping the queue fast and the download manageable, not about restricting what you can do.
When Desktop Calibre Is Still the Better Tool
Browser batch conversion wins for occasional, moderate jobs. Desktop Calibre still wins when:
- You convert hundreds of files on a schedule and want a saved library and presets
- You need per-book tweaks — different metadata, cover rules, or output profiles per title
- You are offline and the files never leave your machine
- You want plugin pipelines (DeDRM aside, the legal ones) that a web tool does not run
The honest call: for up to a few dozen books, the browser is faster to start and needs no setup. For a permanent, automated library workflow, Calibre on desktop is the long-term home. Both use the same Calibre engine under the hood, so output quality is consistent.
A Simple Batch Workflow
A reliable pattern for a shelf migration:
- Gather the source files in one folder and confirm they are DRM-free (converters reject DRM files on upload).
- Pick the target format by destination device — EPUB for Kobo/Apple Books, AZW3 for modern Kindles, PDF only when you need a fixed layout.
- Run the batch in the browser converter, or in Calibre if the count is large.
- Spot-check three outputs — open one on the target device before trusting the whole batch.
- Keep the originals until you have confirmed the converted files read correctly.
For the destination-specific format choice, Ebook Formats Explained maps each format to the readers that want it.
Key Takeaways
- Batch conversion removes click-per-file overhead — feed many files, get one ZIP.
- Browser batch wins for occasional jobs up to ~20 files; no install, no setup.
- Desktop Calibre wins for hundreds of files, saved presets, offline work, and plugin pipelines.
- One target format per batch — split mixed destinations into separate runs.
- Always spot-check before trusting the batch, and keep originals until outputs are confirmed.