Why does Serato read tags every time it opens?
Some tag reading when Serato starts is normal, and on a large library on a USB drive it can take a while. It becomes a problem when Serato reads, or re-analyzes, the whole library on every launch. That usually means one of four things: another app keeps changing your files or library, Serato cannot save to the files, the drive is slow, or Serato’s library database is out of step with the files. Rescan ID3 Tags, a button in the Files panel, makes Serato re-read the tags of every file in the library. It is the fix for tags edited in other apps and for an analyzer that keeps processing tracks it has already analyzed. It reads your files, and it does not delete cue points or beatgrids.
Stop Serato reading tags on every launch
-
Check whether it is reading or analyzingThe Analyze Files panel shows three bars: reading tracks, analyzing them, and writing tags. Reading is quick per track. If the middle bar is busy on tracks you analyzed before, Serato is re-analyzing, which is the bigger problem.
-
Connect the music drive directlyA slow USB drive or a hub makes every tag read slow. Plug the drive straight into the Mac, and use an SSD for a large library if you can.
-
Run Rescan ID3 Tags onceOpen the Files panel, click Rescan ID3 Tags and let it finish. Serato’s own tip: if the analyzer starts on tracks you know are analyzed, stop it, rescan, then analyze again so only new tracks are processed.
-
Turn off the Music app import if you don't use itWith Setup > Library + Display > Show iTunes library ticked, Serato imports your Music app library every time it starts. If you don't DJ from the Music app, untick it.
-
Stop other apps rewriting your filesTag editors and library tools change files Serato then has to re-read. Serato strongly advises against iCloud Music Library, which can replace your files with Apple’s copies and remove cues, beatgrids and loops.
-
Make sure Serato can write to the filesA gold lock in the Status column means the file or drive is read-only. Serato cannot save analysis to it, so the work only lasts until you quit and is redone next time. Fix the permissions, or move the music off an NTFS drive.
-
Rebuild the library database if it still happensIf none of the above explains it, the database may be out of step with your files. Back up, then restore or rebuild it as described in the corrupt database guide.
-
Rescan after editing tags anywhere elseQuit Serato before editing tags in another app, then open Serato and run Rescan ID3 Tags so the library picks up the new values.
What Rescan ID3 Tags actually does
Serato keeps its own copy of each track’s details (artist, title, BPM, key and so on) in its library database, and reads the full data, including cue points, loops and beatgrids, from the tags inside each audio file. Rescan ID3 Tags makes Serato read every file in the library again and update its database to match.
Use it when:
- You edited tags in another app. Serato’s advice is to rescan after changing tags in another program, so it picks up the changes.
- The analyzer re-processes tracks you already analyzed. Rescan first, then analyze, and only new tracks get processed.
- You moved or copied your music. After a move, a rescan flags the tracks that are no longer where Serato expects as missing, ready for Relocate Lost Files. See Relocate Lost Files not working.
- You restored or rebuilt the database. A rescan brings the new database in line with the files.
It does not analyze audio, rename files or delete anything. Because your cue points and beatgrids live in the file tags, a rescan reads them back rather than wiping them. On a large library it can take a while, so don’t start one just before a gig.
Reading, analyzing and writing are different jobs
Serato’s analyzer shows its work in three bars. The first is reading tracks. The second builds the waveform overview, checks the file for damage, and works out auto gain, BPM and key. The third is writing tags, which saves that analysis back into the file. Reading tags at launch is the cheap part. A full re-analysis is the slow part, and Serato normally only analyzes tracks that have not been analyzed yet.
One clue worth knowing: if the status bar shows Writing Tags on a file that is not in the analyzer’s list, Serato’s support team says that file may be corrupt. If the analyzer freezes or crashes on a file, see why Serato keeps crashing or freezing.
Why it happens on every launch
- The Music app library is being imported. On a Mac running Serato DJ Pro 4.0.9, Serato’s own log shows it importing the Music app library on every launch while Show iTunes library is on.
- Something else keeps changing the files. Tag editors, library managers, key detection apps and iCloud Music Library all rewrite files, and Serato has to read them again.
- Serato cannot save. On a read-only file or drive, Serato says metadata changes last only for the session, so whatever it worked out is gone the next time it opens.
- The drive is slow. A big library on a spinning USB drive, or on a drive behind a hub, simply takes longer to read.
- The database is out of step. On Serato’s forum, one DJ with 35,000 tracks reported launch dropping from 20 minutes to 30 seconds after rebuilding a damaged database. See how to fix a corrupt Serato database.
Editing tags outside Serato, safely
Three habits prevent most tag trouble. Quit Serato before another app edits your files, so the two never write to the same file at once. Don’t change tags and file names in one pass in another app: Serato warns that doing both without updating its database breaks Relocate Lost Files and orphans the old entries. And run Rescan ID3 Tags afterwards. That applies to every tag editor, including Crate Cleaner’s bulk tag editor.
If the analyzer keeps starting on your whole library, you often only need to analyze a handful of tracks. Crate Cleaner reads the same tags Serato does and lists every track with no BPM or key, so you can drag just those onto Analyze Files instead of forcing a full re-analysis. The scan is read-only and free on your real library.
FAQ
Is it normal for Serato to read tags when it starts? Yes, some reading at launch is normal, and it takes longer on a big library or a slow USB drive. Reading or re-analyzing the whole library on every launch is not, and usually has a cause you can fix.
Does Rescan ID3 Tags delete my cue points or beatgrids? No. Cues, loops and beatgrids are stored in each file’s tags. A rescan reads them back into Serato’s library rather than removing them.
Why does Serato re-analyze files I already analyzed? Usually because its library is out of step with the files, or it could not save the analysis to a read-only file. Serato’s fix is to stop the analyzer, run Rescan ID3 Tags, then analyze again.
How long does Rescan ID3 Tags take? It depends on library size and drive speed. A few thousand tracks on an internal SSD is quick; tens of thousands on a USB hard drive can take much longer. Let it finish rather than interrupting it.
Why does Serato say Writing Tags on a file it is not analyzing? Serato’s support team says that file may be corrupt. Check it, and replace or re-encode it if it will not play properly.
Analyze only what needs it
Crate Cleaner lists tracks with no BPM or key, plus missing and corrupt files, across your whole Serato library in one read-only scan. Free plan on your real library.