Why does my CDJ show E-8305 UNSUPPORTED FILE FORMAT for FLAC or WAV?
Updated October 9, 2026
A track playing on your computer does not prove that a standalone CDJ or XDJ can decode it. Support depends on the exact player model, audio format, encoding, sample rate, and bit depth. When the format or parameters are unsupported, the player may display E-8305: UNSUPPORTED FILE FORMAT.
A file may also be missing from the USB or referenced by the wrong library. Check those cases before assuming every playback problem requires conversion.
What does E-8305 UNSUPPORTED FILE FORMAT mean
E-8305: UNSUPPORTED FILE FORMAT means the player cannot play the loaded audio in its current format. E8305 without the hyphen is another common way to write the same error code. A related E-8304 can also appear with the unsupported-format message.
Start with the exact player's supported formats and the affected file's encoding, sample rate, and bit depth. AlphaTheta's CDJ-2000 E8304 and E8305 explanation also notes that a problem with the file data can cause these errors. If the original audio is damaged or missing, changing its extension or attempting conversion cannot recreate it. If it is readable but incompatible, use LastCUE's compatibility check to identify an appropriate conversion, then test the result on the intended player.
Why can FLAC fail on one player and work on another?
FLAC support differs between models. For example, the XDJ-RX2's documented standalone formats include MP3, AAC, WAV, and AIFF, while the CDJ-3000 also supports FLAC.
That is a reason to check the actual booth model instead of using a general statement that all CDJs either support or reject FLAC.
Why can a WAV file still be unsupported?
WAV is a file container. Files with the same extension can have different audio encoding and parameters.
A high sample rate, unsupported bit depth, floating-point encoding, or an invalid file header can prevent playback. Changing the filename extension does not convert the underlying audio.
For example, the CDJ-3000's published playable lossless specifications list 16- and 24-bit audio at 44.1, 48, 88.2, and 96 kHz. Its internal audio processing specifications should not be read as permission to load every 32-bit floating-point WAV.
How do I narrow down the problem?
| What you see | What to check next |
|---|---|
| E-8305: UNSUPPORTED FILE FORMAT appears when loading a track | The loaded file's format, encoding, sample rate, bit depth, and integrity against the exact player's supported formats. |
| The same track works on a newer player but fails on an older one | Model-specific codec and audio-parameter support. |
| Only some WAV files fail | Encoding, sample rate, bit depth, header validity, and firmware. |
| A playlist entry exists but its audio cannot be found | Whether the referenced file is actually present on the USB. |
| rekordbox reports a corrupted Device Library | The library database and recoverable data, rather than audio conversion alone. |
An E-8305 unsupported-format message points you toward the audio file and the player's supported formats. It does not, by itself, prove that the exported library database is corrupted or that conversion will fix every cause.
How does LastCUE help?
Select the intended player in Device compatibility check or the format-conversion workflow. Review the flagged tracks and reasons. LastCUE checks the local export data and available audio information against its supported player profiles.
For supported FLAC and WAV conversion inputs, you can choose MP3 128 kbps, MP3 320 kbps, or WAV 16-bit PCM at 44.1 kHz. Conversion cannot recreate a source audio file that is missing.
Use the profile result as a preparation check, then load representative converted tracks on the real player before the set. A profile check is not a hardware playback test.
Where can I confirm the player's specifications?
Use the exact model's current manual and firmware notes. Examples of primary references are the XDJ-RX2 official format answer and CDJ-3000 published specifications.