How FeedFlow Syncs Feeds Across Devices
Updated
FeedFlow does not force you into one sync model. You can keep everything local on a single device, sync through iCloud on Apple hardware, use Dropbox or Google Drive for cross-platform cloud sync, or connect to a self-hosted service such as FreshRSS, Miniflux, Feedbin, or BazQux. The right choice depends on how many devices you read on and whether you want your feed data sitting in someone else's cloud.
The sync options at a glance
| Sync method | Works across | Account needed | Data lives |
|---|---|---|---|
| Local only | One device | No | On your device |
| iCloud | Apple devices (iOS, macOS) | Apple ID | Apple iCloud |
| Dropbox | Android, iOS, macOS, Windows, Linux | Dropbox | Dropbox |
| Google Drive | Android, iOS, macOS, Windows, Linux | Google Drive | |
| FreshRSS / Miniflux / Feedbin / BazQux | Cross-platform | Per service | Your server or the service |
FeedFlow is available on Android, iOS, macOS, Windows, and Linux, so the sync method you pick also decides which of those platforms can see the same read state and subscriptions.
Choosing based on your situation
If you read on one device only
Stay local. FeedFlow requires no account, and your articles stay on your device. This is the simplest setup and the one to pick if privacy or offline use matters more than multi-device access. The trade-off is obvious: nothing follows you to a second device.
If you live entirely in Apple's ecosystem
iCloud is the natural fit. It syncs across Apple devices without adding a third-party account, and it keeps the setup inside the ecosystem you already use.
If you mix platforms
Dropbox or Google Drive is the cross-platform route. Because FeedFlow runs on all five major platforms, this is what lets a Windows desktop and an Android phone share the same feed list and read state. Pick whichever cloud account you already trust with your data.
If you want to own the backend
Point FeedFlow at a self-hosted or independent service: FreshRSS, Miniflux, Feedbin, or BazQux. This is the option for people who already run a feed server or want to avoid the big cloud providers. One reviewer noted it "works great with my FreshRSS server," which is the typical use case here.
What stays consistent no matter which you pick
- No lock-in. FeedFlow states there is no lock-in, so you can change sync setups later rather than committing permanently.
- OPML import and export. You can migrate from another reader in minutes, and move your subscriptions between setups.
- Organization carries over. Categories, bookmarks, keyword blocking, and search work alongside whichever sync method you choose.
A practical way to decide
- Count your devices. One device means local-only is enough.
- Check the platforms. All-Apple points to iCloud; a mixed set points to Dropbox, Google Drive, or a self-hosted service.
- Decide who holds the data. If the answer is "nobody but me," go local or self-hosted. If convenience wins, use a cloud drive you already have.
Because the sync layer is swappable and there is no lock-in, this is not a permanent decision — you can start local and add sync later, or move from a cloud drive to your own server when your needs change.