The Archive Problem: What Goes When a Blog Goes

By Rook Castellane · Platform writer · Published 16 August 2026

Blogs on BDSMLR and networks like it go dark. Sometimes the owner deletes one in an afternoon, sometimes it’s an account that stops loading and never starts again, sometimes it just stops updating and a year later the whole thing is gone without anyone announcing it. Anyone who has followed the same tags for a few years has a short list of blogs they used to read and can’t find now.

The images from those blogs are mostly still out there. The blogs are not, and the gap between those two facts is the thing worth understanding before it applies to yours.

What a blog is holding

If you’ve run a blog for a couple of years, take an inventory of what’s actually on it that exists nowhere else:

• The selection. Thousands of decisions about what belonged and what didn’t. That’s the work, and it isn’t stored in any of the files.
• The order. What sat next to what, which post you spaced out and which run you let build. Invisible until it’s gone.
• Your captions and tags. Usually the hardest part to reconstruct, because you wrote them once, quickly, and have no memory of them.
• The source trail. Every link on your blog that pointed at an original. When your blog goes, those pointers go, and they were often the last surviving copy of where something came from.
• Anything of your own. Originals you posted, which may live only there and on whatever reblogs happened to catch.

The images are the only item on that list that other people have copies of. Everything else is yours alone, which is a strange thing to realise about a blog made almost entirely of other people’s pictures.

”It’s all still online somewhere”

This is the sentence that stops people backing anything up, and it’s true in a narrow sense and misleading in every useful one.

Popular posts do survive. Something reblogged a few thousand times will still be findable, minus its caption, minus its credit, spread across blogs that will themselves go dark eventually. So the images with the widest reach persist and everything else quietly doesn’t.

The parts of your blog you’re most attached to are usually the least-reblogged ones. The odd find nobody else picked up. The post that got eleven notes and was the best thing you put up that month. Reach and quality are only loosely related, and the archive that survives by accident is selected purely on reach.

Then there’s the retrieval problem. Even for content that technically still exists, “somewhere online” means an unnamed blog among many thousands, with no caption to search for, no source to look up and no title. You can’t find an image again by remembering it. Search on a network like this runs on tags, and tags belong to posts rather than to the thing in the picture.

The three losses arrive together

What makes a blog going dark feel worse than it should is that the media, the arrangement and the trail all vanish in the same instant. A post you reblogged with a source link and a caption becomes, in the same moment, an image you can’t find, in an order you can’t remember, from a creator you can no longer name.

That last one is why archiving connects directly to credit and sourcing. Every blog that keeps its source lines is holding part of the network’s memory of where things came from. When enough of those go, an image doesn’t just lose one attribution, it becomes permanently unattributable, and no amount of later goodwill undoes it.

What an export habit actually protects

Backing up doesn’t protect the pictures. Other people have those. It protects the parts of your blog that only exist as your blog, which changes what you should be saving.

The mechanics of saving media and exporting are covered separately. What matters at the practice level is that a folder of images is a weak archive, because it drops the exact things that were unique. A useful archive keeps the media alongside a record: what the post was, what you wrote on it, what tags you used, where it came from, roughly when you put it up.

If that sounds heavy, note that the record on its own, with no media at all, rebuilds more of a blog than the media on its own does. A list of a few hundred posts with sources and captions can be worked back through. A folder of a few hundred untitled images cannot be worked back into anything.

Keeping a list, not just a folder

The habit that survives is the one that costs almost nothing per week:

• Save your own originals at full resolution the day you post them. These are the only items nobody else can restore.
• Keep a plain running file of anything you’d be annoyed to lose: a line per post with the source and your caption. Plain text, dull, portable, still readable in ten years.
• Export on a schedule, not on a feeling. Whatever interval you’ll actually keep. The archive you update twice a year beats the one you plan monthly and abandon.
• Do it while everything is fine. You can’t export a blog you can’t reach, and the moment you most want a backup is the moment it’s no longer possible to make one.
• Keep two copies in two places. One device failing shouldn’t take the record with it.

Nobody does all of this. Doing the first two puts you well ahead of where most blogs stand when they end.

The queue’s quiet role

A well-stocked queue is a partial archive by accident. Everything sitting in it has already been chosen and is waiting somewhere other than the public blog, which means a queue with a few weeks in it is a few weeks of curation that survives a bad afternoon on the platform.

That’s a side effect and not a backup strategy, and it cuts the other way too: a queue is stored on the same platform as the blog, so it goes when the blog goes. Worth knowing rather than worth relying on.

When a blog you follow disappears

You’ll notice it late, usually weeks after the fact. There’s a small window while your own reblogs still remember: search your blog for the name, look at what you took from them, and save the ones you’d want. Your own archive is often the last surviving index of somebody else’s blog, which is a decent argument for keeping one even if you never lose anything yourself.

And if the blog that stopped was yours, or is heading that way, the deciding is its own question. The archiving is the part to do first, in either direction, because it’s the only step that can’t be taken afterwards.

In practice

Blogs on reblog networks end, and when one does the images usually survive somewhere while the blog itself does not. What actually disappears is the part nobody else has a copy of: which posts were chosen, the order they sat in, the captions and tags the owner wrote, every source link that pointed outward, and any original work that lived only there. People assume all of it is recoverable because the pictures are still circulating, but the widely reblogged posts are the ones that persist, and those are rarely the posts an owner would most want back. The blogs that come through a loss intact are the ones whose owners kept a dull, boring record alongside the files.

For beginners

Save your own originals at full resolution on the day you post them, because those are the only items nobody else can restore. Then keep a plain text file with a line per post you'd hate to lose: what it was, your caption, the source. That file rebuilds more of a blog than a folder of untitled images ever will. Do it on a schedule you'll actually keep, while everything is working, since you can't export a blog you can't reach.

For experienced users

Long-running curators archive the metadata as seriously as the media, and keep two copies in two places. They also know their own archive doubles as an index of other people's blogs: when a blog they followed goes dark, their own reblogs are often the last surviving record of what was on it, which is worth acting on in the first week rather than the first year. They treat a stocked queue as a small accidental buffer and not as a backup, since it lives on the same platform as the blog and goes when the blog goes.