The file you download carries a real Serato beatgrid inside it. Import it and it is ready — no analysis pass, no dragging the first downbeat, no typing the key into the comments.
Serato stores its beatgrid in a GEOB frame inside the file's tags. A constant-tempo grid is one terminal marker: a downbeat anchor and a tempo. Getting that anchor and tempo right on a separated stem is the hard part, and the reason it works here is that neither is measured on the stem — both come from the full mix, where the drums still exist.
Every write is then read back out of the finished file and compared against what was intended before the file is offered for download. A tag that silently failed to write is worse than no tag at all, so nothing ships unverified.
If the detected beats do not sit convincingly on the tempo about to be claimed, the file ships with a key and a tempo but no grid. That is deliberate. A missing grid costs you one analysis pass; a confidently wrong grid costs you a rebuild in front of people. Across the 2,579-track test corpus, grids that were claimed were correct 95.3% of the time.
Drop a track and check the grid yourself on the free 30 seconds. No account, no card.
Open the toolNo. The beatgrid and tags are written into the file itself, so Serato reads them on import. That is the entire point of the product.
Not yet. Serato is the only one supported, because Serato is the only one the output has actually been verified against. An untested export would be a claim rather than a feature.
Writing ID3 tags into a WAV corrupts its RIFF header. AIFF is lossless, Serato-native and holds the tags safely, so AIFF and MP3 320 are the two delivery formats.