In the age of the cloud, we like to imagine our data is immortal. We upload, sync, and back up with the quiet faith that somewhere, on a server blinking in a desert warehouse, our digital selves will outlast our bones. But there is a quieter, stranger truth: files decay. Not in the physical sense—no rust, no water damage—but in the ontological sense. They become unreadable, forgotten, orphaned by software updates, locked in obsolete formats, or simply lost in the infinite recursion of folders within folders. I call this condition Filepo —a portmanteau of file and epitaph —the slow, silent poetry of digital rot.
In a corporate context, Filepo is a liability. In a personal context, it is a kind of digital archaeology. But in an artistic or philosophical sense, it is a mirror. Our files are extensions of our memory. When they rot, we confront the fragility of our own recall. The .jpg that now only renders the top third of a photograph—what face is missing? The .mp3 that plays static instead of a song—what melody is lost? We become archivists of our own forgetting. filepo
Some might call this a problem to be solved: better emulation, more robust standards, AI reconstruction. But that misses the point. Filepo is not a bug; it is a feature of the digital condition. It reminds us that information is not eternal, no matter what the cloud vendors promise. It teaches us that every save is also a potential goodbye. And it gives us, in its silent, broken way, a strange and beautiful genre: the literature of what no longer renders. In the age of the cloud, we like