How Manga2Ink works

From chapters to books

Manga2Ink converts and optimizes manga and comics for e-readers, with chapter organization and local sharing in the same desktop app. Its page settings cover dimensions, margin cropping, contrast, grayscale or color output, and double-page spreads. See conversion settings to choose your device and format, and advanced conversion options for examples of what each setting changes.

Choose a chapter folder, a library of manga folders, or a CBZ. Check the volumes, set your device and format, and process the queue. You can then save the books or share them with your reader.

Behind the scenes

Two tools handle the processing:

• mangabind groups chapters into volumes.
• mangaprep adjusts the pages and creates EPUB, CBZ, or PDF books.

Both come with Manga2Ink.

Local processing

Organization, conversion, and saving happen on your computer. Online searches for volume information or an author are optional. They use the title you enter and the selected work’s identifier and language where needed; your manga pages stay local.

Network sharing is enabled from the Share panel. Keep the app open while your reader downloads the books.

Known limitations

Manga2Ink is an alpha.

• A whole series in one CBZ has no table of contents or bookmarks; an EPUB has a table of contents and a PDF has bookmarks.
• The author is written into EPUB and PDF books only. A CBZ carries no author.
• Pending books are local to this installation and are not a backup. Once a conversion has been deleted, or cleaned up after all its books were saved, getting its books again means processing the source again.
• Sharing the ready books shares all of them, including old conversions that were never saved or deleted.
• A link in a manga folder, or in a shared folder, that leads outside that folder is not followed.
• The app is in English, Brazilian Portuguese and Japanese, as the guide is.
• Updates are manual: the app can tell you that a newer version is out (App settings, Updates), but you download and install each release yourself.
• The installers are not code-signed or notarized, and no build attestation (a signed record of where each file was made) is published.
• macOS builds are for Apple Silicon only. There is no AppImage, and the Arch package is a direct download, not an AUR submission.

Follow the quickstart to try it. For implementation details, see the architecture guide.