When we talk about preserving video games, the first thing that often comes to mind is keeping the files.
The executable still exists. The disc has been archived. The ROM has been dumped. The original assets have been stored somewhere safely.
Technically, the game has survived.
But is that enough?
Games are unusual compared with many other forms of media because preserving the original data does not always preserve the experience.
A photograph can still be viewed decades later.
A recording can be transferred to a new format.
A book can be scanned and read on almost any modern device.
A game is different.
It may depend on a particular operating system, graphics API, controller, authentication server, online service or piece of hardware that no longer exists.
You can have every original file and still be unable to actually play it.
That raises an important question about what video game preservation is supposed to protect.
Is the goal to preserve the original software exactly as it was?
Or is the goal to preserve the ability for future players to experience the game?
Those two goals are not always the same.
Imagine an old PC game that no longer launches on a modern operating system.
A community patch might change a few files, replace an obsolete library or modify the renderer so the game works again.
It is no longer completely untouched.
But without those changes, the original version may eventually become practically inaccessible.
Which version is better preserved?
The untouched game that no longer runs, or the modified version that people can still play?
Online games make the problem even more complicated.
A complete copy of the client may survive, but if the original servers disappear, major parts of the game can disappear with them.
Menus may open.
Characters and textures may still exist.
The executable may even launch.
But the actual experience — the world, matchmaking, progression, events or interactions that depended on those servers — may be gone.
In that situation, preserving the files is almost like preserving the pieces of a machine without preserving the ability to turn it on.
There is also the issue of context.
Games change through patches.
Music or licensed content can be removed.
Servers change balance values.
Expansion packs alter systems.
Community mods sometimes become essential for running older titles.
Even identifying the version that should be preserved can become difficult.
Should preservation focus on the launch version?
The final official patch?
The version most people remember?
Or every significant version of the game?
There may not be one correct answer.
But I think game preservation has to involve more than preventing files from disappearing.
Documentation matters.
Compatibility matters.
Servers can matter.
Manuals, patches, tools and community knowledge can matter.
Sometimes even the hardware surrounding the game is part of understanding how it was originally experienced.
The most successful preservation may therefore be the kind that protects both things:
the original historical material and a practical way to experience it.
Because a game that exists somewhere on a hard drive but can never be played again has been preserved in one sense.
In another sense, part of it has already been lost.
What do you think should count as true video game preservation?
Is saving the original software enough, or should preservation also make sure future players can actually run and experience it?
And when modifications are necessary to keep an old game playable, do those changes protect the game or change what is being preserved?
When we talk about preserving video games, the first thing that often comes to mind is keeping the files.
The executable still exists. The disc has been archived. The ROM has been dumped. The original assets have been stored somewhere safely.
Technically, the game has survived.
But is that enough?
Games are unusual compared with many other forms of media because preserving the original data does not always preserve the experience.
A photograph can still be viewed decades later.
A recording can be transferred to a new format.
A book can be scanned and read on almost any modern device.
A game is different.
It may depend on a particular operating system, graphics API, controller, authentication server, online service or piece of hardware that no longer exists.
You can have every original file and still be unable to actually play it.
That raises an important question about what video game preservation is supposed to protect.
Is the goal to preserve the original software exactly as it was?
Or is the goal to preserve the ability for future players to experience the game?
Those two goals are not always the same.
Imagine an old PC game that no longer launches on a modern operating system.
A community patch might change a few files, replace an obsolete library or modify the renderer so the game works again.
It is no longer completely untouched.
But without those changes, the original version may eventually become practically inaccessible.
Which version is better preserved?
The untouched game that no longer runs, or the modified version that people can still play?
Online games make the problem even more complicated.
A complete copy of the client may survive, but if the original servers disappear, major parts of the game can disappear with them.
Menus may open.
Characters and textures may still exist.
The executable may even launch.
But the actual experience — the world, matchmaking, progression, events or interactions that depended on those servers — may be gone.
In that situation, preserving the files is almost like preserving the pieces of a machine without preserving the ability to turn it on.
There is also the issue of context.
Games change through patches.
Music or licensed content can be removed.
Servers change balance values.
Expansion packs alter systems.
Community mods sometimes become essential for running older titles.
Even identifying the version that should be preserved can become difficult.
Should preservation focus on the launch version?
The final official patch?
The version most people remember?
Or every significant version of the game?
There may not be one correct answer.
But I think game preservation has to involve more than preventing files from disappearing.
Documentation matters.
Compatibility matters.
Servers can matter.
Manuals, patches, tools and community knowledge can matter.
Sometimes even the hardware surrounding the game is part of understanding how it was originally experienced.
The most successful preservation may therefore be the kind that protects both things:
the original historical material and a practical way to experience it.
Because a game that exists somewhere on a hard drive but can never be played again has been preserved in one sense.
In another sense, part of it has already been lost.
What do you think should count as true video game preservation?
Is saving the original software enough, or should preservation also make sure future players can actually run and experience it?
And when modifications are necessary to keep an old game playable, do those changes protect the game or change what is being preserved?