How to Preserve Old Software and Media Yourself

Physical storage media from past decades — floppy disks, cartridges, tapes — degrades over time, and a meaningful amount of software history exists nowhere except on aging physical media somebody still happens to own. This walks through preserving it properly before it’s lost.

Step 1: assess physical media condition before attempting to read it

Check for visible damage, mold, or magnetic media
  degradation signs before inserting into any drive

A visibly damaged disk can potentially damage a drive, or fail entirely on a first read attempt — a careful visual inspection first, and cleaning where appropriate, reduces the risk of losing your only chance to image a specific piece of media.

Step 2: use appropriate period-correct or specialized reading hardware

Kryoflux, Greaseweazle, or similar specialized
  floppy-imaging hardware read at a lower level
  than a standard, modern floppy drive

Standard consumer floppy drives and controllers are often unable to correctly read certain older, non-standard, or copy-protected disk formats — specialized preservation hardware reads the raw magnetic flux directly, capturing formats a standard drive would simply fail on or silently misread.

The distinction between the two capture levels is worth understanding before buying anything. A sector image (.img/.ima, .adf, .d64 and similar) records the decoded data a drive controller returns; a flux image (formats like SCP or A2R) records the raw magnetic transitions themselves, tens of times larger but capable of representing copy protection, weak bits, and deliberately nonstandard track layouts that decoding destroys. The practical rule: you can always derive a sector image from a preserved flux image later, and never the reverse — so for anything rare, image at the flux level. On hardware, Greaseweazle has become the community default because it is open-source hardware available for little money, KryoFlux is the older proprietary equivalent, and Applesauce is the specialized (and widely praised) option for Apple II-family disks.

Step 3: create a raw disk image, not just a file copy

Image the entire disk (including boot sectors,
  file system metadata, and any copy-protection
  scheme's own data) rather than copying
  individual visible files

A raw image preserves the disk exactly as it exists at the bit level, including anything a simple file copy would miss — critical for older software using copy-protection schemes that depend on exact low-level disk characteristics.

Step 4: verify the image with a checksum immediately after imaging

sha256sum disk-image.img

Recording a checksum immediately after imaging creates a verifiable baseline — useful for confirming later that a copy of the image hasn’t been silently corrupted during storage or transfer.

Different media fail differently, and the failure mode dictates the technique. Magnetic tape and some floppy stocks suffer binder hydrolysis — the oxide layer’s adhesive absorbs moisture and sheds during playback — which archivists mitigate with controlled low-temperature baking before a single, carefully monitored read. Optical discs suffer localized rot, where a tool like ddrescue earns its keep: it images the readable regions first, then retries damaged sectors across multiple passes, maximizing what one deteriorating disc can still yield. Cartridge mask ROMs are comparatively durable, but save-game memory backed by decades-old coin cells is not — leaking batteries destroy board traces, so removing or replacing them is itself a preservation act. Matching method to media is most of the craft here.

Step 5: store multiple copies across different physical media and locations

Following the general “3-2-1” backup principle (three copies, on two different media types, with one copy stored offsite) applies just as much to a preserved vintage disk image as to any other irreplaceable digital file — a single copy on a single drive is one hardware failure away from losing the preservation effort entirely.

Step 6: document what you actually preserved

Record: original media type, apparent software title
  and version, condition notes, imaging date and
  tool/settings used

Documentation captured at the time of imaging — while you still have the physical media in hand for reference — is much harder to reconstruct accurately later, once the original media may have been discarded, damaged, or simply forgotten.

Step 7: consider contributing to an established preservation project

Organizations like the Internet Archive and various
  platform-specific preservation communities accept
  contributed disk images, subject to their own
  rights and format review processes

An individually preserved image sitting only on your own drive remains at risk of being lost if something happens to you or your storage — contributing verified images to an established archive with its own redundant storage and ongoing maintenance meaningfully improves long-term survival odds.

Step 8: check whether the specific title has already been preserved before duplicating effort

Search existing preservation databases and archives
  before assuming a specific title needs first-time
  imaging

Checking existing collections first avoids duplicating imaging effort on a title that’s already been properly preserved and verified elsewhere, letting you focus your own effort on genuinely at-risk, not-yet-preserved media instead.

Why individual preservation effort still matters in the archive era

Large institutions and organized preservation projects can’t personally track down every individually-owned piece of physical media still sitting in someone’s closet — a meaningful fraction of software history that will otherwise be lost forever depends on individual owners taking the imaging and archiving steps here before the physical media itself degrades past the point of being readable at all.

Related:

Sources: