Say you find an old personal project folder. The files are still there, but the program you used has gone. An export opens, but the interactive part you wanted to see again is missing.
That leaves two different questions. Can you still get to what’s in it? And does the version you can open keep what matters about it?
Keeping the storage device is only one part of the job. The data has to survive, software has to be able to read it, and you have to be able to get to a copy that works. Start by choosing the records worth that ongoing care.
This module is for personal digital records whose loss would matter, and whose ongoing care you can realistically keep up.
What you’ll get from this module
In this module
By the end of this module, you’ll know how to judge whether an important digital record still works. Preservation guidance, a museum’s account of a recovery and two accounts of services closing explain what copies and conversions can keep. You’ll apply these ideas to a situation from your daily life and finish with a plan you can manage, or a clearly named gap.
Ask Jing
Become a Jingius.
What has to survive for a file to remain useful?
Library framework: keeping a way to interpret the file.
The Library of Congress’s 2025 “Sustainability Factors” explains how a format’s features affect whether it can be kept. Its framework looks at how clearly a format is written up, which programs can read it and how simply it stores information. It also looks at descriptions, and at whether it depends on particular hardware or software.
A specification describes how information is stored in a file. When that description is available and different programs can use it, you don’t have to rely only on the original program to read the file.
The framework also values a description of what the record holds and what it needs to work. Without that, someone might have the data and still be unable to understand or use it.
Why it matters: These factors affect how hard and costly it is to keep something. A familiar file ending alone can’t tell you whether your own record will keep working. The useful question is what you would still need to read it if today’s favourite program disappeared.
Read the library’s format-sustainability framework.
Practitioner guidance: copies need different ways to fail.
The Digital Preservation Coalition’s 2015 handbook recommends several separate copies in different places. It also describes checking for damaged data, and fixing a damaged copy from another copy that’s intact.
A device can fail without the record being lost everywhere: another copy may still hold it. Checking the copies and fixing damage helps keep that protection in place.
The handbook also names failures that hit copies together, including software errors and deletions that spread to linked copies. So the number of copies only tells part of the story. Ask whether something that damages one could damage or delete the others too.
Why it matters: This is guidance for organizations’ preservation systems. Its useful idea for a personal collection is to think about which failure your extra copy would actually survive.
Read the preservation handbook’s storage guidance.
Guidance and museum recovery account: readable content and original behaviour can differ.
The Digital Preservation Coalition’s 2015 preservation guidance explains that losing support in the original program doesn’t mean every other way of reading it is gone. It also warns that changing file formats can bring in errors or lose information.
Its advice is to name the content and features that matter, check that a conversion keeps them and keep the original as a fallback. Copying a file to another device is different from converting it to another format.
The Centre for Computing History’s 2010 Domesday diary makes that difference concrete. The 1986 publication needed playback hardware that was hard to find in working order. The museum combined parts from two faulty systems to get one that worked.
Its July 2010 account describes recovering the National and Community Disc data and showing text and images online. That flat export lacked the original interactive features; capturing the video was a separate job, and the diary left it partly unfinished.
Why it matters: The recovery kept useful content without bringing back every part of the original experience. That’s why “it opens” needs a follow-up question: does it still hold what you wanted to keep?
Read the handbook’s preservation-action guidance.
Read the museum’s Domesday preservation diary.
Archive account: a service can close while some records survive elsewhere.
Internet Archive’s account of its GeoCities collection records that the service ended on October 26, 2009. Before it closed, the archive made extra sweeps to save sites.
It didn’t have a full list of GeoCities pages, and couldn’t promise that any particular site had been saved. A separate copy existed, but it didn’t cover everything.
Why it matters: The closure removed the original service as a way in. It didn’t show that every page had vanished everywhere. For someone who cared about a particular site, the important question was whether a working copy of that site survived outside the service.
Read the archive’s GeoCities collection account.
Service-transition account: retained originals change the outcome.
Apple’s 2024 account records that My Photo Stream shut down on July 26, 2023. This was short-term storage for sharing photos, separate from iCloud Photos.
Apple said users wouldn’t lose photos through that change, as long as they kept the device that held their originals. That condition matters: the promise depended on where the original photos were.
Why it matters: This account is a useful contrast with GeoCities. A closure notice tells you that one way of reaching your records is ending. You still need to find out whether you can reach copies elsewhere that hold what you need.
Read the My Photo Stream shutdown account.
Preservation guidance: choose a commitment you can maintain.
The Digital Preservation Coalition’s 2015 guidance on taking in material weighs its value against what it takes to keep it. Organizations have to think about staff, skills, money and ongoing access when deciding what to take on.
The Library of Congress’s undated guidance on personal records starts with choosing important documents. It advises writing descriptions, keeping at least two copies in different places and checking they can be read at least once a year.
These sources tie choosing records to looking after them. Saving a file today is different from taking on the work of keeping it readable. Choosing a smaller collection limits how much you need to look after.
Why it matters: An organization has resources one person may not have. For your own collection, weigh what losing a record would mean, and how hard it would be to replace, against the care you can give.
Read the handbook’s acquisition and appraisal guidance.
Read the library’s personal digital records guidance.
What this means for you
Start with three questions: what do you want to keep, what could stop you using it, and what care can you keep giving? You don’t need to commit for good to every file you’ve stored.
Choose what deserves continuing care
Ask what losing a record would mean to you. Then think about whether you could easily get a replacement that meets your needs, without relying on the same storage or service.
Choose a record for ongoing care when losing it would matter, replacing it would be hard and you can realistically look after it. If something valuable needs more care than you can manage, get help keeping it.
You can leave out material that’s easy to replace or that you wouldn’t miss much. Leaving it out means you aren’t promising to keep it working; it doesn’t mean you have to delete it. If nothing is worth the effort, you can stop without starting a new routine.
Records you look after as part of your job, or have to keep by law, need their own standards or specialist help. So does complex material whose software has to work exactly as it did. Use those routes when they apply.
Define what a usable copy must retain
Name the content and features you need before you judge an export. These could be text, images, sound, structure or interactive parts. “The file opens” isn’t enough if the feature you care about has gone.
Say your old project holds an interactive presentation. If you want to reread its visible pages, an export that keeps those pages may do. If you want the original interactive parts, the same export falls short.
So the same export can meet one purpose and fail another. Compare it with the original for the content and features you chose to keep; opening it is only the first check.
Look for a well-documented file format that different programs can read. The fewer other programs or devices it needs, the less you have to keep working alongside it. Keep a note of what it holds and what it needs, too.
If you need complex software to keep how the record works, get specialist help. An export of visible pages may not keep that behaviour.
Never experiment on your only original. Keep the original when it has features the export lacks, or as a fallback. Check the converted copy before you rely on it.
Check independence against a specific failure
Keep at least two copies that hold what you need. Make sure at least one can be reached outside a single provider’s control. Keep them apart so the physical failure you’re planning for wouldn’t take both. Two is a practical minimum, not a promise that they’ll survive.
Ask whether losing one device, one place or one provider would also cut you off from the other copy. A folder with a different name, or a second account, doesn’t answer that question on its own.
Also think about whether a damaging change or a deletion would reach both copies. If the same problem could hit both, find a copy that would survive it, or note the gap. Two places only help with a local failure if the other copy can still be reached when that place is lost.
Check readability and respond to change
Use a yearly review as a starting point for the records you chose. Find the copies and check that the records open with the content and features you need. Write down the last check that worked, and any change in the software, devices or services needed to use the records.
A spot check tells you about the records you checked. If the collection is too big to look after, choose fewer records or get help. Checking a sample doesn’t show that everything else can be read.
Review sooner when a service announces it’s closing or changing exports, a working way to read the files gets hard to find, a device starts failing or a copy fails a check. These events can change what you need to do before your planned review.
Match the response to the problem. Move files to another supported storage device when storage is failing. Convert to another format when you need to for reading, then check that the content and features you need came through. Keep the original when you need it as a fallback.
If you can’t confirm a copy works, or moving the files is beyond your skills, note the problem and get the right help. A copy you haven’t checked leaves that question open.
How about your daily life?
Which personal records would be hard to replace? Think about an old creative project, a family document or a recording you want to come back to.
Where do you rely on one program or service to open them? Which records need more than their visible text or images to stay useful?
List situations you’d like to understand better. One good idea is enough.
| A personal record or collection | What I want to remain usable |
|---|---|
| ____________________ | ____________________ |
| ____________________ | ____________________ |
My chosen situation: ____________________
Carry one situation into the exercise below. Choosing it doesn’t yet commit you to keeping it.
Plan for readable records
Start with your chosen situation. If you came straight here, choose a personal record whose loss might matter and whose ongoing care you could realistically keep up.
Never experiment on your only original. Use the right standards or specialist help for records you look after as part of your job or have to keep by law. Do the same for complex material whose software has to work exactly as it did.
- Decide whether to commit. Describe what losing the record would mean, whether you could easily get a suitable replacement elsewhere and what care you can keep up. If the loss is bearable or replacing it is easy, you can stop without committing to keep it. Leaving a record out of the set doesn’t mean deleting it.
Commit, decline or seek help—and why: ____________________ - Name what must survive. List the text, images, sound, structure or behaviour you need. Name a file format you can read, and the information needed to understand and use the record. Compare an export with what you need. Keep the original when you need it for missing features or as a fallback.
Content, file format and explanation needed: ____________________ - Locate adequate independent copies. Aim for at least two, including one outside a single provider’s control. Check that they’re separate against losing a device, a place or a provider, and against a damaging change reaching both. If you’re not sure what a copy holds, or which failure it would survive, write down what you still need to check.
Copy locations, what they rely on and gaps: ____________________ - Choose a review and earlier triggers. Start with a yearly review you can keep. Find the chosen copies, open the records and check the content you need. Write down what you checked and the date of the last check that worked. Cut down a set that’s too big, or get help; a spot check doesn’t vouch for the rest.
Review sooner after news of a closure or export change, when ways to read the files get scarce, when a device has trouble or when a check fails. Move files to another storage device when storage is the problem. Convert to another format when you need to for reading, then check that the content and features you need came through. Keep the original when you need it as a fallback.
Review occasion, earlier trigger and next action: ____________________
Ask Jing
Become a Jingius.
Your next step
Finish by deciding whether to take on the ongoing care. If you do, write down what must survive, where the copies are, what’s still uncertain and when you’ll check again. Naming a gap, or a need for help, is a useful result.
A note on the evidence
Preservation guidance explains useful practices; the historical accounts show what happened in particular recoveries and closures. Their lessons depend on what survived and where it could still be reached. They don’t give personal odds of loss, or a lasting promise for any format.
How we prepared this module
This module brings together library and preservation guidance with a museum’s diary and accounts of services closing. A made-up project example explains how an export can meet one purpose while missing another. The exercise helps you apply these ideas to a commitment you can manage.
Sources
- Library of Congress (LOC). (Updated 2025-02-14). Sustainability Factors. Sustainability of Digital Formats. Disclosure; Adoption; Transparency; Self-documentation; External dependencies.
- Digital Preservation Coalition (DPC). (2015 edition; page revision date unstated). Storage. Digital Preservation Handbook, second edition, web edition. Resilient storage systems; Redundancy and diversity; Fixity, monitoring, repair; Storage reliability.
- Digital Preservation Coalition (DPC). (2015 edition; page revision date unstated). Preservation action. Digital Preservation Handbook, second edition, web edition. Technological obsolescence of formats; Format migration; Emulation.
- Centre for Computing History. (Diary June–September 2010; page update date unstated). BBC Domesday Preservation Project (page title: Domesday Disc Preservation Project). Project account and diary. Preservation of the BBC Domesday Data; diary entries for 11th, 19th and 20th July 2010.
- Internet Archive. (2009 collection; current update date unstated). GeoCities Special Collection 2009. Web archive special collection. Saving a Historical Record of GeoCities; Special Collection 2009 Content.
- Apple. (Published 2024-07-23; event 2023-07-26). Information about the My Photo Stream shutdown. Apple Support. Historical service-transition record. Opening; What is My Photo Stream?; If you don’t use iCloud Photos.
- Digital Preservation Coalition (DPC). (2015 edition; page revision date unstated). Acquisition and appraisal. Digital Preservation Handbook, second edition, web edition. Appraisal/retention policy; Skills, resources and capacity; Costs of acquisition and ingest.
- Library of Congress (LOC). (Undated). Keeping Personal Digital Records. Personal Archiving (NDIIPP website). Archiving Tips: Decide which documents have long-term value; Organize the selected documents; Make copies and manage them in different places.
