What is the _Serato_ folder? Serato's database, explained

The _Serato_ folder is the part of your DJ library you do not see in the decks. It is where Serato stores the library database, crates, history, smart crates, and DJ metadata.

Your music files are separate. The _Serato_ folder is not a folder full of MP3s. It is the library data Serato uses to know what you have, where it lives, and how it is organized.

That distinction matters when you back up, move to a new Mac, clean duplicates, or troubleshoot orange files.

Where the _Serato_ folder lives

On the Mac’s boot drive, the main Serato folder usually lives here:

~/Music/_Serato_

That is the library data for the music Serato manages from your Mac.

There can also be more than one _Serato_ folder. If you keep music on an external drive, Serato can create one at the root of that drive:

/Volumes/Your Drive/_Serato_

That drive-level folder stores library data related to tracks on that drive. This is why backup advice says to copy every relevant _Serato_ folder, not only the one in Music. For the full workflow, see How to back up your Serato library.

What’s inside the _Serato_ folder

The important file is the main library database file, named:

database V2

It has no file extension. For normal DJ work, you do not need to open it. Think of it as Serato’s main index for library entries, file paths, and DJ metadata.

You may also see a Subcrates folder. That is where Serato stores crate files. Each .crate file represents a crate. A crate file is organization, not audio.

Cue points, loops, beatgrids, and other per-track DJ metadata are stored as part of Serato’s library data. The exact storage details are not something you should edit by hand.

The folder can also include history and session data, smart crate definitions, and analysis-related data. The safe level of detail is purpose, not byte layout.

Rules of thumb

Do not edit files inside _Serato_ by hand.

Even when a file looks understandable, Serato expects its own structure. Hand edits can break crates, paths, history, or metadata.

Quit Serato before copying the folder.

Serato writes to its database while it is open. If you are making a backup, migrating, or copying the folder, close Serato first.

Deleting _Serato_ resets the library for that location, but it does not delete the audio.

Your MP3, WAV, AIFF, and FLAC files live in your music folders or on external drives. Removing the library database can make Serato forget the organization, but it does not erase the audio.

Deleting a .crate file removes crate organization, not tracks.

That can still be a serious loss if the crate took years to build. Treat crate files as library data.

Why Serato’s design causes classic library problems

Serato tracks files by path.

If a track was added from:

/Users/you/Downloads/Track.mp3

and later added again from:

/Users/you/Music/DJ Music/Track.mp3

Serato sees two library entries because those are two different paths. The audio may be identical, but the database records are not the same.

That is the root of many duplicate problems. Re-importing old folders, dragging files from Downloads, copying between laptop and drive, or rebuilding a crate from another folder can all create extra entries.

The deeper duplicate workflow is covered in Why duplicate tracks keep reappearing in Serato. For a full cleanup order, see Serato library cleanup: the complete guide for DJs.

The same path design explains orange missing files.

If the database points at a file path and the file is moved, renamed, deleted, offloaded, or left on a disconnected drive, Serato still has the entry but cannot load the audio.

The repair workflow belongs in Serato’s relocation tools, not manual database editing. Start here: How to fix missing orange files in Serato DJ.

Where CrateSweep fits

CrateSweep reads the Serato database directly to find duplicates.

That matters because filename sorting only catches obvious cases. If the same track is saved under two slightly different names, a manual name sort can miss it.

CrateSweep does not ask you to edit _Serato_ by hand. It scans the library, groups duplicates for review, and backs up the Serato database before any deletion run. Selected audio files are moved to the Trash.

Scanning and review are free. Deletion is a one-time $19 unlock.

For duplicate cleanup, see how CrateSweep finds duplicate tracks. For the backup side of the deletion workflow, see Serato library backup and one-click restore.

The practical takeaway is simple: treat _Serato_ as the working memory of your Serato library. Back it up, do not hand-edit it, and understand that it points to audio files rather than containing them.