Troubleshooting guide

Send to Kindle E999 Internal Error: What It Means and How to Fix It

E999 is Amazon's generic internal-error code — not a single problem, but four distinct failure modes each requiring a different fix. This guide identifies which cause applies to your file and walks through the resolution. For general Send to Kindle problems not tied to an error code, see Send to Kindle not working: 7 fixes.

By Joe Fowler — Updated May 22, 2026

What the E999 error actually means

When Amazon's Send to Kindle service returns E999, it is reporting a generic internal error — the same code covers four different root causes, which is why a single fix rarely works for everyone. Understanding which cause applies to your specific file is the only reliable path to resolving it.

The four root causes behind an E999 error are:

File too large.The Send to Kindle email method imposes a 50 MB limit; the web uploader at amazon.com/sendtokindle allows up to 200 MB. Files over these thresholds trigger E999 without a descriptive message.
Malformed EPUB.Amazon's conversion pipeline requires strict XHTML-compliant EPUBs. A file that opens correctly in Calibre or Apple Books may still be rejected if it fails Amazon's manifest or spine validation.
DRM-protected file.Files with digital rights management are silently rejected. Amazon's service cannot convert DRM-protected content regardless of file type, and it returns E999 without explaining why.
Transient server-side failure.Amazon's conversion infrastructure occasionally produces errors that clear on retry. If none of the above causes apply to your file, a retry after 30 minutes often succeeds.

In addition to E999, Send to Kindle produces two other failure patterns worth understanding: authentication failures (the app cannot verify your Amazon credentials — unrelated to the file) and silent non-delivery (the file is accepted without error but never appears on your device). Both are covered in the sections below.

The diagnostic sections that follow address all three failure classes in order. Identify which pattern you are seeing — an explicit E999 code, an authentication message, or accepted-but-missing — and go directly to that section.

E999 internal error — diagnostic fixes by cause

File too large for Send to Kindle

The Send to Kindle email attachment limit is 50 MB. The web uploader at amazon.com/sendtokindle accepts files up to 200 MB. If your file is over 50 MB but under 200 MB, switching to the web uploader resolves the majority of E999 errors on large PDFs without any other changes.

If your file exceeds 200 MB, your options are USB transfer (no size limit — connect your Kindle, copy the file into the Documents folder) or convert and sideload via leafbind's PDF to KFX converter (handles files up to 100 MB on Premium; split files over 100 MB before converting).

Malformed or invalid EPUB

Amazon's EPUB processing requires strict compliance with XHTML 1.1 and EPUB 2/3 manifest rules. An EPUB that opens correctly in Calibre, Apple Books, or other readers may still be rejected if it contains malformed HTML tags, missing spine items, or content files that are not valid XHTML.

To diagnose and fix a malformed EPUB:

Open the EPUB in Calibre and convert it to EPUB (output format: EPUB 2) — Calibre's conversion pipeline normalizes most structural issues.
Run the resulting file through the EPUB validator at validator.idpf.org to confirm it passes validation.
Send the Calibre-converted EPUB to your Kindle.

If the Calibre-converted EPUB still triggers E999, try exporting the source document to PDF and sending the PDF version instead.

DRM-protected file (silently rejected)

Amazon's Send to Kindle service cannot process DRM-protected files. This includes EPUBs purchased from stores that apply Adobe DRM or proprietary encryption, and PDFs with copy or print restrictions enforced by the publisher. The rejection comes back as E999 without identifying DRM as the cause.

To check whether DRM is the cause: open the file in Calibre. If it shows a padlock icon or reports an error when you attempt to view its full metadata, the file is DRM-protected.

DRM-protected files must be obtained without DRM from the original source — the publisher, library, or store — to be usable with Send to Kindle.

Transient server-side conversion failure

If your file is within the size limits, passes EPUB validation, and carries no DRM, the E999 error may be a transient failure on Amazon's conversion servers. These are not related to the file — they are temporary infrastructure failures.

