KCC (Kindle Comic Converter): fullscreen manga for E-ink readers

What KCC fixes that generic ebook converters do not

Most manga conversion pipelines for E-ink readers produce pages with visible margins. KCC's stated goal is the opposite: true fullscreen from top to bottom, with fixed layout support so the reader does not reflow the page. That single constraint drives everything else in the project.

The audience is comic and manga readers, not publishers. The README draws that line explicitly: KCC is not Amazon's Kindle Comic Creator and is not endorsed by Amazon. Amazon's tool is aimed at publishers and, per the README, involves a lot of manual effort. KCC assumes you already own the files and want them on your device with as little work as possible.

Input can be JPG or PNG files in folders, archives such as CBZ or EPUB, or PDF. Output can be MOBI or AZW3, EPUB, KEPUB, CBZ, PDF, or a folder of images. The README points at DRM-free PDFs from Humble Bundle or Fanatical as the highest quality source, noting those files can be x12000 resolution while even a 10 inch Kindle Scribe is x2480. That gap is the whole argument for downscaling rather than shipping the original.

The conversion pipeline: downscale, fix black levels, split spreads

The README describes four concrete transformations. First, KCC downscales to the native resolution of your specific device. The README gives one figure: a 600 MB manga volume from Humble Bundle compressed to 100 MB, mostly through that downscale. It also claims this improves battery life, page turn speed and general performance on underpowered readers with small memory and storage.

Second, it corrects black levels, which the README frames as a fix for the gray or faded blacks found in many Kindle Store manga. Third, it addresses the rainbow effect on Kaleido 3 color E-ink without blurring. Fourth, it can semi-automatically detect 2-page spreads from pages that were pre-split into single images, and the reader can view combined spreads rotated or not, with the split halves placed before or after the combined spread.

Two paths exist for the output stage. Without a jailbreak, MOBI manga opens in Kindle's native reader. With a jailbroken Kindle running KOReader, the README lists three gains: 4-bit PNG and WEBP support (visually lossless on a 4-bit E-ink panel, described as better quality at half the file size of 8-bit JPG), no dependency on kindlegen (described as up to twice as fast conversions, converting to CBZ directly), and dithering or cropping inside KCC instead of KOReader.

Installing KCC and a first conversion

The README sends you to the releases page and tells you to click Assets on the latest release. Pick the asset matching your machine: `KCC_*.*.*.exe` for Windows, `kcc_macos_arm_*.*.*.dmg` for Apple Silicon, `kcc_macos_i386_*.*.*.dmg` for Intel Macs on macOS 14 or later. Legacy macOS 10.14+ and Windows 7 experimental builds also exist. The `c2e` and `c2p` assets are command line tools for power users. Flatpak, Docker and AppImage versions are documented in the wiki rather than the README.

If you would rather install from source, setup.py documents the Python package route:

python3 setup.py install

Running that installs KCC as a Python package. The same file documents the binary build commands, `python3 setup.py build_binary`, `build_c2e` and `build_c2p`, which are for producing release artifacts, not for normal use.

The GUI workflow is deliberately short. Drop your input files into the KCC window, press convert, then copy the output onto your device's `documents` folder over USB. The README notes that most people only need the options checked in its screenshot, and that hovering over each option shows a tooltip. Some checkboxes can show a half-check mark, which is a tri-state rather than a simple on/off. After the copy, the converted comics appear in the reader's library alongside regular books.

Two platform notes matter before you start. On macOS, if the app refuses to open, the README points to Apple's guide for opening an app from an unknown developer. And if you are on macOS with a 2022 or newer Kindle, the README says you may need Amazon USB File Manager for Mac or OpenMTP.

Where KCC is the wrong tool

The README carries a warning that is easy to skim past: Kindle Scribe 2025 MOBI support is limited and converted books may have blank pages, with PDF recommended instead. If your target device is that model, the default output path is the one that fails, and you should plan around it rather than discover it after a batch conversion.

The KOReader benefits are conditional. 4-bit PNG and WEBP output, the faster CBZ path without kindlegen, and in-KCC dithering all require a jailbroken Kindle. On a stock device you get the MOBI/AZW3 route and its constraints. That is a meaningful fork in what the tool can do for you, and it depends on a decision about your hardware, not about KCC.

The README's FAQ answers one question bluntly: should you use Calibre? No, because per the README Calibre does not properly support fixed layout. That is a strong claim stated without qualification, and it is the kind of thing worth verifying against your own files if Calibre is already part of your workflow.

Finally, KCC is a desktop and command line tool. There is no hosted converter and no Android build in the README, so a phone-only reading setup is out of scope.

KCC versus Amazon's Kindle Comic Creator

The comparison the project itself invites is with Amazon's Kindle Comic Creator. The README states plainly that KCC is not that tool and is not endorsed by Amazon. The difference in approach is about who does the work. Amazon's tool targets comic publishers and, according to the README, involves a lot of manual effort. KCC targets readers and tries to reduce the job to dropping files in, pressing convert, and copying the result to the device.

There is a second, less obvious difference. Amazon's tool is tied to Amazon's ecosystem. KCC outputs to MOBI/AZW3, EPUB, KEPUB, CBZ, PDF or plain image folders, and the README names Kindle, Kobo and ReMarkable as targets, with KOReader as an optional path. If you read across more than one brand of E-ink device, that output spread is the practical argument.

The README also disposes of a naming collision: `KC2` is not a replacement for KCC, and the project says it will carry on developing. That matters because searching for "Kindle Comic Creator" and "Kindle Comic Converter" returns overlapping results, and the two tools are not interchangeable.

Maintenance, licensing and upgrade cost

The repository is not archived, and the last push was on 2026-09-21. Releases v11.3.0, v11.3.1 and v11.3.2 all landed on 2026-09-16 and 2026-09-17, so the project is shipping patch releases on a short cycle. The README lists Alex Xu as active from 2023 to present, with the founder and a previous maintainer listed as active in earlier periods.

KCC is licensed under the ISC license, a short permissive license in the same family as MIT and BSD. The practical implication for most readers is that you can use and redistribute the tool freely; if you plan to bundle it inside a commercial product, read LICENSE.txt in the repository rather than relying on this summary. Nothing here is legal advice.

The upgrade cost is mostly environmental. requirements.txt pins PySide6 below 6.10 and sets floors for Pillow, psutil, requests, python-slugify, packaging, mozjpeg-lossless-optimization, natsort, numpy and PyMuPDF. The Dockerfile pins numpy at 2.3.4 and PyMuPDF at 1.26.6 explicitly because, in the Dockerfile's own comment, they take too long to compile. If you build from source, expect those two to dominate install time. If you use the released binaries, upgrades are a download and replace.

The README also notes commissions and sponsors, including free code signing on Windows from SignPath.io. That is why Windows builds carry a signature rather than tripping SmartScreen, and it is a maintenance dependency worth knowing about if the signing arrangement ever changes.

Editorial conclusion

Adopt KCC if you read DRM-free manga or comics on an E-ink device and want pages downscaled to that screen's native resolution instead of the margins most converters leave. Skip it if you need a hosted converter or an Android app: the project ships desktop binaries, c2e and c2p command line tools, plus Docker, Flatpak and AppImage builds described in the wiki. Before committing, check the release assets for your platform, read the warning about limited MOBI support on the 2025 Kindle Scribe, and confirm your source files are DRM-free PDFs, CBZ or image folders.

Frequently asked questions

Official sources

1. ciromattia/kcc on GitHub
2. Issues
3. License: ISC
4. README
5. Releases