Feed Viewer logo Feed ViewerRead the web on your terms
Curation

How to Share an OPML Bundle People Will Actually Import

Someone asked me in September for my feeds on soil science and small presses. I did what I had done a dozen times before, exported everything, opened the file, deleted the folders that were none of her business, and sent her a 310 kilobyte...

Text editor showing an OPML file with a single folder of feed entries

Someone asked me in September for my feeds on soil science and small presses. I did what I had done a dozen times before, exported everything, opened the file, deleted the folders that were none of her business, and sent her a 310 kilobyte OPML with 94 subscriptions in it. She wrote back three days later. She had imported it, her reader had gone from 40 unread to 1,900 overnight, and she had unsubscribed from all of it by Friday.

That was my fault, not hers. A curated OPML bundle is not an export. An export is a backup of your habits, including the eleven feeds you keep out of guilt and the four that have not posted since 2021. A bundle is an edited object, and almost nobody edits one before sending it. I have made and shared nine of them since that September, and the ones people stayed subscribed to shared a few boring properties.

Twelve feeds, not ninety

The single strongest predictor of whether a bundle survives a week is how small it is. My soil and small press disaster had 94 feeds. The bundle I sent the same person in October had 11, and she still reads nine of them.

The arithmetic is not complicated. A reader with 11 subscriptions that each publish twice a week delivers about 22 items. That is a sitting. A reader with 94 subscriptions, which is a normal number for me and an insane number for a new arrival, delivers 300 or more, and the only rational response to 300 unread is to stop opening the app. I keep around four hundred subscriptions under control only because I have fifteen years of folder habits and filters propping them up, and I would not hand that scaffolding to anyone.

So the real work of making a bundle is subtraction, and the number I have settled on is eight to fourteen feeds. Under eight the thing feels like it was not worth the file. Over about fifteen you are back to handing someone your reading problem.

Volume is the thing you check, not quality

Here is the part I got wrong for years. I chose feeds for quality and ignored how often they publish, which meant a bundle of twelve excellent sources could still include one wire service that posts 60 times a day and quietly becomes the entire feed.

Before a feed goes in a bundle, I count its posts over the last 30 days. Anything over 25 posts a month gets a second look. Anything over 60 either goes out or goes in as a filtered feed, and since filters do not travel inside an OPML file, in practice it goes out. One high volume source will drown eleven good ones, and the person receiving your bundle will blame the bundle rather than the one offender.

A rough target for the whole bundle: 40 to 90 items a month arriving in total. That is one to three a day, which a person can read standing in a kitchen. My small press bundle lands around 55.

How to actually build the file

You do not need a tool for this. OPML is plain XML with one line per feed, and every reader I have tested handles a hand edited file without complaint.

  1. Make a fresh folder in your reader named for the bundle, something like Soil and Presses. Do not reuse a working folder.
  2. Drag or re-add the feeds you want into that folder. Re-adding is safer, because dragging in some readers moves the feed out of the folder where you actually use it.
  3. Export. Most readers export everything, not one folder, so expect to clean up. Inoreader and Feedly both dump the whole account. NetNewsWire exports per account.
  4. Open the file in a text editor and delete every outline element except your bundle folder and the feeds inside it. The structure is nested, so delete whole blocks, not single lines.
  5. Check the title attribute on the folder. Some readers write the folder name into the text attribute only, and a reader that reads title will import your feeds loose at the top level instead of grouped.
  6. Rename the file to something a stranger can identify six months later. Not feeds.opml. Something like soil-and-small-presses-2026-10.opml, with the month in it, because you will revise it.
  7. Import it yourself into a throwaway account before sending. This catches the one dead feed that has gone to a parked domain and the one that now redirects to a login wall.

That last step takes four minutes and has saved me embarrassment twice. The second time, a feed I had recommended for years had been sold and was publishing affiliate roundups under the same title, and I would not have noticed from my own folder because I had muted it with a keyword filter months earlier.

The advice I think is wrong

The common recommendation is to publish a public OPML file at a stable URL and keep it updated so subscribers always have the current version. It sounds obviously right. In practice I have stopped doing it.

Two reasons. First, almost no reader subscribes to an OPML file the way it subscribes to a feed, so updating the file does nothing for anyone who already imported it. Those 94 feeds sat in her reader regardless of what I did to my copy afterward. The stable URL creates an illusion of maintenance that only helps future importers.

Second, a public bundle gets built for an audience of nobody in particular, and that is exactly how you end up with 94 feeds again. The bundles that worked for me were made for one named person with a stated interest, which gave me permission to leave out the three feeds I love and she would not. Making one per request sounds like more work. It is maybe twenty minutes, and it is the difference between a file that gets used and a file that gets imported once as a courtesy.

If you do want something public, publish a page of annotated links instead and let people subscribe to the two or three they want. The annotation is the valuable part anyway, and writing those annotations well is a skill worth more than the file format.

What to send alongside the file

An OPML attachment on its own is a stack of URLs. I now send three short things with it, and the reply rate on whether people actually read the feeds went up noticeably once I started.

One: a count. Eleven feeds, roughly two items a day. People decide whether to import based on expected load, and giving them the number removes the fear.

Two: two sentences on why each of the three best ones is in there. Not all eleven. Three. The rest can earn their place.

Three: an exit instruction. Tell them to delete anything that annoys them in the first week, without asking you, and that you will not be offended. Readers accumulate guilt the way closets accumulate coats, and giving explicit permission to prune is the most useful thing in the message. If they ever want to do the bigger version of that pruning, our guide to auditing your subscriptions walks through it, and the curation section has the rest of how I keep four hundred of them from turning into noise.

FAQ

Do all RSS readers import OPML the same way?

Close enough. Folder handling is where they differ. Some flatten nested folders, some import the folder but not its name, and a few cap how many feeds they will add at once. Importing into a spare account first tells you which one you are dealing with.

Can I include newsletters in an OPML bundle?

Only if the newsletter has a real feed or you are sharing a gateway address, and a gateway address is yours, not theirs. Sending someone your personal newsletter inbox address in an OPML file is a mistake you make once.

How often should I revise a shared bundle?

I date the filename and revisit it when someone asks again, which in practice is every four to six months. Dead feeds, not new ones, are the usual reason for a revision.

What size file is too big to send?

Size is not the constraint, count is. A 12 feed bundle is around 3 kilobytes. If your file is over about 40 kilobytes you are sending an export, not a bundle.

LF
Leocadia Fennimore

Leocadia has used RSS since the days of Google Reader and never stopped. She edits the site's feed and reader coverage and keeps around four hundred subscriptions under control.

More posts by Leocadia

More in Curation

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto