Copyright & permissions · How we test and maintain this guide
Make the important decisions before a batch
A short check can prevent a long, neatly named collection of the wrong takes or unresolved permissions. Use this page when starting a project, changing the intended use or preparing a set for another person. It is an optional planning aid. It does not add a new approval step to the workspace or certify a legal conclusion.
| Before preparation | Record or decision to make |
|---|---|
| Source | Exact song URL, identifier and intended take |
| Permission | The applicable evidence and what use it covers |
| Intended use | Private listening, publication, monetisation or delivery |
| Format | What the actual destination can read |
| Selection | Which songs belong in this export |
| Destination | Where you will save and verify the files |
Open the intended source and check its identity. Similar titles are not interchangeable takes. For a public playlist, review the entries before adding them to the batch. Importing metadata does not fetch the audio, and a listed entry can still be unavailable or unsuitable for your intended use.
Keep the permission question concrete. Record the terms or permission you rely on, relevant dates and any conditions. A publicly visible song or working download does not fill that field for you. For a timing question involving source-platform rights, use the first-party material linked in the personal and commercial use guide and seek clarification if the evidence remains unclear.
Check what the workspace is about to save
- Choose MP3 or Original for the destination, remembering that Original means the available source encoding, not a guaranteed official master.
- Start with one representative permitted file if the player, source or format is unfamiliar.
- Read failed-row messages and preserve successful results. Do not repeatedly retry an access or rate-limit refusal.
- Listen to the prepared takes and set the checkboxes deliberately. Compare ready and selected duration.
- Choose a naming style, build the selected ZIP, then use Save ZIP to complete the separate browser-save step.
A useful count check is the controlled example from our collection functions: twenty result rows, twelve ready, ten selected. The intended archive has ten audio files and two records. The eight failed rows and two unchecked ready rows remain visible in the bookkeeping, but they do not become selected audio entries. Use the same reasoning for your own counts.
If you change naming or selection after building an archive, build it again. Keep the newer ZIP distinguishable from any earlier download on disk. A matching archive filename alone cannot tell you which selection it contains, especially when the browser adds suffixes or saves to another folder.
Verify the local result before leaving
Check the browser's download record, locate the file and open it. For a ZIP, extract into an empty checking folder and compare selected filenames with tracks.csv and manifest.json from that archive. Listen to the actual saved file in the destination application. A working browser preview is useful evidence, but it is not the final file check.
Keep source archives and working edits separate. If you later rename, tag or convert copies, record those changes and preserve a map to the source. A renamed copy may keep the same bytes, while a tag edit can change the complete-file hash. An old manifest is still a source record; it does not automatically describe every later transformation.
Before sharing, review both music and accompanying records. A CSV can contain source URLs and titles that you did not intend to publish. Permission correspondence can contain personal details. Give a recipient the files and information they need, and retain the more detailed project evidence in an appropriately restricted place.
A blank file you control
Download the preparation worksheet. It contains fields for source identity, intended use, evidence, unresolved questions and export checks. Fill it locally, keep it with the project and update it when the purpose or version changes. Downloading or completing it does not send its contents to TuneBundle.
Use honest states such as proceed, hold or seek clarification. A blank evidence field should stay unresolved rather than being filled with a technical success message. The worksheet is useful precisely because it distinguishes the decision about use from the checks that a file was prepared and saved correctly.
If you find an error in these instructions, use ordinary support with the page and specific correction. If the concern is about rights or restricted material, use the separate reporting process. Keep the exact source and issue available so the maintainer can review the right thing.