File streaming

Checksums and editorial validation for shared media

Know what a matching checksum proves—and what still needs an application-level check before the next handoff.

Verify both the bytes and the intended result

A checksum can help confirm that two copies contain the same bytes when the same suitable algorithm is used correctly. It cannot establish that the file is the right take, has the intended audio channels or belongs to the approved revision. A useful shared-media handoff combines integrity evidence with an application-level check.

Suite makes the shared result accessible through ordinary file paths. That gives editors and authorized verification tools a common place to work, without turning every validation task into a manually assembled transfer package.

Choose the check for the question

If the question is whether a transfer preserved an asset, use the organization's approved integrity procedure and record the source, destination and algorithm. If the question is whether a deliverable is editorially correct, open it and inspect the relevant content. Both checks may be appropriate; neither substitutes for the other.

Amazon S3's integrity documentation describes checksum support for object transfers. Do not assume an arbitrary object identifier or every ETag is a full-file checksum. Use the documented integrity value and scope for the operation being checked.

Make validation proportional to the assignment

For a camera original, the production's ingest procedure may require full verification. For a temporary review thumbnail, verifying that it depicts the intended source and opens correctly may be the relevant acceptance check. A full-file hash reads the file; include that read in planning rather than assuming verification requires no data movement.

Consider a handoff of a stereo review export. Matching its approved reference checksum can show byte identity. Listening to the intended language track and checking the slate can show that the reference itself was the correct delivery. If the wrong export was selected before hashing, a perfect hash match only preserves that mistake.

Give the next person usable evidence

Record the asset ID, revision, validation method, result and reviewer. Keep “not checked” distinct from “failed.” An agent should state whether it checked a complete file, a sample or metadata only, so a person can decide whether additional verification is needed.

The shared filesystem makes this evidence easier to connect to the exact asset the team uses. Explore our file-access model, and make one complete, verified handoff part of the first project rather than treating availability alone as the finish line.

Put the idea to work

Start with your workflow.

Bring shared files into your familiar applications with Suite Managed, or connect your own supported storage with S3 Native. S3 Native requires at least 20 TB of active storage.