Troubleshooting · How we test and maintain this guide
A batch result is a list of outcomes
If you submit 20 links and only 12 become ready, the first job is to preserve those 12 results. A failure elsewhere in the list does not invalidate a prepared file. Avoid refreshing the tab or clearing the input while you work out what happened: prepared audio lives in that tab, and a restored list of links cannot restore the discarded audio.
Read three different numbers. The input count describes the distinct links retained for preparation. Ready tracks have an audio result that the browser accepted. Selected tracks are the ready results currently checked for the next ZIP. A ready track can be deliberately unselected, so a ZIP containing fewer audio files than the ready count can be correct. Neither the ready count nor the selected count proves that your browser has saved a file to disk.
An example you can inspect
We ran the site's manifest and CSV functions with 20 explicitly simulated metadata rows. Twelve were marked ready and eight failed; two of the ready rows were unchecked. This is a controlled bookkeeping example, not a successful transfer of 20 Suno songs. Download the example CSV and matching JSON manifest to follow the columns yourself.
| Measure | Result from the example |
|---|---|
| Input rows | 20 |
| Ready rows | 12 |
| Selected for ZIP | 10 |
| Failed rows | 8 |
| Ready duration | 13:18 |
| Selected duration | 11:08 |
In the CSV, filter status to ready to see prepared rows. Then check included_in_zip: only yes rows are intended for the selected archive. The two unchecked ready rows still have filenames and prepared-file information, but their inclusion field says no. The eight failed rows do not acquire valid audio simply because they have a title or source link.
The JSON uses slightly different names. Its top-level readyTotal counts all prepared results, while ready counts selected prepared results. Within each track, included is the selection flag. Compare meaning rather than assuming that the same English label always maps to the same field across CSV, JSON and the screen.
Save the good files before recovering the rest
- Preview the ready tracks you intend to keep. Confirm the title and take; a technically valid file can still be the wrong artistic version.
- Choose a naming style and review the checkboxes. Export CSV if you want a record of the full result list before making further changes.
- Build the ZIP of selected ready files, then use Save ZIP. Alternatively, save important ready tracks individually.
- Read the note beside each failed result. A malformed link, access refusal and audio-decode failure require different actions.
- Use Retry failed tracks for failed or cancelled items when the cause has been addressed. It is not a reason to repeat an access-denied or rate-limited request continuously.
Changing selection or naming invalidates the previously prepared ZIP. Rebuild it before saving the revised collection. If you downloaded an archive before the change, keep it separate until you have checked which version contains the intended selection. Reusing the same folder name can make an older archive look like the latest export.
Compare records with the files actually saved
Extract into a new folder. Count audio files separately from tracks.csv and manifest.json. In this example, the intended result is ten audio entries plus the two records, not twelve audio files and not twenty. Compare each selected CSV filename with an extracted filename. File size and SHA-256 help distinguish a byte-identical file from a renamed or re-encoded version.
If the CSV claims a selected file that is absent, check that you extracted the matching archive and that your download completed. Do not solve an unexplained mismatch by editing the CSV to agree with the folder. Preserve the original records, note what is missing, and prepare a smaller reproducible run if you need to contact support.