Audio and artwork
The exception to the save rule
Files are the one place where the staged-save rule does not apply. By the time you would press Save, the file has already left your browser, so an upload commits itself. Deleting one commits immediately too - but it asks first, because unlike an upload it destroys something.
Uploads go straight from your browser to storage. The application only signs the request; the file itself never passes through it, which is what makes a large master practical to upload.
Audio
Uploaded from the Audio card on a Recording.
| Formats | WAV, FLAC, MP3 |
| Maximum size | 1 GB |
| One per recording | A second upload replaces the first |
Once a master is present, the card offers Replace audio and a delete button, and a play button appears - both there and in the Audio column of the recordings list.
Artwork
Uploaded from the Artwork card on a Release.
| Format | JPG |
| Maximum size | 10 MB |
| One per release | A second upload replaces the first |
The thumbnail is what appears in the releases list and on the Dashboard. Clicking it opens the full-size image.
Replacing and deleting are permanent
Storage keeps no version history. Both of these destroy the previous file with nothing to fall back on:
- Replacing overwrites the existing file in place. The old one is gone, and there is no confirmation - the replace is the confirmation.
- Deleting asks first and then removes the file for good.
For audio this matters more than for artwork: the master in storage is sometimes the only copy a supplier has to hand. The wording in the confirmation dialog - "This cannot be undone" - is literal, not boilerplate. Keep your own copy of anything you cannot re-create.