A request, a prepared file and a saved file
These are three different stages. A request asks the service to identify a song and make the relevant resource available to the browser. Preparation produces a checked audio file in the open tab. Saving asks the browser to write that file to your computer. A song title in the results, a ready status and a completed browser download each tell you something different about progress.
TuneBundle provides one workspace for a single track and for a small selected collection. The same basic processing steps apply in both modes. It does not operate a shared music library, sign in to your Suno account or scan your private songs. Before any download, check permission for the work and the route. This technical explanation describes behaviour, not authorisation from the source platform.
- You submit an individual public song or share link.
- The service requests song details and the playback information needed by the current workflow.
- The browser obtains the source audio, directly where possible or through a bounded temporary relay.
- The browser checks the audio and prepares the chosen output.
- You preview, select and save files, optionally with a ZIP and records.
What crosses the network
The submitted public link is sent to our service. That service contacts Suno for the song information needed to resolve it. The source and its delivery providers receive requests under their own policies. Network infrastructure also receives information such as an IP address, request time and headers. This is why it would be inaccurate to describe the entire process as offline or to say that a pasted link never leaves your browser.
Audio is normally requested from the source delivery network. If a direct request is unavailable, audio can pass through our relay, which enforces request and size boundaries. Temporary media tickets restrict relay requests to resolved resources and have a limited lifetime. They are access information, not public permanent download links. Do not share tickets, account cookies or credentials in a support request.
The application does not write the audio into a server-side music catalogue, database or disk library. That does not mean infrastructure providers keep no operational or security records. Cloudflare provides hosting and delivery, and the service uses an IP-based rate limiter. The privacy policy describes these recipients and distinguishes application behaviour from the providers' own retention practices.
What happens in the open tab
After receiving the source, the browser checks that it can decode the audio and compares its measured duration with the song information. It also examines sampled audio to reject apparent silence. The checks can catch several kinds of bad response or damaged file, but they do not guarantee musical quality, check every creative detail or determine who holds rights in the work.
For MP3 output, a supported non-MP3 source is encoded in the browser at 192 kbps. An existing MP3 source is retained without another encode. Original keeps the source encoding after required playback processing, with an extension based on the detected container. It is not an official master-export service. The format guide explains compatibility and the limitations of conversion.
Ready results include a preview and an output file held by the tab. The browser can still need substantial memory for decoding, encoding and packaging. A small compressed source can require more memory while being processed than its saved file size suggests. If a larger collection strains your browser, save the successful results and work with smaller groups.
Selection, filenames and records
Ready tracks are selected by default. The selected duration adds only the checked ready tracks, while ready duration covers all prepared audio. Changing selection does not remove a prepared file from the workspace. It changes which files should enter the next ZIP. When selection or naming changes, rebuild the ZIP so the archive and its manifest describe the current choices.
The CSV and JSON manifest are generated from the same collection information used for file naming and selection. A CSV row can describe a failed, skipped or unselected item, so row count is not the same as audio-file count. The manifest is a record of preparation and intended ZIP membership, not a receipt proving a browser save completed. Compare it with the actual extracted folder using the collection checking guide.
What stays, and for how long
Session storage remembers the input field and selected options so that a refresh can restore them. Prepared audio, preview resources and ZIPs live in tab memory and are discarded when the page refreshes or closes. Browser session restoration can preserve input text, but it does not reconstruct the prepared audio. Clear releases prepared results; remove the input text separately if that is also your intention.
Files already saved to your computer remain there until you manage them with your browser or file manager. TuneBundle does not rename, move, synchronise or delete those local files. Its limits are 20 distinct input links, 10 minutes per track, 64 MiB per source and 256 MiB of prepared audio per batch. These are implementation limits, not a platform subscription allowance or a guarantee about every computer's capacity.
Choose what you share
Optional Analytics is loaded only after you allow it. Declining it leaves the tool usable. You can reopen that choice through Analytics settings in the footer. Advertising behaviour is described separately in Privacy; an analytics choice is not advertising consent. The analytics integration does not send pasted links, song titles, song IDs, audio or exported lists.
Before sending a ZIP to someone else, inspect its CSV and JSON files. They contain source links and titles as well as technical information. Before contacting support, copy the visible error and browser version, and describe the step that failed. Share a public song link only if you are comfortable doing so. Read troubleshooting for targeted checks, or contact the maintainer when those checks do not explain the result.