BEATRENDER

How to upload beats: what to settle before you click

10 MIN READ·

Most upload guides tell you where the button is. The button was never the problem. What costs you plays and sales happens earlier: a master delivered at the wrong level, cover art that turns to mush at thumbnail size, an empty metadata field that drops you out of a search filter, an undeclared sample that pulls the track six months later. Here is the preparation work, the part that is the same on every platform — the upload procedures themselves are covered in the dedicated guides.

What uploading actually means

A released beat is not a file, it is a set of files that agree with each other: a master, a tagged preview, cover art, a video, a description, a licence tier. Most upload trouble comes from that set drifting apart — the YouTube video quotes a price the store page contradicts, the marketplace cover is not the one in the video, the WAV delivered to the buyer still carries the voice tag.

The practical consequence is that you do not prepare an upload, you prepare a release. The work below is done once per beat and then serves everywhere, however many platforms you are on. It is also what makes automation possible later: you can only automate what you first made regular by hand.

Preparing the audio file

The delivery format

Deliver a WAV, not an MP3. Every platform re-encodes what you send, in its own codec at its own bitrate: starting from an MP3 adds a generation of loss that the re-encode then amplifies, in exchange for a file size saving that is not even yours to keep. 48 kHz is the sample rate of video formats, so it avoids a resample if your beat ends up as a video — which it does the moment it hits YouTube. 44.1 kHz is perfectly fine if that is your project rate: converting 44.1 to 48 to "keep things clean" buys you nothing.

24-bit rather than 16-bit for the file you sell: the extra headroom is for the buyer who will mix vocals on top, not for you. It is one of the rare places where the format you deliver has an audible effect on someone else’s work.

Loudness, without mastering gear

Every streaming platform normalises playback volume: it turns down what exceeds its target and, in some cases, turns up what falls below. A master crushed into a limiter to "sound loud" will therefore not come out louder — it will come out at the same volume as everyone else, minus its dynamics. That is the only argument that matters against the loudness war, and it is a mechanical one, not a matter of taste.

The concrete method with no equipment: install a free loudness meter (Youlean Loudness Meter, or the one built into your DAW) and read two numbers. Integrated loudness tells you where you sit; true peak tells you whether you will clip after re-encoding. Each platform publishes its own normalisation target in its help centre, and those targets differ from one platform to the next: go and read the one that concerns you rather than aiming at a figure you heard somewhere.

The useful reflex is not to hit a number, it is to compare. Drop three references from the same genre into your project, listen at matched volume, and judge yours next to them. A master that survives the comparison will survive normalisation.

The preview and the voice tag

The public file and the sold file are not the same file. The preview carries your voice tag, spread through the track rather than sitting on the intro — a tag only at the top gets cut in ten seconds. The sold file carries none. Accidentally delivering the tagged version is the most common and most embarrassing incident in beat selling, and it is solved by naming the two files differently at export time.

Cover art: one image, several crops

A square cover serves marketplaces and streaming platforms; a 16:9 thumbnail serves YouTube; a vertical frame serves TikTok and Shorts. These are not three different visuals, they are one visual designed to survive three crops. The method is to compose square while keeping the subject and the text centred, with breathing room at the edges: whatever spills out will be lost in a crop, and whatever touches the edge will be cut.

Always export larger than you need. Scaling a large image down is visually free; scaling a small one up never is. Minimum dimensions and maximum file size vary by platform and change regularly: check them in the help centre of the platform you are targeting at the time you publish, rather than trusting a number you memorised.

The test that matters is done in real conditions: shrink your cover to phone-thumbnail size and look at it. If the reference artist’s name is no longer readable, the cover is not the problem — the text hierarchy is. It is the same test as for a YouTube thumbnail, and the video guide goes into it in detail.

Metadata, field by field

The title

The title is the field most read by search engines and by buyers, in that order. It carries the reference artist, the beat name and the content type — which is what people actually type. BPM and key belong there when they fit, because they are search criteria in their own right for a rapper looking to write at a specific tempo.

Settle on a template and stop changing it. A catalog where half the tracks follow one convention and half another goes invisible for the very queries the first half captures. Switching templates midway always costs more than keeping an imperfect one.

BPM and key

