Category: Digital Preservation

Bit Preservation

Also known as: Bit-Level Preservation, Bit Level Preservation

Simply put

Bit preservation is the practice of keeping a digital file exactly as it is over time, so that not a single bit of its data changes even as the storage hardware and media around it are replaced. It is concerned only with maintaining the underlying data intact, and does not on its own guarantee that the file can still be opened, read, or displayed in the future. It is often described as the foundational building block on which broader digital preservation practices are built.

Formal definition

Bit preservation refers to the set of storage-oriented practices that ensure the sequence of bits comprising a digital object remains unchanged and retrievable over time, keeping the file in its original format with each bit preserved in its original order while physical storage media are migrated or refreshed. It addresses the integrity and continued existence of the stored data stream but does not, in itself, address future renderability, format obsolescence, or the interpretive and functional preservation needed to keep content usable. Bit preservation is typically treated as one level or building block within a more complete digital preservation program that adds processes for sustaining accessibility and usability; the reliability of bit preservation in practice depends on the behavior of actual storage systems, which may fail to meet stated integrity requirements.

Why it matters

Bit preservation matters because it addresses the most basic requirement of any digital preservation effort: that the underlying data survive intact over time. Digital objects are stored on physical media that degrade, become obsolete, or fail, and storage hardware is periodically replaced or refreshed. Without deliberate practices to ensure that every bit is retained in its original order, the data stream that constitutes a digital record can be silently corrupted or lost, undermining the authenticity and integrity on which a record's evidentiary value depends. For this reason, bit preservation is widely described as the foundational building block on which more complete digital preservation practices are built.

At the same time, bit preservation has an important limitation that professionals should understand clearly: keeping the bits unchanged does not, in itself, guarantee that a file can still be opened, read, or rendered in the future. Format obsolescence, the loss of software able to interpret a file, and other interpretive concerns fall outside the scope of bit preservation and must be addressed by additional processes aimed at sustaining accessibility and usability. Confusing bit preservation with full digital preservation can leave an organization holding data that is intact but no longer usable.

There is also reason for measured caution about how well bit preservation performs in practice. Research into the behavior of actual storage systems has indicated that such systems may fail to meet stated integrity requirements, meaning that the assurance offered by bit preservation depends heavily on the reliability of the underlying storage and on active verification. Organizations should therefore treat bit preservation as a practice requiring ongoing monitoring rather than a one-time guarantee.

Who it's relevant to

Digital preservation specialists

Those responsible for the long-term survival of digital content need to understand bit preservation as the foundational layer of their program. They should recognize that keeping the bits intact is necessary but not sufficient, and should build additional processes for accessibility and usability on top of it.

Records managers and archivists

Professionals managing digital records as evidence rely on the integrity of the underlying data to support authenticity and reliability over time. Bit preservation helps ensure the data stream remains unchanged, but they should be aware it does not on its own address future renderability or format obsolescence.

Storage and infrastructure teams

Because bit preservation depends on migrating and refreshing physical media while keeping the bit stream unchanged, teams operating storage systems play a central role. Given that actual storage systems may fail to meet stated integrity requirements, these teams are important to the ongoing monitoring and verification that bit preservation requires.

Information governance leads

Those overseeing broader accountability for information should understand where bit preservation fits within a more complete digital preservation strategy, so that resources and policies address not only data integrity but also the continued usability of content.

Inside Bit Preservation

Fixity

The property of a digital object remaining unchanged at the bit level over time. Bit preservation depends on the ability to detect any unintended alteration to the stored bitstream, typically through fixity information generated at capture and rechecked over the object's storage life.

Checksums and hash values

Computed values (such as those produced by common hashing algorithms) that serve as fingerprints of a bitstream. Comparing a stored value against a freshly computed one allows corruption, incomplete transfer, or tampering to be identified. The specific algorithm chosen depends on organizational policy and risk tolerance.

Storage redundancy

Maintaining multiple independent copies of a bitstream, often across separate media, systems, or geographic locations, so that the loss or corruption of one copy does not result in loss of the object. The number and distribution of copies typically reflect the assessed risk and the value assigned to the material.

Integrity monitoring

Ongoing, scheduled verification that stored bitstreams still match their recorded fixity information. This is a continuing activity across the storage lifecycle rather than a one-time check performed only at ingest.

Media and storage management

Attention to the physical or cloud storage carrying the bitstream, including monitoring for media degradation and planned migration of bits to new storage before existing media becomes unreliable or obsolete. This concerns the carrier of the bits, not the interpretability of their content.

Scope boundary

