User Rating 0.0
Total Usage 9 times
Source & Metadata
📁

Drag text or HTML file here

Supports .txt, .html (Max 20MB)

PalmDOC Compression
Auto-Chapter Detection
Cover & Output
📷

Drop Cover JPG

600x800 recommended
Conversion Log
System ready. Engine initialized.
Ready 0%
Is this tool helpful?

Your feedback helps us improve.

About

This is not a wrapper. This is a full-scale binary compiler for the Mobipocket file format, running entirely in your browser. Unlike generic converters that rely on server-side scripts (exposing your intellectual property), this tool constructs the Palm Database (PDB) structure bit-by-bit locally.

We solve the specific fragmentation problem of the e-Reader ecosystem. While the industry moves to EPUB, millions of robust, functional E-Ink devices (Kindle 3, 4, Voyage, Oasis) still rely on the legacy MOBI standard. The challenge is not just wrapping text; it is managing the PalmDOC compression (LZ77) to ensure large manuscripts fit on devices with limited storage, and correctly calculating the EXTH Headers so that cover art appears on the lock screen - a notorious failure point in open-source tools.

This engine implements the MOBI 6 standard, ensuring backward compatibility while utilizing modern high-density cover images. It handles the record offset calculations, bitwise attribute flags, and text encoding normalization automatically.

kindle converter mobi generator ebook tools epub to mobi palmdoc compression offline converter

Formulas

The core of the MOBI format is the Record List Offset calculation. The file is a sequence of headers followed by a list of pointers to data chunks. The offset O for the i-th record is defined as:

Oi = Hpdb + (N × 8) + 2 + i-1k=0 len(Rk)

Where N is the total number of records, 8 is the size of a record entry (4 bytes offset + 4 bytes attributes), and 2 is the gap padding.

PalmDOC Compression Efficiency:
The compression ratio η is determined by the frequency of repeated substrings. A length-distance pair <L, D> replaces a string if:

3 L 10 D < 2048

If the overhead of the pair (2 bytes) is less than the length of the string L, compression occurs.

Reference Data

Technical ParameterStandard MOBI (Legacy)This Converter (Engine v2.0)Kindle Limit (Ref)
Container FormatPalm Database (PDB)PDB + MOBI Header v6N/A
Compression AlgoNone / PalmDOCAdaptive PalmDOC (LZ77)Slow Decompression
Record SizeVariable4096 Bytes (Fixed)Max 4096
Max Text SizeUnbounded20 MB (Browser Safe)Device RAM
Cover ImageEmbedded in TextEXTH Record 201127 KB
Character EncodingASCII / Latin-1UTF-8 (65001)UTF-8
Navigation (NCX)Manual InlineRegex HeuristicsXML / NCX
Header Overhead~80 Bytes~300 Bytes (Rich Meta)Flexible

Frequently Asked Questions

The PalmDOC (LZ77) algorithm requires scanning the text window for every byte to find repeating patterns. For a large book (e.g., 500k words), this involves millions of comparisons. We perform this on the main thread to ensure data integrity, which may cause a momentary visual pause. We utilize an adaptive chunking method to keep the browser responsive.
No. Sideloaded files (files transferred via USB) do not sync reading progress across devices via Amazon's servers. They are treated as "Personal Documents". However, they will function perfectly on the specific device you transfer them to, including font resizing and dictionary lookups.
This refers to the "Cover Offset" metadata in the Extended Header. If this pointer is missing or incorrect, the Kindle will default to a generic document icon. Our engine explicitly calculates the byte offset of the injected image record and writes it to EXTH Type 201, ensuring your cover art appears in the library grid.
This is a legacy constraint of the Palm OS filesystem, which the MOBI format is built upon. While modern processors could handle larger blobs, the internal addressing system of the format (and older e-reader firmware) expects text to be segmented into 4KB chunks. Violating this can cause the device to crash or display blank pages.
Once converted to a binary .mobi file, editing requires a hex editor or specialized software like Calibre. It is strictly recommended to verify all metadata (Author, Title, ISBN) in our dashboard *before* clicking "Build Binary".