On a marketplace, these two fields feed filters. An empty field does not make you neutral: it removes you outright from the results of anyone filtering on it. And a wrong value is worse than a missing one, because it puts you in front of people who were looking for something else and who leave.

If you are revisiting an old project and no longer have the exact tempo, do not guess by ear: an automatic detector will give you tempo and key in seconds, including from an exported file whose session you have lost.

Tags, genre and mood

Three to five genuinely close artist names beat twenty vague ones. The reasoning is not moral, it is statistical: an off-topic tag exposes you to an audience that does not convert, and that lack of engagement is then charged back to you in recommendations. Genre and mood, meanwhile, decide whether you appear in themed lists and marketplace playlists — often the fields rushed fastest and among the most profitable.

ISRC and credits

An ISRC is a unique identifier assigned to a recording; it exists for royalty tracking, not for search ranking. If you go through a distributor, they issue you one. If you publish directly, it comes from your country’s national agency. Not every platform offers a field to enter it, and its absence does not stop you selling a beat: it is a monetisation topic for the day you distribute, not a prerequisite for uploading.

Credits, on the other hand, get filled in from the very first track: co-producers, sample rights holders, features. A rights split that was never written down at release time becomes very hard to untangle once the track starts working.

Rights: what actually gets a track pulled

A takedown almost never comes from the file itself, but from what is inside it and what you claimed about it. Three causes come back:

  • An uncleared sample, even chopped, even short. Slicing and pitching do not remove the rights, and automated detection finds excerpts the ear no longer recognises.
  • A kit or loop used outside its licence: many packs allow use in a production but forbid reselling the loop as-is, or require credit.
  • A visual that is not yours — a music video clip, an artist photo. The track can stay online while the video itself is blocked or demonetised.

The defence is administrative and boring: keep a written trace of the licence for every sample and every pack, in the project folder rather than in an inbox. The day a claim lands, what decides the outcome is your ability to produce that document within minutes.

A misleading title is the same class of risk: presenting a beat as official, or as a remix it is not, invites a takedown for a reason that has nothing to do with the music. The reference artist’s name is a tag, not an attribution.

Where to upload, and in what order

Platforms do not play the same role. YouTube is the search engine: that is where the buyer discovers the beat. The marketplace is the cash register: that is where they pay. Short-form is the shop window: it sends people to the other two. Publishing everywhere without those pages pointing at each other is opening three shops with no signs on them.

The order that works is therefore: the store page first, so you have a permanent link; the video next, with that link in the description; short-form last, since it points at the video. Doing it the other way round forces you back into already-published posts to fix links — exactly the kind of debt nobody ever pays off.

The detailed procedure for each platform is covered separately: the guide on bulk uploading to YouTube covers multi-upload, scheduling and description templates, and the BeatStars guide covers licences, pricing and syncing with the video.

Should you automate?

The question is not settled by volume but by the nature of what you repeat. As long as each release calls for decisions — which visual, which angle, which words — automation has nothing to automate. The moment you apply the same template for the tenth time and your only variable is the filename, you are no longer producing: you are doing data entry, and data entry is precisely what a machine does better than a tired human on a Sunday night.

The honest test is this one: time one complete release, from export to the last link pasted. Multiply by your monthly pace. If the total fits inside the time you are willing not to spend producing, stay manual — it is free and it keeps you in control. If not, the first thing to take out of your hands is not the upload itself, it is building the video and the thumbnail, which weighs the most and lends itself best to a template.

That is what BeatRender does: a video, a thumbnail, a title and tags generated from the audio file, then a scheduled release to YouTube, Shorts, TikTok and BeatStars. None of which obliges you to use a tool — a folder of templates, a naming convention you actually hold to, and one grouped preparation session a month produce the same effect on consistency, which is the only thing that really counts.

The checklist before you click

  • The master is a WAV, and the sold file does not carry the voice tag.
  • Loudness has been measured, not estimated by ear on uncalibrated speakers.
  • The cover is still readable at phone-thumbnail size.
  • The title follows the same template as the rest of the catalog, with no "just this once" exception.
  • BPM and key are filled in, and correct.
  • The licence for every sample used is archived in the project folder.
  • The store page exists, and its link is in the video description.
  • The release date is scheduled, and not the same as the four other tracks in the batch.

READ NEXT