Category: Digital Preservation

Bit-Level Preservation

Also known as: Bit Preservation, Bitstream Preservation

Simply put

Bit-level preservation is the practice of keeping a digital file exactly as it is over time, ensuring that not a single bit of its underlying data is altered even as the storage media and technology around it change. It focuses on protecting the original binary content of a file rather than guaranteeing that the file can still be opened or displayed in the future. In this sense it is typically regarded as a foundational layer of digital preservation on which more complete preservation practices are built.

Formal definition

Bit-level preservation refers to maintaining the exact binary representation of a digital object over time, keeping each bit intact and in its original order while the physical storage media are refreshed or migrated around it. It typically preserves a file in its original format without transformation, safeguarding the integrity and completeness of the bitstream, but does not by itself address future renderability, format obsolescence, or long-term usability, which depend on additional factors and practices. It is commonly characterized as one of two broad levels of digital preservation, distinct from and more limited in scope than functional or logical preservation approaches (such as format migration or emulation) that aim to keep content accessible and interpretable; organizations often treat bit-level preservation as a building block for those more comprehensive strategies. The precise scope, guarantees, and supporting factors vary depending on institutional policy and the nature of the digital collection.

Why it matters

Bit-level preservation matters because it addresses the most fundamental risk in managing digital records: that the underlying binary content may be silently altered, corrupted, or lost as storage media age and technology changes. Without assurance that each bit remains intact and in its original order, none of the properties that make a digital object trustworthy as a record, its authenticity, integrity, and reliability, can be sustained over time. For this reason it is often described as the building block for the more complete set of practices and processes needed to ensure the survival of digital content, and organizations typically treat it as the foundational layer on which broader digital preservation strategies are built.

At the same time, its scope is deliberately limited, and understanding that limitation is important for records and preservation professionals. Bit-level preservation protects the original bitstream, but it does not by itself guarantee that a file can still be opened, rendered, or interpreted in the future. Factors such as format obsolescence and long-term renderability depend on additional practices and are not resolved by keeping the bits unchanged. Institutional guidance in this area, such as that published by the Library of Congress, often makes explicit the extent to which an organization commits to preserving digital collections material and the factors that affect future renderability, precisely so that these boundaries are not misunderstood.

Because the guarantees and supporting factors vary depending on institutional policy and the nature of a given collection, organizations benefit from stating clearly what their bit-level preservation commitments do and do not cover. Presenting bit-level preservation as if it ensured continued usability can create a false sense of security; conversely, neglecting it undermines every higher-order preservation effort. Treating it as a necessary but not sufficient foundation is generally the more defensible position.

Who it's relevant to

Digital preservation staff and archivists

Those responsible for born-digital and digitized collections rely on bit-level preservation as the foundational layer of their preservation programs. They need to understand that keeping each bit intact and in its original order safeguards the integrity of the bitstream, but does not on its own resolve format obsolescence or future renderability, which require additional functional or logical preservation practices.

Records managers and information governance officers

Professionals accountable for records as evidence of activity have an interest in bit-level preservation because it underpins the authenticity, integrity, and completeness of digital records over time. It is relevant to how they frame retention and disposition of digital material, while recognizing that continued usability depends on factors beyond keeping the bits unchanged.

Institutions setting preservation policy

Organizations that publish or maintain digital collections often need to state explicitly the extent to which they preserve material and the factors that affect future renderability. Because the scope and guarantees of bit-level preservation vary depending on policy and the nature of the collection, defining these commitments clearly helps avoid overstating what preserving the bitstream alone can achieve.

Inside Bit-Level Preservation

Fixity

The property of a digital object remaining unchanged at the level of its stored bits over time. Fixity is typically verified using checksums or cryptographic hash values (such as MD5, SHA-1, or SHA-256) generated when the object is captured and recalculated periodically to detect unintended alteration or corruption.

Bitstream integrity

The maintenance of the exact sequence of bits that constitute a digital object, so that the stored data is neither altered, truncated, nor corrupted. Bit-level preservation is concerned with protecting this bitstream, not with ensuring the object remains renderable or interpretable by current software.

Storage management and redundancy

The practices used to hold digital objects safely, often including multiple copies, geographically distributed storage, and controlled storage media. These measures typically aim to guard against media failure, accidental deletion, and localized loss.

Integrity monitoring and repair

Routine processes that check stored objects against their recorded fixity values and, where a redundant good copy exists, restore corrupted bitstreams. This monitoring is what distinguishes active bit-level preservation from mere storage.

Scope boundary against logical preservation

Bit-level preservation addresses only the survival of the bits themselves. It is generally treated as distinct from logical or functional preservation activities, such as format migration and emulation, which address continued usability and interpretability of the object.

