1 November 2026 — clearer guidance and rights reporting
The homepage now explains the brand's collection workflow, while the existing downloader remains at its original address. Guides are organised by troubleshooting, naming and folders, formats, and copyright. The copyright-report page explains contact requirements, reviewed restrictions and dispute handling. Testing and maintenance methods are now described separately from product marketing.
The table records substantive editorial work in this release. It does not imply that each page has a different author or that the site existed before its actual launch. New test results identify their controlled inputs and limitations; they are not presented as a performance study of the Suno catalogue.
| Page | Change recorded |
|---|---|
| MP3 or Original: choose your Suno download format | Added specific follow-up guides and evidence links while retaining this overview and URL. |
| Fix a Suno download or batch ZIP problem | Added specific follow-up guides and evidence links while retaining this overview and URL. |
| Track file names, duplicate links and same-title songs | Added specific follow-up guides and evidence links while retaining this overview and URL. |
| Only part of your batch is ready: read the CSV before retrying | Added a reproducible 20-row metadata example distinguishing 12 ready files from 10 selected files. |
| MP3 and Original: a reproducible 10-sample processing test | Published 20 measured outputs, complete-decode checks, archive timings, CSV and reproducible signal generation. |
| A song link is rejected: check the address before retrying | Added executed URL examples and the distinction between input duplicates and resolved song identity. |
| A playlist stops loading: keep the list and recover the next page | Documented the 50-to-64 recorded import exercise, retained selection, cancellation and public-only boundary. |
| A ZIP has fewer songs than expected: check selection and the saved file | Added a count-by-count archive diagnostic using the 20-row partial example and checked ZIP records. |
| ZIP filenames look wrong: separate cleanup from a text-encoding problem | Added six executed title examples and a non-destructive comparison workflow for extracted filenames. |
| The track is ready, but the file is missing from Downloads | Added a save-stage diagnostic based on verified browser downloads and exact byte comparisons. |
| After a refresh, links return but prepared files are gone | Explained tested link restoration, temporary audio loss and the distinction between memory, session storage and disk. |
| Audio checks fail: distinguish transfer, duration and silence | Published eight exercised audio cases, including synthetic silence, mismatched duration and incomplete input. |
| MP3 conversion fails or makes a larger file | Connected an injected encoder failure to measured passthrough and conversion results from ten generated signals. |
| Access is refused or requests are paused: what to check next | Documented pause behaviour, reviewed per-song restrictions and safe support details from current handler tests. |
| A large batch or ZIP stalls: reduce memory demand without losing ready tracks | Added explicit binary limits, a labelled PCM memory calculation and observed archive sizes from the controlled benchmark. |
| A music folder structure that separates sources, working copies and delivery | Added an adaptable four-folder workflow tied to verified export records and local copy checks. |
| Keep same-title takes distinct from exports and edits | Added a three-level identity model and an original take-selection worksheet example. |
| Deduplicate music files without deleting a different take | Added measured rename, metadata and restored-copy hash comparisons with a reversible deduplication workflow. |
| Write music tags on a copy, then verify what actually changed | Added a reproducible FFmpeg tagging example with probed tags, byte counts and identical decoded-audio hashes. |
| Keep playlist order when filenames and player tags disagree | Added executed numbering examples and a source-to-delivery order mapping that preserves selected-track gaps. |
| Verify a music backup by restoring a file, not just seeing a sync icon | Added a measured local restoration result and an explicit restore-check procedure without claiming cloud-service acceptance. |
| Personal listening and commercial use need different evidence | Added a practical use-and-evidence worksheet with dated first-party sources and an explicit unresolved timing boundary. |
| A public song link does not describe every permitted use | Added a three-way evidence comparison and a rights-request example without inferring permission from public access. |
| A practical checklist before you prepare and share music files | Added a reusable blank worksheet and a complete preparation-to-delivery check without gating the existing tool. |
- MP3 or Original: choose your Suno download format
- Fix a Suno download or batch ZIP problem
- Track file names, duplicate links and same-title songs
- Only part of your batch is ready: read the CSV before retrying
- MP3 and Original: a reproducible 10-sample processing test
- A song link is rejected: check the address before retrying
- A playlist stops loading: keep the list and recover the next page
- A ZIP has fewer songs than expected: check selection and the saved file
- ZIP filenames look wrong: separate cleanup from a text-encoding problem
- The track is ready, but the file is missing from Downloads
- After a refresh, links return but prepared files are gone
- Audio checks fail: distinguish transfer, duration and silence
- MP3 conversion fails or makes a larger file
- Access is refused or requests are paused: what to check next
- A large batch or ZIP stalls: reduce memory demand without losing ready tracks
- A music folder structure that separates sources, working copies and delivery
- Keep same-title takes distinct from exports and edits
- Deduplicate music files without deleting a different take
- Write music tags on a copy, then verify what actually changed
- Keep playlist order when filenames and player tags disagree
- Verify a music backup by restoring a file, not just seeing a sync icon
- Personal listening and commercial use need different evidence
- A public song link does not describe every permitted use
- A practical checklist before you prepare and share music files
Earlier verified work
1 November 2026 — collections and public playlist import
The tool gained selected-track archives, ready and selected duration totals, CSV export and naming choices. A public playlist can be loaded, reviewed and selected into the existing batch workflow. The importer reads pages of up to 50 entries, displays up to 1,000 entries in a session, and limits each prepared batch to 20 distinct links. These are interface limits, not a guarantee that every full batch or source will succeed.
Supporting changes added the CSV checking and file-name guides, expanded format and error explanations, and documented the request and temporary-file lifecycle. The core downloader URL was retained. Actual behaviour and boundaries are described in the linked guides rather than inferred from this short release record.
31 October 2026 — first public TuneBundle release
The independent public site launched with a single-track and batch workspace, supporting information pages and a working support contact. That release is the start of this public site's history. Earlier local or private experiments are not presented as public TuneBundle releases.
An update date is not a freshness decoration
Substantive changes earn a new entry. Rebuilding unchanged pages, moving a deployment, or correcting internal evidence alone does not justify advancing every article date. Several entries may share a day because the changes were completed together. The publishing identity remains TuneBundle unless a real contributor and their role are added with a verifiable basis.
This page does not claim a search-engine recrawl, an advertising approval or a legal review. For the evidence categories behind a guide, read the editorial method. To propose a correction, include the page and the exact issue through support.