Comic Library Utilities

Open-source comic library management, honestly reviewed. Written for people who want control over their CBZ files, not just another thing to stream them.

TL;DR

• What it is: A Docker-based comic library management and editing tool — not primarily a reader, but a utility layer for organizing, converting, metadata-scraping, and batch-editing CBZ/CBR/PDF collections [README][1].
• Who it’s for: Comic collectors with large libraries who need to clean up filenames, fix metadata, download from GetComics, or manage their files remotely without SSH access to the server [README].
• Cost savings: $0 license (GPL-3.0). CLU is self-hosted only — there’s no SaaS tier to compare. The savings come from replacing time spent on manual file management, not a recurring subscription [README].
• Key strength: Hands-on library surgery that Komga and Kavita don’t offer — GUI editing of CBZ internals, bulk operations, auto-download from GetComics.org, and metadata scraping from multiple providers including Metron, ComicVine, MangaDex, and GCD [README][1].
• Key weakness: 203 GitHub stars as of this review — this is a small, one-developer project with a growing but still modest community. It is not a feature-equivalent replacement for Komga as a reading server; it’s a management companion that is gradually becoming standalone [README][1].

---

What is Comic Library Utilities

Comic Library Utilities (CLU) started as a set of utilities the developer built while migrating a 70,000+ comic library to Komga [README]. That origin story matters because it explains what CLU actually is: a tool built by someone who hit the wall of what file managers and comics servers can do, and decided to write the missing pieces themselves.

The project has since pivoted away from being a Komga accessory. As of v4.0, CLU includes its own visual collection browser, reading history tracking, and reading streaks, positioning it as a standalone app [1][website]. Whether it fully replaces Komga or Kavita depends on what you need — more on that below.

The core premise is browser-based remote management of a comic library that lives on a server or NAS. You access CLU through a web interface, navigate your filesystem, and perform operations that would otherwise require SSH, command-line tools, or manually unzipping CBZ files on a desktop machine. The app handles CBZ, CBR, and PDF formats and runs entirely on Docker [README].

The developer — GitHub username allaboutduncan — is actively shipping. The project went from v4.3 to v4.12 in roughly two months, adding manga metadata support, multiple library configurations, and Komga reading sync in the process [1]. There’s a Discord community and a growing number of contributors, though this is still largely a one-person operation.

---

Why people choose it

The comparison that appears repeatedly in community discussions is CLU versus the “just use Komga” answer. They’re solving different problems.

Komga is excellent at serving comics — browsing, reading, user accounts, OPDS feeds. It is not built for editing your library. If your CBZ files have wrong covers, broken metadata, inconsistent filenames, or embedded ads on the first page, Komga doesn’t help you fix those things. CLU does [README].

The r/selfhosted thread from the developer [1] shows where users actually get value: managing the transition into Komga (or any comics server), bulk-renaming directories, stripping bad metadata, scraping correct metadata from multiple providers, downloading missing issues from GetComics.org, and keeping the library pristine after the fact. The comment thread on that post shows users asking about bulk XML features and metadata priorities — the kinds of requests that suggest CLU is filling a real gap for collectors with large, messy libraries.

Versus Kavita: The XDA Developers review [3] covers Kavita as a strong reading-focused alternative. Kavita has a polished reader, Generate Colorscape for cover aesthetics, CBL import for reading order, and an EPUB reader. It doesn’t have CLU’s editing surface. The two can coexist: Kavita serves, CLU curates.

Versus Stump: Stump [5] is an MIT-licensed Rust-based comics and manga server that was still marked as WIP and development-only at time of review. Not a practical CLU alternative yet.

The honest positioning: CLU is not winning on reading experience or polish. It’s winning on “I have 50,000 comics and the filenames are a disaster and I need to fix them from a browser without touching the command line.” That’s a real and underserved problem.

---

Features

From the README and v4.3-to-v4.12 changelog [README][1]:

