1. Introduction
I love archiving old Quake files.
For me, it is part nostalgia, part historical research and part treasure hunt. There is something incredibly satisfying about finding a file that has been missing for decades, identifying an unknown release or reconstructing the history of a modification that has almost disappeared from the internet.
I have been creating and maintaining Quake archives for more than five years, covering Quake 1, Quake II and Quake III Arena. During that time, I have developed a collection of research techniques, tools and habits that help me find old files and make sense of incomplete historical information.
This guide brings together everything I have learned.
It is not intended to describe the only way, or even necessarily the best way, to archive old Quake material. It describes the way I do it, the methods I have found most productive and the approach I recommend based on my own experience.
My hope is that sharing these methods will help you create better archives, avoid some of the mistakes I have made and perhaps recover files that would otherwise remain lost.
Why I Archive Quake
I was in high school during the mid to late 1990s, when Quake 1, Quake 2 and Quake 3 were released.
These games had an enormous impact on me.
It was an exciting time to be interested in computers and games. The internet was still relatively new to most people, and Quake had an incredible community of players, programmers, artists and hobbyists creating new things.
There were modifications that changed how the games were played, bots that allowed you to fight computer-controlled opponents, new maps, utilities, total conversions and all kinds of experiments.
You could download something new, try it out and then look for something else. There was always another project, another update or another interesting idea.
Many of these projects were created by individuals or small groups of enthusiasts, often in their spare time. They were shared through personal websites, FTP servers, gaming news sites, forums and collections of files passed around the community.
Much of that material has since disappeared.
Websites went offline. FTP servers were shut down. Hosting services changed hands. Personal hard drives failed or were thrown away. Files that were once easy to download became difficult or impossible to find.
Sometimes I wish I could travel back to 1996, 1998 or 1999 and tell my younger self to back everything up.
Save those ZIP files. Copy those websites. Burn a few more CDs. Keep every version of that modification, including its readmes, patches, screenshots and source code.
Imagine having a complete record of a favourite Quake modification from its earliest development builds through every public release, with all the original files and contemporary announcements preserved.
That is the dream.
Everything we do as Quake archivists today is an imperfect attempt to reconstruct something that could have been preserved at the time.
Sometimes that is frustrating. You might know that a particular release existed, have its original filename and even know exactly where it was hosted, yet still be unable to find a surviving copy.
Other times it is incredibly exciting.
You discover an old FTP mirror, locate a forgotten magazine CD or find a file buried inside a collection that has not been properly indexed. Suddenly, something that seemed lost is available again.
I find the whole process genuinely fun.
It is a treasure hunt where the treasure is a 30-year-old ZIP file that might mean absolutely nothing to most people, but everything to someone who remembers playing it.
Archiving is also a way for me to give something back to a community that I loved growing up and still care about today.
My Experience Creating Quake Archives
Over the past five or more years, I have created a large number of archives covering different aspects of Quake history.
Some are substantial projects that attempt to reconstruct the complete release history of a modification or collection. Others are smaller investigations focused on finding particular files or documenting the known releases of an obscure project.
A few of my larger archives have become widely used and referenced by other members of the community.
For example, I maintain archives of the official releases of the three Quake games:
- Quake Official Archive
https://github.com/Jason2Brownlee/QuakeOfficialArchive - Quake II Official Archive
https://github.com/Jason2Brownlee/Quake2OfficialArchive - Quake III Arena Official Archive
https://github.com/Jason2Brownlee/Quake3OfficialArchive
I have also spent considerable time researching historical Quake bots, including:
- Quake Bot Archive
https://github.com/Jason2Brownlee/QuakeBotArchive - Quake 2 Bot Archive
https://github.com/Jason2Brownlee/Quake2BotArchive
Other projects focus on particular modifications and their development history include:
- ThreeWave Capture The Flag Archive
https://github.com/Jason2Brownlee/ThreeWaveCTF - TeamFortress Quake Archive
https://github.com/Jason2Brownlee/TeamFortressQuakeArchive - Quake Rally Archive
https://github.com/Jason2Brownlee/QuakeRallyArchive
And many more.
Not every archival project needs to be this comprehensive.
Sometimes someone contacts me looking for a particular modification or asking about its release history. I might spend a few days investigating the project, collect whatever releases and historical references I can find, and publish a small document containing everything I have established.
That might include known filenames, release dates, original download URLs, surviving copies and a list of missing files.
For example:
- Abyss of Pandemonium Research
https://gist.github.com/Jason2Brownlee/e0495a8da9ea301a278d9bce79e6db7f - Quake Matrix Research
https://gist.github.com/Jason2Brownlee/c4542f6142813a2489e2506f2343229d - Stalker Quake Research
https://gist.github.com/Jason2Brownlee/b2b7559a661f18dbfa182434bf773e8b
And many more.
Even if I never investigate the project again, the information is available for someone else to use.
I have found this smaller approach surprisingly valuable. You do not always need a large repository or months of research to make a useful contribution.
Working on so many different projects has given me experience with the problems that Quake archivists regularly encounter.
I have spent a great deal of time investigating historical FTP archives, searching the Wayback Machine, examining old CD-ROM collections, comparing releases, reconstructing file histories and contacting people who might still have missing material.
Over time, you begin to recognise patterns.
You learn which sources are most promising, how historical files were typically named and distributed, which search techniques tend to work and when a particular lead is unlikely to go anywhere.
You also develop a feel for the kinds of mistakes that can occur when reconstructing software history from incomplete evidence.
This is the experience I want to share.
My hope is that you can use these methods to save time, avoid unnecessary work and become more productive in your own archival projects.
Why I Wrote This Guide
There are two main reasons I decided to write this guide.
The first is to improve my own archival process.
After years of researching and maintaining archives, I had accumulated a collection of techniques, tools, websites and approaches that I used regularly.
Much of this knowledge was informal. I knew what to do because I had done it many times before, but I had never really sat down and documented the complete process.
Writing everything out forced me to think carefully about how I actually work.
What do I do when starting a new archive? What information do I record? Which sources do I check first? What techniques consistently produce useful results? How do I decide when to stop searching?
Thinking through these questions has helped me clarify and improve my approach.
In fact, while writing this guide, I discovered additional files for some of my existing archives.
Describing particular research techniques reminded me of websites I had not checked, alternative directory structures I had overlooked and different ways of searching for missing releases.
I would stop writing, try the technique on an existing project and occasionally find something new.
That alone made writing the guide worthwhile.
I now have a more systematic process that I can refer to when starting future archival projects. It should help me avoid forgetting useful research techniques and make my archives more consistent.
The second reason is that people have asked me how I create my archives.
I have received questions about where to find old Quake files, how to search historical websites, how to identify different releases and how to put together an archive.
Rather than repeatedly explain individual techniques, I thought it would be useful to document the entire process in one place.
This is my attempt to share what I have learned and give something back to the community.
If it helps another Quake enthusiast recover a missing release, preserve a favourite modification or start their own archive, then it has served its purpose.
I also suspect many of the techniques will be useful to people preserving other retro games and historical software.
The details may differ, but the underlying problems are often the same.
Who This Guide Is For
This guide is primarily for people who want to create an archive of old Quake material.
Perhaps you have a favourite modification that is becoming difficult to find. Perhaps you have a collection of old files and want to organise and publish them. Or perhaps you simply enjoy researching Quake history and would like to preserve something for the community.
I will explain why I think this work is worthwhile and walk through the practical steps I use to create an archive.
The guide is also intended for people who already maintain Quake archives.
You may have your own research process and preferred tools. I am not suggesting you abandon them.
Instead, I hope you find a few useful techniques, resources or ideas that you can incorporate into your own work.
Even one new search method or historical file archive could help you recover something that has been missing for years.
The guide is probably most useful to people with a technical background, particularly those who work in IT or have some programming experience.
It helps to understand files, archive formats, websites, FTP servers, directory structures and basic scripting.
Some of the more advanced techniques involve writing small programs to search archived websites, compare files or process large collections of directory listings.
That said, programming is not required to get started.
You can accomplish a great deal with a web browser, a text editor, patience and a willingness to follow research leads.
I suspect a lot of people who grew up playing Quake ended up working in IT anyway. For many of us, messing around with computers, configuring games, downloading mods and learning how things worked was part of the attraction.
In some ways, Quake archiving feels like a continuation of that experience.
A Note About How This Guide Was Written
I used AI to help write this guide.
I started by making detailed notes about everything I could think of from my years of creating and maintaining Quake archives.
These included the steps I follow, the websites I use, the problems I encounter, the tools I have developed and the techniques I have found most useful.
I then used AI to help organise those notes into chapters and turn them into readable prose.
From there, I heavily edited, corrected and refined the material based on my own experience and what I believe would be most helpful to someone creating an archive.
The research methods, examples, recommendations and opinions presented here are based on how I actually approach Quake archiving.
I wanted to write this guide, but I also wanted to spend most of my time thinking about the substance rather than struggling to turn years of accumulated notes into polished chapters.
AI helped make that possible.
If using AI in the writing process bothers you, I understand.
Perhaps this guide is not for you. Or perhaps you can still dip into a chapter, discover a useful resource or pick up a research technique that gives you a new idea.
I am much more interested in whether the information is useful than in how the prose was produced.
A Final Thought Before We Begin
Quake archiving can be a surprisingly deep hobby.
You might start by looking for a single missing ZIP file and end up investigating a network of historical FTP mirrors, reading 30-year-old Usenet discussions or contacting someone who worked on a modification when they were a teenager.
Sometimes you will find exactly what you are looking for.
Sometimes you will find something completely unexpected.
And sometimes, despite your best efforts, you will find nothing at all.
That is part of the experience.
You do not need to recover every file, resolve every historical question or create the definitive archive of a modification.
Start with something that interests you. Preserve what you can find. Document what you learn. Make it available to others.
You may discover that someone else has the missing pieces, or that the work you publish helps another person continue the search years later.
For me, the most rewarding part is knowing that a small piece of Quake history is a little less likely to disappear.
And, of course, the excitement of discovering something that has been missing for decades.
I hope you enjoy the hunt as much as I do.
Jason Brownlee
Melbourne, Australia
November 2026
https://JasonBrownlee.me