freshrss.org No paid content found

What is FreshRSS?

FreshRSS is a free, self-hostable RSS and Atom feed aggregator. In plain terms, it is software you run on your own server to collect articles, podcasts and video posts from many sites into one place, then read them in a web interface. Because it is self-hosted, your subscriptions and reading data stay on infrastructure you control rather than with a commercial feed service.

Its main appeal is the combination of control and capability. The project describes itself as lightweight, powerful and customizable, and it lists a broad feature set: reading articles inside the app, saving searches, generating feeds by scraping external websites, building new feeds from filters, importing and exporting with OPML, and WebSub for near-real-time updates. It also supports themes and extensions, third-party mobile apps, and translations in more than 15 languages.

Who it suits

• Privacy-conscious readers who want their feed list and reading history on their own hardware.
• Heavy feed users who follow many sources; the project says it can handle 1M+ articles and 50k+ feeds.
• Tinkerers who want to extend or theme their reader, or create custom feeds from sites that do not offer one.
• People who want to try before committing, via the project's demo or an existing public server.

Trade-offs

Self-hosting means you handle installation, updates, backups and server costs. That is more work than signing up for a hosted reader, but it gives you ownership and flexibility. If you would rather not run a server, a hosted service such as Feedly or Inoreader may be a better fit; if you want a mature open-source reader that runs on your own machine or server, FreshRSS is a strong candidate. The project is free software under AGPL 3, so it is also community-oriented and open to contributions.

Next step

If you are curious, start with the demo at demo.freshrss.org to see the reading interface, then decide whether you want to install it yourself or join an existing server. The official site is FreshRSS.

How do I install FreshRSS on my own server?

FreshRSS is installed by downloading its code and following the project's own setup instructions on a server you control. The official site points you to the code and an installation guide rather than a one-click hosted signup, so the process is a small self-hosting exercise: prepare a web server with PHP and a database, place the FreshRSS files where your web server can serve them, then run the built-in installer in your browser and create your admin account.

The project describes itself as lightweight and easy to work with, and its feature list gives you a sense of what the installation needs to support: syndication of websites, podcasts and video channels, article reading, search with saved queries, OPML import/export, WebSub for real-time updates, themes and extensions, and translations in more than 15 languages. Those are product features, not installation requirements, but they explain why a typical setup involves a normal PHP hosting environment rather than a static file drop.

A practical installation path

1. Confirm your server can run PHP and a supported database. FreshRSS is a PHP application, so shared hosting with PHP and MySQL/MariaDB or PostgreSQL is usually the simplest starting point.
2. Download the code from the official project and read its installation instructions before uploading anything.
3. Upload or clone the files into a directory your web server can reach, for example a subdomain or a /freshrss path.
4. Set the required file permissions so the installer can write configuration and cache data.
5. Open the installer URL in your browser, provide database credentials, and create your first user account.
6. Log in, add a few feeds, and confirm that articles appear. Then import an existing OPML file if you are migrating from another reader.

If you would rather not manage a server, the project offers a demo and mentions signing up to an existing server, which is the lower-effort way to evaluate it before committing to your own installation.

What to check before you start

• Hosting type: A VPS gives you full control over PHP versions and scheduled tasks; shared hosting is easier but may restrict background jobs.
• Database: Decide between MySQL/MariaDB and PostgreSQL based on what your host supports and what you already maintain.
• Updates: Self-hosting means you are responsible for applying FreshRSS updates and keeping PHP and the database patched.
• Backups: Back up both the database and the FreshRSS configuration/data directory so you can restore feeds and settings.
• Access: Consider HTTPS and, if the instance is public, authentication or network restrictions.

For the exact commands and supported versions, use the project's own guide at FreshRSS. If you want a hosted alternative to compare effort levels, Inoreader and Feedly are established commercial readers, while Miniflux is another self-hosted option worth evaluating if you prefer a minimal reader.

Can FreshRSS handle large numbers of feeds and articles?

Yes. FreshRSS is built to stay usable at scale: the project states it can manage over 1 million articles and more than 50,000 feeds. That is far beyond what most individual readers accumulate, so the practical question is usually not whether it can hold your subscriptions, but how you configure it and where you host it.

What "large" looks like in practice

• A heavy personal reader: dozens to a few hundred feeds, thousands of unread items. This is comfortable territory; the main limit is how often you refresh and how many full-text or scraped feeds you add.
• A shared or team instance: multiple users, hundreds to thousands of feeds, long retention. Here database choice, server memory and refresh scheduling matter more than the feed count itself.
• Aggressive archiving: keeping years of articles instead of weeks. Storage and search performance become the deciding factors.

Features that help at scale

• Search and saved queries let you avoid scrolling through a huge backlog.
• Web scraping and feed generation create extra feeds from sites that lack one, which increases volume but keeps everything in one place.
• OPML import/export makes it practical to move a large subscription list in or out.
• WebSub supports real-time updates rather than constant polling.
• Themes and extensions and mobile support (including third-party apps) let you tune the reading experience without changing the backend.

Trade-offs to weigh

A useful next step

If you are unsure, try the project's demo at demo.freshrss.org before committing, or start with a small self-hosted install and import a subset of your OPML file. Then add feeds in stages and watch refresh times and database growth. For background, the project itself is at FreshRSS, and general RSS tooling context is covered by Opensource.com.

How does FreshRSS compare to other RSS readers like Feedly?

FreshRSS and Feedly solve the same core problem — keeping many sites, podcasts and video channels in one reading list — but they sit at opposite ends of the hosting spectrum. FreshRSS is software you install on your own server; Feedly is a hosted service you log into. That single difference shapes cost structure, privacy, control and how much maintenance you take on.

Where the two diverge

What FreshRSS actually offers

The project describes itself as lightweight, powerful and customizable, and the feature list backs that up: reading articles directly in the interface, saving search queries for quick reuse, OPML import and export, WebSub for near-real-time updates, and mobile access with or without a third-party app. It also supports generating feeds by scraping external websites and building new feeds from filters you define. On scale, the site claims it can handle over a million articles and 50,000 feeds. It is free software under AGPL 3 and translated into more than 15 languages.

Practical trade-offs

Self-hosting buys you control: your reading history stays on hardware you choose, you can extend the interface, and there is no subscription to cancel. It costs you effort: you install it, keep it patched, and fix it when it breaks. A hosted reader flips that — nothing to maintain, but your data lives elsewhere and you depend on the provider's roadmap and pricing.

A useful test: if you already run a server or a home NAS and enjoy that kind of work, FreshRSS is a natural fit. If you want to open a browser and just read, a hosted service is the easier path. You can sample FreshRSS before committing by trying the project's demo instance.

Choosing between them

• Pick FreshRSS if data ownership, customization or avoiding a subscription matters more than convenience.
• Pick a hosted reader if you would rather not think about servers at all.
• Consider both if you want to trial FreshRSS while keeping a hosted fallback.

If you want to compare against other self-hostable options, Miniflux and Tiny Tiny RSS occupy similar territory, and Feedly is the hosted benchmark you are weighing against.

What customization options and extensions does FreshRSS offer?

FreshRSS is built around the idea that you host it yourself, so most customization happens through its settings, themes and extensions rather than a fixed feature set. The project describes itself as configurable "thanks to a lot of options," and lists themes and extensions as a distinct capability.

What the page confirms

• Themes and extensions: You can customize the look and behaviour of FreshRSS with themes and extensions, and the community contributes to both.
• Configurable options: A broad set of settings lets you adapt the reader to your preferences rather than accepting one default layout.
• Internationalisation: The interface is translated into more than 15 languages, which matters if you read or share feeds across language groups.
• Mobile flexibility: You can follow your feeds with or without a third-party application, so the web interface is not the only way to read.
• Feed-level customisation: Web scraping generates feeds from sites that do not publish one, and feed generation creates new feeds based on your own filters. Both let you reshape what content enters your reader.
• Search and saved queries: You can search and save queries for quick access, which is a lighter form of personalisation than building a full extension.

Practical reading

The extension model is most useful when you want behaviour the core does not ship with: for example, altering how articles are rendered, adding keyboard shortcuts, or changing how feeds are fetched. Themes are the simpler route if you mainly care about readability and screen density. Because FreshRSS is self-hosted, the real constraint is usually your own server and maintenance time, not the number of options.

If you are deciding whether to commit, try the project's demo first and compare it against a hosted reader you already use. If the demo's defaults feel close enough, install it on your own server and add themes or extensions only when a specific annoyance appears. For the code, installation instructions and community channels, start at FreshRSS.

How can I contribute to the FreshRSS project?

You contribute to FreshRSS mainly through its community channels, and the project describes itself as free software under AGPL 3 and "community-friendly" with a "Join the community" section pointing to a guide, a contact route, contribution paths, and credit for contributors.

H3 Practical ways to help

• Code and extensions: FreshRSS is extensible with themes and extensions, so developers can work on the core aggregator or build add-ons.
• Translation: The interface is translated into more than 15 languages, making localisation a concrete contribution area.
• Documentation and support: The project links a guide and a contact route, which typically need writers and people answering user questions.
• Testing and bug reports: Trying the demo or an existing server and reporting issues helps the maintainers.
• Community presence: The testimonials show active users on social platforms, so advocacy and helping newcomers also count.

H3 A reader scenario Suppose you run FreshRSS on a small server and notice a missing feature or a confusing setting. Rather than only patching your own copy, you can check the contribution guide, open an issue or pull request, and offer a translation or documentation fix alongside it. That turns a personal workaround into something other self-hosters benefit from.

H3 Next step and decision criterion Start at the project's own site to find the guide and contact details: FreshRSS. Choose your entry point by skill: code or extensions if you program, translation if you are fluent in another language, and documentation or support if you prefer writing and helping users. If you are unsure, install it or try the demo first, then contribute where you personally hit friction.