ToolAct

MOBI to EPUB Converter

Upload a Kindle MOBI e-book and convert it to the universal, reflowable EPUB format

Upload E-book

Drop a MOBI file here, or click to select

Supports .mobi format (DRM-free), max 5 MB

What is MOBI to EPUB?

MOBI to EPUB is an online e-book conversion tool that migrates .mobi files into EPUB, the open e-book standard maintained by the W3C since IDPF merged into it in 2017. MOBI is the Mobipocket format (the company was acquired by Amazon in 2005): its text lives as PalmDOC-compressed HTML fragments inside a Palm Database (PDB) binary container. EPUB takes the opposite approach - it is a standardized ZIP package (the OCF container, defined by ISO/IEC TS 30135) holding standards-compliant XHTML content documents, an OPF package document that describes metadata and reading order, and a navigable table of contents. Both formats are reflowable, so converting between them changes how the book is packaged rather than how it reads: font size, line spacing, and page flow still adapt to any screen.

The conversion pipeline runs in four stages. First the server parses the PDB record table and the three headers packed into record 0 (PalmDOC, MOBI, EXTH) to recover encoding, compression, and metadata. The text records are then decompressed into the original restricted HTML dialect, cleaned up, and normalized into well-formed XHTML an XML parser can accept without complaint. Metadata from the EXTH header maps onto Dublin Core terms (dc:title, dc:creator, dc:language) in the OPF; image records referenced through recindex are extracted as standalone picture files; and filepos anchors are rewritten into explicit id targets so chapter navigation survives the trip. Finally everything is assembled into an EPUB container: mimetype first and stored uncompressed per spec, META-INF/container.xml pointing at content.opf, plus both an EPUB 3 nav document and a legacy toc.ncx so older readers navigate correctly too. Processing happens server-side, and both the upload and the result are deleted automatically once you download.

Why bother migrating? Amazon stopped accepting MOBI through Send to Kindle at the end of 2022 and now recommends EPUB instead; Kobo, Apple Books, Google Play Books, Calibre, and virtually every modern reader treat EPUB as a first-class citizen; and the Mobipocket ecosystem has been frozen for well over a decade. If you hold DRM-free MOBI files - self-made books, public-domain titles, or documents you legitimately own - this tool moves them into a living standard format with one click, no Calibre installation required.

How to Use

How to use

  1. Click the upload area or drag and drop a MOBI file - only .mobi is supported
  2. Click "Convert to EPUB" and the server will decompress, restructure, and package the book in seconds
  3. Once done, click "Download EPUB" to save the file to your device
  4. Need to convert more files? Click "Convert Another File" to start fresh

Conversion Checks

  • Conversion quality depends on how complete the source MOBI's encoding, styles, and images are; older MOBI files cannot embed fonts, so typography in the EPUB is decided by whichever reader opens it.
  • Open the converted EPUB in a mainstream reader before sharing and check chapter jumps, the cover, and inline images - especially for illustration-heavy books.

Use Cases

Move old Kindle purchases into other readersKobo devices, Apple Books, and most Android reading apps no longer import MOBI gracefully, if at all. Convert the DRM-free MOBIs you already own to EPUB once and sideload them everywhere - chapters, cover, and illustrations carry over, and your reader can finally apply its own fonts and themes instead of wrestling with a fifteen-year-old private format.
Re-upload personal files via Send to KindleAmazon's Send to Kindle now accepts EPUB but has dropped MOBI. If your personal MOBIs never came from the Kindle store, convert them here first and send the resulting EPUBs - Amazon translates them server-side so the same book syncs across all your Kindle devices and apps, reading positions included.
Publish homemade or public-domain books widelyOlder writing workflows exported MOBI alongside everything else, while today every major storefront and library platform asks for EPUB uploads. Converting your back catalogue once gives you a distributable master copy that passes ordinary validation - not a dead-end format readers have to hunt down software for.
Future-proof long-term archivesThe Mobipocket format has been frozen since the store closed, and each OS update makes opening such files slightly harder. EPUB is an open standard backed by permanent free tooling (epubcheck validation, cross-platform readers), so archiving your titles as EPUB keeps them openable decades from now.
Share books with people who don't use KindleHanding someone a .mobi usually sends them hunting for compatible software. Nearly every device opens EPUB out of the box or with a free app like Thorium or Calibre. The converted file keeps your original filename with a .epub extension, so recipients know exactly what they received.

Technical Principle

A MOBI file is a Palm Database (PDB) binary container following the PalmOS database specification. It opens with a 78-byte header: a database name (32 bytes), attributes, version, creation/modification times, a type identifier (usually BOOKMOBI), a creator identifier (MOBI or TEXt), the record count, and a record offset table - one entry per record giving its byte position in the file. Everything (text, images, indices) is chopped into roughly equal chunks of about 4096 bytes stored sequentially as records: record 0 holds the headers, records 1 through N the compressed text, later records the images.

Record 0 packs three consecutive headers. The PalmDOC header declares the compression scheme (1 = none, 2 = PalmDOC LZ77 dictionary compression, other values meaning Huffdic Huffman dictionaries), total text length, text record count, per-record size, and encryption type - a nonzero encryption field marks DRM, which the converter refuses to touch. The MOBI header adds text encoding (CP1252 or UTF-8), the index of the first image record (firstImageIndex), and the EXTH flag. When set, the EXTH header follows immediately: a series of type-length-value entries carrying author, updated title, publisher, ISBN/ASIN, publishing date and similar metadata.

