In a recent communication, Amazon has alerted Kindle users about significant changes set to take effect from next month. The notification pertains to the phasing out of support for sending MOBI (.mobi, .azw, .prc) files through the “Send to Kindle” feature, starting November 1, 2023. This change, as News18 pointed out, specifically impacts users attempting to send MOBI files via email and Kindle apps on iOS, Android, Windows, and Mac.
Why are kfx files often larger and sometimes double the size?
Lacks compression?
Don’t know if it really matters, though. 8GB of storage holds a lot of books, even if they’re illustrated, and that’s what base-model e-readers are coming with.
It matters to me, since I find the differences in sizes to be stark when I compare them. I already find page turns on my Paperwhite a tad slow (even with page refresh off). So converting all of my books to kfx (which was my initial plan) seems like a bad idea.
KFX is actually faster at page turning, as it doesn’t need to calculate how to spread words to fill the most lines per page.
That makes sense to me. Access speed and disc space are often inversely related. It’s like pre-optimizing the file for faster consumptionater by adding more information at “compile time” vs “run time”.
A source to read more about this and how exactly kfx works and it’s enhanced typesetting would be cool.
Do you know of alternative methods of producing kfx files other than the official Amazon app and Calibre’s plugins for it?
And how would I go about editing a kfx file?