Prepping Tracks for Rekordbox and Serato: Formats, Bitrates, and Analysis

Every DJ library starts as a junk drawer: 320s from one store, FLACs from Bandcamp, V0 rips from the vinyl era, a few 128 kbps strays of unknown ancestry, and that one folder of AIFFs from a producer friend. Rekordbox and Serato will swallow all of it — and then punish you slowly, with beatgrids that drift, waveforms that render differently track to track, and the special stage fright of a club CDJ refusing a file at 1 a.m. Preparation is not glamorous, but it is the difference between performing and troubleshooting.

This guide covers what DJ software actually does when it analyzes a track, the format and bitrate standards that survive contact with club hardware, and the conversion workflow that turns a mixed-format collection into a play-anywhere library.

What analysis actually does

When Rekordbox or Serato imports a track it decodes the audio and computes a beatgrid (where every beat lands), BPM, musical key, and the waveform overview you mix by. Everything downstream — sync, quantized cues, loops that stay locked — depends on that analysis being right. Analysis quality depends on the audio you feed it:

• Low-bitrate files smear transients. Kick attacks lose definition below about 192 kbps, and beatgrid detection gets measurably less confident on 128 kbps material, especially with swung or live-drummed rhythms.
• Consistency matters as much as quality. A library that is uniformly 320 kbps MP3 behaves predictably; a mixed bag means every problem is a new problem.
• Re-analysis after replacing a file is mandatory. Swap a 128 for a proper 320 and the old grid may no longer line up — re-analyze and re-check your cue points.

The format hierarchy for DJs

What the software accepts

Both major platforms handle MP3, AAC/M4A, AIFF, WAV, and FLAC (Serato added FLAC years ago; Rekordbox likewise). So the limiting factor is rarely the laptop — it's the hardware ecosystem you plug into.

What club hardware accepts

Exported USB sticks are where formats go to die. Older CDJs — the 2000 and 2000nexus generation still installed in plenty of booths — do not play FLAC at all; lossless support arrived with the NXS2/XDJ generation. Every CDJ ever made plays MP3, and all of them read FAT32 sticks. Hence the working standard that has emerged among touring DJs:

• 320 kbps CBR MP3 as the universal performance format — transparent on a club system, small enough for large crates, playable on every player back to the 2000s.
• Lossless (AIFF/WAV/FLAC) at home if you like, as your archive and editing source.
• FAT32 sticks, always, for anything that might touch a CDJ.

Converting the junk drawer

The conversion pass is one honest evening of work:

• FLAC purchases: keep the FLAC as archive, convert a performance copy with the FLAC to MP3 converter at 320 kbps. The FAQ on lossy vs lossless explains what you're trading — at 320 kbps over a club PA, effectively nothing audible.
• AIFF and WAV files: playable as-is, but ten times the size on your stick. Convert stick copies via the AIFF to MP3 or WAV to MP3 converter and keep the lossless originals at home.
• Existing MP3s below 320: here is the critical rule — do not re-encode them upward. Converting a 128 kbps file to 320 with the 320 kbps converter produces a bigger file with identical (or slightly worse) sound; the detail is already gone. Re-encoding upward is only justified for compatibility labeling, never for quality. For any track you actually play out, re-buy it properly — one store purchase costs less than one trainwreck.
• Anything at 128 kbps or below: quarantine it. Low-bitrate cymbals audibly swirl on a big system even when they pass on earbuds.

For background on what the numbers mean, the FAQ on audio bitrate is the five-minute version.

Loudness: analyze, don't flatten

Tracks from different eras and labels vary hugely in loudness, and both Rekordbox and Serato ship auto-gain that compensates at playback using their analysis — which is generally the right tool, because it's non-destructive and per-session. Save destructive normalization for the exceptions: your own edits and bootlegs that came out far quieter than everything else. A pass through the MP3 normalizer brings those in line permanently so they behave on other people's setups too. Whatever you do, do it before analysis, not after — gain changes invalidate waveforms.

Metadata and library hygiene

DJ software lives on tags. Before the collection gets big, standardize:

• Artist and title filled correctly — search in the booth depends on it.
• Filenames with artist and title, not track07final2.mp3, so files stay identifiable outside the software.
• No duplicate copies of the same track in different formats inside the library — the software will analyze both and you will someday load the wrong one. One performance copy per track; archives live outside the DJ library folder.
• Back up the library database (cues, grids, playlists) as religiously as the audio — it represents hundreds of hours of preparation.

The pre-gig export checklist

• Stick formatted FAT32.
• Everything on it MP3 320 CBR (or NXS2-safe lossless if you know the booth).
• Every track analyzed, grid-checked at the drop, cues set.
• Export via the software's export function — not drag-and-drop — so cues and grids travel with the files.
• Test the stick in the software's export/player mode before leaving the house.

The bottom line

DJ prep is standardization. One performance format — 320 CBR MP3 via the FLAC, AIFF, and WAV converters — one loudness approach, clean tags, FAT32 sticks, and a hard rule against upward re-encoding. Do the boring evening of conversion once, and every booth from a house party to a festival main room becomes the same booth: plug in, load, play.