calibre Conversion Stuck or Failed: How to Fix It

A calibre conversion that stays at the same percentage, ends with an error, or never produces an output file is usually caused by one of four things: a damaged or unusually complex source book, a problematic conversion option, an operating system restriction, or interference from security software or a plugin. The fastest solution is not to reinstall calibre or rebuild your library. Instead, confirm whether the problem follows one book, one format, or the entire installation, then use the job log to identify the stage that failed.

This guide focuses specifically on conversion jobs. If calibre can convert books but cannot send them to a device, connect to a server, download metadata, or open a library, that is a different troubleshooting path. Work through the tests below in order, stopping as soon as you can repeat a successful conversion.

1. Confirm the Symptom With a Small Safe Test

Before changing settings, determine whether calibre itself is failing or whether the original source file is the problem. A small controlled test can answer that question in a few minutes.

1.1 Check the Jobs Panel and Error Details

Start the failing conversion again and watch the Jobs indicator in the lower-right area of the calibre window. Click it to open the Jobs panel. When a job finishes or fails, double-click the job entry to open its detailed log.

Read the final portion of the log first. The last several lines often identify the input plugin, conversion stage, file operation, or system resource involved. Look for references to permission errors, missing files, invalid markup, image processing, temporary folders, output paths, or a specific plugin.

A job that appears stuck may still be processing a large image, analyzing a complex document, or extracting content from a PDF. Check whether the elapsed time or system activity is changing before canceling it. However, if the log stops at exactly the same point during repeated attempts, treat that point as a useful clue rather than waiting indefinitely.

Success looks like this: the job reaches 100 percent, the output format appears in the book's format list, and the resulting file opens. Once that happens consistently, stop changing settings.

1.2 Convert a Known-Good Small Book

Use a small, unprotected EPUB or another simple document that you are legally permitted to convert. Convert it to EPUB, AZW3, or another supported output format using default options. Avoid using the original failing book for this control test.

• If the test book converts, calibre's basic conversion system is working.
• If the test book also fails, investigate temporary storage, permissions, antivirus software, plugins, and the calibre configuration.
• If only one source format fails, focus on that format's input file and input options.
• If every book fails only when producing one output format, focus on output settings and the output plugin.

Do not change device detection, email delivery, Content server, metadata download, or viewer settings unless the job log specifically points to one of those components. They normally do not control a standard local conversion.

2. Check the Source File and Conversion Options

When one title fails but other books convert normally, the source file is the leading suspect. A file can open in a viewer and still contain malformed markup, missing resources, invalid archive entries, damaged images, or structural errors that interrupt conversion.

2.1 Test Another Source Format

If the book record contains more than one format, open the conversion dialog and check the input format selected in the upper-left corner. Try converting from a different available format. For example, use EPUB instead of PDF when both are present.

You can also obtain a fresh, authorized copy of the source from its original location and add it as a separate test. Do not overwrite the existing file until the replacement converts successfully. calibre does not convert books protected by DRM, and this guide does not recommend removing or bypassing copy protection.

Success looks like this: the alternate or freshly downloaded source converts with the same output settings. At that point, the original source was damaged, incomplete, unsupported, or structurally unsuitable. Keep the working source and stop modifying global calibre settings.

2.2 Check EPUB and AZW3 Structure

For an EPUB or AZW3 file you are allowed to edit, make a backup and open it with calibre's Edit book feature. Run the book-checking tool and review reported errors. Malformed HTML, broken links, missing images, invalid CSS, and incorrect package information can cause an input stage to fail.

Apply automatic corrections cautiously and save a separate copy when possible. A warning does not always explain the conversion failure, so prioritize fatal parsing errors and missing resources that also appear in the conversion log.

After saving, convert the corrected copy with default settings. If it works, open the output and inspect several chapters, images, links, and the table of contents before replacing any original file.

2.3 Treat Complex PDFs as a Special Case

PDF is a fixed-layout page format rather than an ideal reflowable e-book source. Multi-column pages, scanned pages, unusual fonts, vector drawings, mathematical notation, tables, and layered graphics can be slow or impossible to reconstruct accurately. A conversion that spends a long time processing a large PDF is not necessarily frozen.

Try opening the PDF outside calibre and moving through every page. If the viewer reports damage, fails on a page, or displays missing content, obtain a clean source. If an EPUB, DOCX, HTML, or other reflowable edition is legally available, use it instead.

Image-heavy PDFs may consume substantial memory and temporary disk space. Close memory-intensive applications, verify that the system drive has free space, and test a smaller PDF. If small PDFs work but one complex document does not, stop changing calibre-wide preferences. The document's structure or resource requirements are the likely cause.

2.4 Reset Book-Specific Conversion Settings

calibre can retain conversion options for an individual book. A previously selected heuristic, search-and-replace expression, font option, page setup profile, or structure-detection rule may therefore affect later attempts.

Open the conversion dialog and restore the conversion settings to defaults where available. Test with minimal customization. In particular, temporarily remove custom CSS, search-and-replace rules, aggressive heuristic processing, embedded font requests, and unusual output profiles.

