unsubbed.co

Mylar3

Mylar3 handles automated Comic Book (cbr/cbz) downloader program for use with NZB and torrents as a self-hosted solution.

Automated comic library management, honestly reviewed. No marketing fluff, just what you get when you decide to manage your own comic collection.

TL;DR

  • What it is: Open-source (GPL-3.0) automated downloader and library manager for digital comic books (CBR/CBZ format) — think of it as Sonarr or Radarr, but for comics instead of TV shows or movies [1][README].
  • Who it’s for: Comic book collectors who already run a self-hosted media server, understand the “arr” stack (Sonarr, Radarr, Prowlarr), and want to automate comic acquisition and organization rather than pay recurring subscription fees [3].
  • Cost savings: ComiXology Unlimited runs $5.99/mo, Marvel Unlimited $9.99/mo, DC Universe Infinite $7.99/mo — and none of them let you own the files. Mylar3 software is free; you pay only for the VPS it runs on [README].
  • Key strength: Deep integration with the wider media automation stack — Prowlarr syncs indexers directly to Mylar3 with no per-app configuration required, SABnzbd and NZBGet handle downloads automatically, and story-arc tracking is something no subscription service offers [2][README].
  • Key weakness: This is niche, technical tooling. It assumes you already have NZB/torrent infrastructure running and understand how to configure a multi-service Docker stack. A non-technical founder who just wants to read Batman will not enjoy this setup process.

What is Mylar3

Mylar3 is the Python 3 rewrite of the original Mylar — an automated comic book downloader and library manager for CBR and CBZ format files. You create a watchlist of series you want to collect. Mylar3 monitors indexers (Usenet NZB services, torrent trackers) for new issues as they’re released, grabs them automatically, renames them according to your naming scheme, and adds metadata via a built-in fork of the ComicTagger tool [README].

The project lives on GitHub at mylar3/mylar3, has 1,385 stars and 149 forks, 74 contributors, and 64 releases — the latest landing August 17, 2025 [README]. The codebase is primarily Python (74.6%) with a web UI written in HTML and JavaScript.

What makes it part of a coherent system rather than a standalone tool is how tightly it plugs into the “arr” ecosystem. Prowlarr — the centralized indexer manager used by Radarr, Sonarr, and Lidarr — natively syncs its indexers to Mylar3 [2]. That means you configure your Usenet providers and torrent trackers once in Prowlarr and all your media managers inherit them. In a mature self-hosted media setup, Mylar3 fits into an AutoPirate-style stack alongside SABnzbd or NZBGet for downloads, Prowlarr for indexers, and your media server of choice for reading [1].

The comparison class is not traditional SaaS software automation — it’s the subscription comic services: ComiXology (now folded into Amazon’s Kindle ecosystem), Marvel Unlimited, and DC Universe Infinite. Those services give you access to large catalogs on a rental basis. Mylar3 gives you files you own.


Why people choose it

There’s no large body of standalone Mylar3 review content — it’s a specialized tool with a self-selecting audience. What does exist comes from the broader self-hosted media community, and the reasons people run it map predictably onto the reasons people run Sonarr or Radarr.

Ownership over access. Subscription comic services have a history of removing titles, changing catalogs, and — in ComiXology’s case — being absorbed into Amazon’s ecosystem in ways that broke existing workflows and removed features like guided view for long-form reading. When you download CBR/CBZ files and manage them with Mylar3, the files are yours regardless of what a platform decides next quarter.

Comic-specific automation nobody else does. Mylar3 supports pull-list monitoring — it can watch the weekly new-release list up to four weeks in advance and automatically grab issues from your watchlist as they appear [README]. It tracks story arcs across series, which is genuinely difficult metadata work that no subscription service surfaces cleanly. It generates series.json files for third-party applications, handles TPBs (trade paperbacks) and GNs (graphic novels) alongside individual issues, and retries failed downloads automatically [README]. This level of automation doesn’t exist in a subscription app because subscription apps don’t need it — you click “read.”

Part of an existing stack. Most people who run Mylar3 are already running Sonarr for TV, Radarr for movies, and Lidarr for music. Adding Mylar3 means one more service in a Docker Compose file, one more Prowlarr integration to sync, and a consistent operational model they already understand [1][2]. The AlternativeTo “Best Personal Media Apps” list explicitly updated from Mylar to Mylar3 in May 2022, reflecting the project’s continued position in the standard self-hosted media toolkit [4].


Features

From the README and documentation:

Library management:

  • Watchlist-based series monitoring — add a series, Mylar3 watches for every new issue [README]
  • Scan existing library and identify missing issues automatically [README]
  • Configurable file and folder renaming with flexible naming schemes [README]
  • Support for TPBs, GNs, and story arcs — not just single issues [README]
  • series.json file generation for integration with reading apps [README]
  • Automatic metatagging via a modified ComicTagger integration (runs during or after post-processing) [README]

