This is the most-asked question in this whole category, and the usual answer is a red dot next to the word Failed. There are about ten real causes. Here they are, with what each one looks like and what fixes it.
@kindle.com and lives in Personal Document Settings.
Where to find it → Amazon only accepts documents from addresses on your Approved Personal Document E-mail List, and your RoutineInk address isn't on it yet. Since April 2025 Amazon requires the full address — a wildcard like @send.routineink.com will not work. Add exactly this address, then send again.
Amazon says there's no device at that address. Check it under Manage Your Content and Devices → Preferences → Personal Document Settings — the address usually ends in @kindle.com.
This one came to 25+ MB and the mail limit is 25 MB. It's almost always images. Turning images off — or down to grayscale, which is what your reader shows anyway — fixes it.
Amazon stopped accepting MOBI for new sends in 2023 and is phasing out older formats. EPUB works everywhere current; switch this device to EPUB.
Amazon caps how many personal documents one account can receive in a day. We'll retry the rest tomorrow — nothing is lost, and you don't need to do anything.
Before the first real send we mail a one-page test document and wait to hear that it arrived. That's how we catch a missing approval before it eats a week of your reading.
The page loaded but there was no readable body — usually a landing page, a video, or a site that builds its text in the browser. Sending it from the browser extension works in those cases, because the extension reads the page you're already looking at.
That site refuses server requests. Use the RoutineInk browser extension on the page instead — it extracts the article inside your own logged-in session, so the site sees you, not us.
We've failed to reach this feed several times running. If it has moved, update the URL; we'll keep trying meanwhile.
This send needs a larger plan.
These never ask you to do anything. They are listed because a service that hides its own failures is a service you cannot trust about the others.
Sometimes there is no error anywhere. The mail was accepted, no notice came back, and the document never appeared. That silent drop is the failure that makes people give up on these tools, because there is nothing to react to.
Three things reduce it to nearly zero, and RoutineInk does all three:
Amazon has narrowed this feature repeatedly. If a setup that worked has stopped, one of these is usually why:
| When | What changed |
|---|---|
| 2023 | MOBI ingestion ends for new sends. EPUB becomes the format for personal documents. |
| February 2025 | "Download & transfer via USB" is removed from the Kindle store. |
| 1 April 2025 | Approved-sender entries must be full email addresses. Domain wildcards stop working, and failed sends start generating a notice back to the sender. |
| 9 February 2026 | Send to Kindle is removed from Microsoft Word on all platforms. |
| 20 May 2026 | Send to Kindle stops working on Kindles made before 2013 — they cannot negotiate current TLS — and older formats begin being phased out. |
| 30 June 2026 | The legacy Kindle for PC application is shut down. |
None of these were aimed at services like this one; all of them cost every service like this one engineering time. Every file we send is also in your library as a download, so a change on Amazon's side never takes your reading with it.
Send the delivery id from the dashboard to help@routineink.com. It carries the exact sending address, the destination, the file size and whatever Amazon said back, which is usually enough to answer without a conversation.
Amazon, Kindle, Kindle Scribe and Send to Kindle are trademarks of Amazon.com, Inc. or its affiliates. RoutineInk is not affiliated with Amazon.