A childhood archive your kid can actually inherit

Here’s an uncomfortable exercise: whatever you’re keeping your kid’s childhood in right now — an app, a cloud album, a subscription service — imagine it in 2044. Your kid is grown. The company was acquired twice and sunset the product in 2031. What, exactly, do they inherit?

For most services the honest answer is: whatever you remembered to download before the shutdown email’s deadline, in whatever format the export tool produced, if you still had a login. That’s not an archive. That’s a lease with sentimental stakes.

A digital memory box for your child is what every one of these services says it is. Every childhood time capsule app makes some version of the same promise. Almost none are built like one. A box has one defining property: it doesn’t need the company that made it. You can put it in a closet for a decade, hand it across a kitchen table, open it with your hands. The digital versions mostly need a login, a server, a subscription in good standing, and a company still around to answer the door. The difference between those two objects is the subject of this essay — what survives twenty years, what quietly doesn’t, and how to tell which one you’re keeping.

What twenty years actually filters out

Twenty years is longer than most startups, most file formats’ fashionability, and several entire platforms. It is not longer than JPEG, MP4, MP3, or plain text — boring formats with billions of files in them survive because the world can’t afford to lose them. So the first rule of an inheritable archive: the moment it leaves the app, it must be ordinary files in boring formats, organized by something a human understands. Folders by date qualifies. A proprietary backup blob does not.

It’s worth naming the boring formats, because “ordinary files” sounds vague and isn’t. JPEG has opened on everything since 1992. MP4 plays on every device either of you will ever own. MP3 outlived the entire industry that fought over it. Plain text opens on any computer ever sold. And HTML — a page any browser can read — is the closest thing software has to paper. None of these formats has an owner who can discontinue it, and that’s the property that matters. A format with an owner can be licensed, metered, or retired. A format with billions of files in the wild belongs to everyone who has one.

Boring wins for a boring reason: the cost of abandoning these formats is spread across the whole world, so nobody can afford to pay it. An exciting format is a bet on a company. A boring one is a bet on inertia, and inertia has the better twenty-year record. The corollary cuts the other way — a database only one app can read, a “memories” bundle that needs the company’s viewer, a backup that only restores into the service it came from — each of those is a bet that one specific business outlives your kid’s childhood. Some will. You don’t get to know which.

An export that needs a server isn’t an archive. It’s a hostage with visiting hours.

That sentence is the whole test. It doesn’t matter how generous an export looks on paper if reading it requires the company’s server to still be answering. An archive is something that works in a drawer — no account, no internet, no one’s permission. If the files only make sense while the service is alive, what you own isn’t the archive. It’s the visiting hours.

The index is the inheritance

A shoebox of ten thousand unlabeled photos and a hard drive of ten thousand unlabeled files are the same object at different temperatures. What makes an archive inheritable isn’t storage — it’s that a stranger can find something in it. Dates, ages, and above all context: what was asked, what was answered, why this photo exists. Text is the miracle format here. It’s tiny, it’s greppable, and it will open in anything, forever.

Folders by date is the entire organizing system required, and its plainness is the point. Not albums, not tags, not an app’s idea of a “moment” — a folder named 2029, folders inside it named by month, files inside those. Dates are the one ordering principle a stranger can read without instructions. Your kid at thirty, opening this cold, knows what a year is. They can’t be expected to reconstruct what your tagging system meant, and no future software can be expected to guess what a discontinued app meant by a smart album.

This is also where the camera roll, for all its real strengths, falls short as an inheritance. The photos are safe and superbly backed up. But it’s an archive of your whole life with a childhood scattered through it, and the context lives in your head, not in the files. The fuller, fairer version of that argument is in why not just use your camera roll — the short version is that it stores pictures very well and reasons not at all.

What makes a digital memory box inheritable

Put the pieces together and inheritable turns out to mean three specific things, none of them technically impressive. The files are ordinary — formats the world can’t afford to lose. The order is legible — folders by date, so a stranger can walk in without a map. And the context travels with the thing it explains — what was asked, what was said, how old they were, in plain text sitting next to the file it belongs to. Everything else about a memory app is furniture. Those three are the house.

There’s a fourth property, and it changes how you write: an inheritable archive has a reader, and the reader isn’t you.

The clearest case is a sealed letter. Write your kid a letter meant to be opened at eighteen and every ambiguity falls away. You know exactly who it’s for. You know they can’t read it now. You know you won’t be standing next to them to explain it, so you explain it on the page — you date it, you say who you are and who they are this month, not just what happened. A letter like that is written for the heir instead of the writer, and it’s the one entry in the whole archive where that’s unavoidable. Once you’ve written one, the rest of what you keep tends to improve, because you’ve finally met the person you were keeping it for.

Letter

Write them a letter about exactly who they are right now. Seal it until a birthday you choose.

No app is required for that one. Paper in an envelope passes every test in this essay: ordinary format, obvious to a stranger, context included, opens without a server. If it lives digitally instead, the same rules hold — plain text, dated, filed under the year it was written, with the opening date somewhere nobody can miss it.

Questions to ask any app holding a childhood

Can I export everything, free, without support tickets? Is the export readable with no account and no internet — double-click a file, see the childhood? If I stop paying, is anything deleted, and what exactly? And is there a written answer to “what happens when they turn eighteen?” — because handoff is the entire point, and an app with no answer is telling you it never thought about the person all this was for.

An app worth trusting has answered these in public, in writing, where walking an answer back would cost something. Ours are on the promise page — exactly what happens if you stop paying, and exactly what happens if we go away — because an answer that lives in a support inbox isn’t a policy. It’s a mood.

We built Vellum’s export to pass this interview: a zip of ordinary files in date folders, plus an index.html that opens in any browser, offline, forever. Free even if you stopped paying years ago. But whatever you use — make it pass. Someone specific inherits this, and they can’t log in.