Wait 30 minutes and retry. If the error persists after two or three retries across different times of day, the problem is likely the file itself — revisit the size, format, and DRM checks above before trying again.

Authentication failure (Send to Kindle app)

An authentication failure means the Send to Kindle app cannot verify your Amazon account credentials. This is a separate failure class from E999 — it does not indicate a problem with the file itself.

Expired authentication token — sign out and back in

The most common cause of authentication failures is an expired session token. Amazon's app sessions expire without warning, and the error message is the same regardless of cause. To resolve: sign out of the Send to Kindle app completely, then sign back in with your Amazon credentials. Force-close the app before signing out to ensure a clean session state.

Account region mismatch

Amazon accounts are region-specific. A US Amazon account cannot deliver content to a Kindle registered in the UK store, and vice versa. If you recently changed your Amazon store region or your device is registered in a different store from your account, Send to Kindle will fail at the authentication step.

Check your device's registered region at amazon.com/mycd → Devices, and verify it matches your account's store.

App version out of date

Older versions of the Send to Kindle app on iOS, Android, and desktop can lose authentication silently after Amazon updates its auth endpoints. Check for available updates in the App Store, Google Play, or your browser's extension manager. Install any available update and sign in again after updating.

“Send to Kindle doesn't work” — silent delivery failures

Silent failures are cases where Send to Kindle accepts the file — no error code shown — but the file never appears on your device. These are delivery and account-configuration problems, not conversion errors.

File accepted but not appearing on Kindle (check library first)

Before assuming delivery failed, check your Amazon library at amazon.com/mycd. Amazon documents that delivery can take up to 15 minutes, and device sync often lags behind server-side delivery. If the file appears in the library but not on the device, toggle Wi-Fi off and back on, or pull down on the Kindle home screen to force a sync.

If the file does not appear in the library after 30 minutes, the most likely cause is the approved sender list — Amazon silently drops messages from email addresses not on your Approved Personal Document E-mail List. See Send to Kindle not working: 7 fixes for the full approved-sender walkthrough.

Wrong destination device selected

If your Amazon account has multiple registered Kindles, tablets, or Kindle apps, Send to Kindle may have delivered to a different device than expected. Check your library at amazon.com/mycd — personal documents delivered to one device are visible there and can be re-sent to the correct device from the library.

kindle.com vs. free.kindle.com address confusion

Each Kindle has two personal document email addresses: one ending in @kindle.com (delivers over Wi-Fi, 3G, or cellular — older accounts may incur a per-file fee) and one ending in @free.kindle.com (delivers over Wi-Fi only, no charge). Sending to the wrong address when the device is not on Wi-Fi can result in non-delivery. Find both addresses at amazon.com/mycd → Preferences → Personal Document Settings.

When to skip Send to Kindle entirely

Most E999 errors are fixable through the diagnostic steps above — oversized files go through the web uploader, malformed EPUBs are normalized by Calibre, and transient errors clear on retry. If you have worked through the diagnostic and the error persists, or if Amazon's conversion delivers the file but the result is unreadable (garbled columns, missing footnotes, broken headings), converting and sideloading is the most reliable exit.

leafbind converts PDFs to KFX — Kindle's native format — using coordinate-based extraction to handle multi-column layouts, footnotes as tappable Kindle popups, and heading detection for a navigable table of contents. Transfer the resulting KFX file via USB to any Kindle released since 2018. No Amazon account settings required, no email approval list, no 50 MB email cap.

leafbind is specifically useful for three E999 root causes where Amazon cannot help:

File too large even for the web uploader:if your PDF still exceeds the 200 MB limit after any compression, convert and sideload.
Conversion quality failure: Send to Kindle delivers the file but the result is unreadable due to column collapse, missing footnotes, or flat headings.
Repeated transient failures: the error persists across multiple retries over several days with no file-level cause identified.

leafbind does not help with DRM-protected files — those require a DRM-free version from the original source.

