For anything you may need in five or twenty years, keep the working original and create a preservation copy in a widely adopted, well-documented format. A file extension alone does not preserve a file. Long-term access depends on the format, the software available to interpret it, the integrity of the stored bits and the existence of more than one copy.
What makes a format durable
The Library of Congress evaluates sustainability factors such as public documentation, adoption, transparency, external dependencies, patents and technical protection mechanisms. A durable format is not necessarily the newest or smallest. It is one that can be understood and implemented without depending entirely on a single vanished vendor, account or secret specification.
Prefer formats with broad software support and published specifications. Avoid making a cloud application's internal project format the only copy of essential work. Export before closing an account or retiring a program. For a complex project, save both a rendered version for viewing and the source package needed for future editing.
Useful preservation choices
- Documents: PDF/A or ordinary well-formed PDF for a stable reading copy, plus DOCX, ODT or plain text when future editing matters.
- Tables and datasets: CSV for simple rectangular data, accompanied by a data dictionary; keep XLSX or ODS when formulas and formatting matter.
- Images: TIFF or high-quality PNG for lossless masters; high-quality JPEG for photographic access copies when size matters.
- Audio: WAV or FLAC for lossless masters; MP3 or AAC for convenient listening copies.
- Video: retain the highest-quality original and an interoperable playback copy, documenting codec and container.
No list fits every purpose. PDF can flatten formulas or interactive elements. CSV does not preserve multiple sheets, formulas, formatting or data types reliably. A screenshot preserves appearance but not searchable text, structure or underlying data. Use complementary copies rather than forcing one format to do every job.
Package the context
A future reader needs more than bytes. Use clear filenames, dates and version labels. Include a short README explaining what the files are, which software created them, what each column means, and any fonts or linked assets required. Export email with attachments and headers when the conversation itself matters. For websites or interactive work, save content, assets and a rendered reference because behavior may be difficult to reproduce later.
Protect integrity
Keep at least three copies, on two types of storage, with one copy separated from the main device or account. This familiar backup pattern protects against device failure, theft, ransomware and synchronized deletion. Generate checksums for archival collections so later checks can reveal silent corruption. Encryption protects sensitive material, but preserve the keys and instructions separately; perfectly encrypted data with a lost key is perfectly inaccessible.
Review instead of forgetting
Storage media and formats age. Once or twice a year, open a sample of important files, verify backup status and check for errors. When a format or application loses support, migrate while the current software can still read it. Keep the original alongside the migrated copy and record what changed. Preservation is a process, not a one-time export.
A practical save routine
- Keep the editable source.
- Export a stable viewing copy.
- Use descriptive filenames and a README.
- Copy the package to independent storage.
- Verify checksums or at least open-test representative files.
- Schedule periodic review and migration.
The best format is the one future software can interpret and future you can understand. Broad support, clear documentation, useful context and verified copies matter more than a fashionable extension.
