FreshRSS vs Miniflux

FreshRSS — strengths

• Feature-rich: labels, filters, custom extensions, themes, and sharing
• Broad database support (MySQL, PostgreSQL, or SQLite) — runs even on cheap shared PHP hosting
• Compatible with many mobile apps via the Google Reader and Fever APIs
• WebSub (PubSubHubbub) for near-real-time updates on supported feeds
• Active extension ecosystem to tailor behaviour to your workflow

FreshRSS — weaknesses

• More moving parts (PHP + DB) to maintain
• Busier UI out of the box
• Extension quality varies

Miniflux — strengths

• Single Go binary — trivially light, fast, and easy to run
• Clean, distraction-free, keyboard-driven reading experience
• Built-in readability/scraper rules and content filters
• Many native integrations: Wallabag, Pocket, Nunux, Matrix, webhooks, and more
• Compatible with Google Reader and Fever APIs for mobile apps

Miniflux — weaknesses

• No extensions or themes by design
• PostgreSQL required (no SQLite/MySQL)
• Limited customization

When FreshRSS fits

• Power user with hundreds of feeds who wants labels, filters, and custom extensions to tame the firehose: FreshRSS's customization handles that organisation.
• Someone on cheap shared PHP/MySQL hosting without Docker: FreshRSS installs like a normal PHP app, whereas Miniflux expects a Go binary and PostgreSQL.

When Miniflux fits

• Minimalist who wants a fast, keyboard-first reader that just shows articles cleanly: Miniflux is opinionated in exactly that direction with no clutter.
• User who saves articles to Wallabag or Pocket and wants those integrations built in rather than via plugins: Miniflux ships them natively.

FreshRSS gotchas

• As a PHP app, you keep PHP and its extensions updated — more moving parts than a single binary
• The denser, highly configurable UI can feel busy compared to Miniflux's minimalism
• Extension quality and maintenance vary
• Performance on very large feed counts depends on your database choice and tuning

Miniflux gotchas

• Intentionally minimal — no themes and no plugin system, which frustrates users who want heavy customization
• Requires PostgreSQL (no MySQL or SQLite), so slightly more infrastructure than PHP-on-shared-hosting
• Opinionated defaults mean you adapt to it rather than it to you
• No deep folder/label hierarchy like some heavier readers

Choose FreshRSS when

Pick FreshRSS if you want a customizable, feature-rich reader with extensions, themes, and flexible database options — including running on cheap shared PHP hosting.

Choose Miniflux when

Pick Miniflux if you want the lightest, fastest, most minimal keyboard-driven reader with great built-in integrations, and you're happy to run a single Go binary with PostgreSQL.

Migration

Both readers speak the Google Reader and Fever APIs and both import and export OPML, so moving your subscriptions is easy — export an OPML file from one and import it into the other. What doesn't transfer is read/starred state, labels, and per-feed settings; those are recreated on the new side. Because both support the same mobile-app APIs, your reader apps (Reeder, FeedMe, and others) can simply be re-pointed at the new server. Import your OPML, re-star anything critical, and keep the old instance until your feeds and apps are confirmed working against the new one.

Frequently asked questions

Which is lighter?

Miniflux, a single Go binary, is the lighter of the two at idle. FreshRSS is still light for a PHP app but has more moving parts.

Can I use mobile apps with both?

Yes — both implement the Google Reader and Fever APIs, so apps like Reeder or FeedMe work with either. That shared API support also makes switching between them easy.

Which is more customizable?

FreshRSS, by far — it has themes, an extension system, labels, and filters. Miniflux is deliberately minimal, with no plugins or themes.

Do they need a database?

FreshRSS supports SQLite, MySQL, or PostgreSQL, so it runs even on minimal hosting. Miniflux requires PostgreSQL specifically.

Can I move my feeds between them?

Yes — both import and export OPML, so subscriptions move in seconds. Read/starred state and labels don't carry over and are rebuilt on the new instance.

Which handles full-text/readability better?

Miniflux has built-in scraper/readability rules and content filters out of the box. FreshRSS can do full-text extraction via an extension.

Which should I pick for hundreds of feeds?

Both handle large feed counts. FreshRSS gives you labels, filters, and extensions to manage them; Miniflux keeps things fast and minimal. Choose based on whether you want organisation features or speed and simplicity.