Publié
How Send to Kindle Works (and Where It Stops)
Send to Kindle is a genuine conversion service, not a simple hand-off — a file goes in, gets rebuilt into Amazon's own format, and comes out the other side. Most of the time that's invisible. This looks at what happens in between, and the three places the pipeline stops on purpose: DRM, fixed layout, and an approved-sender list most people never open.
Send to Kindle looks like one button. Under it is a real conversion pipeline: a file goes in, gets rebuilt into Amazon's own format, and comes out the other side looking like it always belonged on a Kindle. Most of the time you never see that step happen. That's exactly why it pays to know what it's doing, and where it eventually says no.
This matters if you already live the phone-as-library workflow: AirDropping a chapter to yourself, emailing a contract, sending a PDF to read later. Send to Kindle is one of the oldest versions of that habit, and its limits are a useful map of what "converting" a document actually costs.
What Send to Kindle Actually Is
Send to Kindle isn't one mechanism. It's an email address, an app, a browser extension, and a web upload page, all feeding the same conversion service. Each Kindle device and app gets its own address at kindle.com; send a file there, or drop it into the app or upload page, and Amazon's servers do the rest.
The service currently accepts PDF, DOC, DOCX, TXT, RTF, HTML, common image formats, and EPUB, with a combined size limit around 50MB per delivery. Larger sets can be zipped — the conversion service opens the archive automatically and processes what's inside.
How the Conversion Actually Works
An EPUB or DOCX file doesn't just get renamed when it lands on a Kindle. Since 2022, Send to Kindle converts EPUB files server-side into Amazon's KF8 format (file extension .azw3) — the same reflowable format Kindle books have used since 2011, not the older AZW or the now-retired MOBI. That's a real rebuild: line-breaking, typesetting, and pagination all get recalculated for Kindle's own rendering engine. It's part of why Kindle files won't open anywhere else once they've been through it.
Reflowable formats are the ones this process handles best. A DOCX or a clean EPUB goes in with structure — headings, paragraph breaks, a table of contents — and that structure survives the conversion, because reflowable formats are built to be reflowed. Knowing what EPUB 3 adds and what it can break in the source file helps here, since anything unusual there tends to get lost first.
Where PDFs Push Back
PDF is where the pipeline shows its limits most visibly. A PDF is a fixed-layout format — it exists to reproduce a page exactly as designed, not to adapt to whatever screen it lands on. Sent to Kindle, a PDF mostly keeps its original page geometry rather than becoming reflowable text the way an EPUB does. On a smaller device, that means the font size that made sense on a laptop screen stays that size on a six-inch display. Panning around a page becomes the normal way to read it.
This isn't a bug in the conversion. It's the same tension between reflowable and fixed-layout formats that shows up anywhere a fixed page meets a variable screen. Send to Kindle doesn't pretend to solve it; it just passes the PDF through mostly as-is.
Where It Stops
Three limits are worth knowing before you rely on the service for something important.
DRM-protected files. Kindle's own DRM scheme doesn't recognize the ADEPT scheme that DRM-protected EPUBs commonly carry, so a protected file simply fails to convert — it doesn't arrive locked, it doesn't arrive at all. That's a deliberate incompatibility, not a bug to route around.
The approved-sender list. Every Kindle address only accepts mail from senders on the account's Approved Personal Document Email List. Mail from anyone else is rejected silently — no bounce, no error, just a file that never shows up. It's the most common reason "I sent it and nothing happened" turns out to have a simple explanation.
Language and formatting edges. PDF conversion support is limited to a short list of languages, and complex DOCX formatting — footnotes, embedded objects, unusual styles — is where conversion fidelity tends to break down first. None of this is arbitrary. It's the honest cost of rebuilding a document into a different format.
How Margina Handles the Same File
Margina skips the rebuild entirely. A PDF, EPUB, Word document, plain text file, or Markdown file opens as what it already is — no conversion queue, no approved-sender list to maintain, no server round-trip between you and the page. That's part of what it means to keep owning your books as files, not apps: the format you started with is the format you keep reading.
The app has no account and no server, so there's nothing tracking which files you've opened. If you want a copy elsewhere, back it up to your own iCloud or Drive — the free tier covers a first library's worth of documents before that becomes a question worth asking. You can find Margina on the App Store and Google Play.
Frequently Asked Questions
Can Send to Kindle convert a DRM-protected EPUB or PDF?
No. Amazon's Kindle DRM scheme doesn't support the ADEPT scheme that DRM-protected EPUBs commonly use, so a protected file fails to convert rather than arriving with restrictions intact. If a file is protected, it needs to come from a source that can deliver it DRM-free.
Why does a PDF I send to Kindle look tiny on my device?
PDF is a fixed-layout format — it reproduces the page exactly as designed rather than reflowing text to fit the screen. On a smaller Kindle, the original page geometry (and its font size) stays fixed, which is why zooming and panning around a PDF often feels different from reading a native Kindle book.
Why didn't my document ever arrive after I emailed it to my Kindle address?
The most common cause is a sender address that isn't on the account's Approved Personal Document Email List — Amazon silently rejects mail from anyone not on that list. Check that list before assuming the file itself was the problem.
The Takeaway
Send to Kindle's limits aren't incidental. DRM incompatibility, fixed-layout PDFs, and an approved-sender gate are all by design, not oversights waiting to be patched. Knowing where a conversion pipeline stops is part of knowing how to use it well, whether that means sending the right file the first time or deciding a document is better read exactly as it is.