calibre Send to Device Not Working: How to Fix It

When calibre detects your e-reader but the Send to device action fails, sends an unwanted format, or places the book somewhere the device cannot display it, device detection is no longer the main problem. The failure is usually caused by format selection, automatic conversion, the destination storage location, a sending template, insufficient writable space, a damaged source file, or a device-specific limitation. The safest approach is to test one known-good book, inspect the resulting job, and change only the setting connected to the observed failure.

1. Confirm the Symptom With a Small Safe Test

Begin by separating a send failure from a detection failure. If calibre displays a Device button or device library after you connect the reader, calibre has detected something it can manage. You do not need to repeat every device-detection fix unless the connection disappears, repeatedly disconnects, or opens with an error.

1.1 Use One Known-Good Test Book

Select a small, uncomplicated, legally obtained e-book that opens correctly in calibre. EPUB is a practical test for many Kobo devices, Android reading apps, PocketBook models, and other EPUB-compatible readers. For a Kindle model that accepts files through calibre over USB, test a simple format the particular device supports, often AZW3 for older USB workflows. Device capabilities differ, so confirm the supported formats for your exact model rather than assuming every reader accepts the same files.

Before sending, open the book with calibre's viewer. This does not prove that the destination device will support the format, but it confirms that calibre can access and read the library copy. If the file will not open locally, replace or repair the source before troubleshooting the USB transfer.

1. Select only the test book.
2. Right-click Send to device.
3. Choose Send specific format to, then select the intended format and main memory.
4. Wait for the Jobs indicator to return to zero.
5. Open the Device view in calibre and look for the title.
6. Eject the device through calibre before disconnecting it.
7. Allow the reader time to scan or import newly transferred books.

Success means the job completes without an error, the selected format appears in calibre's Device view, and the reader lists or opens the book after a safe eject. Once this happens, stop changing connection and operating system settings. Compare the successful test with the book or workflow that fails.

1.2 Identify Which Failure You Actually Have

• The job fails immediately: Inspect Job details for a format, path, permission, plugin, or file-access error.
• A conversion starts and fails: The requested device format is missing, so calibre is attempting an automatic conversion.
• The job completes but the book is absent: Check the destination memory, folder structure, format support, and the reader's import process.
• The wrong format arrives: Review the device driver's format order, the preferred output format, and the exact Send to device command used.
• Only one book fails: Suspect its source file, metadata, filename, conversion settings, or unusually large size.
• Every book fails: Suspect storage, write permissions, USB mode, device configuration, or a plugin conflict.

2. Check the calibre Settings Directly Related to Sending

A connected device does not guarantee that calibre will choose the format or destination you expect. The Send to device button uses the available book formats, the active device driver, its configured format preference, and the default button action.

2.1 Send a Specific Format Instead of Relying on Automatic Choice

Right-clicking Send to device exposes more precise commands than clicking the main button. Choose Send specific format to and explicitly select both the format and destination. This bypasses uncertainty about which copy calibre is choosing when the library contains EPUB, PDF, AZW3, and other versions of the same title.

If the explicit send succeeds, the USB connection and destination are probably sound. The problem is more likely the normal format-selection order or automatic conversion. You can continue using the explicit command or adjust the relevant device preferences after confirming which format works.

2.2 Review the Preferred Output Format

calibre has a preferred output format under Preferences, Interface, Behavior. This preference can influence workflows that need a default conversion target, but it does not make an unsupported format compatible with a device. Set it to a format that fits your main reading ecosystem, such as EPUB for an EPUB-based reader or an appropriate Kindle-compatible format for a supported Kindle workflow.

Do not change this setting repeatedly if Send specific format to already transfers the correct file. A successful explicit transfer shows that your immediate problem has been identified. Change the global preference only if calibre routinely selects an unsuitable conversion target in other workflows.

2.3 Understand Automatic Conversion During Send

If the selected book does not contain a format accepted by the active device driver, calibre may offer to convert it before sending. The transfer can therefore fail even though device detection is working perfectly. In this case, the failed stage is conversion, not USB communication.

Convert the test book manually before sending it. Select the book, choose Convert books, select an output format supported by the reader, and complete the conversion. Open the converted result in calibre, then use Send specific format to. Manual conversion makes the sequence visible and lets you determine whether the failure occurs before or during transfer.

Success means the conversion job finishes, the new format appears in the book's format list, and that exact format transfers successfully. Once it does, stop changing USB or permission settings.

2.4 Check the Device Plugin Configuration

With the device connected, open the device configuration available from the Device button or inspect the relevant device interface plugin under Preferences and Plugins. Depending on the driver, you may be able to review enabled formats, their order, destination folders, metadata behavior, and subfolder support.

Place the reader's most reliable format ahead of formats you do not want calibre to choose. Do not enable formats merely because calibre can convert to them. The physical reader, its firmware, or its reading application must also support them.

If the problem began after changing a device plugin or installing a third-party integration plugin, temporarily return that plugin to its defaults or disable it for a controlled test. Avoid disabling several plugins at once because you will not know which change mattered.

2.5 Verify Main Memory, Storage Card, and Default Action

The Send to device menu can target main memory or an available storage card. It also lets you set the default action performed by the main toolbar button. A book sent successfully to the wrong destination can look like a failed transfer, especially when the reader does not automatically scan that location.

Use Send specific format to main memory for your first test. In calibre's Device view, confirm the storage area containing the book. If main memory works but a storage card does not, inspect the card for free space, write protection, filesystem errors, or unsupported folder behavior.

2.6 Simplify the Sending Template and Metadata

calibre can create device folders and filenames from book metadata. The template is configured under Preferences, Import/export, Sending books to devices. A complicated template can produce deep folder trees, long paths, unusual characters, or locations that a basic reader does not scan.

Temporarily use a simple template based on title and author. Also clean obviously malformed metadata, such as an empty title, an extremely long series name, or unexpected path-like characters. Metadata plugboards can change the metadata written inside a book during sending, while the sending template controls its path and filename. Check both if books transfer but appear under surprising names.

Success means the book is placed in a short, predictable path and becomes visible after the reader refreshes its library. If that works, add template complexity back gradually.

2.7 Keep Unrelated calibre Features Out of the Test

Email delivery, the Content server, the viewer, the editor, metadata downloads, and news downloads use different paths from a direct USB Send to device action. Do not change email or server settings to fix a USB transfer unless you are intentionally using those methods instead.

The viewer is useful for checking whether a source file opens. The editor can help validate or repair supported e-book files, but it is not required for an ordinary transfer. Keep the initial test limited to one library book, one supported format, and one connected device.

3. Check the Device and Operating System

3.1 Confirm the Device Is Writable and Has Free Space

A reader can be detected and browsed even when calibre cannot write a new file. Check free space in calibre's device information and in the operating system. Leave more room than the book's displayed size because conversion, temporary files, cover data, and the reader's database may require additional space.

If the device or card is mounted read-only, do not attempt to force calibre past the restriction. Check for a physical lock switch on an SD card adapter, filesystem errors, device safety warnings, or operating system mount permissions. On Linux, inspect how the volume was mounted. On Windows and macOS, try creating and deleting a harmless test folder through the file manager only if the device's documentation permits normal file access.

Success means the destination accepts a small file and calibre completes the send without a permission or read-only error. If it does, stop adjusting security settings.

3.2 Use the Correct USB Mode

Android-based devices may connect in charging mode instead of file-transfer mode. Unlock the device, open its USB notification, and select File transfer or MTP when appropriate. Approve any prompt asking whether the computer may access device data.

On macOS and Linux, another application may take exclusive control of an MTP device. Close file-manager windows, Android transfer utilities, sync applications, and other e-book managers before restarting calibre. Detection can appear successful at first but writes may fail when two programs compete for the same connection.

3.3 Check the Cable and Connection Stability

A marginal cable can allow identification but fail during sustained writing. Connect directly to the computer instead of through an unpowered hub, try another known data-capable cable, and avoid moving the device during transfer. A charge-only cable usually prevents detection entirely, but a damaged data cable can produce intermittent send failures.

If calibre's Device button disappears during the job, prioritize cable, port, USB mode, power, and connection stability. Format preferences are not the first concern when the device disconnects mid-transfer.

3.4 Review Security and Cloud-Sync Interference

Antivirus, endpoint security, controlled-folder protection, or restrictive filesystem permissions can block calibre from reading its library copy or writing temporary conversion output. Read the exact error before creating exclusions. If the message names a library file, temporary folder, or device path, verify permissions for that specific location.

A calibre library stored in OneDrive, Dropbox, iCloud Drive, a network share, or another synchronized location can also produce temporary locks or unavailable placeholder files. For a safe test, copy or import one small book into a local test library stored on an ordinary local folder. Pause sync only if the error clearly points to a locked or unavailable source file.

3.5 Respect Reader-Specific Limitations

Some readers scan only particular folders, reject unsupported subfolders, require an internal database refresh, or ignore formats they cannot index. A file's presence in storage does not guarantee that it will appear in the device library.

After a successful send, eject safely and wait for the device to process new content. Search by title and author, not only through a recent-books screen. If the file is visible in calibre's Device view but absent from the reader interface, test a shorter path and a known-supported format. Restart the reader once if its documentation recommends doing so after sideloading.

4. Use calibre Logs and Job Details

4.1 Read the Failed Job Before Trying Another Fix

Click the Jobs indicator in calibre after a failure and open the failed job's details. Copy the complete error into a text file before closing it. The final line alone may omit the path or operation that caused the problem.

Look for practical clues:

• Permission denied or read-only: Investigate the named source, temporary, or device path.
• No space left: Free space on the destination identified in the message.
• Conversion error: Test the source and perform a manual conversion.
• Unsupported format: Send a format listed for the reader and enabled in its device configuration.
• File not found: Confirm that the library format is locally available and has not been moved or replaced by a cloud placeholder.
• Path or filename error: Simplify the sending template and metadata.
• Device disconnected: Check the cable, port, USB mode, and competing applications.

Once a change removes the named error and the test book appears on the reader, stop. Additional changes can hide the original cause or create a new one.

4.2 Use Debug Device Detection for Driver Problems

