An EPUB is the open, standard ebook format: reflowable text that adapts to any screen size, with chapters, a table of contents, and styling packed into a single file. MOBI is the older format Amazon used for early Kindle devices. Converting EPUB to MOBI repackages the same book so it opens on a Kindle that does not accept EPUB directly.
The important thing to understand is that both formats hold the same kind of content: flowing text that reflows to fit the page, rather than fixed pages. So this conversion is a repackaging, not a flattening. Your chapters, your reading order, and your table of contents carry over. What changes is the container the book lives in. Understanding what those two containers actually are makes it clear both why the conversion is usually clean and why MOBI is a format you should only reach for deliberately.
What this conversion really does
EPUB and MOBI are both built around reflowable HTML and CSS under the hood. When you convert EPUB to MOBI, the text, the chapter breaks, and the navigation are rebuilt into MOBI's older container so an older Kindle can parse them. Because the text stays reflowable, readers on the Kindle can still change the font size, the margins, and the line spacing, exactly as they could in the EPUB.
Where the two formats differ is in how modern their styling support is. EPUB, especially EPUB 3, understands richer CSS, embedded fonts, and more precise layout.[2] MOBI is older and simpler, so some advanced formatting can be simplified or dropped when it does not have an equivalent. For a normal text-first book, novels, guides, long-form nonfiction, this is rarely noticeable.
EPUB and MOBI both hold reflowable text, so your book stays readable and resizable. MOBI is just the older container an older Kindle can open.
Inside EPUB: a website in a zip
An EPUB file is, quite literally, a ZIP archive with a specific structure defined by the W3C, which now maintains the standard at version 3.3.[1][2] Unzip one and you find a small website inside: one or more XHTML documents holding the actual chapters, CSS stylesheets controlling their appearance, image and font files, and a set of packaging files that tie it all together. A manifest lists every resource in the book, a spine declares the linear reading order of the chapters, and a navigation document defines the table of contents. This is why an EPUB reflows so naturally: each chapter is genuinely an HTML document, and the reader application lays it out with the same flowing logic a browser uses for a web page.
Because it is built on open web standards, EPUB 3 can carry rich CSS, embedded fonts, scalable vector graphics, and even scripting and audio.[2] That expressive power is exactly what a simpler, older format cannot always reproduce, which is the crux of what can be lost when you convert down to MOBI.
Inside MOBI: Mobipocket and PalmDOC
MOBI descends from the Mobipocket format, which was itself built on the older Palm Database (PDB) container used by PalmDOC on Palm handhelds.[3] Amazon acquired Mobipocket in 2005 and adopted the format for the first Kindle in 2007, which is how MOBI became the early Kindle standard. Under the hood a MOBI file stores the book's text as HTML that has been compressed (typically with a PalmDOC-style or Huffman scheme) and split into records inside the PDB container, alongside index records for the table of contents and image records for any pictures.[3]
The limitation is that this HTML dialect and its styling support are frozen in an earlier era of the web. MOBI understands only a subset of the CSS and layout features that modern EPUB takes for granted, so features with no MOBI equivalent must be approximated or dropped during conversion. Amazon later layered a more capable format called KF8 (sometimes packaged so that a single file contains both an older MOBI section and a newer KF8 section for backward compatibility), but plain MOBI itself remains the lowest common denominator.
How the repackaging works
A converter reads the EPUB by unzipping it and following the spine to assemble the chapters in reading order, then translates that content into MOBI's structure. The XHTML of each chapter is mapped to MOBI's simpler HTML dialect, the stylesheets are reduced to the styling MOBI can express, images are re-stored as MOBI image records, and the navigation is rebuilt as MOBI's index so the Kindle's table of contents and chapter jumps work.
Crucially, the text remains marked-up, reflowable content rather than being flattened into fixed pages. That is why font size, margins, and line spacing stay adjustable on the device after conversion. The step where fidelity can slip is the CSS translation: any layout the source EPUB expressed with modern CSS that MOBI has no way to represent gets simplified to the nearest thing MOBI supports.
Why MOBI is a legacy format now
MOBI is a legacy format. Amazon has moved on from it: newer Kindles and the Send to Kindle service now accept EPUB directly, and Amazon retired MOBI as a supported Send to Kindle input format in 2022. Its own newer formats (KF8, and the AZW/KFX files current Kindles actually use) long ago superseded plain MOBI. That means you usually only need MOBI for one reason, which is an older Kindle that predates that shift and simply will not read an EPUB.
If your device is recent, check whether it takes EPUB directly before converting, because it almost certainly does. But if you are dealing with a first- or second-generation Kindle, or an old library of MOBI books, this conversion is exactly how you get an EPUB onto it.
| Aspect | EPUB | MOBI |
|---|---|---|
| Standard body | Open, maintained by the W3C | Proprietary, originally Mobipocket then Amazon |
| Underlying container | ZIP archive of XHTML and CSS | Palm Database (PDB) records |
| Styling support | Modern CSS, embedded fonts, SVG | Older, limited HTML and CSS subset |
| Text behavior | Reflowable | Reflowable |
| Where it opens | Most current readers and Kindles | Older Kindle devices and apps |
| Status | Current and recommended | Legacy, retired by Amazon for new input |
Convert EPUB to MOBI, step by step
Open the converter and add your EPUB
Open the FileFormer ebook converter and drop your EPUB in. Everything runs on your own device, so the book is never uploaded to a server.
Choose MOBI as the output
Select MOBI so the result opens on older Kindle hardware. The converter rebuilds the reflowable text and the chapter list inside the MOBI container.
Convert and preview
Run the conversion and check that the table of contents and chapter order came through. For a text-first book this is almost always clean.
Download and side-load
Download the MOBI, then copy it to your Kindle over a USB cable or by emailing it to your device's send-to-Kindle address.
Side-loading over USB is the most reliable path for a legacy device: connect the Kindle, let it appear as a drive, and copy the MOBI into its documents folder. The book then shows up in the library the next time you open it. The email path, sending the file to your personal send-to-Kindle address, is convenient but is exactly the route Amazon has been steering toward EPUB, so on a modern account it may convert or reject a MOBI rather than accept it as-is. If the email route balks, USB side-loading onto the older device almost always still works, which is another reason MOBI conversion is really an old-hardware solution rather than a modern one.
What the reading experience keeps
It is worth being concrete about what survives the trip, because the fear with any legacy conversion is that the book will arrive broken, and for ordinary books it does not. The text content comes across in full, in the correct reading order set by the EPUB spine. The chapter structure and the table of contents are rebuilt as MOBI's own navigation, so the Kindle's menu and chapter-jump controls work. Basic typographic distinctions, bold, italic, headings, block quotes, and paragraph spacing, are preserved because they map to styling MOBI understands. Inline images embed as MOBI image records and display in place.
Just as importantly, the reading controls stay live. Because MOBI carries reflowable text rather than a frozen page, the reader on the device can still change the font size, the typeface, the margins, and the line spacing, and the book reflows around each choice exactly as it would in the EPUB. That is the practical payoff of both formats being reflowable at heart: converting for an old Kindle does not cost you the adjustable, comfortable reading that makes an ereader worth using. What thins out is only the advanced presentation, the elaborate CSS layouts, custom embedded fonts, and pixel-precise design that a modern EPUB can express and an older container cannot.
What can shift, and when to skip it
Because MOBI is the simpler, older format, expect the occasional rough edge in books that lean hard on design. Complex tables, precise image placement, drop caps, and heavy custom CSS can be simplified, since MOBI has no exact equivalent for every EPUB 3 feature.[2] Embedded fonts and scalable vector graphics may not survive intact. Plain prose, headings, block quotes, and inline images convert cleanly, which covers the overwhelming majority of novels and nonfiction.
Skip this conversion if your Kindle already accepts EPUB, since going to a legacy format only loses fidelity for no gain. If you want a book for reading on any device rather than a specific old Kindle, keeping the EPUB or making a fixed PDF is usually the better call. And if you are trying to feed a modern Kindle, sending the EPUB itself through Send to Kindle is now the supported path, not producing a MOBI at all.
Convert your EPUB to MOBI now
Repackage your ebook for an older Kindle in your browser, with nothing uploaded.
Key takeaways
- EPUB and MOBI both store reflowable text, so your book stays resizable and readable after converting.
- MOBI is a legacy Kindle format, largely retired by Amazon in favor of EPUB and KF8.
- Convert only when you have an older Kindle that will not read EPUB directly.
- Heavy custom styling can be simplified; plain, text-first books convert cleanly.