Try the release before taking on a source build
Koharu is worth evaluating if your manga workflow needs OCR correction, translation and page composition in one editor. Our source build at commit 988a6cd stopped when pkg-config could not find GTK4. We did not launch the desktop application or measure translation quality.
The installation guide recommends a release build for translation work and development setup for changing Koharu's code. For an editor assessing the workflow, the release is the sensible starting point. It still needs a trial on the intended machine and a representative page.
The English README documents selectable detection, OCR, translation and inpainting stages at page or project scope. It also describes proofreading, manual cleanup, text placement and layered PSD export. These are documented capabilities; their output quality was not established by our run.
What happened when we ran it
On September 29, 2026, our sandbox installed 1,544 dependencies in 460 seconds and used 2,143 MB on disk at commit 988a6cd. The build failed with exit code 1 after 336 seconds. Vitest completed successfully in 30 seconds with 102 passes and no failures.
The build log reports that pkg-config could not find gtk4. It says the required gtk4.pc file needs to be installed and its parent directory included in PKG_CONFIG_PATH, which was unset. This establishes a failed GTK4 lookup. It does not distinguish an absent installation from a search-path problem, or show a defect in OCR, translation or inpainting.
The recorded sandbox configuration had 3 CPUs, 8 GB RAM and image lab-node:22. The label does not establish an actual Node or operating-system version. The checkout contained 783 files and roughly 212,717 source lines, with monorepo workspaces. The dependency footprint describes that source workspace, not a downloaded release or its model collection.
The passing Vitest suite does not establish desktop launch, canvas initialization, inference quality or export behavior. Those remain untested in this run.
Downloads and graphics remain part of release evaluation
The installation guide describes release packages for Windows, macOS and Linux. It also tells Linux users to install desktop-library dependencies reported by their package manager, so choosing a release does not guarantee an environment without additional setup.
First launch can take longer while native packages download. Model files download when you first use the selected model. The guide names GitHub release assets, PyPI for CUDA and AMD's repository for ROCm as runtime sources, with model weights from Hugging Face. Prepare the selected assets before relying on an offline workflow.
The editor canvas uses WebGPU and requires a current graphics driver even when inference runs on the CPU. CPU inference therefore does not remove the graphics requirement. The README also documents Metal on Apple silicon and CUDA, ROCm/HIP and Vulkan on Windows and Linux, with compatibility depending on the selected path. Our run provides no inference results with which to rank them.
Translation can use a local language model or a remote API. Choose the processing route according to the project's privacy requirements before importing unpublished pages. Local inference and hosted translation are separate options.
Source contributors should follow the platform setup instructions linked from the README. Rust, Bun and LLVM are prerequisites; installing the Bun workspace alone did not establish that our native application could build.
Compare batch work with interactive correction
Manga Image Translator documents a local batch mode. Evaluate it when processing a folder through a batch command is your starting point.
BallonsTranslator documents mask editing and WYSIWYG rich-text editing. Compare it when repairing cleanup masks and adjusting lettering are central to your workflow. Neither alternative was measured against Koharu in our sandbox.
What the documentation rating means
Documentation receives 4 on this editorial scale: 1 means essential instructions are absent, 3 means a usable path has material gaps, 4 means the supplied instructions explain the main evaluation requirements but have not been checked across all documented paths, and 5 requires independently checked coverage across those paths. The English README and installation guide explain release selection, first-launch downloads, graphics requirements and the distinction between translation work and source development. That supports the documentation judgment, not a compatibility guarantee.
Setup ease, community support and finished-product maturity remain unassessed. We did not reproduce release installation and launch, inspect support responsiveness, or exercise model output and exports.
For your trial, choose a page with narrow speech bubbles and lettering over artwork. Run the selected stages, correct the text and cleanup, then inspect both the preview and exported layers. The adoption decision is how much correction that page still needs on your machine.

