Reference Formats
MOBI
A reflowable eBook container built on the Palm Database format, used by early Amazon Kindle devices before Amazon deprecated it in favor of KF8/AZW3 and KFX.
Extension
.mobi
Full name
Mobipocket eBook / Kindle MOBI Format
Introduced
2000 (as Mobipocket, originally .prc); adopted by Amazon for the first Kindle in 2007
Vendor
Mobipocket SA (acquired by Amazon in 2005)
What is inside the container
A MOBI file is a Palm Database (PDB) container wrapping simplified HTML-like markup, embedded images, and a metadata header (title, author, ASIN, cover). Early MOBI (Mobipocket-era) supported only basic HTML 3.2-style formatting with no CSS; Amazon's later KF8/AZW3 generation, sometimes still saved with a .mobi/.azw3 extension, added HTML5/CSS3 support. It carries no fixed layout, DRM is optional but common on Amazon-distributed copies, and it has no relation to 3D or image asset structures — it is purely textual/document content with inline raster images.
How to open it
For archives
Amazon stopped accepting MOBI uploads to Kindle Direct Publishing in 2021, so MOBI is a legacy delivery format, not a target for new production — a DAM holding MOBI files should treat them as archival source material and convert a working copy to EPUB (the open, actively maintained standard) for long-term preservation and repurposing. Most DAM platforms cannot render eBook text-flow previews at all; at best they generate a thumbnail from the embedded cover image and expose title/author metadata, so plan on an external reader or Calibre-based conversion step for actual content QA. Keep the original MOBI alongside any converted EPUB rather than replacing it, since older Kindle devices and some publishing workflows still expect it.
MOBI began life as the native format of Mobipocket, a Paris-based company founded in 2000 that built an e-reading application for early PDAs and smartphones. The format packaged text and images inside a Palm Database (PDB) container inherited from Palm OS, a pragmatic choice at the time since Palm devices were among the first mainstream e-reading platforms. Amazon acquired Mobipocket in 2005, two years before launching the first Kindle, and adapted the format — adding its own DRM layer — to become the Kindle’s original AZW/MOBI ebook format.
Amazon subsequently layered newer formats on top of the original MOBI shell: KF8 (also called AZW3) added HTML5 and CSS3 support in 2011 for the Kindle Fire, and KFX arrived in 2015 with improved typesetting, both still sometimes distributed with a .mobi extension in casual use even though the underlying structure had changed substantially. In 2021, Amazon dropped MOBI as an accepted input format for Kindle Direct Publishing, formally retiring it in favor of EPUB ingestion, which KDP converts internally.
For a DAM, MOBI shows up almost exclusively as legacy backlist content — publisher archives, self-published author libraries, or digitized backlists that predate the EPUB-first workflows most publishing DAMs now standardize on. Because the format is deprecated at the source (Amazon) and unsupported for new submissions, the practical DAM task is triage and conversion: identify which assets are MOBI-only, convert working copies to EPUB, and retain the MOBI as a dated original rather than a distribution-ready file.
Frequently asked
Can a DAM preview the contents of a MOBI file directly?
Most DAM platforms cannot render MOBI's text flow; they can extract the embedded cover image and PDB metadata (title, author, ASIN) for a thumbnail and record card, but reading the actual book requires an external tool like Calibre or a Kindle app.
Is MOBI still a valid format to store as a delivery asset?
No — Amazon stopped accepting MOBI for new Kindle Direct Publishing uploads in 2021, so it should be treated as a legacy or archival format rather than a current distribution target; EPUB is the modern submission format.
What's the difference between MOBI, AZW, AZW3, and KFX in a DAM inventory?
MOBI is the original Mobipocket-derived format; AZW is MOBI plus Amazon DRM; AZW3/KF8 added HTML5/CSS3 support in 2011; KFX (2015) is Amazon's newer proprietary format with improved typesetting — a DAM should tag each precisely since they aren't interchangeable.
How should a publishing DAM convert legacy MOBI assets?
Batch conversion through Calibre (open source, scriptable via its command-line tools) to EPUB is the standard approach; the EPUB becomes the new master and the MOBI is retained as the dated original for provenance.
Does MOBI carry usable metadata fields for a DAM catalog?
Yes — the PDB header and MOBI-specific fields carry title, author, publisher, ASIN, and language, which most conversion and metadata-extraction tools can read and map into DAM catalog fields.
Can MOBI files be DRM-protected, and does that affect DAM storage?
Yes, Amazon-distributed MOBI/AZW files are often DRM-locked to a specific Amazon account; a DAM should flag DRM status explicitly since DRM-locked files cannot be freely converted, re-rendered, or redistributed even internally.
Why would a DAM still encounter MOBI files in 2026?
Backlist publisher archives, author personal libraries, and pre-2021 distribution copies that were never migrated; MOBI persists as historical source material even though it's no longer a live production format.
Is MOBI related to 3D or image asset formats in a DAM?
No — despite superficially fitting into a generic 'file formats' list, MOBI is a text/eBook container with embedded raster images, unrelated to 3D geometry or CAD interchange formats; it should be filed under document/publishing assets, not 3D assets.
Sources
- Mobipocket SA was a French company incorporated in March 2000 that created the .mobi e-book format checked 2026-08-07 — Wikipedia — Mobipocket
- Amazon acquired Mobipocket in 2005 and later adapted its format for the Kindle, adding AZW3/KF8 in 2011 and KFX in 2015 checked 2026-08-07 — Wikipedia — Kindle File Format
- Amazon retired direct MOBI uploads to KDP in 2022, no longer accepting MOBI as an input format checked 2026-08-07 — How-To Geek — What Is a MOBI File