Prompt
Why are duplicate brand files still showing up in our library?
Latest observation
Nov 3, 2026
OpenAI APIWeb search: off
Duplicate brand files can still show up in a library for a few common reasons:
-
The same file was uploaded more than once
- Even if the filename looks identical, the system may treat each upload as a separate asset if it has a different file ID, timestamp, or storage path.
-
Files were imported from different sources
- A brand asset might have been added from desktop upload, cloud sync, shared folder, or an integration, creating multiple copies.
-
No duplicate detection is enabled
- Some libraries only deduplicate by exact filename, while others require content-hash matching. If that isn’t configured, duplicates stay visible.
-
Metadata differences make them appear distinct
- Two files can have the same name but different tags, folders, versions, or ownership, so they won’t be automatically merged.
-
Versioning vs duplication
- In some systems, a revised brand file is stored as a new asset rather than replacing the old one, which can look like a duplicate.
-
Sync or migration issues
- If the library was migrated or synced from another system, duplicate records may have been created during import.
If you want, I can help you narrow it down by checking:
- whether the duplicates have the same filename
- whether they have the same file size/hash
- whether they were uploaded by the same user or integration
- whether your library has a deduplication/versioning setting enabled