AIMP CUE Sheet Points to Missing Audio File: How to Fix It

When an AIMP CUE sheet points to a missing audio file, the player can read the album's track layout but cannot open the FLAC, WAV, MP3, APE, or other audio file named inside the sheet. You may see an unavailable-file warning, get tracks that refuse to play, or find that AIMP loads the album as one long recording instead of separate tracks. The usual causes are a filename mismatch, a changed extension, a moved album folder, an incorrect relative path, or restricted storage access on Android. Work through the checks below in order. Once the CUE tracks load and play correctly, stop changing settings because output devices, skins, plugins, and codecs are generally unrelated to a broken file reference.

1. Confirm the Symptom With a Small Safe Test

Before editing anything, verify that the problem is the CUE reference rather than the underlying recording. Keep the original files unchanged until you know which part is failing.

1.1 Play the audio file directly

Open the album folder and add the large audio file directly to AIMP without opening the CUE sheet. For a single-file album image, this is usually the largest FLAC, WAV, APE, or MP3 file in the folder.

• If the audio file plays, AIMP's output method, audio device, and basic format support are working. Focus on the CUE sheet.
• If the file does not play, confirm that it opens in another trusted player and that its size is plausible. A zero-byte, incomplete, corrupted, or unavailable network file cannot be repaired by changing the CUE sheet.
• If the audio plays on Windows but not Android, check storage access and filename case before changing the text.

Success looks like this: the full album recording starts playing when opened directly. At that point, stop adjusting output devices, exclusive mode, Bluetooth settings, skins, and visual plugins. They cannot correct a CUE sheet that names the wrong file.

1.2 Create a temporary same-folder test

Copy the CUE sheet and its referenced audio file into a new local folder with a simple name, such as C:\Music\CueTest on Windows or Music/CueTest on Android. Do not use a cloud, Samba, WebDAV, USB, or synchronized folder for this first test.

Open the copied CUE file in AIMP. If it works locally, the original problem is likely related to a network location, an unavailable drive, cloud placeholders, credentials, or Android folder permissions. If it still fails, inspect the CUE's FILE line.

2. Check the FILE Line and Exact Filename

A CUE sheet is a plain-text description of tracks and timestamps. Its FILE command tells AIMP which recording contains the audio. A typical line looks like this:

FILE "Album Name.flac" WAVE

The filename inside quotation marks must identify the real audio file. Do not assume that similar-looking names are equal.

2.1 Compare the complete names

In File Explorer on Windows, enable file-name extensions before comparing the entries. A file displayed as Album Name may actually be Album Name.flac, Album Name.wav, or even Album Name.flac.flac. Compare the full name with every character inside the CUE's quotation marks.

Common mismatches include:

• Album.flac in the folder but Album.wav in the CUE
• Artist - Album.flac in the folder but Album.flac in the CUE
• An added suffix such as (Remastered), [24-96], or - copy
• Different hyphens, apostrophes, spaces, brackets, or accented characters
• A hidden duplicate extension caused by renaming a file while extensions were hidden

The simplest AIMP CUE sheet points to missing audio file fix is normally to make the FILE entry match the real recording. Alternatively, rename the recording to match the CUE, but only if no other playlist, application, or synchronization rule depends on its current name.

Success looks like this: reopening the CUE creates separate playlist entries and the first track begins playing. If that happens, stop troubleshooting.

2.2 Check extension mismatches after conversion

A frequent cause is converting an album image from WAV or APE to FLAC without updating the sheet. The timestamps may remain valid, but AIMP still searches for the old filename. For example, after converting Concert.wav to Concert.flac, change only the referenced filename where appropriate:

FILE "Concert.flac" WAVE

The final token describes the CUE file type syntax and is not necessarily the same text as the filename extension. Avoid making broad replacements throughout the document. The critical correction is usually the filename inside quotation marks.

2.3 Inspect every FILE command

Some releases use multiple audio files, with a separate FILE line before each group of tracks. Search the entire CUE document for FILE. Confirm that every referenced recording exists and that each track block remains under the correct command.

If only one disc or track group fails, do not rewrite the whole sheet. Correct the specific missing reference and test again.

3. Check Relative Paths and Folder Moves

Most portable CUE sheets use a relative filename, meaning AIMP looks for the recording relative to the CUE file's location. If both files are in one folder, the line should normally contain only the filename rather than a full drive path.

3.1 Keep the CUE and audio together

If the sheet contains FILE "Album.flac" WAVE, place Album.cue and Album.flac in the same folder. Moving only the CUE into a playlists directory breaks that relationship. Moving only the recording has the same effect.

If you reorganized your library after creating the CUE, either reunite the files or update the path. A relative reference to a subfolder may look like FILE "Disc 1\Album.flac" WAVE on a Windows-created sheet. Cross-device use is usually more reliable when each CUE and its recordings remain together in a self-contained album folder.

3.2 Replace obsolete absolute paths

An absolute reference can break when a drive letter, username, mount point, network share, or folder structure changes. For example, a sheet created on another computer might refer to D:\Rips\Artist\Album.flac, even though your copy is stored on E:\Music\Artist\Album.flac.

If the CUE and audio file are now in the same directory, replace the obsolete full path with the filename alone. This also makes the album easier to move between Windows, Android, external storage, and backups.

Success looks like this: the copied album folder continues working after being moved as a unit. That confirms the reference is portable and no longer tied to the old location.

4. Edit the CUE Sheet Safely

Because a CUE is plain text, it can be repaired with a basic text editor. The safest approach is to make one narrow change, save, and test.

4.1 Back up the original

1. Close or remove the affected CUE from the active AIMP playlist.
2. Duplicate the CUE file and give the backup a clear name such as Album.original.cue.
3. Open the working copy in a plain-text editor.
4. Locate each FILE line.
5. Correct only the filename or path inside quotation marks.
6. Save as plain text, preferably using UTF-8 encoding.
7. Remove the old broken playlist entries and add the corrected CUE again.

Do not edit track indexes unless the album plays but track boundaries are wrong. The INDEX timestamps do not cause a missing-file message. Also avoid word processors that may insert smart quotes or formatting characters. The filename must remain inside ordinary straight quotation marks.

4.2 Handle case and special characters on Android

Windows commonly treats filename case as equivalent, but Android storage providers, network servers, and Linux-based file systems may distinguish Album.flac from album.flac. Match uppercase and lowercase letters exactly when an album works on Windows but fails on Android.

Special characters can also change during extraction, synchronization, or copying. Compare apostrophes, accented letters, ampersands, non-English characters, and Unicode punctuation carefully. If necessary, temporarily rename both the recording and its CUE reference to a simple test name such as album.flac. This is a diagnostic step, not a requirement to simplify your entire library.

Success looks like this: the Android playlist displays the CUE tracks and can start more than one track, not merely the full recording. Once confirmed, preserve the working spelling.

5. Check Android Storage and Network Access

On Android, AIMP may be able to see ordinary audio files while lacking sufficient access to read a neighboring CUE file. This can make the recording playable by itself even though the album cannot be split into tracks.

5.1 Grant access to the album folder

Use AIMP's file-adding interface to browse to the parent music folder. If AIMP displays a restricted-access warning, use the offered option to grant full access and approve the folder through Android's system folder picker. Grant the narrowest practical folder, such as your Music directory, rather than changing unrelated security controls.

After granting access, remove the failed entries and add the album again from that authorized folder. Merely tapping the old playlist item may leave a stale unavailable reference.

Also confirm that Android still allows AIMP to access music and audio. Permissions can be revoked after an app has not been used, after storage is reinserted, or when a provider connection changes. Do not disable Android security features permanently.

5.2 Test external and remote locations locally

If the album is on an SD card, USB device, Samba share, WebDAV server, or cloud-backed provider, copy one affected folder to internal storage. A successful internal-storage test points to the source connection rather than the CUE syntax.

• For Samba or WebDAV, reconnect with current credentials and confirm the audio file is available through the same path as the CUE.
• For cloud storage, download both files completely. A placeholder visible in a file list may not be available for local playback.
• For an SD card or USB device, verify that it is mounted and that its folder authorization remains valid.
• For battery-managed devices, allow AIMP enough background access for remote playback, but treat this as relevant only if playback stops after the files were found successfully.

Bluetooth profile, headset controls, output method, and device volume do not explain a message saying the referenced file is missing. Investigate them only when AIMP finds and starts the track but no sound reaches the device.

6. Refresh AIMP Without Changing Unrelated Settings

Correcting the files on disk may not immediately repair playlist entries that still hold old paths. Refresh the specific data source instead of reinstalling AIMP.

6.1 Re-add the corrected sheet

Remove the unavailable CUE-derived tracks from the playlist without deleting the source files. Then add the corrected CUE again. This forces AIMP to parse the current FILE line rather than relying on old playlist data.

If the album is managed through the music library, update or rescan the relevant monitored folder. If it comes from a folder-based or synchronized playlist, use the available content-update or find-new-files action. A tag rescan alone may refresh titles and artwork without repairing an obsolete file path.

6.2 Separate metadata issues from file-reference issues

AIMP's file information and tag editor can confirm which physical recording is open, but tags and cover art do not determine whether an external CUE can locate its audio file. A missing image, wrong album title, or unexpected tag source is a separate problem.

Likewise, skins normally change presentation rather than path resolution. Disable a third-party plugin only if the failure occurs exclusively for a format or remote protocol handled by that plugin. The converter matters only if it renamed, relocated, or failed to create the referenced output file. In that case, check the converter destination and log, then update the CUE to the output that actually exists.

7. Run a Clean Temporary Test Before Reinstalling

If the reference looks correct but AIMP still reports a missing file, create a controlled test before deleting playlists or reinstalling the application.

1. Create a new local folder with a short, simple path.
2. Copy one known-playable audio file into it.
3. Copy the CUE into the folder.
4. Rename the audio file to album.flac, using its real extension.
5. Change the CUE's relevant line to FILE "album.flac" WAVE.
6. Create a new empty AIMP playlist.
7. Add only the test CUE and try the first two tracks.

If the clean test works, AIMP itself is functioning. Compare the working folder against the original for path length, permissions, special characters, network availability, and stale playlist data. If it fails while the audio opens directly, restore the backup and inspect the sheet for malformed quotes, missing commands, multiple incorrect FILE blocks, or text-encoding damage.

A temporary clean AIMP profile may be useful only after the same valid local test fails in a new playlist. Reinstallation should be a last step because it does not rename the missing recording, repair a path, or grant access to the correct Android folder automatically.

8. Quick Fix Checklist

• Play the underlying album recording directly in AIMP.
• Enable filename extensions on Windows.
• Compare the real filename with the quoted FILE value character by character.
• Correct WAV, FLAC, APE, or MP3 extension mismatches.
• Search the CUE for more than one FILE command.
• Keep the CUE and referenced recordings in the same album folder when possible.
• Replace obsolete absolute paths with a portable relative filename.
• Match capitalization and special characters exactly on Android and network storage.
• Save the repaired sheet as plain UTF-8 text with straight quotation marks.
• Grant AIMP full folder access through Android's system folder picker when required.
• Download cloud placeholders and reconnect unavailable network sources.
• Remove stale playlist entries and add the corrected CUE again.
• Stop changing settings as soon as the split tracks load and play.

9. Frequently Asked Questions

9.1 Why does the FLAC play but the CUE does not?

The FLAC can play because its decoder and AIMP's output system are working. The CUE fails because its FILE line identifies a different name or location, or because Android can read the audio file but not the neighboring CUE metadata. Compare the exact filename first, then verify folder access.

9.2 Should the CUE and audio file have the same base name?

Using matching base names is a reliable arrangement and can help automatic discovery. More importantly, the audio filename written inside the CUE must match the actual recording. Keeping both files together and using consistent names reduces failures after copying albums between devices.

9.3 Can I use a full path in the FILE line?

A full path may work on the computer where it was created, but it is fragile. Drive letters, usernames, network mounts, and Android locations can change. If the CUE and recording are in the same folder, a filename-only relative reference is usually more portable.

9.4 Does changing the output device fix a missing CUE audio file?

No. Output settings matter after a file has been opened. A missing-file error occurs earlier, while AIMP is trying to resolve the path in the sheet. Change the output method, exclusive mode, or Bluetooth configuration only if playback starts but produces no sound.

9.5 Do I need to reinstall AIMP?

Usually not. Reinstallation does not correct a misspelled filename, restore a moved recording, update an obsolete path, or authorize an Android storage folder. Try a same-folder local test and a new playlist first. Consider a clean profile or reinstall only if a known-valid test pair still fails.

9.6 What if the CUE loads but the track times are wrong?

That is a different symptom. It may mean the sheet belongs to another edition, master, or audio image, or that the recording was altered after the CUE was created. Restore a CUE generated for the exact source file rather than guessing new index times. A sheet that opens successfully but seeks to incorrect positions is no longer a missing-reference problem.