At OpenAsset, we use a robust system to ensure you aren't storing the exact same file multiple times. It's important to understand exactly how we define and detect a "true" duplicate to avoid confusion during uploads.
The Power of the MD5 Hash
OpenAsset identifies duplicates based on a file's MD5 Hash, which acts as a unique, digital fingerprint for every file.
Same File, Same Hash: If two files have the exact same MD5 Hash, they are considered true duplicates, even if they have different filenames or are stored in different projects.
Example: Renaming a file from photo_A.jpg to image_new.jpg does not change its MD5 Hash. OpenAsset will block the upload of the renamed file because it's a true duplicate of the original already in the system.
Any Change, New Hash: The MD5 Hash is extremely sensitive. If a file’s content is edited or changed in any way, its MD5 Hash will be completely different.
Examples of changes that alter the hash:
Resizing (even by a single pixel).
Recoloring (e.g., converting from CMYK to RGB or vice versa).
Editing the pixels in any way.
True Duplicates vs. Visually Identical Files
OpenAsset is designed to filter out true duplicates—files that are bit-for-bit identical, confirmed by the MD5 Hash.
Upload Blocked: If you attempt to upload a file whose MD5 Hash exactly matches a file already in the system, OpenAsset will block the upload and notify you that it is a duplicate.
Upload Allowed: If you edit an image, even a minor edit that makes it look visually identical to the original (e.g., a tiny crop, a slight color adjustment), the MD5 Hash will change. Because the hash is different, OpenAsset will not flag it as a true duplicate and will allow the upload to proceed.
This is the key distinction: OpenAsset only prevents the upload of the exact same file. It cannot detect files that look the same but are digitally distinct due to modification.
Best Practice Before Uploading
To keep your library clean and avoid uploading multiple, near-identical files:
Review Your Source Files: Please confirm that the files you intend to upload have been reviewed and are the desired versions before sending them to OpenAsset.
Avoid Redundant Modifications: If you need to use a file you suspect is already in OpenAsset, check the library first. If you must upload a slightly modified version, be aware it will be stored as a new, unique asset.