The Quiet Succession of the File Format Heir
Last week, I tried to open a document from 2007. It was a simple project proposal, saved with a ‘.sxw’ extension. My modern word processor shrugged. So did Google Docs. It was a digital artifact from my own past, yet it was as inaccessible as if it had been carved on a stone tablet. After a brief, frantic search for a converter, I found it: the file opened, pristine, in a niche open-source application I’d never heard of. This minor crisis wasn't caused by data loss or a broken link. The file was perfectly preserved. The problem was subtler: I had lost the crown prince, the designated successor to the software that created it.
In the kingdoms of digital preservation, we talk a lot about the longevity of data itself—the immutable bits on a disk. But we talk less about the quiet, ongoing drama of succession planning for the applications that give those bits meaning. Every proprietary file format is like a monarchy; it relies on a single, ruling piece of software to interpret its laws. What happens when that software is dethroned? When a company goes under or a product is sunset, the format’s kingdom can fall into a dark age unless a clear heir is appointed. An ‘heir’ in this context is an application, often open-source, that can not only read the old format but is itself built to be maintained by a community, ensuring its own line of succession stretches into the future.
The Problem of the Childless Monarch
This is where the metaphor becomes painfully real. Consider the ‘.sxw’ file. It was the native format for OpenOffice.org 1.0, a revolutionary suite in its day. But OpenOffice.org, as a project, was eventually superseded by forks like LibreOffice and Apache OpenOffice. The original ‘monarch’ effectively abdicated. My file was an orphan until LibreOffice, the legitimate heir, recognized its claim to the throne. This succession was peaceful only because the original format was open. The source code was available, allowing new stewards to learn its language and keep the court running.
This is the critical difference between open and closed formats. A closed format, like an ancient proprietary CAD drawing or an old video game save file, is an absolute monarchy with no line of succession. When the last copy of the original software ceases to run on modern hardware, the format’s meaning dies with it. The data remains, but it’s gibberish. It becomes a puzzle for digital archaeologists, who must reverse-engineer the royal decrees from fragments and rumors. The appointment of an heir is impossible because the laws of the kingdom are secret.
The work of web archiving and digital preservation, then, isn't just about making copies. It’s about actively cultivating these heirs. It’s about advocating for and using open, well-documented formats—the equivalent of establishing a constitutional monarchy with a clear and democratic process for succession. PDF/A for documents, FLAC for audio, TIFF for images: these are formats whose specifications are public knowledge. Their rule does not depend on the health of a single corporation. They have many potential heirs, any of whom can step up to interpret the data when the time comes. My ‘.sxw’ file had a lucky escape. It serves as a humble reminder to ensure our own important records are governed by formats with a future, not just a past.
Notes & further reading
A few pages I came back to while writing this: