Browse articles

Audio file requirements

The exact audio specs Run accepts, the warnings that do not stop a release, and how to export a master that clears the checks first time.

4 min read Updated

On this page
  1. The specs
  2. The warnings
  3. How to export correctly
  4. Uploading
  5. What is checked, and what is not

One lossless master per track: WAV or FLAC. That is the whole answer for most people, and it is the same file the stores want, so there is nothing to convert afterwards.

Every master you upload is decoded and measured when you submit. Anything in the first table below stops the release and sends it back to you. Anything in the second table is a warning: the release keeps moving, and the note goes to the reviewer along with it.

The specs

RequirementWhat Run accepts
FormatWAV or FLAC only
WAV bit depth16, 24 or 32-bit, including 32-bit float
FLAC bit depth16-bit only. Deliver WAV for anything deeper
Sample rate44.1 kHz minimum, 192 kHz maximum
ChannelsStereo, meaning exactly two channels
LengthAt least 1 second
File sizeUp to 2 GB per track
ContainerA real WAV or FLAC file. A FLAC stream wrapped in another container is not accepted

Lossy files are refused outright. MP3, AAC, M4A, OGG and Opus are not masters. AIFF is not accepted either, even though it is lossless: if your session bounces to AIFF, convert it to WAV before uploading.

The wizard’s file picker only offers WAV and FLAC, so a lossy file rarely gets that far. The checks are there for the file that claims to be one thing and is another.

The warnings

None of these stop your release. They are worth fixing anyway, because each one is something a listener or a store will notice.

WarningWhat it means
True peak above -1 dBTPThe master has under 1 dB of headroom. Store transcodes can clip it
Loudness above -9 LUFSStores normalise to around -14 LUFS, so a master this hot is turned down a long way and mostly loses its dynamics for nothing
More than 2 seconds of silence at the start or endUsually an export that was not trimmed. Deliberate silence is fine, and the reviewer can see the difference
Both channels identicalA mono recording sitting in a stereo file. Fine if the recording really is mono
The spectrum stops around 16 kHzThe master probably came from a lossy file

That last one is worth saying plainly: exporting an MP3 as a WAV is detected. A lossy encoder cuts the top off the spectrum, and re-wrapping the file as a WAV does not put it back. The check looks for that missing top end, and it catches the common case (a source at roughly 192 kbps or below). A higher-bitrate source can slip past it, which is why this is a warning rather than a hard failure. It is still not a master: if you have the original lossless file, upload that one instead.

How to export correctly

  1. Export from your session, not from a file you downloaded or bounced for reference. The chain should be session to master to Run, with no lossy step anywhere in it.
  2. Choose WAV. 24-bit is a good default; 16-bit is fine. Use FLAC only at 16-bit.
  3. Keep the session’s own sample rate as long as it is 44.1 kHz or higher. Upsampling a 44.1 kHz mix to 96 kHz adds nothing.
  4. Export stereo, even for a mono recording. The file has to have two channels.
  5. Leave headroom. Set the limiter ceiling around -1 dBTP rather than 0.
  6. Do not chase loudness. Every store normalises, so a master at a sane loudness arrives sounding the way you mixed it.
  7. Trim silence at the head and tail, unless it is part of the track.
  8. Check the length. A file shorter than a second is treated as an error, not a track.

Uploading

Add one file per track in the Tracks section of the wizard at app.run.audio/releases/new. Uploads run in the background while you keep filling in the release, and a large file resumes rather than restarting if the connection drops, which is what makes a 2 GB master practical to send.

A track with no audio file attached cannot be submitted. If a master fails the checks after submission, reopen the release, replace that one file and submit again: see editing and resubmitting.

What is checked, and what is not

The checks read the file itself: format, bit depth, sample rate, channels, length, size, levels and the shape of the spectrum. They do not judge the mix, the arrangement or the performance.

Separately, every track is run through content matching against a catalog of existing recordings, which is about rights rather than audio quality. A match does not fail your release on its own, but it goes to a person, and covers, remixes and samples need their clearance documents on file. See covers, remixes and samples and what review checks.