Troubleshooting · How we test and maintain this guide
Loading a list is different from preparing audio
Import playlist reads titles, identifiers and available durations. It does not fetch each song's audio as soon as the dialog opens. You choose the songs, add their individual links to the batch, and then select Prepare tracks. If titles are visible but no download appears, first check whether you have completed those separate steps.
Use a public playlist address or a supported playlist share link. A profile, private collection or account-only view is not an interchangeable source. Check the playlist in Suno before trying again. The importer does not log in on your behalf, and a song displayed in a playlist can still be unavailable or outside the tool's duration limit.
Three limits describe different things
| Count or limit | Meaning in the workspace |
|---|---|
| 50 entries per request | One page of playlist metadata |
| Up to 1,000 displayed entries | The importer session browsing limit |
| Up to 20 selected songs | The limit for the batch you are assembling |
| 50 of 64 in the recorded case | The first page is loaded; the end has not been reached |
| 64 of 64 after Load more | The recorded playlist is fully listed, not fully downloaded |
In our recorded interface exercise, the first response listed 50 of 64 entries. We selected an entry, deliberately failed the next request, and checked that the original list and selection remained available. A manual retry then loaded the remaining entries. Selecting 20 songs prevented additional unchecked choices while still allowing changes to the selection. This describes the tested interface, not a claim about every public playlist today.
The importer merges selected song links with links already in the batch. If the merged list would exceed the batch limit, it reports the problem rather than silently promising all items will be prepared. Review what is already in the main input. A selection of twenty in the dialog is not automatically safe if your batch already contains different songs.
Recover the part that actually failed
- Keep the dialog open when a later page fails. Note the loaded count and the visible error.
- Check that previously loaded entries and selections are still present. Do not clear useful work merely because the total has not been reached.
- If the response indicates a temporary failure, use Load more again manually. For an access or rate-limit message, pause rather than repeatedly clicking.
- You may add a smaller selection from the already loaded entries. A partially browsed playlist can still supply a useful batch.
- Review the main input after adding links, choose the output format, then prepare the audio.
Closing the importer cancels its active request and ignores a late response from that cancelled operation. In the controlled test, an old response did not overwrite a later dialog state. Closing the dialog does not prove a network operation elsewhere has finished, and it does not save audio to your Downloads folder. Treat the main workspace and the import dialog as different stages.
An unavailable entry should stay unavailable in the list rather than inviting repeated selection. If the source itself changes visibility, is removed, or becomes restricted, loading more pages cannot repair it. For your own work, check its status in the official service. For another person's work, do not treat visibility in a playlist as permission to save or reuse it.
Give support a sequence it can reproduce
A useful report says whether the first page failed, a later page failed, selected links could not be added, or audio preparation failed after import. Include the loaded and total counts, the selected count, browser version and exact message. If comfortable, provide the public playlist URL and identify whether the same source opens publicly. Do not send account cookies or private playlist contents.
When reporting a large list, describe a small reproducible subset before sending a long catalogue. The recorded 64-entry test verifies pagination and selection bookkeeping; it does not establish the reliability of every 1,000-entry session or a full 20-song audio run. Keeping that distinction makes a report much easier to investigate.