Preferences, Miscellaneous, Debug device detection is most useful when calibre selects the wrong driver, reports unusual device information, or cannot reliably open the device. Run it with the device connected and save the output. Because this article focuses on devices that are already detected, use this tool after ordinary send checks, not as the first step.

The output may contain technical details. You do not need to interpret every line. Preserve it when reporting a reproducible problem through calibre's support channels, along with the operating system, device model, destination, requested format, and full job error.

4.3 Capture Conversion Debug Output When Needed

If the send fails during automatic conversion, reproduce the conversion manually and enable conversion debug output in the conversion dialog. calibre can save intermediate stages of the conversion pipeline to a folder. This is especially useful when one particular source file fails while other books convert and send normally.

Do not use conversion settings to bypass DRM or retailer restrictions. If a file is protected or restricted, use the retailer's supported application, delivery method, or device authorization process.

4.4 Use calibre-debug Only for Persistent Reproducible Failures

Advanced users can start calibre's graphical interface from a terminal with calibre-debug -g to capture diagnostic output. This is not necessary for most format or destination mistakes. Use it when the normal Job details are incomplete, calibre closes unexpectedly, or a maintainer asks for terminal output.

On Windows, macOS, and Linux, reproduce only the smallest failing action: start calibre, connect one device, select one test book, send one specific format, and save the output. Avoid including unrelated private library information when sharing logs publicly.

5. Run a Clean Temporary Test Before Reinstalling

Reinstalling calibre rarely fixes a bad format choice, unwritable device, malformed template, damaged book, or third-party plugin setting. Deleting the library is even less appropriate and risks unnecessary data loss. Instead, build a reversible test that isolates the transfer path.

1. Create a new temporary calibre library in a local folder.
2. Add one small, known-good, unrestricted EPUB or appropriate AZW3 test file.
3. Use simple title and author metadata.
4. Temporarily disable only the third-party plugin most directly involved with the device, if applicable.
5. Connect one device directly with a reliable cable.
6. Choose Send specific format to main memory.
7. Open Job details and verify completion.
8. Eject safely and check the reader.

If this succeeds, calibre's core send function, the connection, and the device are capable of working together. Return to the normal library and compare the failing book, device template, plugin behavior, and conversion settings. If the clean test also fails, focus on the device's writable storage, driver, operating system permissions, and the exact job error.

Do not delete your original library or configuration. Do not make several system-wide changes together. A controlled test is valuable precisely because every change is reversible and its result is clear.

6. Quick Fix Checklist

• Confirm the Device button remains visible throughout the send.
• Test one small EPUB or device-appropriate AZW3 that opens in calibre.
• Right-click Send to device and choose a specific format and main memory.
• Check whether calibre is automatically converting the book.
• Confirm the selected format is supported by the exact reader model or app.
• Review the device plugin's enabled formats and their preference order.
• Check the default Send to device destination.
• Simplify the sending template, filename, metadata, and subfolder structure.
• Verify that the device or storage card is writable and has free space.
• Use File transfer or MTP mode on devices that require it.
• Close other programs that may be controlling the device.
• Open calibre's Jobs window and read the complete error details.
• Run a local temporary-library test before reinstalling calibre.
• Use Debug device detection only when the driver or connection remains suspect.

7. Frequently Asked Questions

7.1 Why Does calibre Detect My Device but Fail to Send Books?

Detection proves that calibre can identify and open a device interface, but sending also requires a supported output format, a writable destination, sufficient space, a valid source file, and an acceptable path. Open the failed Job details and test one explicit format to main memory. That distinction prevents you from repeating detection fixes for what is actually a conversion or write failure.

7.2 Why Is calibre Sending the Wrong Format?

The library may contain several formats, and calibre or the device driver may prefer one over another. Use Send specific format to for an immediate fix. Then review the preferred output format and the device configuration's enabled format order. Stop once the explicitly selected format transfers and opens correctly.

7.3 Why Does calibre Convert a Book When I Click Send to Device?

Automatic conversion usually occurs because the library does not contain a format that the active device driver is prepared to send. Convert the book manually to a format the reader supports, verify it in calibre, and send that specific format. If manual conversion fails, troubleshoot the source file and conversion job rather than the USB connection.

7.4 Why Does the Job Finish but the Book Not Appear on the Reader?

The file may be in the wrong storage area or folder, or the reader may not support or index its format. Check calibre's Device view to confirm the path and extension. Eject safely, allow the device to scan, and search by title and author. If necessary, send a known-supported format to main memory with a simple, shallow folder structure.

7.5 Can Metadata Stop a Book From Being Sent?

Ordinary metadata errors usually affect naming, sorting, or display rather than the raw USB connection. However, very long values, unusual characters, sending templates, and metadata plugboards can create problematic paths or unexpected titles. Simplify the template and test with clean title and author values.

7.6 Should I Reinstall calibre or Delete My Library?

Not as an early step. Reinstallation does not usually correct device storage, unsupported formats, conversion failures, or custom templates. Never delete a library as a routine troubleshooting measure. First run a temporary local-library test with one known-good book. Reinstall only when evidence points to damaged application files, and preserve your library and configuration backups.