Professional video workflows depend on reliable media transfers. File verification ensures that camera footage is copied completely and without corruption during offload, backup, and archive operations. This article explains how checksum verification and ASC Media Hash List (MHL) files work, why they are essential in modern production environments, and how Limecraft Edge helps production teams securely offload, back up, and verify media with automated verification and industry-standard manifest support.
TABLE OF CONTENTS
- What is File Verification?
- Why File Verification Matters
- How File Verification Works
- Common Hashing Algorithms
- What is an ASC Media Hash List (MHL)?
- File Verification in Limecraft Edge
- Typical Use Cases
- Conclusion
What is File Verification?
In professional video production, file verification is the process of confirming that media files have been copied completely and without alteration during offload, backup, transfer, or archive operations.
When camera cards are copied to backup drives or shared storage, you need certainty that every clip, folder, and metadata file has been transferred correctly. Even a single corrupted or incomplete file can result in lost footage, delayed deliveries, or expensive reshoots.
File verification solves this problem by comparing the copied files against the original source using mathematical fingerprints called checksums or hashes. If the hashes match, the copy is confirmed to be identical to the source.
Limecraft Edge includes built-in file verification during offload and backup operations, allowing productions to create reliable backups, reusable camera cards, and verifiable handovers to post-production and archive systems.
Why File Verification Matters
Modern productions generate large amounts of irreplaceable media every day. Camera cards are often reused immediately after shooting, which means the backup process must be trustworthy before media is erased from the original card.
Without verification, several issues can go unnoticed:
- Incomplete file copies
- Corrupted media files
- Missing clips
- Broken folder structures
- Damaged storage devices
- Human error during copying
- Transfer interruptions caused by unstable connections
A standard file copy operation only confirms that data was written somewhere. It does not guarantee that the copied result is identical to the original source.
Verification ensures that:
- The backup is an exact replica of the source media
- Files remain unchanged during transfer
- Post-production receives complete material
- Archive copies can be trusted later
- Camera cards can safely be formatted and reused
How File Verification Works
File verification relies on checksum algorithms. A checksum algorithm analyses the contents of a file and generates a unique value called a hash. Even the smallest modification to a file changes the resulting hash value completely.
During offload:
- A checksum is calculated for the original source file
- The file is copied to the destination
- A new checksum is calculated for the copied file
- The verification manifest is made available at the destination in Json, PDF or MHL file format
- Files and folders can be compared by comparing the checksums or verification manifests
If the values match, the transfer is verified successfully. If they do not match, the copy is considered corrupted or incomplete.
This process allows productions to detect:
- Empty files
- Changed files
- Missing files
- Incomplete folder copies
- Added or removed files
- Altered folder structures
Common Hashing Algorithms
Limecraft Edge supports several commonly used checksum algorithms:
MD5
MD5 is one of the most widely adopted verification algorithms in media workflows. It is highly compatible with third-party tools and commonly used in broadcast and archive environments.
Advantages:
- Industry standard
- Broad compatibility
- Reliable verification
Considerations:
- Slower than newer algorithms
xxHash64
xxHash64 is a modern high-performance hashing algorithm designed for speed.
Advantages:
- Extremely fast
- Efficient for large productions
- Lower CPU usage during offload
Considerations:
- Less universally adopted than MD5
xxHash3 64-bit
xxHash3 is the newest and fastest option supported in Limecraft Edge.
Advantages:
- Very high performance
- Optimised for modern hardware
- Excellent for high-volume productions
Considerations:
- Compatibility depends on external verification tools
Limecraft allows productions to select the appropriate algorithm depending on workflow requirements and compatibility needs.
What is an ASC Media Hash List (MHL)?
An ASC Media Hash List (MHL) is a standardised manifest file containing checksums for media files and folders.
The MHL file travels together with the media and allows another system, facility, or archive to independently verify the integrity of the copied files later in the workflow.
More info: Media Hash Lists
File Verification in Limecraft Edge
Limecraft Edge includes integrated verification during offload and backup operations. During the backup process, Limecraft Edge can:
- Verify copied bytes automatically
- Generate manifest files
- Create ASC MHL files
- Store human-readable verification reports
- Maintain machine-readable verification logs
- Support multiple simultaneous backup destinations
Verification is enabled by default and should normally remain active during offload operations.
For reliable media management workflows:
- Always enable verification during offload
- Create at least two backups
- Preserve original folder structures
- Keep MHL and manifest files together with the media
- Use standardised checksum algorithms when collaborating externally
- Verify before formatting camera cards
- Store verification reports as part of production documentation
More info about using Limecraft Edge for Offload and Verification.
Typical Use Cases
On-Set Data Wrangling
Immediately after filming, camera cards are copied to multiple backup drives with verification enabled. Once verified successfully, cards can safely be reused.
Post-Production Handover
Travel drives delivered to post-production include MHL manifests so the receiving facility can independently verify the files.
Long-Term Archiving
Archives can periodically re-verify stored media against original checksum manifests to detect corruption over time.
Multi-Site Productions
Distributed teams can confirm that transferred media remains unchanged across different locations and storage systems.
Conclusion
File verification is an essential part of professional media workflows. It ensures that valuable footage remains complete, unchanged, and traceable throughout production, post-production, and archive operations.
Limecraft Edge simplifies this process by combining:
- High-speed offload
- Automated checksum verification
- ASC MHL support
- Multi-destination backup
- Human-readable reports
- Machine-readable manifests
This allows production teams to work faster while maintaining confidence that their media is protected at every stage of the workflow.