Pull every Engine DJ track and playlist out into a clean Artist/Album folder layout with M3U playlist files. Reverse-engineer back to plain folders.
You want out of Engine DJ entirely — back to plain folders for use with Plex, Navidrome, Roon, or just for backup. But Engine DJ keeps everything inside Engine DJ m.db. Manually moving files breaks playlists, and there's no built-in "export everything to a folder tree" option.
Supported today
Rekordbox · Serato DJ · VirtualDJ (incl. Favorite Folders) on Windows 10+ and macOS (Apple Silicon + Intel).
Most DJ apps treat their library as the source of truth and don't offer a clean "back to folders" export. MLD reads Engine DJ m.db directly, writes the files out by Artist/Album (or any layout you choose), and emits M3U files so playlist intent survives. From there your library is ready for any media server or just plain filesystem browsing — and a timestamped backup of the original Engine DJ library is taken first so the source stays intact.
No. The Engine DJ library is read-only during export. A timestamped backup is taken anyway, so nothing on the Engine DJ side can be lost.
Default is Artist/Album/Track.ext with M3U files at the top level for each playlist. You can choose a flat layout, by-genre, or custom — MLD shows the preview before writing.
Yes. Every Engine DJ playlist becomes an M3U file with relative paths to the exported tracks. Plex, Navidrome, Roon, foobar2000, and most media players read M3U directly.
Cues and beatgrids are Engine DJ-internal — the file system has no concept for them. MLD documents which metadata translates and which doesn't before the export runs.
Yes. The exported folder is plain audio files plus M3U playlists, which means any DJ app (or media server) can import it. You can use Folder Library to Rekordbox to come back in the other direction.
Free tier covers detection and viewing. Lifetime access is $49 — $19 for the first 100 DJs.