Download automation:

  • Pull-list monitoring: view and act on upcoming releases up to four weeks ahead, or historical lists months back [README]
  • SABnzbd and NZBGet support for Usenet downloads [README]
  • Multiple torrent client support plus Blackhole folder mode [README]
  • Multiple Newznab indexer support, raw indexer mode, and direct download [README]
  • Failed download handling: if one grab fails, it finds an alternative [README]
  • Prowlarr integration: indexers sync automatically, no per-app configuration [2]

Platform and deployment:

  • Runs on Windows, Linux, macOS, Raspberry Pi [README]
  • Docker image maintained by LinuxServer.io (lscr.io/linuxserver/mylar3) [1]
  • Install via git clone or Docker [README]
  • Web UI on port 8090 [1]
  • Discord community (826+ member server) and forum support [README]

Notifications:

  • Snatch and download notifications via various notification services [README]

What’s not here:

  • No built-in reading interface — Mylar3 manages and downloads, you read with a separate app (Komga, Kavita, or similar)
  • No mobile app
  • No cloud sync or hosted version — self-hosted only

Pricing: What you’re actually replacing

Mylar3 itself is free software (GPL-3.0). The cost equation is different from a tool like Activepieces or n8n because there’s no SaaS version of Mylar3 to compare against. What you’re comparing is self-hosting against the subscription comic platforms:

Subscription comic services:

  • ComiXology Unlimited: ~$5.99/mo — limited catalog selection, Amazon-owned, guided view removed in the 2022 migration
  • Marvel Unlimited: $9.99/mo (~30,000 issues, Marvel catalog only, some recent releases delayed by 3-6 months)
  • DC Universe Infinite: $7.99/mo (DC catalog only, streaming model)
  • Comixology “buy to own”: individual issue pricing, $1.99–$4.99 per issue, no self-hosting

None of these give you a file you can keep, move, or read offline without their app.

Self-hosted with Mylar3:

  • Software: $0 (GPL-3.0) [README]
  • VPS to run the stack on: $5–15/mo depending on provider and whether you’re running a full arr stack or just Mylar3
  • Usenet provider (if going the NZB route): $5–15/mo for a reputable indexer and a provider like Eweka or Newshosting
  • Torrent route: indexer membership costs vary; many are invite-only

The honest math: For a collector focused exclusively on comics, the pure software cost is comparable to or lower than a single subscription service. The hidden cost is the infrastructure: Usenet is not free, and the torrent route requires either a seedbox or managing your own client. If you’re already running a Radarr/Sonarr stack and paying for Usenet, adding Mylar3 costs nothing incremental — it’s one more container sharing existing infrastructure.

For someone starting from zero who only wants comics: the setup cost is meaningful. You’re not replacing a $9.99/mo bill with a $6 VPS. You’re replacing a $9.99/mo bill with a $6 VPS plus a $12/mo Usenet provider plus however long it takes you to learn the stack.


Deployment reality check

The geek-cookbook AutoPirate recipe [1] shows the standard deployment pattern: Mylar3 runs as a service in a Docker Compose or Swarm stack alongside SABnzbd, Prowlarr, and other arr tools, fronted by Traefik as a reverse proxy. The service definition is straightforward — one container, config volume, media volume, port 8090.

What you actually need:

  • A Linux host (VPS, NAS, home server, or Raspberry Pi) with Docker installed [1][README]
  • A reverse proxy if you want HTTPS external access (Traefik, Nginx, or Caddy)
  • At minimum one indexer configured — either via Prowlarr sync [2] or directly in Mylar3
  • A download client: SABnzbd or NZBGet for Usenet, or a torrent client for torrents [README]
  • A Usenet provider subscription or torrent tracker access for actual downloads
  • Optionally, a comic reading server (Komga, Kavita, or similar) for reading the resulting files

What integrates cleanly: Prowlarr’s native Mylar3 support is the standout ease-of-use feature — if you already have Prowlarr managing indexers for Sonarr and Radarr, adding Mylar3 to the sync list takes minutes [2]. No re-entering API keys and indexer URLs for each app.

What can go sideways: The documentation lives on mylarcomics.com rather than in a GitHub wiki, which means it’s one more site to read and potentially one more resource that can go stale. The community skews toward hobbyists on Discord and forums rather than enterprise documentation [README]. The source data for this review didn’t surface detailed user complaints, but a 1,385-star project with 74 contributors is meaningfully smaller than the Sonarr/Radarr community — expect thinner Google results when you hit an edge case.

Realistic time estimate: Someone already running Sonarr and Radarr via Docker Compose can add Mylar3 and have it operational in under an hour. Someone starting from scratch building a complete stack (Prowlarr + download client + Mylar3 + reading app) should budget a full weekend.


Pros and cons

Pros

  • Part of the standard arr stack. Prowlarr native integration means indexer configuration is a one-time task, not per-app busywork [2]. If you run Sonarr, adding Mylar3 is incremental, not a new project.
  • Story arc and pull-list tracking. No subscription service offers this level of automation for release monitoring and arc management [README]. For serious collectors, this is the feature that justifies the setup effort.
  • Active maintenance. 64 releases, latest August 2025, 74 contributors — the project is alive [README]. The Python 3 rewrite (Mylar3) fixed the long-term viability issue the original Mylar faced as Python 2 went EOL.
  • ComicTagger integration. Automatic metadata tagging means your reading app gets clean series info, issue numbers, and cover art without manual intervention [README].
  • Runs on anything. Windows, Linux, macOS, Raspberry Pi — and the LinuxServer.io Docker image handles most of the OS differences for you [1][README].
  • Failed download handling. If an NZB or torrent grab fails, Mylar3 finds an alternative without manual intervention [README].