The body text decompresses record-by-record into a restricted HTML dialect close to HTML 3.2/4: limited CSS support, no SVG or embedded fonts, images referenced as <img recindex="00001"> pointing at the nth image record after firstImageIndex, and table-of-contents anchors written as byte offsets like <a filepos="0000023289">. To become EPUB this markup must be upgraded to well-formed XHTML: tags closed and nested correctly, attributes quoted, unsupported constructs folded into safe equivalents, recindex references rewritten into manifest image entries such as <img src="images/xxx.jpg">, and every filepos target given an explicit id attribute so chapter links keep working.

Assembling the EPUB then means building the OCF ZIP container. The mimetype entry (containing exactly application/epub+zip) must be the first file in the archive and stored uncompressed; META-INF/container.xml points to the package document; content.opf lists every component in the manifest and fixes the linear reading order in the spine, while its metadata block carries Dublin Core terms mapped from EXTH fields (author to dc:creator, updated title to dc:title, and so on). Navigation is written twice - an EPUB 3 nav.xhtml for modern readers and a legacy toc.ncx for backward compatibility. On the desktop side, Calibre's ebook-convert ships a mature MOBI input plugin and remains the de facto command-line standard, and KindleUnpack can split a MOBI into HTML plus images beforehand. This tool only processes DRM-free MOBI - Amazon-encrypted purchases cannot be parsed - and .azw3/KF8 files use a different, EPUB-like structure requiring their own converter.

  • PDB container structure: 78-byte Palm database header (database name, type BOOKMOBI, creator, record offset table); all content split into roughly 4096-byte records stored sequentially
  • Record 0 holds three headers: PalmDOC header (compression scheme, text length, encryption type) -> MOBI header (encoding CP1252/UTF-8, firstImageIndex, EXTH flag) -> EXTH header (type-length-value metadata such as author and title)
  • Text recovery: records 1 through N are decompressed per the PalmDOC header (none / PalmDOC LZ77 / Huffdic Huffman) and concatenated into the source HTML
  • HTML upgrade: the restricted HTML is normalized to well-formed XHTML; recindex image references become manifest files; filepos byte anchors become explicit id targets
  • Metadata mapping: EXTH fields map onto Dublin Core terms (dc:title, dc:creator, dc:language...) in the OPF metadata block
  • OCF packaging: uncompressed mimetype entry first, META-INF/container.xml, content.opf manifest + spine reading order, navigation written both as EPUB 3 nav.xhtml and legacy toc.ncx
  • Limits & ecosystem: DRM-free input only; Calibre ebook-convert and KindleUnpack cover desktop needs; Amazon's Send to Kindle accepts only EPUB since late 2022

Examples

Revive an Old Kindle Library

Convert years-old DRM-free MOBI novels to EPUB once, then read them on Kobo, Apple Books, or any phone reader

Send Personal Files to Kindle Again

Amazon retired MOBI uploads - turn your own MOBIs into EPUB and let Send to Kindle sync them to every device

Distribute Public-Domain Classics

Package public-domain titles as validated EPUB masters ready for storefronts, libraries, or project uploads

FAQ

Does my MOBI file stay on my device?

No. The .mobi file is uploaded to our conversion server, rebuilt there as an EPUB package, and returned as a download. Treat anything you upload as if it leaves your device, and avoid sending unredacted sensitive material. Both the uploaded file and the converted result are deleted from the server automatically.

Which e-book formats does this tool accept?

Only .mobi. For fixed-layout output meant for printing, use our MOBI to PDF tool instead; .epub sources are handled by the EPUB to PDF tool; and .azw3/KF8 - MOBI's modern successor whose structure sits closer to EPUB itself - needs its own AZW3 converter.

Can I convert DRM-protected MOBI files?

No. Titles locked with Amazon's DRM cannot be opened by the converter. Use a DRM-free MOBI obtained legitimately - a book you made yourself, a public-domain title, or a file you have explicit permission to convert.

Are the table of contents, cover, and images preserved?

Yes, wherever the source provides them. Chapter markers recovered from the MOBI's embedded index or filepos anchors become entries in both navigation documents so readers can jump between sections; a suitable early image record is flagged as the cover; inline JPEG/GIF/BMP pictures are extracted into individual manifest-listed files. A MOBI that never contained a proper index simply yields text without TOC links.

Should I convert my MOBI to EPUB or to PDF?

It depends on what happens next. EPUB keeps the text reflowable - readers pick their own font, size, and theme, and the book adapts, which is ideal for actual reading on phones and e-readers. PDF freezes a fixed layout with stable page numbers, ideal for printing, citation, and preserving a specific look. Choose EPUB when the goal is reading anywhere; choose PDF when the goal is exact pages.

Can I send the converted EPUB back to my Kindle?

Yes. Since late 2022 Amazon's Send to Kindle accepts EPUB and no longer takes MOBI: emailing or uploading the converted file lets Amazon translate it on their servers, and the book syncs across your Kindle devices and apps with reading progress intact. Direct sideloading behavior varies by firmware generation, which is another reason going through Send to Kindle is the dependable route.

Why is the resulting EPUB bigger or smaller than my MOBI?

Both formats compress aggressively, so plain-text novels usually come out about the same size or smaller. Differences appear with media-heavy books: EPUB stores each image as a separate standard file, which the ZIP layer deflates globally, while the added structural overhead (OPF, nav documents, XML namespaces) contributes a few kilobytes either way. Check the size-change figure shown in the result panel for how it played out for your specific book.