Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
upstream: github.com/tt-rss/tt-rss (opens in new tab) · github.com/FreshRSS/FreshRSS (opens in new tab)
Pick Tiny Tiny RSS
If you already use it and its plugins, want a PHP reader on PostgreSQL, and are comfortable following the community continuation of the retired original.
Pick FreshRSS
If you want a single project with one home, the smaller footprint we measured (~16 MB against ~69 MB of RAM), the Google Reader API for apps, XPath scraping and extensions.
Tiny Tiny RSS and FreshRSS are the two long-running PHP feed readers in our catalog, and both give you a web reader you host yourself. The big news for anyone choosing is that Tiny Tiny RSS changed hands: the original project was retired and development continues in a community fork. FreshRSS is one active project with one home. If you are also looking at a Go option, Miniflux vs FreshRSS covers it.
Tiny Tiny RSS is a web-based news feed reader and aggregator with a plugin
system. Per its README, "The original tt-rss project, hosted at
https://tt-rss.org/ and its various subdomains, was retired on 2025-11-01", and the
repository at github.com/tt-rss/tt-rss "is a fork of tt-rss as of 2025-10-03,
created by one of its long-time contributors". The stated goal "is (as you might
expect) to continue tt-rss development", and "No major breaking changes are
planned." The main branch "is intended to be stable and safe for use."
FreshRSS's README says it is "a multi-user application with an anonymous reading mode", and "lightweight, easy to work with, powerful, customizable". It supports "extensions for further tuning" and "natively supports basic Web scraping, based on XPath, for Web sites not providing any RSS / Atom feed."
This is the real difference. Tiny Tiny RSS's docs now live in a recreated
repository, and the site at tt-rss.org says it "uses a continuous development
model based on the main branch, which is considered stable." Images for
linux/amd64 and linux/arm64 are published to Docker Hub (supahgreg/tt-rss) and
GitHub Container Registry (ghcr.io/tt-rss/tt-rss); our install pins to one of
those builds. The copyright line still reads "Copyright (c) 2005 Andrew
Dolgov", and the licence is GPL-3.0.
If you used Tiny Tiny RSS years ago, check which image and repository your setup follows before updating. FreshRSS has no such transition to manage.
FreshRSS supports mobile and native apps "via two distinct APIs": the Google Reader API, which its README calls the better one, and a more limited Fever API. It also has a command-line interface.
Tiny Tiny RSS has its own JSON API, documented in the API Reference in its
docs, and is built around a plugin system; its plugins were
mirrored to GitHub as tt-rss-plugin-* repositories. If you rely on a
particular client or plugin, check that it works with the fork before moving.
FreshRSS runs on "PostgreSQL 10+ or SQLite or MariaDB 10.6+ or MySQL 8.0+", and
our install is one container. Our Tiny Tiny
RSS install is heavier: PHP-FPM, nginx, an update daemon and a PostgreSQL
container, four services in all. Feeds are refreshed by the updater service
there. In FreshRSS, automatic refresh is off until you set CRON_MIN, which is
in our snippet.
Tiny Tiny RSS is GPL-3.0; FreshRSS is "GNU AGPL 3". The AGPL matters only if you modify FreshRSS and offer it to others over a network; for a private install both are fine.
We list a minimum of 512 MB of RAM for Tiny Tiny RSS and 256 MB for FreshRSS; both are our own estimates. In our install check (GCP e2-standard-2, Ubuntu 26.04), idle at first boot with the default install snippet and no feeds subscribed, Tiny Tiny RSS used ~69 MB of RAM and ~742 MB of disk (November 2026), and FreshRSS used ~16 MB of RAM and ~356 MB of disk (September 2026). Those are idle numbers, not a reader polling hundreds of feeds.
Both are 2 out of 5. FreshRSS is one docker run with the installation
finished in the web UI; Tiny Tiny RSS is a compose file with a generated
database password and admin password in .env.
Choose Tiny Tiny RSS if you already use it and its plugins, want a PHP reader with PostgreSQL, and are comfortable following a community continuation.
Choose FreshRSS if you want a single project with one home, a smaller footprint (the lower RAM and disk we measured), the Google Reader API for mobile apps, XPath scraping and extensions.
Both installs are verified on Ubuntu 26.04; the files are on the Tiny Tiny RSS and FreshRSS pages. Either fits the smallest plan most providers sell. Put a reverse proxy with TLS in front of either one, and keep a backup of the database or data volume.
FreshRSS lists a lower minimum: 256 MB vs 512 MB for Tiny Tiny RSS.
No. Tiny Tiny RSS is GPL-3.0, FreshRSS is AGPL-3.0.
FreshRSS for the smaller footprint (~16 MB against ~69 MB idle in our first-boot check), a single-container install, the Google Reader API and XPath scraping. Tiny Tiny RSS if you already rely on it and its plugins and accept following the community fork.
Its README says the original project at tt-rss.org "was retired on 2025-11-01" and the tt-rss/tt-rss repository is a fork as of 2025-10-03, created by a long-time contributor, with the stated goal to continue development. Our install pins one of the images that fork publishes.
Its README lists PostgreSQL 10+, SQLite, MariaDB 10.6+ or MySQL 8.0+. Our Tiny Tiny RSS install runs on PostgreSQL.
In FreshRSS only once you set CRON_MIN; our snippet does. Our Tiny Tiny RSS install has a separate updater service.
Paid link — we earn a commission if you shop through it.
Minimalist single binary vs. feature-rich and themeable.
A whiteboard-and-docs workspace on a plain Compose file vs. native apps on a commercial server.
A full identity platform vs. a passkey-only sign-in box.