Skip to content

Supported File Formats

Producer Dashboard works with a wide range of audio and project file formats so you can import tracks from any DAW or export source. Understanding which formats are supported helps you get the most out of the app’s import, organization, and analysis features.


When you import bounces, stems, or other audio exports, Producer Dashboard supports the following formats. Each format is automatically detected during import and processed accordingly.

FormatExtensionCommon Use
MP3.mp3General exports, demo sharing
AAC/M4A.m4aHigh-quality Apple exports
Compressed formats use lossy compression, which reduces file size at the expense of some audio quality. These work perfectly for imports and BPM/key analysis, though if you have the option, exporting in a lossless format ensures the cleanest possible audio for analysis.
FormatExtensionCommon Use
WAV.wavIndustry standard, maximum quality
AIFF.aiff / .aifApple/Avid standard
FLAC.flacOpen-source lossless, good compression

Lossless formats preserve every detail of your audio, making them ideal for final exports and stems. When you run BPM or key detection, lossless files give the analysis engine the cleanest signal to work with.


Producer Dashboard recognizes project files from all major DAWs. Project files are typically used to link back to your original session so collaborators can open the project in the same software.

DAWExtensionNotes
Ableton Live.alsEntire project folder is imported
Logic Pro.logicxmacOS only format
FL Studio.flpFruity Loops project
Pro Tools.ptxSession file
Cubase.cprCubase project
Reaper.rppReaper project
Reason.reasonReason project file
Studio One.songPresonus Studio One

When you import a project file, the app reads the metadata and links it to the track group. The actual project file stays in place — the app creates a reference so you and your collaborators can quickly open the session in the original DAW.

Project files are scanned from your designated projects/ inbox folder. The import process:

  1. Detects project files by extension
  2. Matches them to existing track groups or creates new ones
  3. Organizes them into your tracks/ folder hierarchy
  4. Syncs the reference to your dashboard workspace

For Ableton Live projects specifically, the entire project folder (including the Samples/ subfolder) is moved, not just the .als file. This ensures the session opens correctly without broken sample references.


When you run a local import, the app scans three inbox folders in your Producer Dashboard directory:

  • bounces/ — Audio exports of finished or in-progress tracks
  • stems/ — Individual instrument or vocal stems
  • projects/ — Original DAW session files

Files are classified by which folder they come from, not by their extension. This means a WAV file in bounces/ is treated as a bounce, while the same WAV in stems/ is treated as a stem. This gives you flexibility in how you organize your exports.

Files are grouped into track groups based on their normalized song names. The system compares filenames to find likely matches for the same song.


When you trigger BPM or key detection on a track, the analysis engine works with any of the supported audio formats. The process typically takes 1–3 seconds per file, and the results (BPM and musical key) are stored with your track metadata.

The analysis happens locally on your machine when using the desktop app, which means your audio never leaves your device during analysis. Supported formats for analysis include WAV, MP3, FLAC, AIFF, M4A, and OGG. (OGG is supported for analysis but is not scanned during file import.)


If you connect a Dropbox account, the app can also sync files from your cloud storage. In this case, the same audio formats are supported, and the analysis happens in the cloud if you’re using the web version.

When importing from Dropbox, make sure your audio files are in a folder labeled “Audio Bounces,” “audio-bounces,” or “Audio_Bounces.” The app looks for supported file extensions (.wav, .mp3, .aiff, .aif, .flac, .m4a) within these folders during sync.


When preparing files for import, consider these best practices:

  • Use consistent naming — Include the song name clearly in each filename so grouping works smoothly
  • Keep formats consistent — If you export stems in WAV, try to export bounces in WAV too for easier organization
  • Include version info — If you need to track versions (like “v1” or “final”), the app handles this during normalization, but being explicit helps

If your bounces/ folder contains a mix of MP3, WAV, and FLAC files of the same song, the app groups them all together. You might see multiple file entries in the same track group, each with its own format indicator. This is normal and useful for having quick MP3 previews alongside your master WAV files.

The import system automatically skips files that are actually symbolic links pointing to files already organized in your tracks/ folder. This prevents duplicate entries and keeps your dashboard clean. If a file isn’t appearing after import, check that it isn’t a symlink and that it has a supported extension.