Ora DJ logo
Product & Tech·6 min read

Everything you need to know about DJing with your USB stick

Cheap flash, the wrong format or a skipped eject can cost you a track or your whole library on the CDJ. How to buy, format and eject a USB stick for DJing.

Your whole set fits on something smaller than a lighter. Years of digging, every cue point, every beatgrid you nudged into place. All of it sits in a jacket pocket and gets pushed into a stranger's CDJ just before midnight. Most nights, that works.

These sticks, and the way they work, are more fragile than you might think.

The short version to not land in a messy situation

  1. Don't buy cheap sticks. Cheap flash memory has spots that simply don't store data reliably. If you're lucky, that means a glitch in one track. If you're not, it's the stick's library index, and the CDJ can't find your playlists at all.
  2. Format for the player, not your computer. FAT32 is the safe default. HFS+ (Mac OS Extended, Journaled) is better if you don't need to plug it into a Windows machine. Never APFS, never NTFS.
  3. Always eject, on your computer and on the CDJ. Pull a stick that's still mounted and the next device to write to it, the CDJ included, can write over music you just synced. Again: maybe one track, maybe the library index, and then the whole stick is useless.

1. Don't buy cheap sticks

A USB stick is a grid of flash memory cells, each holding a tiny charge that stands for a 0 or a 1. A good stick pairs decent chips with a controller that checks its own work and steers around weak cells. A cheap one skimps on both. The result is a stick with patches that just don't hold data properly: you copy a file, the stick reports success, and what it actually stored is slightly different from what you sent.

We tested high quality and cheap sticks. One of our cheap test sticks, a 64 GB drive, failed three times in three days. The clearest case was a regular 15.9 MB MP3 track. Ora DJ copied it to the stick and read it straight back. 1,440 bytes had changed. Every one of them sat inside a single 16 KB patch about 64 KB into the file, and almost all of them were off by exactly one bit: a 0 stored as a 1, or the other way round. We read it again and got the same wrong bytes. The damage wasn't a hiccup in transfer. It was written into the stick.

The next day it got stranger: two files, untouched, gave different answers when read 30 seconds apart.

That pattern, scattered single-bit flips packed into one block, is what failing flash looks like. A loose port or a bad hub can corrupt data too, so if a stick acts up, try it once more in a different port with no hub in between.

What makes this dangerous is how quiet it is. The copy "works". Nothing tells you anything happened unless something reads the file back. Then it depends where the bad patch lands. If you're lucky, it's in the audio: a click, a skip, a track that cuts for a barely audible split second. If you're unlucky, it lands in the library index, the database file the CDJ reads to list your tracks, playlists, cues and BPMs. Then it isn't one track anymore. Playlists go missing, or the player can't make sense of the stick at all.

And a stick that has failed once will fail again.

What to do about it

  • Buy known brands from proper retailers. Marketplaces are full of fake capacity sticks: a "128 GB" stick that really holds 16 GB and silently overwrites older files once it's full.
  • Test a new stick before it goes anywhere near a gig. Fill it completely and read everything back. Free tools do this: F3 on Mac and Linux, H2testw on Windows.
  • Retire a stick the first time it damages a file. Sticks are cheap. Gigs are not.
  • Carry a second stick with the same music on it.

Cheap sticks also tend to write far slower than the number on the packaging or don't give you a write speed at all, and writing is the slowest part of any sync.

What Ora DJ does: every file it copies is read back from the stick and checked against a fingerprint of the original before your new library goes live. If anything doesn't match, the sync stops and your previous library stays as it was. If a track is damaged, Ora DJ names it and offers to copy it again. If that fails too, it tells you the drive looks unreliable and to bring a different one to the next gig. "Mirror to" syncs the same playlists to several sticks in one go, so the backup stick is never out of date.

2. Format for the player, not your computer

Your computer and the CDJ read the stick with completely different software. A stick that opens perfectly on your laptop can show up as blank on a player, and both computers default to formats the players don't understand.

