Choose how much context the name should carry
A filename should help you recognise the right take after the browser tab is gone. TuneBundle offers three naming styles for prepared files. They change the proposed output names, not the song on Suno, the audio performance or files already saved to your computer. You can inspect the proposed name beneath a ready result before using an individual save button or building the next ZIP.
| Style | Useful for | What to remember |
|---|---|---|
| Title + song ID | Distinguishing takes and keeping a source reference in the name. | The longer name includes the full song identifier. |
| Number + title | Browsing a prepared collection in order. | Numbers follow ready-track order; excluding tracks can leave gaps. |
| Title only | A short readable name in a small folder. | Keep the manifest if source identity matters. |
The default is Title + song ID. Choose it when several versions share a title or when you may need to match a file with a source link later. Numbered names are convenient for a session sequence, but the numbers are not permanent song identifiers. Title only removes that context from the filename; it does not remove it from the CSV or JSON manifest.
A duplicate link is not a duplicate title
Repeated identical URLs are merged before preparation. Different URLs can also identify the same song, such as a share link and a full song link. Once the tool resolves the song ID, it can recognise that duplicate and avoid preparing the same song twice in that run. A skipped duplicate is a processing result, not another audio file in the ZIP.
Two different songs can have the same title. They should remain separate when their song IDs differ, even if the titles look identical. Conversely, changing a display title does not necessarily create a new song identity. When checking an apparent duplicate, compare the source ID and link in the records before deciding that a file is redundant.
This is identity-based deduplication, not a music-similarity detector. The tool does not listen for repeated melodies or prove that two different IDs contain different performances. If you have multiple versions with similar names, preview them and decide which takes to include. Use the selected-duration display as a collection check, not as evidence that the music is unique.
Why the filename can differ from the title
Some characters in a song title are unsuitable for a portable filename. TuneBundle replaces characters such as slashes, colons and question marks with spaces, collapses repeated spacing, and removes problematic trailing dots or spaces. The title portion is limited in length. A title that becomes empty receives a fallback name, and reserved device-style names are adjusted.
For an illustrative example, a title like Night / Take: 2? can become Night Take 2 in the filename. The exact output also depends on your selected naming style and the detected extension. These changes help a file work across common file systems. They do not edit the displayed source title or add information to an audio tag.
The extension comes from the prepared output rather than from arbitrary title text. Original may produce a different extension from MP3 because it preserves a different source container. Do not change an extension to pretend the file uses another format. If an editor needs a different encoding, read the format guide and use an appropriate permitted conversion or official export.
How repeated output names are handled
Within the prepared collection, the naming plan checks for collisions without relying on letter case. With Title only, two ready songs called Evening can become Evening.mp3 and Evening (2).mp3. This example illustrates collision handling; it is not a claim that these songs exist in your batch. The suffix helps keep one prepared file from replacing another in the archive.
The plan considers ready tracks, including ones you may later uncheck. As a result, a selected ZIP can contain a numbered name or suffix with a gap. A gap does not necessarily indicate a missing file: inspect the corresponding manifest rows and selection. The CSV checking guide shows how to compare included rows with extracted files.
Your computer's existing files are outside this plan. If you save an individual file twice, the browser or operating system may add another suffix, ask to replace an existing file or offer a different location. TuneBundle cannot see those local names or guarantee the final browser-chosen name. A clean destination folder makes repeated export checks easier to understand.
Set names before the final export
- Prepare the tracks and inspect the ready results.
- Select the takes you intend to include.
- Choose the naming style and review the visible filenames.
- Build a new ZIP after any change to selection or names.
- Save, extract and compare the audio with the records inside that ZIP.
A previously saved ZIP keeps the names and selection from when it was built. A standalone CSV exported later may describe newer choices. Use the records inside the same archive for an exact check, or deliberately export a new archive and record together. Naming changes are not written into older downloads and do not rename your project folders.
TuneBundle does not provide an ID3 editor, a cover-art editor or a synchronised music library. A well-chosen filename is useful organisation, but it is not a substitute for player metadata or rights documentation. Keep official source exports and any required permission records in your own filing system. Before sharing, read download rights and check what the manifest reveals.
For the full preparation workflow, use Batch ZIP. If a ready result has an unexpected name, compare the title, chosen style, source ID and duplicate status first. If those do not explain it, send a reproducible report with the visible result and browser version, without credentials or private account information.