Cons

  • GPL-3.0, not MIT. The license is more restrictive than MIT — relevant if you’re considering embedding this in a commercial product, but not a practical concern for personal use [README].
  • Requires existing infrastructure. Mylar3 is not a standalone solution. Without a Usenet provider, torrent tracker, Prowlarr instance, and download client already running, you’re building a stack, not installing an app [1][2].
  • No built-in reader. Mylar3 downloads and organizes; it does not serve or display comics. You need a separate reading application [README].
  • Smaller community than Sonarr/Radarr. 1,385 stars versus Sonarr’s 35,000+. When things break, you’re more likely to debug yourself than find an answered Stack Overflow question [README][3].
  • Niche use case by definition. This tool does exactly one thing: automate comic book acquisition and organization. If your interest in comics is casual, the setup cost doesn’t pencil.
  • Limited third-party review coverage. The absence of detailed user reviews in the wild is itself a signal — the user base is small enough that mainstream tech publications haven’t covered it.

Who should use this / who shouldn’t

Use Mylar3 if:

  • You’re already running a self-hosted arr stack (Sonarr, Radarr, Prowlarr) and you collect comics — the incremental setup cost is minimal.
  • You’re a serious comic collector building a permanent local library and want automated pull-list monitoring and story-arc tracking.
  • You’re comfortable managing Docker containers and troubleshooting services via logs and community forums.
  • You have a Usenet provider subscription you’re already using for other media.

Skip it (stay on Marvel/DC subscription) if:

  • You read comics casually — a few series here and there. Subscription services are simpler and the per-month cost is trivial.
  • You’ve never touched a Docker container and don’t have someone to help with initial setup.
  • You only want to read recent releases — subscription services often have newer content more easily accessible.

Skip it (look at Kapowarr or Komga instead) if:

  • You want a comic server that also handles reading, not just file management.
  • Your priority is serving an existing local library rather than downloading new content automatically.

Alternatives worth considering

From the AlternativeTo list and the arr ecosystem:

  • Kapowarr — newer comic manager with a similar automation model; smaller community than Mylar3 but has an integrated reading interface [3].
  • Komga — comic book server and reader, excellent for organizing and reading an existing library, but it doesn’t automate downloading [3].
  • Kavita — similar to Komga, reading-server-first rather than download-automation-first.
  • LANraragi — manga/comic reader, serves local files, no automation.
  • Marvel Unlimited — $9.99/mo for the Marvel catalog; the right call if you only read Marvel and don’t want infrastructure.
  • ComiXology (Amazon) — catalog is large but the 2022 migration removed features; file ownership is not on the table.

For building an automated comic acquisition and organization pipeline, Mylar3 is currently the most established open-source option. Kapowarr is the closest competitor worth evaluating if you’re starting fresh and want to compare [3].


Bottom line

Mylar3 is the Sonarr of the comic book world — mature, actively maintained, and built for people who take their collection seriously. It doesn’t try to be a reading app or a social platform. It does one job: watch for comics you want, grab them, organize them, and tag them. For someone already running the arr stack who also collects comics, adding Mylar3 is a no-brainer. For someone starting from zero, the infrastructure prerequisites are real — you’re not replacing a subscription with a Docker container, you’re building a multi-service media pipeline that happens to save you $10/mo on a reading app. Know what you’re signing up for and it delivers. Go in expecting a turnkey app and you’ll be frustrated before you’ve downloaded your first issue.


Sources

  1. Funky Penguin’s Geek Cookbook“How to run Mylar3 in Docker (AutoPirate recipe)”. https://geek-cookbook.funkypenguin.co.nz/recipes/autopirate/mylar/
  2. Funky Penguin’s Geek Cookbook“Install Prowlarr in Docker (AutoPirate recipe)” — covers Prowlarr’s native Mylar3 indexer sync integration. https://geek-cookbook.funkypenguin.co.nz/recipes/autopirate/prowlarr/
  3. AlternativeTo“Best Personal Media Apps” — community-curated list including Mylar3 alongside Sonarr, Radarr, Lidarr, and Komga. https://alternativeto.net/lists/1877/best-personal-media-apps/
  4. AlternativeTo“OpenFLIXR: Media Server” — list note confirms “Replaced Mylar with Mylar3” in May 2022. https://alternativeto.net/software/openflixr/about/
  5. SaaSHub“Turing Pi 2 Home cluster” — dev.to post synthesis showing Prowlarr + Mylar3 as part of a home Kubernetes media stack. https://www.saashub.com/alternatives/post-dev-2024-10-06-turing-pi-2-home-cluster-2366273

Primary sources:

Features

Search & Discovery

  • Tags / Labels