If the default conversion succeeds, reintroduce only the setting you actually need, one at a time. Run a new conversion after every change. The first option that reproduces the failure is the one to leave disabled or correct.

2.5 Look for Oversized or Damaged Images

Very large cover images, page scans, and malformed JPEG, PNG, GIF, or SVG resources can stall image processing or exhaust available memory. A log that stops while processing a named image gives you a strong lead.

If the book is editable, make a backup and inspect the named resource in Edit book. Replace a damaged image with a valid copy or resize an unnecessarily huge image using a reputable image editor. Do not simply delete images referenced by the book unless you also correct the relevant links.

Success looks like this: conversion passes the previously repeated image-processing point and produces a readable output. Once it does, avoid unrelated metadata or library changes.

3. Check Temporary Storage, Permissions, and Security Software

Conversion happens in a separate job process and uses temporary files. calibre may therefore open normally while conversion fails because the job cannot create, read, rename, or write a required file.

3.1 Verify Temporary Folder Access

Check that the operating system's temporary location exists, has free space, and is writable by your user account. Problems are more likely after moving system folders, changing environment variables, restoring a profile, using cleanup software, or applying restrictive permissions.

On all platforms, a practical test is to create a new local folder owned by your account, give it a simple path, and temporarily direct calibre's temporary storage there with the documented CALIBRE_TEMP_DIR environment variable. Restart calibre after changing the environment. Advanced customization should be temporary and documented so it can be reversed.

Avoid placing the test folder on a network share, removable drive, cloud-synchronized folder, or protected system directory. A plain local folder helps eliminate locking, latency, and synchronization variables.

Success looks like this: the same source and conversion settings work after calibre uses the new writable temporary folder. This indicates a storage, permission, path, or cleanup problem in the previous temporary location.

3.2 Test a Local Output and Local Library Copy

If the library is stored in OneDrive, Dropbox, iCloud Drive, a network share, or another synchronized location, pause synchronization briefly and repeat the test. Better still, create a temporary local test library and add a copy of one book to it.

This is a diagnostic step, not an instruction to move or delete the main library. Background synchronization can lock, rename, upload, or replace files while a conversion job is writing its result. Network storage may also handle file locking differently from a local disk.

If the local test works, stop experimenting with the source book. Address synchronization exclusions, on-demand file availability, permissions, or library placement before resuming normal work.

3.3 Check Antivirus or Endpoint Protection

Security software may allow calibre's main interface while blocking a conversion worker process from creating executables, opening temporary files, or writing the converted output. This can appear as an unexplained access error, a vanished job process, or a job that fails immediately.

Review the antivirus or endpoint protection history for detections at the exact time of the failure. If your security policy permits it, add a narrow exception for the official calibre installation and the temporary test folder rather than disabling protection broadly. In a managed workplace, ask the administrator to review the blocked process or file event.

Download calibre only from its official site. If security software reports a suspicious file, verify the installation source before creating any exception.

Success looks like this: the conversion completes after a confirmed false-positive block is removed or the required process is permitted. Restore normal protection and keep the exception as limited as possible.

3.4 Confirm Available Memory and Disk Space

Large PDFs, comics, embedded fonts, and high-resolution images may require considerably more working space than the source file's final size suggests. Verify free space on the system volume, the temporary volume, and the volume containing the library.

Close other memory-heavy applications and retry once. If the job succeeds only after freeing resources, reduce source image sizes where appropriate or process the book on a system with more available memory. Repeatedly restarting the same resource-starved conversion without changing conditions is unlikely to help.

4. Use Logs and Debug Output to Locate the Failure

When simple tests do not resolve a calibre conversion stuck or failed error, collect evidence before reinstalling anything. A detailed log can distinguish an input failure from a transformation, image-processing, or output-writing failure.

4.1 Read the Job Log From the Bottom Up

Open the Jobs panel, double-click the failed job, and copy the full log into a text file. Begin with the final error, then search upward for the last named stage or resource.

• An error near input processing points toward the source file or input plugin.
• An error naming HTML, CSS, an image, or a font points toward book content.
• An access or permission error points toward a folder, security tool, or filesystem.
• An error during output creation points toward the selected output format or its options.
• A plugin traceback may justify testing with that third-party plugin disabled.

Do not publish a log without reviewing paths, usernames, email addresses, server details, and other personal information.

4.2 Save Conversion Debug Output

The conversion dialog provides an option to save debug output to a folder. This records intermediate stages of calibre's conversion pipeline, including the material produced by input processing and later transformations.

Create an empty local folder and enable debug output for one controlled conversion. If files appear only in the early pipeline folders, the log may show which later stage failed. If the input-stage material is already malformed, the source or input processing is the better target. If intermediate content looks reasonable but final output creation fails, investigate the output format and its options.

Debug output can be large and may contain the book's text and images. Store it privately and delete it when troubleshooting is complete.

4.3 Run ebook-convert for Clearer Terminal Output

Advanced users can reproduce the conversion with calibre's ebook-convert command. This does not require programming knowledge, but it does require accurate file paths and basic Terminal, Command Prompt, or shell use.

A basic command follows this pattern:

ebook-convert "input.epub" "output.azw3" -vv

The input and output extensions determine the conversion formats. Quotation marks are important when paths contain spaces. On macOS, calibre's command-line tools are located inside the application bundle, so the full command path may be required.

For pipeline files as well as verbose output, use a command following this pattern:

ebook-convert "input.epub" "output.azw3" -vv --debug-pipeline "debug-folder"

Run this against a copied source in a simple local folder. A terminal log can make the final exception easier to see than a graphical job window. It also helps determine whether the failure is tied to the graphical interface or occurs in the conversion engine itself.

4.4 Use calibre-debug Only When It Adds Evidence

The calibre-debug utility can launch calibre components in debugging contexts, but it is not the first tool to use for a single damaged book. Start with the Jobs log, conversion debug output, and ebook-convert. Use broader debugging only when the graphical application behaves abnormally, multiple unrelated conversions fail, or support instructions specifically request it.

5. Run a Clean Temporary Test Before Reinstalling

A clean test separates book-specific problems from configuration and plugin problems without risking the main library.

5.1 Create a Controlled Test Environment

1. Close calibre and make sure no conversion job remains active.
2. Create a new local folder outside cloud synchronization.
3. Create a temporary calibre library in that location.
4. Add one small known-good, unprotected EPUB.
5. Convert it with default settings and no metadata download or delivery step.
6. Add a copy of the failing source and repeat the same conversion.

If the known-good book works and the failing source does not, return to source-file troubleshooting. If both fail, test temporary folder permissions and security software next.

5.2 Test Without Third-Party Plugin Influence

Conversion input and output support built into calibre should not normally require a third-party plugin. If a job log names an added plugin, or failures began immediately after a plugin change, disable that plugin temporarily and restart calibre.

Change only one plugin state at a time. If conversion succeeds, check the plugin's official support information before enabling it again. If the plugin is unrelated and the error remains, restore it and continue investigating rather than leaving multiple components disabled.

5.3 Reinstall Only After the Clean Test Fails

Reinstallation is appropriate when known-good files fail in a local test, permissions are correct, security software is not blocking the job, and command-line conversion also fails in a way that suggests damaged program files.

Do not delete your library as part of a routine reinstall. The library contains books and metadata, while the application installation is separate. Back up important data before major changes, download the installer from the official calibre website, and retest with a small book before restoring customizations.

6. Quick Fix Checklist

• Open the Jobs panel and read the complete failed-job log.
• Convert a small known-good EPUB using default settings.
• Try a fresh authorized copy or another source format.
• Reset book-specific conversion options before changing global preferences.
• Check EPUB or AZW3 structure with Edit book on a backup.
• Expect complex, scanned, or image-heavy PDFs to require more resources.
• Inspect any image named immediately before the repeated failure.
• Verify writable temporary storage and sufficient free disk space.
• Test from a local folder outside cloud synchronization.
• Review antivirus history for blocks matching the failure time.
• Save conversion debug output to identify the failing pipeline stage.
• Use ebook-convert with verbose output when the GUI log is unclear.
• Test a temporary library before reinstalling or changing many settings.
• Stop troubleshooting when the same conversion succeeds repeatedly.

7. Frequently Asked Questions

7.1 Why is calibre conversion stuck at 1 percent?

A low percentage does not always mean the job is idle. calibre may be unpacking the source, parsing a large document, or processing images before visible progress advances. Check the Jobs panel, elapsed time, CPU activity, and log. If repeated attempts stop at the same named resource or stage, investigate that resource instead of waiting longer.

7.2 How long should a calibre conversion take?

There is no reliable universal time because source size, format, document complexity, image resolution, output format, storage speed, and available memory all matter. A small, clean EPUB should provide a better control test than a large PDF. Compare the failing book with a known-good file on the same computer.

7.3 Does a failed conversion mean my calibre library is corrupt?

Usually not. If the book remains listed, its source format opens, and other titles convert, the problem is more likely confined to the source file or its saved conversion settings. Do not rebuild or delete the library based on one failed conversion.

7.4 Can metadata cause a conversion to fail?

Ordinary title, author, tag, and series metadata rarely causes a conversion job to hang. However, an invalid cover image, unusual embedded metadata, or a custom metadata-related plugin can contribute. Use the log to confirm a connection before changing metadata fields or download settings.

7.5 Why does the book open but fail to convert?

A viewer may tolerate damage that a conversion parser cannot. The file might contain malformed markup, missing resources, a damaged image, invalid archive entries, or complex fixed-layout content. Test the structure, obtain a clean source, or convert from a different available format.

7.6 Should I reinstall calibre when every conversion fails?

Not immediately. First test a known-good book, a writable local temporary folder, a local test library, antivirus history, and ebook-convert. Reinstall only when these checks indicate that the installed application files or shared configuration are the likely cause.