How to Sync an RSS Reader Across Phone and Laptop
I cleared 46 items on the train on a Tuesday, closed my phone, opened the laptop at my desk, and there they were again. All 46, bold, unread, in a different order.

I cleared 46 items on the train on a Tuesday, closed my phone, opened the laptop at my desk, and there they were again. All 46, bold, unread, in a different order. I spent the next ten minutes marking the same things read a second time, which is a brilliant way to make a tool you chose for calm feel like a chore you inherited.
The thing I had wrong took me embarrassingly long to see. I had installed a good reader on the phone and a good reader on the laptop and assumed that two copies of my subscription list meant one reading session. They do not. An RSS app on its own is a window, and if nothing behind the window is keeping score, each window keeps its own. Sync is a separate decision, it usually costs either money or a server, and it is the single change that turns a reader from fiddly into invisible.
The part nobody tells you about reader sync
Read state lives on a server, not in your apps. When sync works properly, your phone app and your desktop app are both clients talking to the same account, and that account holds three things: which feeds you follow, which items you have read, and which ones you starred. The app is interchangeable. The account is not.
Most of these services speak a protocol inherited from Google Reader, which shut down in 2013 and somehow still shapes this whole corner of the web. Fever, Feedbin and Miniflux all expose variations of it, which is why a client like Reeder can sign in to half a dozen different backends from one login screen. That inheritance is good news for you. It means you can switch apps without touching your subscriptions, and switch backends without rebuying apps.
What it does not mean is that copying an OPML file counts as syncing. An OPML export carries your feed list and nothing else. Do that on two devices and you get two separate reading histories that happen to follow the same sites, which is exactly the trap I fell into on that train.
What the backends cost and who they suit
Prices checked this month. I have used the first four myself for at least three months each, and the two self hosted options for about a year between them.
| Service | Price | Feed limit | Best for |
|---|---|---|---|
| Feedbin | $5 a month | No practical limit | People who want it to just work and never think again |
| Inoreader free | Free | 150 feeds | Trying sync before paying for it |
| Inoreader Pro | About $100 a year | 2,500 feeds | Rules, filters and search across years of archive |
| NewsBlur | $36 a year | Generous | Anyone who likes the training and comment features |
| Feedly Pro | About $8 a month | 1,000 feeds | Teams already sharing boards there |
| Miniflux, self hosted | Free, plus a $5 server | Yours | Low maintenance, very light, no mobile app of its own |
| FreshRSS, self hosted | Free, plus a $5 server | Yours | People who want extensions and full text rules |
| iCloud, via NetNewsWire | Free | Apple devices only | One person, two Apple devices, modest feed count |
Two notes on that table. The self hosted rows are only free if your time is worth nothing, which it is not, so read them as roughly $60 a year in hosting plus an hour or two of attention across the year. And the Inoreader free tier is genuinely useful rather than a crippled demo, so if you follow under 150 sites it is the obvious place to start. The mechanics of running your own are covered in self hosting a reader with FreshRSS or Miniflux.
The free Apple route is weaker than people claim
Every thread on this subject has someone saying you do not need to pay anything, just use NetNewsWire with iCloud sync. I ran that setup for four months on a phone, an iPad and a Mac, and I would not recommend it to anyone following more than about eighty feeds.
The problem is architectural rather than buggy. With iCloud sync there is no server fetching your feeds on a schedule. Each device fetches independently, then tries to reconcile what it found through a shared database. So an article that appeared at 09:00 reaches your Mac when you open the Mac, and your phone when you open the phone, and the read states meet somewhere in the middle later. On my setup, read state took anywhere from twenty seconds to over five minutes to appear on a second device, and twice a week I would see an item come back unread after I had dealt with it.
The second cost is invisible until you look for it. Because every device does its own fetching, your phone is downloading a hundred feeds over cellular rather than receiving a tidy delta from a server. My battery graph on the iPad showed the reader as the third heaviest app in a week when I had barely opened it.
Where the free route genuinely wins is the single device case, or a quiet list of twenty sites checked on a phone and a Mac that are usually both awake. That describes a lot of people, and if it describes you, keep your $5. It did not describe me, and $60 a year to stop re reading things turned out to be the easiest subscription I have ever justified.
Where counts still drift after you fix sync
Proper server sync removes about 90 percent of the weirdness. The remainder comes from settings inside your apps, and these are the four that have cost me the most confusion.
- Mark as read on scroll. On a phone this quietly marks items you flicked past at speed. On the desktop it usually does not, so one device thinks you read things the other still shows. Pick one behaviour and set it the same way everywhere.
- Different refresh intervals. A desktop app polling every 10 minutes and a phone polling hourly will show different totals for up to an hour, and neither is wrong. With a hosted backend you can usually turn client refresh down to manual and let the server do the schedule.
- Per folder sort order. Oldest first on one device and newest first on the other makes the same fifty items feel like two different queues. This is the setting that made me think my sync was broken when it was fine.
- Local caching for offline reading. Apps that pre download articles sometimes hold read state until the next successful connection. If you read on a plane, expect a burst of corrections when you land rather than instant agreement.
If you are setting this up today, do it in this order. Create the backend account first and import your OPML there, not into an app. Then sign both apps in to that account and let each one finish its first full sync before you touch anything, which takes two to fifteen minutes depending on feed count. Then delete the old local subscription lists from both apps, because leaving them creates duplicate items that look like a sync fault and are not. That last step is the one people skip, and it is close kin to the care needed when moving your feeds to a new reader cleanly. The rest of what I have written about readers sits in the readers section.
FAQ
Can I sync without paying anything at all?
Yes, three ways. The Inoreader free tier up to 150 feeds, iCloud sync if you are entirely on Apple hardware, or your own Miniflux instance if you already pay for a server for something else. Each has a real limit, and the $5 a month option exists because those limits annoy people eventually.
Do I lose starred items if I switch backends?
Often, partly. Feed lists move cleanly through OPML, and starred items usually do not, because OPML has no field for them. Most services offer a JSON export of starred articles, so pull that before you cancel anything, and expect to keep it as an archive rather than reimport it.
How many devices can one account cover?
Every service I have listed allows unlimited clients on a personal account. What they rate limit is how often each client may ask for updates, which is why setting your apps to manual refresh and trusting the server schedule gives a better result than three apps all polling hard.
Does sync get slower as the archive grows?
The first sync does, noticeably. Signing a new app into an account with 400 feeds and years of history took about eleven minutes on my phone over wifi. After that it exchanges only changes, and the daily experience is the same whether you follow forty sites or four hundred.
More in RSS Readers
RSS Readers
Duplicate Articles in Your RSS Reader and How to Fix It
One Tuesday in September I opened my reader to 140 unread items and found that 23 of them were the same nine articles.
RSS Readers
How to Find and Remove Dead Feeds From Your RSS Reader
Last month I exported my subscriptions and counted them for the first time in two years. There were 214 feeds.
RSS Readers
Getting Full Text RSS From Feeds That Only Send Summaries
You open your reader on the train, tap a post from a blog you like, and get two sentences and a "Read more" link.