- Grant full folder access so Android exposes CUE files to AIMP.
- Use UTF-8 and match every referenced audio filename exactly.
- Open the CUE directly in a clean temporary playlist.
- Confirm the Symptom With a Small Safe Test
- Grant Full Folder Access in AIMP
- Validate the CUE Encoding and Filenames
- Refresh the Playlist Without Changing Unrelated Features
- Rule Out Source and Playback Problems
- Run a Clean Temporary Test Before Reinstalling
- Quick Fix Checklist
- Frequently Asked Questions
When AIMP for Android ignores a CUE file, the usual symptom is that the app adds or plays one long audio file instead of displaying the individual tracks described by the sheet. In other cases, the CUE file is invisible in the file picker, opens as an empty or broken playlist, or produces entries that cannot be played. The most likely causes are restricted Android storage access, a filename mismatch, unsupported CUE structure, incorrect text encoding, or a stale playlist created before the files were corrected. Work through the checks below in order. After each change, look for the expected result and stop troubleshooting as soon as the CUE tracks appear and play correctly.

Start with free Canva bundles
Browse the freebies page to claim ready-to-use Canva bundles, then get 25% off your first premium bundle after you sign up.
Free to claim. Canva-ready. Instant access.
1. Confirm the Symptom With a Small Safe Test
Before changing AIMP settings or reorganizing your full music library, create a controlled test. This separates an app-access problem from an error inside the original CUE sheet.
1.1 Prepare a Simple Test Folder
Create a normal subfolder in your phone's internal storage, such as Music/CUE-Test. Avoid the Downloads folder, the root of internal storage, and the root of an SD card for this test. Android may prevent apps from receiving full folder access in certain protected locations.
Copy one known-good audio image and its CUE file into the test folder. A basic pair might look like this:
- Example Album.flac
- Example Album.cue
The CUE file should refer to that exact audio filename, including spaces, punctuation, letter case, and extension. For example, its FILE line should resemble:
FILE "Example Album.flac" WAVE
The word WAVE in a CUE sheet is commonly used as the file-type token even when the referenced image is FLAC. Do not change it merely because the source file has a .flac extension.
1.2 Open the CUE Directly
In AIMP, switch to a playlist, use the add-files command, browse to the test folder, and select the CUE file itself. Do not begin by adding only the FLAC, APE, WAV, or other audio image.
Success looks like this: AIMP adds several named track entries with separate start times, rather than one album-length file. Start two or three entries to confirm that playback begins at the expected positions. If that happens, stop changing AIMP settings. The original folder, permission grant, or CUE content is the problem.
If the test CUE is not visible, the folder is probably available only through restricted media access. Continue to the permission steps.
2. Grant Full Folder Access in AIMP
Full folder access is the most important Android-specific check for the “AIMP Android CUE files ignored” symptom. Android can expose recognized audio files to an app while excluding companion files such as CUE sheets. As a result, AIMP can see and play the large audio image but cannot see the instructions that divide it into tracks.
2.1 Recognize Restricted-Mode Storage Access
Restricted access can create a confusing partial success. The FLAC or MP3 appears in AIMP, its embedded artwork may load, and playback works, but the neighboring CUE file is absent or ignored. This does not prove the sheet is malformed. It may simply mean Android gave AIMP access to audio media rather than full access to the folder.
From AIMP's playlist screen, use the add-files command and browse to the album directory. If AIMP displays a restricted-access warning or an option to grant full access, select it. Android should then open its system folder picker. Choose the album folder or, preferably, a parent music folder that contains the albums you want AIMP to read, and confirm with Use this folder.
Success looks like this: when you return to AIMP's file browser, the CUE file becomes visible. Selecting it adds the sheet's individual tracks. Once this works, do not reset permissions or reinstall the app.
2.2 Do Not Use Downloads or an SD Card Root for the First Test
Android's system folder picker may refuse full access to protected locations, including Downloads and the root of an SD card. If the system will not let you choose a location, move the album into a regular subfolder such as Music/Albums or SD Card/Music/Albums. Grant access to that subfolder instead.
This move is a diagnostic step, not necessarily a permanent reorganization. If the same CUE starts working in the new folder, you have confirmed that storage scope was the cause. Stop editing the CUE sheet because its content is already usable.
2.3 Recheck Access After Moving Files
A permission grant applies to the selected folder tree. Moving an album to another directory, replacing an SD card, restoring files from backup, or selecting a different storage provider can put the files outside the previously approved tree.
Browse to the album through AIMP again and grant full access to its current parent folder. Do not assume that Android's general Music and Audio permission gives AIMP access to every non-audio companion file.
3. Validate the CUE Encoding and Filenames
If AIMP can see the sheet but still ignores it, inspect the file on a computer or with a trustworthy plain-text editor. Do not use a word processor because it may add formatting or alter quotation marks.
3.1 Save the Sheet as UTF-8
Save the CUE as plain UTF-8 text. Encoding problems are especially likely when album, artist, folder, or track names contain accented letters, Cyrillic characters, Asian scripts, or other non-ASCII text. A sheet may appear readable in one desktop editor while an Android application interprets some bytes differently.
On Windows, open the sheet in a text editor that shows the current encoding, choose Save As or Convert Encoding, select UTF-8, and save it with the .cue extension. Make sure the editor has not silently produced a file named Example Album.cue.txt.
Success looks like this: after removing the old playlist entries and reopening the corrected CUE, AIMP displays readable track titles and can locate the referenced audio image. If all titles and tracks now work, no output-method, Bluetooth, skin, or equalizer change is needed.
3.2 Match the CUE and Audio Filenames
For reliable automatic association, give the CUE the same base name as its audio image. These are suitable examples:
Example Album.flacwithExample Album.cueExample Album.flacwithExample Album.flac.cue
More importantly, the FILE command inside the sheet must match the real audio filename. Check the entire name and extension. A CUE that says Example Album.wav cannot locate a file that was later converted or renamed to Example Album.flac unless the FILE line is updated.
Watch for subtle differences such as a hyphen instead of an en dash, doubled spaces, trailing spaces, smart quotation marks, or an extension hidden by Windows File Explorer. Keep the CUE and audio file in the same folder during testing so the sheet can use a simple relative filename rather than a computer-specific path.
3.3 Check Whether the Sheet References Multiple Audio Files
A standard album-image CUE usually describes one physical audio file divided by INDEX entries. A sheet that references multiple physical audio files may be handled more like a playlist and may not be attached automatically when you add a folder or open one of the audio files.
If the sheet contains several FILE commands, try opening or importing the CUE directly rather than expecting AIMP to discover it as a sidecar for one image. If each song already exists as an individual audio file, a conventional M3U8 playlist may be more appropriate for that collection.
Success looks like this: direct import produces the expected entries and each entry locates its corresponding file. If it does, use direct import for that multi-file sheet and stop trying to force one-file automatic association.
4. Refresh the Playlist Without Changing Unrelated Features
AIMP playlists can retain entries created before permissions or filenames were fixed. Merely editing the CUE on disk may not transform an already-added album-length entry into split tracks.
4.1 Remove Only the Failed Test Entries
Remove the affected album entries from the current AIMP playlist without deleting the physical files. Then use Add Files to select the corrected CUE directly. If you are concerned about an important playlist, create a temporary playlist and perform the test there.
Do not delete all playlists or clear the entire music library at this stage. The goal is to prevent cached or previously imported entries from obscuring the result while preserving the rest of your setup.
4.2 Separate Playlist Behavior From Library Scanning
A music-library scan may find the large audio image without processing its CUE association in the way you expect. Test through the playlist file browser first. If direct opening works, refresh or rescan the relevant library folder afterward.
Success looks like this: a newly created temporary playlist shows one item per CUE track. If the old playlist still shows one long item, replace only that old entry. There is no reason to rebuild the entire library.
4.3 Use File Information to Identify the Loaded Source
Open AIMP's file information for a track after importing the sheet. Confirm that the source points to the expected audio file and folder. If it points to an older duplicate, a cloud cache, or another storage location, remove that entry and add the CUE from the intended directory.
Tag and artwork problems do not normally make a valid local CUE invisible. Likewise, skins change presentation rather than Android folder access. Temporarily return to AIMP's standard interface only if a custom skin makes the add-files or permission controls difficult to locate.