FormatOn Pioneer DJ playersWorth knowing
FAT32The long standing standard, read by every player we've checkedWorks on Mac and Windows. Each file must be under 4 GB, which only matters for long WAV or AIFF recordings.
HFS+ (Mac OS Extended, Journaled)Confirmed in the manuals for CDJ-2000NXS2, CDJ-3000X and XDJ-AZThe Mac's classic format. Fine if you eject properly (see rule 3).
exFATNewer players only: CDJ-3000, CDJ-3000X, OPUS-QUAD, XDJ-AZ and similarNot read by the CDJ-2000NXS2 and older models, which many booths still run.
APFSNot supportedWhat a Mac picks by default for new drives.
NTFSNot supportedWhat Windows picks by default for big drives.

A few traps catch almost everyone:

  • Use the Master Boot Record (MBR) partition scheme, not GUID. Some players won't recognize a GUID stick at all.
  • On a Mac, Disk Utility only shows the scheme option when you select the device itself rather than the volume indented under it. Turn on View > Show All Devices first.
  • Avoid the "Case-sensitive" flavour of Mac OS Extended.
  • On Windows, File Explorer refuses to format anything over 32 GB as FAT32. The format itself handles bigger sticks; you'll need a third party tool to do it.

FAT32 or HFS+? Here's the subtle bit. "Journaled" HFS+ keeps a running log of changes to the stick's own bookkeeping, so that after an unclean removal the Mac can replay the log and repair itself. CDJs write to HFS+ sticks without touching that log. After a clean eject the log is empty, so it doesn't matter. After a missed eject, the Mac may replay stale changes right over whatever the CDJ wrote. That makes journaled HFS+ the format least forgiving of a forgotten eject.

Our take: if you only use a Mac and you always eject, HFS+ is fine, and it's what Ora DJ's formatting guide suggests. If you also use Windows, borrow other people's laptops, or simply want the format that forgives the most, use FAT32. Use exFAT only if you know every player you'll meet can read it.

3. Always eject, on your computer and on the CDJ

Your stick isn't read-only at the gig. When you play a track, the CDJ writes to the stick. It logs your play history inside the library files and creates a few folders of its own. (Files the player writes are often stamped January 1, 2015, because nobody ever set the CDJ's clock.) Ora DJ uses that history and imports your gig back into your library afterwards.

So the stick is a two way street. Your computer writes it, the player writes it, your computer reads it again. Every handover is a chance for something to go wrong, and ejecting is what makes the handover clean.

Your computer doesn't write everything to the stick the instant you hit copy. It holds changes in memory and writes them in batches, so "the copy finished" doesn't mean "the data is on the stick". Ejecting forces everything out, puts the stick's bookkeeping in a tidy final state, and makes sure nothing else is writing while you pull it.

This can happen on any stick, good or cheap. In our tests, a stick formatted as HFS+ left the Mac without a clean eject, then went into a CDJ for one track. Back on the Mac, the library folder couldn't be opened. Here's what a missed eject can do:

  • The stick loses track of what's in use. On ours, 2.6 GB of freshly synced music was marked as free space.
  • The next write lands on your music. The CDJ logging your play history is enough, and it treats that "free" space as fair game.
  • If you're lucky, you lose a track. If not, you lose the library index, and the CDJ can't read the stick at all.

Disk Utility's First Aid repaired ours, and every file came back. Then we repeated the test with a clean eject: same stick, same CDJ, same format. The stick came back healthy. The eject was the only difference.

What to do about it

  • Eject on your computer before you pull the stick. Every time, even when you're in a hurry.
  • Eject on the CDJ too: press the player's USB stop button and wait for it to release the stick. The player has been writing your history all night.
  • If your computer ever complains that a disk wasn't ejected properly, run a disk check on the stick before you play out with it.

What Ora DJ does: Verify and eject unmounts the stick, mounts it again read-only so nothing (not even Finder) can write to it, reads every byte of every exported file once more, and then ejects the whole device. And if a stick does get pulled in the middle of a sync, it is never left half-written: Ora DJ either rolls back to your previous library or finishes installing the new one, and offers to recover the sync next time you plug it in.


Everything else in the booth belongs to the club. The stick is the one thing you bring. Buy a good one, format it for the player, and give it the few seconds it takes to eject.

Related reading