Why Amazon Deprecated MOBI for Kindle and How In-Browser EPUB Conversion Works

For over a decade, the format was synonymous with Amazon Kindle. If you bought an independent eBook, downloaded a classic from Project Gutenberg, or received an Advance Reader Copy (ARC), you loaded it onto your Kindle as a MOBI file. However, in late 2022 and throughout recent firmware updates, Amazon formally phased out MOBI support for its popular Send to Kindle service in favor of EPUB. In this article, we’ll explore the technical reasons behind Amazon’s deprecation of MOBI, why standard cloud-based converters pose severe privacy risks, and how client-side web technologies allow fast, 100% private in-browser conversion. The Evolution: Why Amazon Retired MOBI To understand why MOBI had to go, we have to look back at its origins: PalmDOC Roots (1990s - 2000s): MOBI was created by Mobipocket in 2000, built on the PalmDOC format designed for early handheld personal digital assistants (PDAs). It relied on an ancient, monolithic database structure known as the Palm Database () format. Amazon's Acquisition (2005): When Amazon prepared to launch the first Kindle in 2007, they acquired Mobipocket and adapted the MOBI format into AZW (Kindle Format 7). Typography & Modern Layout Limitations: MOBI was never designed for modern typography. It lacked native support for complex CSS layouts, media queries, scalable vector graphics (SVG), embedded modern fonts, hyphenation dictionaries, and dynamic dark mode styling. The Rise of EPUB 3: The International Digital Publishing Forum (IDPF) and the W3C standardized EPUB as the open industry benchmark. EPUB is essentially a structured, compressed web package (HTML5, CSS3, XML metadata, and SVG) packaged inside an Open Container Format (OCF) ZIP container. Because modern Kindle readers render KF8 (AZW3) and KFX engines that translate HTML/CSS natively, maintaining legacy MOBI parsers created unnecessary rendering inconsistencies. Amazon officially made EPUB the required format for Send to Kindle. The Hidden Danger of Traditional Online Converters When readers discovered their MOBI libraries would no longer send to Kindle via email, millions turned to generic online converters. Unfortunately, standard web converters share fundamental architectural flaws: Server-Side File Ingestion: Your entire eBook (which may contain proprietary manuscripts, sensitive documents, or private purchases) is uploaded to a remote third-party server. Data Retention & Privacy Leaks: Many free conversion websites store uploaded files in temporary cloud buckets that can remain exposed or get logged in backend analytics. Bandwidth Latency: Uploading a 50MB illustrated volume or technical manual and downloading it back wastes unnecessary time and bandwidth. The Modern Alternative: Zero-Upload Client-Side Conversion Modern browser capabilities—including the WebAssembly (Wasm) pipeline, modern FileReader APIs, and fast binary array buffers—make server-side conversion obsolete for document transformations. Instead of sending your data across the wire, conversion can happen entirely within your local browser memory sandbox: Key Technical Advantages of Local In-Browser Processing Absolute Privacy: Because files never leave / client memory, personal manuscripts and DRM-free purchases stay 100% confidential. Near-Zero Latency: Decompressing PalmDOC records and repackaging into an EPUB archive takes milliseconds directly on your CPU without any network roundtrip. No File Size Caps: While server-based tools enforce arbitrary 10MB or 25MB limits to minimize hosting bills, in-browser conversion is bound only by your device RAM. A great example of this approach in action is the free Mobi to EPUB Converter, which executes 100% of the conversion logic client-side with zero server uploads, making it instantaneous and privacy-preserving for Send-to-Kindle users. Understanding Palm Database (PDB) Parsing in JavaScript For developers interested in implementing their own client-side parser, here is how the PalmDOC record structure works under the hood. Every MOBI file begins with a standard PDB header: Record 0 contains the MOBI Header with metadata tags (title, author, publisher, cover image offsets, and the header), followed by compressed text records. By unpacking these records with client-side LZ77 decompression, parsing the raw HTML, and packaging the result into standard EPUB container structure, you achieve high-fidelity conversions without a single byte leaving the user's computer. Conclusion Amazon's shift from MOBI to EPUB is a long-overdue victory for open web standards and digital typography. And with modern web standards, converting legacy libraries no longer requires compromising document privacy. If you have MOBI files you need to transfer to your Kindle, try using client-side tools like Mobi to EPUB to keep your library organized, updated, and private.