5. Rule Out Source and Playback Problems
If AIMP creates separate CUE tracks but they will not play, the sheet is no longer being ignored. You now have a source-file or playback issue, which requires a narrower test.
5.1 Play the Physical Audio File
Add the underlying FLAC, APE, WAV, MP3, or other image by itself and start playback. If the physical file also fails, confirm that its format is supported, that copying completed successfully, and that another local file of the same format plays in AIMP.
Do not install a Windows codec pack for an Android AIMP problem. Android applications generally use their own playback components or supported platform facilities, and a codec pack installed on a PC cannot repair a file on the phone.
5.2 Copy the Album Again if the File Is Damaged
A truncated or corrupted audio image may allow AIMP to read its name while preventing playback at some or all CUE offsets. Compare the file size with the original and recopy it using a reliable USB, local-network, or storage transfer. Safely eject removable storage after copying.
If the first CUE track plays but later entries fail consistently, test playback near those positions in the full audio image. Failure at the same locations suggests source-file damage rather than a permission or playlist problem.
5.3 Test Local Storage Before Network or Cloud Storage
If the album normally comes from Samba, WebDAV, cloud storage, or another network source, copy the CUE and audio image into the local test folder. CUE sheets depend on resolvable references to their audio files, and network providers may expose companion files or paths differently.
If the local copy works, check network credentials, path availability, filename handling, and whether the CUE references a relative local filename rather than a Windows drive letter. A path such as D:\Music\Example Album.flac will not exist on Android.
Internet radio, podcast, and stream URLs do not use local CUE sheets in the same way as an album image. Radio metadata, podcast chapters, and cloud-provider listings should be troubleshot separately rather than by editing a local CUE.
5.4 Change the Output Method Only After Tracks Appear
AIMP's output method can matter when tracks are listed correctly but playback is silent, distorted, or fails to start on a particular device. It does not normally explain why a CUE file is absent from the file picker.
If the split tracks exist but playback fails, disconnect Bluetooth temporarily and test through the phone speaker or a wired output. You can also try another AIMP output method if the app provides that option on your device. Change one setting at a time and return it to the previous value if there is no improvement.
Success looks like this: the same CUE track plays through a basic local output. If it does, the remaining issue concerns the output route or Bluetooth device, not CUE parsing.
6. Run a Clean Temporary Test Before Reinstalling
Reinstalling AIMP can remove app data and permissions without correcting a malformed sheet or an inaccessible folder. Use a temporary playlist and folder first.
- Create Music/CUE-Test in internal storage.
- Copy one audio image and one matching CUE into it.
- Save the CUE as UTF-8.
- Confirm that its FILE line exactly matches the audio filename.
- Grant AIMP full access to the CUE-Test folder.
- Create a new temporary playlist.
- Add the CUE directly through AIMP's file browser.
- Play the first, middle, and final track entries.
If this test works, AIMP's core CUE support is functioning. Compare the working pair with the failed album and change only the identified difference. That difference is usually the storage location, access scope, encoding, filename, path, or number of physical files referenced.
If the controlled pair fails even though the CUE is visible and the audio image plays independently, preserve the test files and note the exact behavior. This provides a reproducible case for AIMP troubleshooting without exposing or altering your full library.
7. Quick Fix Checklist
- Move the test album out of Downloads and out of the SD card root.
- Place it in a normal subfolder such as Music/Albums.
- Grant AIMP full access to that folder through Android's folder picker.
- Confirm that AIMP can see the
.cuefile. - Save the sheet as plain UTF-8 text.
- Match the CUE basename to the audio-image basename.
- Match the FILE line exactly to the real audio filename and extension.
- Keep the CUE and audio image together during testing.
- Open the CUE directly instead of adding only the audio file.
- Use a new temporary playlist to avoid stale entries.
- Test the physical audio file separately if split tracks appear but do not play.
- Test locally before investigating Samba, WebDAV, cloud, or removable-storage behavior.
- Stop changing settings as soon as the separate tracks appear and play correctly.
8. Frequently Asked Questions
8.1 Why Does AIMP See the FLAC but Ignore the CUE?
Android may have granted restricted media access that exposes recognized audio files but excludes companion CUE files. Grant full access to a normal music subfolder through AIMP's add-files browser. If Android will not allow the selected location, test from a subfolder outside Downloads and outside the SD card root.
8.2 Does the CUE Filename Have to Match the Audio Filename?
Matching basenames provides the most reliable automatic association. The filename written in the CUE's FILE command must also match the actual audio filename. Directly opening a differently named sheet may work in some situations, but matching names eliminates ambiguity and is the best troubleshooting configuration.
8.3 Why Does AIMP Add One Long Track Instead of Separate Songs?
AIMP is probably loading the physical audio image without successfully loading its neighboring CUE sheet. Check full folder access, UTF-8 encoding, the internal FILE line, and the sheet's filename. Remove the old album-length playlist entry and open the corrected CUE directly.
8.4 Should I Rescan the Entire Music Library?
Not initially. Create a temporary playlist and add the CUE directly. If that works, refresh only the affected folder or replace the stale playlist entry. A full rescan adds unnecessary variables and may take considerable time on a large collection.
8.5 Can a Skin, Plugin, Tag, or Artwork Setting Cause This?
Those features are unlikely to make Android hide a local CUE file. A custom skin may make a control harder to find, while tags and artwork may change how entries are labeled. Start with storage access and CUE validity. Investigate display features only after AIMP has created the split tracks.
8.6 When Should I Reinstall AIMP?
Reinstallation should be a last step after a known-good UTF-8 CUE and playable audio image fail in a normal local subfolder with full access granted. Record or export important playlists first. Remember that reinstalling may reset permissions, so you will need to grant folder access again afterward.