Directory-level operations:

• Bulk rename files (configurable patterns)
• Bulk convert CBR → CBZ
• Rebuild CBZ files (re-zip contents)
• Convert PDF to CBZ
• Missing issue check across a series
• Enhance images (quality processing)
• Bulk metadata update
• Remove all ComicInfo.xml from a directory

Single-file operations:

• Full GUI editor for CBZ internals: rename/rearrange pages, add/delete files, crop images — all from the browser [README]
• Crop cover pages
• Remove first image (useful for stripping ads)
• Add blank image at end
• Soft delete with Trash folder — files move to staging instead of vanishing immediately [1]

Metadata and downloads:

• Download comics from GetComics.org [README]
• Metadata scraping from Metron, ComicVine, MangaDex, MangaUpdates, and Grand Comics Database [README][1]
• Metadata provider priority configurable per library (e.g., Metron+ComicVine for English comics, MangaDex+ComicVine for manga) [1]
• Missing ComicInfo.xml indicator and view on collection page [1]
• Pull list: subscribe to weekly releases, auto-download as single issues or weekly packs [README]

Multi-library and collection:

• Map multiple libraries (Comics, Manga, Magazines) as separate Docker volumes [README][1]
• Visual collection browser grouped by publisher [website scrape]
• Source Wall table view for metadata auditing across the whole library [1]
• Komga reading sync — import reading history and progress from an existing Komga instance [1]
• Reading heatmap, daily streaks, reading history by year, favorite authors/artists/characters [README]
• On the Stack view: highlights next issue in series you’re actively reading [1]

File management:

• Browser-based file explorer with drag-and-drop for moving directories and files [README]
• Drag-and-drop CBZ upload into any directory [1]
• Rename directories and files, remove text patterns from filenames in bulk [README]

Folder monitoring (optional daemon):

• Auto-rename on arrival
• Auto-convert to CBZ
• Auto-unpack archives
• Move subdirectories, custom naming patterns [README]

Optional local GCD database support [README] — Grand Comics Database cached locally for offline metadata resolution.

---

Pricing: SaaS vs self-hosted math

CLU has no SaaS tier. There is nothing to subscribe to. The software is GPL-3.0, and you run it yourself [README].

What you actually spend:

• CLU software: $0
• VPS or NAS to run it: whatever you already have, or $5–10/month if you’re starting fresh
• Time to set it up: see deployment section below

The pricing comparison story here is different from tools like Activepieces or Nextcloud, where there’s a real incumbent SaaS you’re escaping. Comic management tooling mostly doesn’t have an equivalent SaaS product to compare against. The comparison is time: hours spent manually unzipping CBZ files, renaming folders, or paying for Mylar3 automations versus having CLU’s GUI handle it.

If you’re already paying for Komga Plus or a Kavita-adjacent service and CLU can replace the need for that, the savings are marginal. The real value is in labor, not subscription cost. A 70,000-issue library with inconsistent naming and bad metadata would take weeks to fix manually. CLU can script most of that work through its bulk operations.

---

Deployment reality check

CLU is Docker Compose only, which is the right call for this kind of app [README]. The compose file is straightforward: one service, port 5577, three or four volume mounts (config, cache, your library roots, optionally a downloads folder for monitoring).

The critical volume mapping is that your primary library goes to /data. Additional libraries (manga, magazines) map to custom paths and get configured in the app’s settings. There’s no auto-discovery — you tell CLU where your files are [README].

First-run checklist:

1. Edit the compose file volume paths to match your actual library locations
2. Set PUID and PGID to match the user that owns your files (the README specifically calls out Unraid’s 99/100 convention) [README]
3. Start the container, visit the config page, save settings, hit Restart App [README]
4. On updates: mapping /config is required so settings survive container rebuilds [README]

What can go sideways:

• Permission errors are the most common first-run issue. If CLU can’t read or write your comic files, you’ll get confusing errors — the PUID/PGID settings exist specifically for this [README].
• The folder monitoring daemon is opt-in (MONITOR=yes/no environment variable). Don’t enable it until you understand what auto-rename rules you want — it will start moving files [README].
• GetComics.org download integration scrapes a third-party site. That site’s availability and structure can change without CLU’s code changing.
• Metadata scraping requires API keys for some providers (ComicVine, Metron). GCD is optional local database support [README][1].

Realistic time estimate: 20–30 minutes for a technical user who has Docker Compose experience. For someone new to Docker on a NAS (Unraid, Synology), budget 1–2 hours and expect to read the PUID/PGID documentation carefully. Full documentation lives at clucomics.org rather than in the README [README].

There is a Discord for support questions [README] — for a 203-star project, having an active Discord with a growing community is genuinely useful, since GitHub issue threads tend to go quiet on smaller projects.

---

Pros and Cons

Pros

• The editing surface is unique. No other self-hosted comic tool lets you open a CBZ in a browser, rearrange pages, crop covers, strip ads, and save — without downloading the file to your desktop. This alone is worth the Docker deployment for anyone managing a large library [README].
• Multi-provider metadata with per-library priority. Metron, ComicVine, MangaDex, MangaUpdates, GCD — and you can configure which sources to try first, per library. Manga and English comics can have completely different metadata strategies [1][README].
• Active development. Nine minor versions in two months (v4.3 → v4.12) [1]. Features are shipping, not stagnating.
• Komga migration path. If you’re moving from Komga or want to stay on Komga as your reader, CLU can sync reading history and progress bidirectionally [1]. You don’t have to choose.
• Bulk operations at scale. Rename 10,000 files, strip all ComicInfo.xml, convert all CBR to CBZ — the whole library in one operation, from a browser, without SSH [README].
• Soft delete. Files go to a staging folder before permanent deletion. Small feature, huge relief for anyone who’s accidentally nuked a directory [1].
• Pull list / auto-download. Subscribe to ongoing series, auto-download new issues from GetComics.org. For active collectors, this replaces manual checking [README].
• $0, no strings. GPL-3.0. No commercial tier, no feature gates, no “enterprise edition” for the useful parts [README].

Cons

• 203 GitHub stars. This is a small project maintained primarily by one person. There is no company backing it, no VC money, no SLA. If the developer loses interest, the project stalls [README].
• GPL-3.0, not MIT. If you want to embed this in your own product or redistribute it commercially, the GPL requires you to open-source your changes. Not a practical issue for personal use, but worth noting compared to MIT-licensed alternatives.
• Not a reading server. CLU does not replace Komga or Kavita as an OPDS server, multi-user library, or polished reading interface. Its built-in reader exists but is not the focus [website]. If your primary need is reading comics rather than managing them, the comparison shifts.
• GetComics dependency. Downloading from GetComics.org is legally ambiguous — that site hosts copyrighted content without authorization. Whether you use this feature is your call, but its inclusion is worth flagging [README].
• No API. There’s no documented REST API for scripting or external integration. Everything goes through the web UI [README].
• No multi-user. CLU is a single-user management tool. No accounts, no per-user libraries, no sharing controls. Fine for a homelab, problematic for any shared deployment [README].
• Windows/WSL setup is non-trivial. The README explicitly links to a separate WINDOWS_WSL_SETUP.md for PUID/PGID configuration on Windows, which signals that edge cases exist [README].
• Third-party source dependencies. GetComics.org, Metron, MangaUpdates — if any of these services change their structure or go down, the features depending on them break. Not CLU’s fault, but a real operational risk for features you might rely on.

---

Who should use this / who shouldn’t

Use CLU if:

• You have a large existing comic library with naming inconsistencies, bad metadata, or files that need editing before ingesting into Komga or Kavita.
• You want to manage your library from a browser without SSH access — on a NAS, a remote VPS, or a server you don’t sit in front of.
• You’re building or migrating a collection and want automated metadata scraping across multiple providers.
• You need manga and English comics treated differently, with different metadata sources.
• You want to auto-download ongoing series from GetComics and you’re comfortable with the legal territory.
• You’re already on Komga and just want better editing tools alongside it.

Skip CLU if:

• Your primary need is a polished reading experience with multi-user support, OPDS feeds, and a mobile-friendly UI — use Kavita [3] or Komga instead.
• You want a reading server you can share with family members or a household — CLU has no user accounts.
• You’re not comfortable with Docker and don’t have someone who can handle the initial setup.
• You need a project with commercial backing and a support SLA — this is a one-developer hobby project.
• Your library is small and well-organized — CLU’s value scales with collection size and disorganization.

---

Alternatives worth considering

Komga — The established self-hosted comics server. Excellent reading experience, multi-user, OPDS, metadata management. CLU was built as a companion to Komga and they work well together. Komga doesn’t do CBZ editing or bulk file operations.

Kavita — Polished reading-first server for comics, manga, and ebooks [3]. Better reader UI than CLU’s built-in, cleaner multi-format support, but no editing or bulk operations surface. Free, open source (GPL-3.0).

Mylar3 — Python-based comic book downloader and manager focused on automated downloads and metadata management. Older project, different architecture (closer to a download client than a library manager). Overlaps with CLU’s pull list feature.

Stump — Rust-based comics server, MIT license, still in WIP/development status as of last review [5]. Not production-ready for most users yet, but worth watching.

Komf — Komga Metadata Fetcher: a standalone metadata agent that runs alongside Komga. More focused than CLU’s metadata features but doesn’t do editing or file management.

Ubooquity — Java-based comics server. Older, less actively developed, but mature OPDS support. Not a management tool.

For most self-hosters, the practical shortlist is CLU + Komga (management + reading) or Kavita alone (reading-first, no management). CLU is the only real option in the “I need to actually edit my CBZ files” category.

---

Bottom line

CLU solves a specific problem that the more popular comics servers don’t touch: actually editing and curating your library at scale. If you have thousands of comics with inconsistent naming, bad covers, embedded ads, and patchy metadata, CLU gives you a browser-based tool to fix all of it without touching the command line. The development pace is real — nine versions in two months with features users actually asked for — and the Discord community suggests the project has momentum beyond just the README [1]. The tradeoffs are also real: 203 stars, one primary developer, no multi-user, and a reading experience that isn’t the point. Use it alongside Komga or Kavita as your reading layer, and you have a solid self-hosted comics stack. Use it as your only comics app, and you’ll notice what’s missing.

---

Sources

1. allaboutduncan, r/selfhosted — “Comic Library Utilities (CLU) - Recent Updates Include Manga Metadata, Bulk XML Features and More” (24 days ago). https://www.reddit.com/r/selfhosted/comments/1s48eww/comic_library_utilities_clu_recent_updates/
2. Ethan Sholly, selfh.st — “Self-Host Weekly (30 May 2025)”. https://selfh.st/weekly/2025-05-30/
3. Ayush Pande, XDA Developers — “This free, self-hosted app is basically Jellyfin for comics and books, and I absolutely love it” (Jul 21, 2025). https://www.xda-developers.com/this-free-self-hosted-app-is-basically-jellyfin-for-comics/
4. Ethan Sholly, selfh.st — “Self-Host Weekly (19 December 2025)”. https://selfh.st/weekly/2025-12-19/
5. libreselfhosted.com — “Stump project”. https://libreselfhosted.com/project/stump/

Primary sources:

• GitHub repository and README: https://github.com/allaboutduncan/clu-comics (203 stars, GPL-3.0 license)
• Official documentation: https://clucomics.org
• Docker image: https://hub.docker.com/r/allaboutduncan/comic-utils-web