Guides

How to Name and Package Slowed Reverb Files for SEO and Sales

2026-01-05 · Updated 2026-10-11

Filename patterns, metadata, folder structure and upload titles for slowed + reverb edits, plus what the editor outputs by default (name-remix.mp3, all-remixes.zip).

Six months into running a slowed and reverb channel, the hard part is no longer making edits. It is finding the one you made in March. Files called track-remix.mp3 pile up, clips get posted under titles that nobody searches for, and a client asks for the 0.80x version and you cannot remember which file that was. Naming and packaging solve this, and they also quietly do SEO work, because the title you give an upload is the first thing a search engine reads. This guide covers filenames, metadata, folder structure, upload titles, and what the slowed reverb maker gives you by default so you know what you are renaming.

The advice applies whether you post for fun, run a channel, or sell edits to artists. If you sell, the commission pricing guide covers the business side; this guide covers what the client receives. If you process many files at once, the batch processing walkthrough is the companion piece.

What the editor outputs

Before you rename anything, know the defaults:

• A single track exports as name-remix.mp3, where name is the input filename without its extension. Load midnight-drive.wav, export, and you get midnight-drive-remix.mp3.
• A batch exports as all-remixes.zip, containing one name-remix.mp3 per track, flat, no folders.
• Format is always MP3, 96 kbps, 32 kHz. There is no WAV option, so you never need a format suffix to distinguish exports from the editor; they are all the same format.

The defaults carry no information about settings. Two exports of the same song at different speeds have the same name. That is the first thing a naming scheme fixes.

A filename pattern that carries the settings

The pattern I recommend has five parts separated by underscores, with hyphens inside each part:

artist_title_speed_preset_version.mp3

Examples:

nova-rae_midnight-drive_085x_haze_v1.mp3
nova-rae_midnight-drive_080x_deep_v1.mp3
nova-rae_midnight-drive_090x_wave_v2.mp3

Why each part is there:

Lowercase everything and avoid spaces because filenames travel through URLs, ZIPs, cloud drives and command lines, and spaces or capitals cause friction in at least one of those.

If you need more settings in the name, append them in a fixed order: _r40_s28_b5_t-3 for Reverb 40%, Space 2.8 s, Bass +5, Tone -3. Most people do not need this because the preset code already implies the values, and you can keep a small text file in each folder listing what each preset code means.

Renaming a batch quickly

Renaming twelve files by hand is tedious. Options:

• On Windows, select all files in Explorer, press F2, type a base name, and Explorer numbers them. Good for sequence, bad for settings. Better: PowerToys PowerRename lets you do regex replacement across a selection, so -remix becomes _085x_haze_v1 in one step.
• On macOS, select files in Finder, right-click, Rename, and use Replace Text to swap -remix for your suffix.
• Any system, a one-line shell loop or a small script. If you process a batch every week, a script that takes the ZIP, extracts it and renames by a pattern pays for itself in a month.

The important habit is to rename immediately after download, while you still remember what the settings were. The bulk tool exports one ZIP per download, so if you Download Selected for each preset variation separately, each ZIP corresponds to one preset code and the renaming is mechanical.

Metadata inside the file

MP3 files carry ID3 tags: title, artist, album, year, comment and more. The editor does not write tags beyond what the encoder adds, so fill them in with a tagger (Mp3tag on Windows, Kid3 on any system, or your music player's editor). For an edit of a song you own or are delivering to a client:

Tags survive copying and renaming, so they are the backup when a filename gets mangled. For files you deliver to clients, tags also look professional in a way a bare file does not. Do not tag edits of music you do not own as if they were releases; keep the comment honest about what the file is.

Folder structure

Two structures work. Pick one and never mix them.

By song, best for channels that make many clips per song:

edits/
  nova-rae_midnight-drive/
    exports/
      nova-rae_midnight-drive_085x_haze_v1.mp3
      nova-rae_midnight-drive_080x_deep_v1.mp3
    clips/
      nova-rae_midnight-drive_085x_haze_04-chorus-a_12s.mp4
      nova-rae_midnight-drive_085x_haze_06-chorus-full_20s.mp4
    notes.txt

By batch date, best for weekly processing sessions:

edits/
  2026-10-11_batch/
    nova-rae_midnight-drive_085x_haze_v1.mp3
    nova-rae_midnight-drive_080x_deep_v1.mp3
    kell-sato_glass-room_085x_haze_v1.mp3
    settings.txt

The notes.txt or settings.txt file records what each preset code means in that folder and anything unusual about a track. Thirty seconds of writing saves an hour of listening later.

Clip filenames extend the export pattern with a segment number, a segment name and a length, as in the example above. When analytics tell you clip 04 outperformed clip 05, the filename tells you what clip 04 was.

Upload titles that search engines and people both read

The filename is for you. The upload title is for the audience and for search. They are different jobs and should not be the same string.

A good title for a slowed edit upload has three parts: the song, the version, and optionally a mood or context. In that order, because people search for the song first.

Keep "slowed" and "reverb" as words rather than symbols or abbreviations, because that is what people type. Avoid stuffing: a title that reads "slowed reverb slowed down slow reverb edit tiktok viral" ranks worse and looks worse than a clean one. The title and thumbnail guide covers titling for written content, and the same honesty principle applies to uploads.

If the music is not yours, do not use the word "official" in the title. It is misleading and platforms treat it as such.

Packaging for a client

When you deliver a commission, the client should receive:

1. The file(s), named with the pattern above, using the client's artist name and title.
2. ID3 tags filled in.
3. A short text file or message listing the settings, the format (MP3, 96 kbps, 32 kHz) and the rights granted.
4. If a WAV master was part of the deal, that file from your DAW, named identically but with .wav.

Zip it with a folder name that matches the job: nova-rae_midnight-drive_slowed-versions_2026-10-11.zip. A client who can find and understand what you sent is a client who comes back.

Packaging for sale

If you sell edits of music you own, or preset packs, the same rules apply plus a readme. A preset pack for this editor would be a list of the seven values per preset (speed, reverb, space, bass, tone, width, preserve pitch) in a text file, because presets live in the browser's local storage and there is no export button for them. Buyers enter the values and click Create preset. State that clearly on the product page so nobody expects a file to import.

Open the free editor: upload MP3, WAV, AAC, OGG or FLAC, adjust speed, reverb, bass, tone, width and space, then export MP3 or a ZIP of many tracks. Everything runs in your browser.