Common questions

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

Does bit-level preservation guarantee that a record will remain usable and understandable over time?

No. Bit-level preservation is concerned with maintaining the integrity of a digital object at the level of its constituent bits, ensuring that the stored sequence of bits does not change over time. It does not, by itself, ensure that the object remains renderable, interpretable, or usable. Sustaining usability typically requires additional preservation activities, such as format management, migration, or emulation, which fall outside the scope of bit-level preservation. Depending on organizational policy and the preservation strategy adopted, bit-level preservation is often treated as a necessary foundation rather than a complete solution.

Is bit-level preservation the same as taking a backup?

Not quite, although the two are related and often confused. Backups are typically operational measures aimed at recovering data after loss or corruption, and they may be overwritten, rotated, or retained only for limited periods according to operational policy. Bit-level preservation is generally a more deliberate, long-term practice focused on verifying and maintaining the fixity of digital objects over extended timeframes, often supported by activities such as integrity checking and controlled replication. A backup regime alone may not provide the ongoing verification and durability characteristics that bit-level preservation typically aims to deliver.

How is the integrity of preserved bits typically verified over time?

Integrity is commonly verified through fixity checking, which involves generating and periodically re-checking checksums or cryptographic hash values for each stored object. If a recalculated value no longer matches the recorded value, this may indicate corruption or unauthorized alteration. The frequency of such checks and the specific methods used generally depend on organizational policy, the value and sensitivity of the material, and available resources.

What role does replication or multiple copies play in bit-level preservation?

Maintaining multiple copies is often a core component of a bit-level preservation strategy, since holding copies in separate locations or on independent storage systems can reduce the risk of loss from hardware failure, disaster, or media degradation. Where an integrity check identifies a corrupted copy, an intact copy may be used to restore it. The number of copies, their geographic or technical separation, and the arrangements for managing them typically vary with the organization's risk tolerance and resources.

How does storage media degradation affect bit-level preservation, and how is it commonly managed?

Storage media can degrade or become obsolete over time, which may threaten the integrity and accessibility of the stored bits. Organizations often manage this through periodic refreshment, which involves copying data onto new media or systems before the existing media fail or become unsupported. Combined with fixity checking, refreshment is frequently used to detect and address problems before they result in loss. The appropriate refreshment cycle generally depends on the media in use and the organization's monitoring practices.

Where does bit-level preservation fit within a broader digital preservation program?

Bit-level preservation is typically positioned as a foundational layer within a wider digital preservation program. It addresses the durable and verifiable storage of digital objects, while other functions address matters such as format sustainability, metadata management, and ongoing usability. Depending on the preservation strategy and the significance of the material, an organization may treat bit-level preservation as a baseline for all holdings and apply more intensive preservation actions selectively to objects that require continued renderability or interpretation.

Common misconceptions

Bit-level preservation guarantees that a digital record will remain accessible and usable over the long term.

Preserving the bits typically does not, on its own, ensure that an object can still be opened or correctly interpreted. Usability depends on continued availability of suitable software, formats, and technical environments, which fall under logical or functional preservation rather than bit-level preservation.

Simply keeping multiple backup copies is equivalent to bit-level preservation.

Redundant copies are often part of a bit-level preservation approach, but backups without active fixity checking may silently degrade. Bit-level preservation generally involves ongoing integrity monitoring and the ability to repair from a verified good copy, not just the existence of copies.

Verifying fixity confirms that a digital object is an authentic and reliable record.

Fixity checks demonstrate that bits have not changed since a recorded value was generated, but they do not by themselves establish the broader recordkeeping properties of authenticity, reliability, or provenance. Those depend on additional controls and contextual metadata beyond the scope of bit-level preservation.

Best practices

Generate fixity information (such as checksums or cryptographic hashes) at the point of capture and record it alongside the object so integrity can be verified against a known baseline.

Schedule regular integrity checks that recalculate fixity values and compare them to the recorded baseline, and document the outcomes so corruption can be detected promptly.

Maintain multiple copies, and where feasible distribute them across separate storage locations or media, so a verified good copy is available to repair any corrupted bitstream.

Establish defined procedures for restoring or replacing a corrupted object from a redundant copy, so integrity monitoring leads to actual repair rather than only detection.

Treat bit-level preservation as one layer within a wider digital preservation strategy, and plan separately for logical or functional preservation activities needed to keep objects usable and interpretable.

Set retention and disposition of preserved objects in line with organizational policy and applicable requirements, recognizing that these depend on jurisdiction and sector, so bit-level preservation applies only for as long as the object is meant to be kept.