Bit preservation addresses only the faithful retention of the bitstream itself. It does not, on its own, ensure that the content remains renderable, understandable, or usable over time; those concerns fall to broader digital preservation activities such as format management and logical preservation.

Common questions

Answers to the questions practitioners most commonly ask about Bit Preservation.

Is bit preservation the same as digital preservation?

No. Bit preservation is a component of digital preservation but not the whole of it. Bit preservation is concerned with maintaining the integrity of the stored bitstream over time, ensuring that the sequence of bits is not altered, lost, or corrupted. Digital preservation is broader: it also addresses the continued usability, renderability, and intelligibility of digital content, which typically requires attention to file formats, software dependencies, metadata, and migration or emulation strategies. Preserving the bits reliably does not, on its own, guarantee that the content will remain readable or meaningful in the future.

If our bits are intact, does that mean the record's authenticity and usability are assured?

Not necessarily. Bit-level integrity confirms that the stored bitstream has not changed, but authenticity, reliability, and usability depend on more than an unaltered stream of bits. A record may remain bit-perfect yet become unusable if the software or formats needed to render it are no longer available, or its evidential value may be weakened if supporting metadata and contextual information are not preserved alongside it. Bit preservation is a necessary foundation for these properties but is not sufficient to establish them by itself.

How is the integrity of a preserved bitstream typically verified over time?

Integrity is commonly verified by generating a fixity value, such as a checksum or hash, at the point of capture and then recomputing and comparing that value on a periodic basis. A mismatch signals that the bitstream has changed, whether through storage media degradation, transfer error, or other causes. The specific methods, frequency of checking, and choice of fixity algorithm generally depend on organizational policy, risk tolerance, and the resources available.

What role does redundancy play in a bit preservation approach?

Maintaining multiple independent copies is a widely used strategy to reduce the risk of loss from media failure, corruption, or localized disaster. Approaches often involve storing copies across different storage media, systems, or geographic locations so that the failure of any single copy does not result in permanent loss. The number of copies, their distribution, and how they are managed typically depend on the value and risk profile of the content and on organizational policy.

How should organizations respond when a fixity check detects corruption?

A detected discrepancy generally indicates that a copy is no longer reliable and should trigger a defined remediation process. Where redundant copies exist and their fixity values remain valid, a common response is to restore the affected copy from a verified good copy. The effectiveness of this depends on having sufficient independent copies, reliable fixity records, and documented procedures. Organizations often address these responses within their preservation policies and monitoring routines rather than treating detection as an end in itself.

How does bit preservation relate to storage media obsolescence and refresh?

Storage media can degrade over time and can also become obsolete as the hardware or systems needed to read them are withdrawn from use. Bit preservation typically involves periodically refreshing or migrating the bitstream onto current storage so that it remains accessible and its integrity can continue to be verified. Because this is distinct from format migration, which addresses the renderability of the content, refreshing storage should be understood as part of maintaining the bits rather than as a guarantee of continued usability.

Common misconceptions

Bit preservation is the same thing as digital preservation.

Bit preservation is typically understood as one component of digital preservation, concerned narrowly with keeping the stored bitstream intact and uncorrupted. Digital preservation is broader and also addresses whether content can still be interpreted, rendered, and used over time, which bit preservation alone does not guarantee.

If the bits are preserved, the record remains authentic and usable.

Preserving the bitstream unchanged supports integrity, but the record's authenticity, reliability, and usability depend on additional factors, including contextual metadata and the continued ability to render the content. An intact bitstream in an unsupported or unreadable format may remain faithfully stored yet effectively inaccessible.

Verifying integrity once at ingest is sufficient.

Bit-level integrity can degrade over time through media failure, transfer errors, or other faults. Effective bit preservation typically relies on repeated integrity monitoring throughout the storage lifecycle rather than a single check performed only when the object is first stored.

Best practices

Generate fixity information (such as checksums or hash values) at the point of capture or ingest and retain it alongside the bitstream so future comparisons are possible.

Schedule regular integrity checks that recompute and compare fixity values across the storage lifecycle, rather than relying on a single check at ingest.

Maintain multiple independent copies of each bitstream, and where the assessed risk warrants it, distribute copies across separate media, systems, or locations.

Monitor storage media condition and plan proactive migration of bits to new storage before existing carriers become unreliable or obsolete.

Document the fixity methods, copy locations, and monitoring routines in policy so that verification and recovery activities are repeatable and auditable.

Recognize the limits of bit preservation and coordinate it with broader digital preservation measures, such as format and metadata management, needed to keep content usable over time.