AIMP Audio Converter ReplayGain Not Applied: How to Fix It

When the AIMP audio converter ReplayGain is not applied as expected, the problem usually falls into one of four categories: ReplayGain was never analyzed, the converter was configured for a different type of normalization, the target file could not store the expected tags, or the tags exist but playback is not using them. The first step is therefore to decide what you expected AIMP to change. ReplayGain metadata and permanently normalized audio are not the same thing.

This guide focuses specifically on converter normalization and ReplayGain. It begins with a controlled test, then covers analysis, track and album gain, converter settings, output tags, playback configuration, Windows access, Android storage, and clean-profile testing. Stop troubleshooting as soon as the test output shows the intended tags or produces the intended playback level.

1. Confirm the Symptom With a Small Safe Test

Do not begin by reconverting an entire music library. Choose two local files that play correctly and have noticeably different perceived loudness. Copy them into a temporary folder so the original files remain untouched.

1. Add only the copied files to AIMP on Windows.
2. Open AIMP's Tag Editor and run ReplayGain analysis on both files.
3. Choose track analysis for a mixed-song test, or album analysis if the files belong to the same album.
4. Save the calculated information if your workflow requires tags on the source files.
5. Open Audio Converter and convert the copies into a new empty output folder.
6. Inspect the converted files before adding other variables.

A successful test has a clear, measurable result. Either the converted files contain ReplayGain fields, or the audio signal was adjusted during conversion and sounds consistently changed even in a player that ignores ReplayGain tags. Those are separate outcomes, so determine which one you need.

1.1 ReplayGain Metadata Versus Audible Normalization

ReplayGain analysis normally calculates recommended gain and peak information. A compatible player reads those values and adjusts playback volume. The audio samples themselves may remain unchanged. Consequently, opening the file in an editor or comparing its waveform may show no permanent amplitude change.

Converter normalization can instead modify the signal while encoding. That makes the change audible on devices that do not understand ReplayGain metadata, but it creates a new file whose audio has been altered. If you expected permanently changed loudness but selected a tag-oriented workflow, AIMP may be working correctly.

Success for a metadata workflow means the output contains valid gain fields and a ReplayGain-enabled player reacts to them. Success for an audio-normalization workflow means the encoded signal has changed appropriately. Once the result matches your intended workflow, stop changing unrelated player settings.

2. Check ReplayGain Analysis Before Conversion

A common cause of AIMP audio converter ReplayGain not being applied is assuming the converter will automatically reuse values previously calculated elsewhere. Treat analysis and conversion as separate stages unless the active converter option explicitly performs the required calculation or normalization.

In AIMP for Windows, open the main menu, go to Utilities, and launch Tag Editor. Add the test files, select them, and use the ReplayGain analysis command. Review the results before saving. If the analysis produces plausible gain and peak values, the source files are readable and the analysis stage is functioning.

If no values appear, confirm that you selected real local audio files rather than playlist references, CUE-based virtual tracks, unavailable network items, or radio URLs. A live stream does not have a fixed, complete program that can be analyzed like a local song.

2.1 Choose Track Gain or Album Gain Deliberately

Track gain treats every song independently. It is appropriate for shuffled playlists, compilations, podcast episodes, or a collection assembled from unrelated releases. Each file receives an adjustment intended to bring its perceived loudness toward the reference level.

Album gain analyzes a group while preserving intentional loudness differences between tracks. It is generally preferable for complete albums, live recordings, classical works, and gapless releases. A quiet interlude should not necessarily become as loud as the album's main track.

If you analyze files as an album but configure playback to use track values, the listening result may differ from what you expected. The reverse is also true. For troubleshooting, use track gain on two unrelated test songs because the result is easier to hear and verify. Return to album gain only after the basic process works.

2.2 Do Not Confuse Peak Normalization With ReplayGain

Peak normalization works from the highest signal peak. ReplayGain estimates perceived loudness. Two tracks can have similar peaks while sounding very different in average loudness, so peak normalization is not a substitute for ReplayGain.

Check the converter's volume or normalization selection carefully. If you need perceived-loudness matching, choose the ReplayGain-related method. If you choose peak normalization, the converter may complete normally without producing the loudness relationship you expected.

3. Verify the Converter Options and Output Format

Open AIMP Audio Converter and review the complete job before starting it. Confirm the selected files, output format, output folder, encoding mode, naming template, tag-copying options, and volume-normalization setting. A saved preset can preserve an old choice, so do not assume that the visible codec alone describes the full job.

Run the temporary test with one source file producing one output file. Avoid combined-file modes, CUE generation, source deletion, automatic moves, and complex folder templates until ReplayGain behavior is confirmed. These options are useful, but they make it harder to determine which output belongs to which source.

3.1 Confirm What the Converter Should Do With Existing Gain Values

If the source already contains ReplayGain information, do not assume the converter will copy those values unchanged. A conversion can change the codec, sample representation, peaks, and possibly the measured result. Depending on the selected process, the converter may calculate new values rather than inherit the source tags.

For the safest workflow, analyze the final converted files after encoding when accurate output metadata is the priority. This ensures that the values describe the files you will actually play. If you need the converter to alter the signal, enable the corresponding normalization operation during conversion rather than relying only on preexisting tags.

Success means the final files either contain newly calculated values that describe their encoded audio or contain an intentional signal-level adjustment. Once one of these conditions is verified, there is no reason to reinstall AIMP.

3.2 Check Whether the Target Format Can Store the Tags

AIMP supports several tag systems, but different audio containers store metadata differently. MP3 commonly uses ID3 or APE tags, while FLAC, OGG, and Opus commonly use Vorbis-style comments. M4A uses its own metadata structure, and WAV tagging can be less consistently recognized across software.

Test with a well-supported format such as FLAC, MP3, OGG, or Opus. If ReplayGain appears in that output but not in your original target format, the problem is likely tag-writing or tag-reading compatibility rather than ReplayGain analysis.

Also remember that Windows File Explorer does not display every custom audio field. The absence of ReplayGain in Explorer is not proof that the tags are missing. Inspect the output with AIMP's Tag Editor or file information tools.

3.3 Inspect the Actual Output File

Open the converted file directly from its output folder. Do not inspect an older playlist entry with the same title, because the playlist may still point to the source file or a previous conversion.

Use file information or Tag Editor to check the file path, codec, modification time, file size, and ReplayGain fields. If the path is wrong, correct the output folder or naming template. If the path is right but the fields are absent, analyze the final files in Tag Editor and save them again.

4. Separate Converter Problems From Playback Problems

ReplayGain tags do nothing unless the playback application is configured to use them. A correctly tagged output can therefore sound unchanged when played with ReplayGain disabled, when a different normalization method takes priority, or when the device ignores the metadata.

In AIMP on Windows, review the volume and ReplayGain playback settings. Confirm that values from tags are enabled if you want AIMP to use stored analysis. Select the appropriate track or album behavior and avoid testing with several volume-processing methods enabled simultaneously.

Temporarily disable unrelated equalizer presets, DSP effects, automatic volume controls, crossfading, and third-party output processing. These do not normally erase ReplayGain tags, but they can make an audible comparison unreliable.

4.1 Refresh Playlists and the Music Library

A playlist or music-library entry can retain cached metadata after a file is rewritten. Remove only the temporary test entry, then add the converted file again from its exact output location. If you use the Music Library, rescan the relevant folder or refresh its information.

A skin controls presentation, not the underlying audio metadata. However, a custom skin may hide fields or place commands differently. Switch temporarily to a standard skin if you cannot locate file information or converter controls. If the tags appear under the standard interface, the file is fine and no audio repair is needed.

4.2 Test With ReplayGain Enabled and Disabled

Play the same converted file twice, once with tag-based ReplayGain enabled and once with it disabled. Keep the system and player volume controls fixed. A noticeable level difference indicates that the metadata exists and is being applied.

If there is no difference, inspect the tags directly. Missing fields indicate an analysis or writing issue. Present fields with no playback change indicate a playback configuration, tag interpretation, or device compatibility issue.

5. Check Windows, Storage, and Source Access

Permissions matter when AIMP must create output files or update tags. Save the test output to a normal user-owned folder such as a temporary folder under Music. Avoid protected application directories, read-only network shares, removable storage with a write-protect state, and cloud placeholders that have not been downloaded locally.

Confirm that the source file opens from beginning to end and that the output folder has enough free space. A damaged or incomplete source may play partially but fail during full-file analysis. If AIMP reports a conversion error, retry with a known-good local file before blaming ReplayGain.

5.1 Network, Cloud, WebDAV, and Samba Sources

Copy one affected network or cloud file to local storage and repeat the test. This isolates ReplayGain processing from expired credentials, intermittent Wi-Fi, WebDAV timeouts, unavailable Samba shares, and cloud files that are only online placeholders.

If the local copy works, restore network access before continuing. Reconnect the account or share, confirm that AIMP can read the complete source, and write the output to a local folder. Do not troubleshoot metadata while the source connection is unstable.

5.2 Output Device Modes and Bluetooth

DirectSound, WASAPI, ASIO, Bluetooth profiles, and device-level loudness features can affect what you hear, but they do not normally determine whether ReplayGain tags were written. Inspect the tags first. Change the output method only if the metadata is present and the audible test remains inconsistent.

For Bluetooth testing, use the normal high-quality media playback profile rather than a call or headset profile. Disable temporary device-level volume normalization if it masks differences. Restore your preferred output configuration after confirming AIMP's behavior.

6. Understand the Android Part of the Workflow

AIMP for Android is primarily a player, while the desktop edition provides the Audio Converter and Tag Editor workflow discussed here. If files were converted on Windows and then copied to Android, troubleshoot conversion on Windows and playback on Android as two separate stages.

First verify the converted file and its tags on Windows. Then copy that exact file to Android, grant AIMP access to its folder, add it to a fresh playlist, and enable the relevant ReplayGain playback behavior. If the file works on Windows but not Android, reconversion is unlikely to help.

6.1 Android Storage and Battery Access

Use Android's folder-access prompt to grant AIMP access to the music location. If the file is on an SD card, confirm that the selected directory includes it. Remove and re-add the test file after changing access so AIMP does not keep an unavailable playlist reference.

Battery restrictions are more relevant when playback stops, scanning is interrupted, or network audio loses access in the background. They do not create ReplayGain tags. Relax battery restrictions only when the symptom includes interrupted scanning or playback, and do not change unrelated security settings.

For Samba or other network playback, verify credentials and test the same file from local Android storage. Internet radio, podcasts, and remote URLs may supply changing streams and metadata, so they are unsuitable for testing whether a converted local file contains ReplayGain information.

7. Use a Clean Temporary Test Before Reinstalling

If the controlled test still fails, create a temporary clean AIMP profile or use a portable test installation where appropriate. Keep the existing profile and playlists intact. Add one known-good local file, analyze it, convert it into a new local folder, and inspect the output without installing skins or third-party plugins.

This test identifies whether the cause is a saved converter preset, plugin, profile setting, stale playlist record, or the file itself. Add custom components back one at a time. Stop when the problem returns, because the last restored component or setting is the strongest lead.

Review the converter's status and error messages after each test. If a specific encoder fails, try another built-in target format using the same source. Success with one format and failure with another points to an encoder or metadata-container issue, not a general AIMP audio player issue.

Reinstallation should be a late step. Reinstalling without testing a clean profile may preserve the same settings and provide no useful evidence. Do not delete playlists, source files, or your entire music-library database to solve a two-file conversion problem.

8. Quick Fix Checklist

• Copy two known-good local files into a temporary test folder.
• Decide whether you need ReplayGain tags or permanently changed audio.
• Run ReplayGain analysis before conversion when using a metadata workflow.
• Use track gain for unrelated songs and album gain for complete releases.
• Select ReplayGain rather than peak normalization when matching perceived loudness.
• Check the converter's saved preset and volume-normalization option.
• Convert one source into one output file in a new local folder.
• Inspect the actual output with AIMP Tag Editor or file information.
• Do not rely only on Windows File Explorer to display ReplayGain fields.
• Analyze the final converted files if source values were not inherited.
• Enable tag-based ReplayGain during playback when testing metadata.
• Refresh playlist entries and rescan the relevant Music Library folder.
• Test a common target format to isolate tag-container compatibility.
• Copy network or cloud sources locally before diagnosing the converter.
• Use a clean temporary profile before reinstalling or deleting data.

9. Frequently Asked Questions

9.1 Why Are ReplayGain Tags Present but the File Sounds Unchanged?

ReplayGain metadata requires a player that reads and applies it. Enable tag-based ReplayGain in AIMP and select the intended track or album mode. If you need consistent loudness on hardware that ignores ReplayGain, use an intentional converter normalization process that adjusts the encoded audio.

9.2 Should I Analyze ReplayGain Before or After Conversion?

Analyze before conversion when your chosen workflow explicitly uses those source values. For the most accurate metadata describing the final encoded files, analyze after conversion. Post-conversion analysis also avoids uncertainty about whether existing values were copied, discarded, or recalculated.

9.3 Why Does Album Gain Sound Less Even Than Track Gain?

Album gain preserves relative differences within an album. A quiet introduction remains quieter than a loud main track. Track gain adjusts each song independently, which is usually more suitable for shuffle playback and mixed playlists.

9.4 Does Normalizing During Conversion Write ReplayGain Tags?

Not necessarily. Signal normalization and writing ReplayGain metadata are different operations. Inspect the output tags and compare playback with ReplayGain disabled. If the audio remains changed when metadata processing is off, the signal itself was adjusted.

9.5 Why Does AIMP on Android Behave Differently?

The Windows application handles the converter and tag-analysis workflow, while Android consumes the resulting files for playback. Confirm the output on Windows first, then check Android folder access, playlist refresh, ReplayGain playback settings, and whether the selected format's metadata is recognized.

9.6 When Should I Stop Troubleshooting?

Stop when the final output contains the expected track or album gain fields and AIMP changes playback when ReplayGain is enabled, or when conversion produces the intended permanent level adjustment. At that point, unrelated skins, radio settings, network credentials, and device controls do not need further changes.