exhentai-manga-manager: The Offline Library That Thinks Like E-Hentai

A local-first Electron app that scans archives, extracts covers, maps tags, and makes a private manga collection search like a live metadata service.

8 min read • View on GitHub • More from SchneeHertz

A crowded stack of unlabeled archive boxes and folder tabs transforms into a disciplined wall of catalog cards, tags, and thumbnail slots. The scene explains how the app turns raw local files into a searchable metadata library.
The core idea is not storage. It is translation: archives on disk become a metadata-rich index that feels web-native.

I wrote a software to read compressed files downloaded from exhentai. https://github.com/SchneeHertz/exhentai-manga-manager. However, you still need to be able to access exhentai in order to use it more effectively.

SchneeHertz, Author / Lead Developer · r/DataHoarder thread on gallery apps
Key Takeaways

Most manga managers stop at browsing. exhentai-manga-manager goes after a sharper problem: how to keep the metadata intelligence of E-Hentai alive after the files are downloaded, renamed, and scattered across local storage. That is why it matters to collectors who care about tags, comments, and search behavior, not just page viewing.

Why This App Exists

The project exists because folder names are a weak substitute for a real library model. A scan of archives can tell you what files you own, but not how those files should be categorized, searched, or compared the way a web gallery would do it. SchneeHertz built a desktop app to preserve that richer layer offline.

A hedcut-style portrait of SchneeHertz based on a verified GitHub avatar. The portrait identifies the maintainer behind the project and grounds the article's origin story in a real contributor.

The Core Trick: Local Files, Web-Style Metadata

The app keeps two worlds distinct. One world is the archive on disk, whether it is a ZIP, RAR, 7z file, or plain folder. The other world is the SQLite-backed metadata layer, where tags, covers, and searchable fields live. That split is the whole product.

This diagram shows the app as a translation pipeline, not a folder browser. Files enter on one side, metadata-rich library behavior comes out the other.

TaskFolder browserexhentai-manga-manager
Find a bookSearches names or directory structureSearches tag-rich metadata and localized labels
Display a coverUsually renders pages or thumbnails on demandExtracts and caches a cover image from the archive
Preserve gallery semanticsNoYes, including E-Hentai-style tag logic
Run without a serverYes, but shallowYes, while still keeping a structured index
Handle metadata depthMinimalDesigned around it

What Happens When You Scan a Library

Ingestion is where the app turns from a reader into a database builder. It detects the container, enumerates files, picks the first image for a cover, hashes it, stores the thumbnail in a cover path, and writes the manga record into SQLite. The point is not just speed. It is repeatability.

detect container
  -> enumerate pages
  -> select first image
  -> generate thumbnail
  -> hash and cache cover
  -> write manga + metadata rows
  -> normalize tags for search
  -> expose results in the UI
A close-up mechanical sorter moves one archive file through a series of precise stages: image extraction, hash stamping, and card filing. A larger interface hand handles the visible app, while a smaller precision tool handles heavy file work. The image explains why the app splits UI work from performance-critical processing.
Rust is not decorative here. It absorbs the expensive file and image work so the interface stays responsive when the library gets large.

The Search Model Is the Real Product

The search experience is not generic filtering. The Pinia store translates raw tags into E-Hentai-style search syntax, localized display strings, and category letters that mirror the source ecosystem. That means the UI is not merely showing metadata. It is speaking the same language as the archive culture it was built for.

Search methodWhat it knowsWhy it falls short
Filename searchOnly visible namesMisses the tag structure that collectors actually use
General media server searchTitles and basic metadataUsually lacks E-Hentai-specific tag syntax
exhentai-manga-managerTranslated tags, categories, and search stringsBuilt for a very specific metadata system, which is exactly the point

That makes the app feel different from a normal library manager. You are not just narrowing a list. You are querying a local clone of a niche metadata ecosystem, with enough fidelity to make offline browsing feel strangely complete.

Why Rust Is in the Room

Electron and Vue handle the interface, but the project does not pretend JavaScript should do everything. The Rust component is the escape hatch for work that becomes costly at library scale, especially image decoding and archive-heavy operations. That boundary keeps the desktop shell pleasant while the engine does the hard labor elsewhere.

This is a practical architecture choice, not a language trophy. If the app is meant to scan thousands of compressed galleries on external drives, then the expensive part needs a lower-level toolchain than the UI layer can comfortably provide.

Why This Beats a General-Purpose Media Server

Komga and Kavita are strong at broad media-server problems. LANraragi is powerful for archive management. exhentai-manga-manager wins when the problem is narrower and stranger: a private collection that needs ExHentai-style metadata fidelity, portability, and no always-on server.

ProjectServer requiredExHentai-style metadataPortable/offline useBest fit
exhentai-manga-managerNoStrongStrongCollectors who want a local metadata engine
LANraragiYesStrongModerateUsers who want a hosted archive manager
KomgaYesLimitedModerateGeneral comics and manga libraries
KavitaYesLimitedModerateBroad ebook and manga serving

That difference is bigger than setup convenience. A serverless desktop app can live on an external drive, travel between machines, and keep private archives self-contained without losing the tag depth that makes the source ecosystem useful.

Who It Is For

This is for people who already know they want more than a viewer. If your library lives on a drive, if you value privacy, if you want archive formats to stay readable without a daemon in the background, and if tag fidelity matters as much as page access, this app makes sense immediately.

It is specialized by design. That specialization is the selling point, because it lets a local machine behave like a tiny, private metadata service without pretending to be a general media platform.