SpeedSize evaluates original asset uniqueness using technical file data rather than visual similarity. Files are recognized as the same original only when their file content and pixel structure match.
File Size and Pixel Structure Uniqueness
A different file size and pixel structure show that two files are not byte-for-byte identical and are therefore treated as separate originals.
Matching file sizes alone is not sufficient. The underlying pixel structure must also match. Reusing the exact same source file in multiple locations counts as one original.
What Makes an Original File Different?
The system evaluates original uniqueness using the following technical criteria:
- Pixel structure uniqueness
- File size
- Resolution and aspect ratio
- File format, encoding, and metadata
- Processing via intermediary tools that alter file content, such as modifying pixel structure uniqueness
Files may therefore appear visually similar while remaining technically different originals.
Quick Reference
| Scenario | Asset usage | Why |
|---|---|---|
| Exact same source file reused in multiple locations | 1 original | The underlying file and pixel structure are unchanged. |
| Two source files with different file sizes | 2 originals | The files are not byte-for-byte identical. |
| Same file size, different pixel structure | 2 originals | Matching file sizes alone is not sufficient. |
| Original file cropped, resized, or modified before upload | 2 originals | The uploaded originals have different file content or pixel structure. |
| SpeedSize dynamic transformations | 1 original | The transformations remain linked to the same original. |
Important
These criteria apply to source originals. SpeedSize’s dynamically generated transformations do not count as additional originals.