Back Up and Move Your Feed List

Published: September 14, 2026. Updated: October 2026 by Andrew Apell, who builds RSS Wrangler and previously built Flookup Data Wrangler

Quick Answer

Here is the short version. Export your feed list to an OPML file, keep dated copies somewhere you control and you can move to another reader in minutes. One thing to remember: OPML carries the list and its folders, not your read history or saved articles.

I would guard my subscription list above everything else in my reader. It is years of sources I found, and no search engine can rebuild it for me. OPML packs the whole lot into one small file. A backup takes seconds and switching readers takes minutes. In this guide I will cover what OPML is, how to export it, where to store it and how to restore from it.

What OPML Actually Is

OPML stands for Outline Processor Markup Language. I only care about what it does: it lists feed subscriptions, usually with titles, feed URLs and folder structure, in plain XML that almost every reader can export and import. There is no read history and no settings in there, just the list. I think of it as a contacts backup for my reading life, not a full clone of my reader.

Exporting Your List

In most readers the option sits under settings, subscriptions or an export menu, often labelled OPML export or download subscriptions. I put the date in the filename, something like feeds-2026-09-23.opml, so I can tell my backups apart. If a reader offers no export at all, I treat that as a warning sign about how portable my list really is.

Where to Keep the Backup

The file is tiny, usually a few kilobytes. I keep several copies without thinking twice:

  • Dated, not overwritten. I keep the last few exports, so a corrupted or accidentally emptied list cannot spread into my only good copy.
  • With my documents. A copy in my normal documents folder or cloud drive survives a lost device.
  • With my password manager. Many managers accept file attachments, which puts the backup behind my strongest authentication.

I export again whenever my list changes meaningfully, and at least once a quarter. There is no reason to ration backups of a file this small.

Restoring and Switching Readers

Importing is just exporting in reverse. I find the import or upload option in the new reader, point it at my OPML file and confirm. Folders usually survive the trip, while read states and starred items generally do not, so I export those separately first if my reader supports it. The whole move takes minutes. It is exactly the position Google Reader's shutdown taught users to want: read our account of what that shutdown taught RSS users.

Think of OPML as a contacts backup for your reading life, not a full clone of your reader.

What Is Actually Inside the File

OPML is a very small format. Knowing what is inside tells me exactly what a backup protects against. Feed lists use version 2 of the specification, and each subscription is one outline element carrying a handful of attributes.

Attribute What it holds
xmlUrl The address of the feed itself. This is the only attribute that matters functionally.
title The name the subscription had in the reader. Cosmetic, and often stale.
htmlUrl The website the feed belongs to, when the reader knew it.
type Usually rss, which distinguishes a feed entry from a folder entry.
category Optional folder path, which is how folder structure survives.

That is the whole format. It is deliberately boring, which is why almost every reader can read and write it. It protects one specific thing: the list of addresses I subscribed to.

What OPML Cannot Carry

I find the boundary as useful as the capability. People have restored a backup expecting a full recovery and found an empty screen.

  • Per-feed settings. Refresh intervals, background refresh flags, mute rules and keyword alerts are local settings, not subscription data.
  • Read and unread state. Nothing in the file records which articles I had already read.
  • Cached article bodies. The file holds addresses, not content. Anything the reader had downloaded is lost with it.
  • Notes and search indexes. Anything I wrote myself stays where I wrote it.
  • Saved articles, favourites and highlights. They usually stay in the reader that created them.

So I hold one model in my head: a contacts backup, not a disk image. It gets my subscriptions into a new reader. It does not get my reading history back.

If You Use RSS Wrangler, Read This Part

Everything above describes OPML, the format nearly every other reader exports. RSS Wrangler uses JSON for its own export and import, so this is the one part that does not apply to the extension you may be reading from. The reasoning is unchanged. Only the file format differs.

  • Export. I open Settings, find Data Management and choose Export Feeds. That downloads a JSON backup of my subscription list.
  • Import. Import Feeds reads JSON only. It adds any feed not already in my list and skips the ones I have, so importing the same backup twice is harmless. OPML files are not supported, and the extension does no conversion.
  • Coming from another reader? Export OPML from the reader you are leaving, read the list and add the feeds here, one at a time or in batches, by pasting each address into Add Feed. It is more manual than an import. That is the honest state of things.
  • Staying on RSS Wrangler? Export before you clear anything, and keep the JSON next to any older OPML backups. The two formats are not interchangeable, so I keep both in one folder rather than assume a single format.

Verifying a Restore Actually Worked

The most common failure after a restore is not an error message. It is a short list and the assumption that it is complete. Two minutes of checking is worth it.

  1. Count before and after. Note how many subscriptions you had in the old reader, then compare with the new one. A silent difference of a dozen is normal, because dead feeds often fail to import. I make it a decision rather than a surprise.
  2. Check the oldest feeds first. The subscriptions most likely to be dead are the ones I added years ago. If a feed will not load, I note the address rather than delete it, so I can look for a replacement later.
  3. Look for duplicates. Importers vary in whether a feed added twice is merged or duplicated. I search my list for a title I recognise twice before assuming the tool handled it.
  4. Confirm folders became categories. If the old reader used folders, I check that the structure survived rather than assume it did.

Once the count and the duplicates agree, I delete the trial export only after the new reader has refreshed successfully at least once. A backup that has not survived a refresh is not yet a backup.

If the exported list opens as a spreadsheet, I find it quicker to clean the exported list before importing, so duplicates and dead addresses do not return.

FAQ

What is an OPML file?

At its core, OPML is a simple XML format for listing feed subscriptions, usually with titles, URLs and folder structure. Almost every reader can export it and import it.

How often should I back up my feeds?

I export whenever my list changes meaningfully, and at least once a quarter. The file is tiny, so there is no reason to ration backups.

Does OPML carry read history?

No. OPML carries subscriptions, titles and folders, not read states or starred items. I treat it as a list backup and export starred items separately if my reader supports it.

Summary

Feeds come and go, but my list should outlive every reader. Export it to OPML, keep dated copies somewhere I control and I can move anywhere in minutes.

Keep Your Feeds Where Shutdowns Cannot Reach

RSS Wrangler keeps subscriptions in your browser. No account, no cloud and offline support.

Add to Chrome
Project Slidecut