Duplicate Detection

When managing large batches of audio, it's easy to accidentally include the same file in multiple uploads over time.

Uploading the same file twice wastes your daily Roblox API quota and clutters your Creator account with duplicate assets. To prevent this, the Roblox Audio Bulk Uploader features a robust duplicate detection system.

1. How It Works

Before the application attempts to upload any file to Roblox, it generates a unique cryptographic "hash" (a digital fingerprint) of the file.

The app then checks this hash against a local record of all your previous successful uploads. If the hash is found in the record, the application instantly knows this exact file has already been uploaded, and it skips the file automatically.

What Defines the "Same File"?

The hash is calculated based entirely on the content of the file, not the file's name.

Renaming a file: If you rename a file from Song.ogg to Song_Final.ogg without changing the actual audio data, the hash remains identical. The app will correctly identify it as a duplicate and skip it.
Modifying a file: If you alter the audio file even slightly (e.g., changing the volume, trimming a second of silence, or running it through the Mix Audio pipeline again), the file content changes, resulting in a new hash. The app will treat this as a brand-new file and allow the upload.

2. What Happens When a Duplicate is Found?

When the system detects a duplicate hash during a batch run:

The file is marked as Skipped in the main queue table.
A message is printed to the bottom-right log panel noting that the file was skipped due to duplication.
Crucially, the upload is not attempted. No network request is made to Roblox, meaning absolutely zero API quota is spent on the duplicate.

3. The `upload_history.json` File

The application keeps track of these hashes in a local file named upload_history.json, located in your src/ working directory.

This JSON file acts as a simple database, storing the file hash alongside the resulting Roblox Asset ID and the time of upload.

(Note: It is completely safe to add this file to your .gitignore to prevent tracking it in version control.)

History is Local-Only: The upload_history.json file is stored purely on your local machine; it is not synced to Roblox or any cloud database. If you switch to a different computer, that new machine will not have the history file and therefore will not recognize files uploaded from the first machine as duplicates.

4. Resetting Your History

There may be legitimate reasons to re-upload a duplicate file (for example, if you accidentally deleted the original asset from your Roblox Creator Dashboard).

If you need to bypass duplicate detection:

To reset a single file: Open upload_history.json in a text editor and delete the specific block containing that file's hash.
To reset all history: Simply delete the entire upload_history.json file from your directory. The app will generate a fresh, empty one on your next successful upload.