Free tier: EPUB output, up to 20 MB, 3 conversions per day, no account required. KFX output (with column detection, footnote linking, and heading classification) is available on premium plans. See pricing →

Frequently asked questions

What does E999 mean in Send to Kindle?

E999 is Amazon's generic internal-error code for Send to Kindle failures. It covers four distinct causes: your file exceeds the size limit (50 MB by email, 200 MB via the web uploader), the EPUB is malformed or fails Amazon's strict XHTML validation, the file is DRM-protected and Amazon silently rejects it, or Amazon's conversion servers experienced a transient failure. Identify which cause applies before attempting fixes.

How do I fix a Send to Kindle E999 internal error?

Fix the E999 error by matching the cause to its solution: if the file is too large, switch to the web uploader at amazon.com/sendtokindle (200 MB limit) or use USB transfer. If the EPUB is malformed, run it through Calibre to normalize it and use an EPUB validator to confirm it passes. If DRM is the cause, the file source must provide a DRM-free version. If it is a transient server error, wait 30 minutes and retry. If none of these apply or conversion repeatedly fails, convert your PDF to KFX with leafbind and sideload via USB.

Why does Send to Kindle say 'authentication failure'?

A Send to Kindle authentication failure means the app cannot verify your Amazon account credentials. The most common cause is an expired session token — sign out of the app completely, then sign back in. If the error persists, check that your Amazon account region matches your device's registered region. Also verify the app is up to date, since older versions can lose authentication silently after Amazon updates its auth endpoints.

What is the file size limit that causes E999?

The Send to Kindle email attachment limit is 50 MB. The web uploader at amazon.com/sendtokindle accepts files up to 200 MB. USB transfer has no size limit. If you receive E999 and your file is over 50 MB but under 200 MB, switching to the web uploader resolves the error in most cases.

How do I check if my file is DRM-protected?

Open the file in Calibre. If it displays a padlock icon or reports an error when you attempt to view its full metadata, the file has DRM. DRM-protected files are silently rejected by Send to Kindle with an E999 error. Amazon cannot convert DRM-protected content, and only the original content source can provide a DRM-free version.

Send to Kindle accepted my file but nothing appeared on my Kindle — what happened?

Check your Amazon library at amazon.com/mycd before assuming delivery failed. Amazon documents that delivery can take up to 15 minutes, and device sync can lag behind server-side delivery. If the file appears in your library but not on the device, toggle Wi-Fi off and back on, or pull down on the Kindle home screen to force a sync. If the file is absent from the library after 30 minutes, the most likely cause is the approved sender list — Amazon silently drops messages from addresses not on your Approved Personal Document E-mail List.

Does leafbind work for files that Send to Kindle rejects with E999?

leafbind helps specifically with the size-cap and conversion-quality cases. If your file exceeds Send to Kindle's limits or Amazon's conversion produces unreadable output, leafbind converts PDFs to KFX — Kindle's native format — using coordinate-based extraction that handles multi-column layouts, footnotes, and heading detection. The KFX file transfers to any Kindle via USB, bypassing Send to Kindle entirely. leafbind does not help with DRM-protected files — those require a DRM-free version from the original source.

Send to Kindle not working: 7 fixes →PDF to KFX converter →How to send PDFs to Kindle →

Sources

Amazon Send to Kindle — supported file types and web uploader (last verified 2026-05-22)
Amazon Send to Kindle for Email — step-by-step instructions (last verified 2026-05-22)
Amazon Help — Personal Document Service (last verified 2026-05-22)

Try leafbind free

Upload a PDF and convert to EPUB at no cost — 3 conversions per day, up to 20 MB, no account required. KFX output with column detection, footnote linking, and heading classification is available on premium plans.

See pricing — plans start at a single conversion credit with no subscription required.

Convert a PDF to KFX →

Joe Fowler is a developer and technical writer who built leafbind after spending an unreasonable amount of time coaxing academic PDFs into something readable on a Kindle. He writes about PDF structure, ebook formats, and the conversion pipeline at leafbind.io.