SANJIESAN LICENSING / Asset verification
Two artwork files have the same name. Are their bytes the same?
A supplier reports opening the current artwork, but the screenshot appears to show an earlier crop. Start by checking which file each side has. A filename and a thumbnail may be insufficient when a file was replaced without being renamed. A digest can help narrow the investigation to the transferred bytes.
Agree the file and digest method
Select one exact deliverable from the manifest and keep the original unchanged. Record the digest algorithm as well as its result. MDN describes a cryptographic digest as a fixed-length value derived from input data. Use an approved local tool or a reviewed project utility for the check, rather than uploading confidential artwork to an unfamiliar public hashing service. Keep large-file handling within the team’s supported workflow.
Compare the received file, not an old download
Ask the recipient to compute the same digest for the actual file they intend to use. If the values differ, compare the archive version, extracted filename and download source before debating the artwork itself. Do not overwrite either file to make the report look tidy. A difference is useful evidence about the handoff; it does not identify which visual version should be approved.
Keep the digest beside the wider review record
When the transfer question is resolved, link the checked file to the reference render and release note. Keep the visual decision, supplier process approval and usage documents as their own records. A matching digest is a byte-comparison aid, not a substitute for those decisions. If the artwork changes later, issue a new revision and compute a fresh digest instead of carrying the old value into a different deliverable.