AIMP Audio Converter CUE Not Generated: How to Fix It

When the AIMP audio converter finishes processing an album but no CUE file appears, the problem is usually not the encoder itself. In most cases, AIMP is using a conversion mode that produces separate files, the tracks are not arranged as one album, the destination is not writable, or the expected CUE filename differs from the name you searched for. The key distinction is that CUE generation belongs to specific single-output conversion modes in AIMP for Windows. It is not a general option applied to every conversion, and the Android player does not provide the same desktop audio-converter workflow.

The safest way to diagnose the AIMP audio converter CUE not generated symptom is to run a controlled test with two short local tracks. Once that test creates one audio file and a matching CUE sheet, stop changing settings and apply the same configuration to the real album.

1. Confirm the Symptom With a Small Safe Test

Before changing plugins, playlists, tags, or installation files, determine whether AIMP can create a CUE sheet under simple conditions. This separates a converter-configuration problem from an issue involving the original album, network location, or destination folder.

1.1 Prepare Two Short Copied Tracks

Choose two ordinary local audio files that AIMP can already play. Short MP3, WAV, or FLAC files are suitable. Copy them into a new temporary folder so that the test does not alter your music library or original album.

1. Create a folder such as C:\AIMP-CUE-Test.
2. Copy two short tracks into that folder.
3. Rename them temporarily to 01 Test Track and 02 Test Track if their order is unclear.
4. Open the copies in AIMP and confirm that both play normally.
5. Add only those two files to the audio converter.

Do not use an internet-radio stream, podcast URL, cloud placeholder, Samba share, WebDAV location, or removable device for this first test. A local test removes network access, credentials, buffering, and provider restrictions from the diagnosis.

1.2 Select a Mode That Can Generate a CUE Sheet

AIMP for Windows offers multiple converter modes. A mode that creates one result for every source produces separate output files and normally has no need to describe them in a new CUE sheet. Select a single-output mode with CUE generation support, such as the mode that combines all selected sources into one result. A folder-based single-result mode can also support CUE creation when its grouping matches the job.

Enable the CUE-generation option associated with that output mode. If the option is missing, unavailable, or disabled, first verify the selected conversion mode. Do not assume that choosing FLAC or WAV automatically enables CUE creation. The output container and the conversion mode are separate decisions.

Success looks like this: the destination contains one combined audio file and one small file ending in .cue. The CUE sheet should list both test tracks in the same order shown in the converter. If these files appear, stop changing global AIMP settings. The converter works, and the remaining problem is specific to the original source list, grouping, naming, or destination.

2. Check the Converter Mode and Album Structure

The most common AIMP audio converter CUE not generated fix is selecting the correct relationship between source tracks and output files. A CUE sheet is most useful when several logical tracks are represented inside one continuous output file.

2.1 Use Single-Output Album Conversion

For one album made from several tracks, arrange the converter to create a single output for the album and enable its CUE-sheet option. Avoid a one-source-to-one-result mode if your goal is one album image plus a CUE file.

Be careful with folder-based grouping. If tracks from one album are spread across multiple directories, a single-folder mode may treat them as separate jobs. Conversely, placing unrelated albums in one conversion group may combine material that should not share a CUE sheet.

For the cleanest result:

• Convert one album at a time while troubleshooting.
• Keep only the intended album tracks in the converter list.
• Use one combined output file for that album.
• Enable CUE generation before starting the job.
• Send the result to a new, empty folder.

Success looks like this: AIMP reports one completed output job, and the folder contains a matching audio-and-CUE pair. If that happens, there is no reason to reinstall AIMP or reset unrelated playback settings.

2.2 Correct the Source Track Order

The converter list supplies the timeline used to build the combined file. If the tracks are out of order, the CUE entries can also be out of order even if their tags contain correct track numbers.

Inspect the list immediately before conversion. Sort by track number or arrange the files manually as needed. Pay particular attention to filenames sorted alphabetically, because names such as 1, 10, and 2 can appear in an unintended order. Leading zeroes, such as 01, 02, and 10, make filename sorting more predictable.

If tracks came from several playlists or Music Library views, create a temporary playlist containing only the album. Put the tracks in final running order, select them, and send that ordered selection to the converter.

Success looks like this: opening the generated CUE sheet in AIMP displays the tracks in album order, with each entry pointing to the same combined audio file.

3. Check the Output Folder and CUE Filename

A conversion can appear successful even when an associated file cannot be written where expected. Testing a simple local destination is faster and safer than changing codecs or installing additional software.

3.1 Use a Writable Local Folder

Create a new folder inside your user Music or Documents directory and use it as the converter destination. Avoid protected Windows directories, application folders, the root of the system drive, read-only media, and destinations controlled by another account.

If the current target is a NAS, Samba share, WebDAV folder, synchronized cloud directory, USB drive, or SD card, test locally first. Network credentials may permit reading without permitting file creation. A cloud client may also display online-only folders that are not ready for ordinary local writes.

After selecting the test destination, manually create and delete a small text file in it. This confirms that your Windows account can write there. If that works, run the two-track conversion again.

Success looks like this: both the combined audio file and CUE sheet appear in the local folder. If local output works, keep AIMP unchanged and troubleshoot the original destination's permissions, connection, available space, or synchronization state.

3.2 Search for the Actual CUE Name

The CUE file normally follows the output album or combined-file naming logic, not necessarily the title of the first source track. Sort the destination by modification time and look for files created at the moment the conversion ended.

In Windows File Explorer, enable filename extensions so that you can distinguish Album.cue from similarly named audio, playlist, or text files. Search the exact output directory and its newly created subfolders for *.cue.

Review the output naming template if the resulting filename is blank, overly long, or built from missing metadata. For testing, use a short fixed name such as CUE Test. Avoid reserved filename characters and unnecessarily deep folder templates.

Success looks like this: the folder contains names such as CUE Test.flac and CUE Test.cue. Once found, stop modifying converter options and correct only the naming template used for the real album.

4. Verify the Playlist, Tags, and Source Files

AIMP can generate track boundaries from the ordered source list, but meaningful CUE labels depend on usable track information. Damaged, inaccessible, or unexpectedly grouped sources can interfere with the intended album result.

4.1 Build a Temporary Album Playlist

Create a new temporary playlist instead of converting directly from a large mixed playlist, search result, smart playlist, or Music Library view. Add the album's local files, remove duplicates, and arrange the final order manually.

A Music Library rescan can help when the library points to moved or renamed files, but it is not required for ordinary local conversion. Confirm that each playlist entry resolves to a real file by opening its file information and checking the path. A stale library entry may still display stored metadata even though its underlying file is unavailable.

4.2 Inspect Track and Album Information

Open AIMP's file information or tag editor and check the title, track number, album, and artist fields. Embedded artwork is not normally required to create a CUE sheet, so missing cover art alone should not prevent generation. Focus on whether the converter can read every source and identify a sensible track order.

If the album uses a naming template based on tags, missing album or title fields can produce confusing output names. For diagnosis, use a fixed output name. After CUE creation works, return to a tag-based template.

4.3 Exclude Unsupported or Unstable Sources

Do not use live radio, changing podcast feeds, streaming URLs, or cloud-only references as the first inputs for a combined album conversion. Such entries may not behave like complete local files with stable durations. Download or copy legitimate source files locally when the service and your access rights allow it, then test those local files.

Also verify source quality. Each track should play from beginning to end without decoder errors, abrupt truncation, or repeated network interruptions. If one file is damaged, remove it temporarily and repeat the test with known-good files.

Success looks like this: the reduced, ordered playlist converts into one playable file, and its CUE sheet loads with the expected number of entries.

5. Rule Out Plugins, Skins, and Profile Problems

A custom skin generally changes presentation rather than conversion logic, but it can make options difficult to locate or obscure their current state. Third-party decoder or encoder plugins can matter when the problem occurs only with one format.

5.1 Return to a Standard Interface for Testing

Switch temporarily to a standard AIMP skin, reopen the audio converter, and verify the output mode and CUE option. This is not a claim that the skin damaged conversion. It is a visibility test that ensures the relevant controls are available and readable.

If conversion succeeds after the switch, repeat it once with the original skin. If it still succeeds, the earlier problem was probably an overlooked setting rather than the skin itself.

5.2 Compare Formats Without Installing Codec Packs

Use formats already supported by your AIMP installation. If a WAV single-output test creates a CUE sheet but a specific encoder does not, the issue is likely tied to that output format, encoder configuration, or plugin. Do not install a general codec pack as a CUE-generation fix. CUE creation is a converter workflow feature, not an audio-device codec problem.

Check AIMP's installed plugins and restore any required built-in component that was intentionally disabled. If a third-party encoder is involved, repeat the test with a built-in supported output format. Change only one variable at a time.

5.3 Use a Temporary Clean Configuration

If every correct single-output test fails, use AIMP's portable capability or another clean temporary profile where appropriate. Add no skins or third-party plugins. Run the same two-track local test with a writable local destination.

Success looks like this: the clean environment produces the combined file and CUE sheet. That result points to a setting or plugin in the regular profile. Compare converter settings rather than immediately deleting playlists or reinstalling everything.

6. Understand What Android Can and Cannot Fix

AIMP for Android supports CUE sheets for playback, but the Windows Audio Converter is the relevant tool for combining multiple sources and generating a new CUE sheet. If you expected the Android player to expose the same converter option, move the source files to a Windows computer and create the album image and CUE there.

6.1 Grant Full Folder Access for Existing CUE Files

Android storage restrictions can prevent AIMP from seeing an existing CUE sheet even when it can see the associated audio file. In AIMP's file browser, grant access to the specific folder containing both files. Keep the audio and CUE sheet together unless the CUE's file reference deliberately points elsewhere.

After copying a Windows-generated result to Android, verify that:

• The combined audio file and CUE sheet are in the same accessible folder.
• AIMP has full access to that folder, not audio-only visibility.
• The filename referenced inside the CUE matches the audio filename.
• Neither file was renamed independently after transfer.
• The transfer completed before the files were added to a playlist.

Battery restrictions, Bluetooth profiles, output-device modes, and audio focus can affect playback behavior, but they do not cause the Windows converter to omit a CUE file. Do not change them for this specific generation symptom.

Success looks like this: selecting the CUE sheet on Android opens its individual track entries while playback reads from the combined audio file.

7. Run a Clean Temporary Test Before Reinstalling

Reinstallation is rarely the best first response because it can leave the same profile and converter settings in place. Before reinstalling, repeat one controlled test:

1. Use two short copied local tracks.
2. Place them in the intended order.
3. Select an all-sources-to-one-result or suitable single-folder-to-one-result mode.
4. Enable CUE-sheet generation.
5. Use a short fixed output name.
6. Choose a new writable local folder.
7. Convert to a built-in supported format.
8. Check for one audio file and one matching CUE file.

If this test works, do not reinstall. Add the original album while retaining the working mode and destination. If it fails only after adding a particular track, folder template, network source, or encoder, you have identified the variable to investigate.

If the clean test fails in both your normal profile and a clean temporary configuration, record the exact mode, source formats, output format, destination type, and visible result. That information is more useful for AIMP support than a general report that AIMP is not working.

8. Quick Fix Checklist

• Use AIMP for Windows for converter-based CUE generation.
• Select a conversion mode that creates one result from multiple album tracks.
• Enable the CUE-sheet option associated with that mode.
• Keep only one album in the converter during diagnosis.
• Arrange source tracks in the correct running order.
• Test with two short copied local files.
• Use a new writable local destination folder.
• Choose a short fixed output name and show file extensions.
• Look for a matching audio file and .cue file.
• Test a built-in output format before blaming an encoder plugin.
• Grant Android full folder access when opening an existing CUE sheet.
• Stop changing settings as soon as the controlled test succeeds.

9. Frequently Asked Questions

9.1 Why Did AIMP Create Separate Tracks but No CUE File?

You probably selected a one-source-to-one-result conversion mode. That mode creates an individual output for each input and does not need a CUE sheet to divide one combined file. Select a supported single-output mode and enable CUE generation.

9.2 Does the Output Format Determine Whether AIMP Creates a CUE?

Not by itself. The conversion mode and CUE option are the primary controls. The encoder still matters because AIMP must successfully create the combined audio file, but choosing FLAC, WAV, or another format does not automatically request a CUE sheet.

9.3 Can AIMP for Android Generate the Same CUE File?

The Android application can use CUE sheets for playback, but the desktop Audio Converter workflow described here belongs to AIMP for Windows. Generate the combined album and CUE on Windows, transfer both files, and grant Android access to their folder.

9.4 Why Can Android See the Audio File but Not Its CUE Sheet?

The folder may have restricted, audio-only access. CUE sheets are not audio files, so Android storage rules can hide them. Grant AIMP full access to the specific folder and then add or reopen the CUE sheet.

9.5 Should I Reinstall AIMP When CUE Generation Fails?

Not until a two-track local test fails with the correct single-output mode, enabled CUE option, fixed filename, writable folder, built-in format, and clean temporary profile. If the controlled test succeeds, reinstalling will not address the album-specific cause.

9.6 How Do I Know the Problem Is Fixed?

The output folder should contain one combined audio file and one similarly named CUE file. Opening the CUE in AIMP should show the expected track count and order, and selecting a track should play the correct section of the combined file. Once those conditions are met, stop changing settings and preserve the working converter configuration.