When music streaming volume changes between songs, compare the same two tracks at the same sections and output level. Then control loudness normalization, album-versus-shuffle behavior, client, EQ, spatial audio, device processing, and volume limits one variable at a time. Different masters can remain perceptually different even when normalization is working; network speed is rarely the cause.

Key Takeaways

Save one repeatable loud/quiet track pair and compare equivalent sections, not a quiet intro with a loud chorus.

Spotify says audio normalization balances soft and loud songs, with settings that vary by device.［1］

Apple Sound Check adjusts playback loudness between songs.［2］

Album, shuffle, web, phone, receiver, EQ, and spatial modes can follow different processing paths.

Normalization targets perceived loudness; it does not erase musical dynamics or make every peak identical.

The streaming troubleshooting hub covers broader playback symptoms. This guide stays with song-to-song level, not crossfade, gapless transitions, or audio/video timing.

1. Can one track pair reproduce music streaming volume changes between songs?

Choose two legitimately streamed tracks that reliably sound different. Note the exact release, album, remaster label, track version, timestamp, and whether playback starts in a verse, chorus, live introduction, or silence. Compare similar musical sections for at least 20 seconds without moving the device volume control. Do not judge only from the first transient.

Save the pair in a small private test playlist in a fixed order. Disable shuffle for the baseline and replay it on the same output. A live recording, classical movement, podcast insert, remaster, explicit/clean edition, or music video may have intentionally different dynamics or a different master. Confirm that both items are music tracks from the expected release.

Record whether the change is repeatable, which direction it goes, and whether the device volume indicator moves. If the on-screen value changes, investigate automation or hardware controls. If the value stays fixed but perceived loudness changes, normalization, mastering, and signal processing are more likely.

2. Is loudness normalization or Sound Check enabled consistently?

Find the service's playback setting called Normalize volume, Audio normalization, Loudness normalization, or Sound Check. Spotify says normalization balances soft and loud songs and documents different setting availability across mobile, tablet, and desktop.［1］ Apple says Sound Check adjusts loudness between songs.［2］ Toggle the relevant control only after saving the original state.

Restart playback and compare the fixed pair again. Some clients apply the setting when a new track begins, so restart both tracks rather than seeking within one. If the service provides target levels such as quiet, normal, or loud, begin with its default. Louder targets can interact with limiting and reduce headroom on energetic masters.

Do not stack every available normalizer during diagnosis. A phone, desktop player, receiver, and smart speaker may each have its own feature. Enable one known layer, disable duplicate processing where safe, and document the result. If the setting is absent on one device, that difference itself can explain inconsistent playback.

3. Does album playback behave differently from shuffle or playlists?

Play the pair inside its original album, then in the test playlist. Album-aware normalization may preserve intentional relationships between tracks, while shuffle or mixed playlists may treat each track independently. A quiet prelude followed by a loud movement can therefore remain different in album context even though a mixed playlist sounds more even.

Check whether gapless playback, crossfade, automix, or DJ features are active, but do not treat them as loudness controls. They can overlap sections and change the perceived transition without changing the stored level. Use the separate gapless and crossfade guide if timing between tracks is the actual symptom.

Repeat without shuffle because a changing order makes comparisons harder. Do not replace an album master with a compilation copy midway through the test. If only one release remains unusually loud or quiet across clients, report the exact release metadata to the service; a catalog or master issue cannot be fixed by global device volume.

4. Do the app, web player, download, and third-party device agree?

Compare the current official mobile or desktop app with the official web player, then one supported speaker or receiver integration. Keep account, track pair, output, and volume fixed. Check normalization separately on every client; an account preference may not sync, and Spotify explicitly notes device-dependent availability.［1］

Downloaded and streamed copies may use different quality settings or stale cached metadata. Remove only the two test downloads through the app and download them again if the service permits. Do not clear an entire library or use an unofficial downloader. Confirm that the web player is not being processed by a browser audio extension.

For a third-party speaker, inspect both the service integration and the device's own loudness settings. If the phone is merely a remote, its local EQ may not affect the speaker. If Bluetooth sends the audio, the phone's processing may apply. State the route precisely instead of concluding that the account is inconsistent.

5. Are EQ, spatial audio, Atmos, or enhancement effects changing perception?

Temporarily choose a flat EQ and disable bass boost, loudness, night mode, dialogue enhancement, headphone accommodation, volume levelling, and vendor sound effects. Change only documented consumer settings and save their previous values. Strong bass or treble boosts can make some masters seem louder and may trigger a limiter on others.

Spatial audio or Dolby Atmos versions can have different mixes from stereo versions. Verify which badge or format is active for each track and whether automatic switching occurs. Compare both tracks in stereo first. If the problem follows Atmos availability, use the Dolby Atmos troubleshooting guide rather than increasing every level.

Head tracking and personalized hearing profiles also change spatial balance. Turn them off for the controlled comparison, not permanently. Never raise headphone output aggressively to compensate for a quiet master; the next normal track can become dangerously loud.

6. Does the output device apply its own volume processing?

Test the device's built-in speaker or a second known output at a safe level. Bluetooth headphones, USB interfaces, smart speakers, televisions, AV receivers, car systems, and hearing devices can apply independent EQ, loudness, dynamic-range compression, or source-specific trim. A receiver may remember different levels for stereo and multichannel input.

Inspect physical buttons and touch controls for accidental changes. Disable automatic volume, adaptive sound, night listening, or loudness compensation for one test if the manual allows it. Avoid factory resets and hidden service menus. If one output alone shows the jump, update its firmware through the maker's official process and document the model and mode.

When Bluetooth is involved, compare a wired or built-in output without changing the track order. Re-pairing is useful only if control values are visibly desynchronized; it does not rewrite mastering. Protect hearing by starting low and never using a known loud track as a surprise test.

7. Are volume limits, hearing safety, or automation changing the level?

Review headphone safety, maximum-volume limits, parental controls, accessibility audio settings, sleep timers, alarms, routines, car speed compensation, and smart-home automations. A limiter may reduce a loud section without raising quiet songs, while an automation can visibly change the system slider when a device connects or a time condition occurs.

Keep safety features enabled unless you understand the consequence. For diagnosis, note when they activate and compare at a moderate level rather than disabling protection. Managed devices may enforce a limit; ask the administrator rather than bypassing it. Check whether another household member or voice assistant controls a shared speaker.

If the level fades within a track rather than changing at track boundaries, observe battery state, calls, notifications, navigation prompts, and Bluetooth route changes. That is a different symptom. Record timestamps and the on-screen volume before and after so support can distinguish content loudness from system gain.

8. What should you report when normalization still looks wrong?

Provide the exact service, account tier if relevant, app and operating-system versions, client type, output route, normalization state and target, EQ and spatial format, fixed device volume, and the two track URLs or catalog identifiers. Include release, version, timestamps, playlist versus album context, and whether another official client agrees. Do not send account credentials or listening-history exports.

ITU-R BS.1770 defines algorithms for measuring program loudness and true-peak audio level.［3］ It helps explain how services can base normalization on measured loudness, but a consumer should not claim a standards violation from a phone meter or subjective comparison. Ask the service to inspect its catalog and loudness metadata.

Compare the same tracks with normalization, app EQ, spatial audio and hardware processing controlled one at a time, while preserving hearing-safety limits. Give the music service or device maker a repeatable example of the volume difference.

Summary

Use a fixed pair of tracks and compare equivalent sections at one safe device level. Align normalization settings, then isolate album context, shuffle, client, downloaded copy, EQ, spatial format, output device, and safety automation. Expect normalization to reduce perceived differences, not erase artistic dynamics. Escalate exact catalog and route evidence instead of repeatedly changing the master volume.

FAQ

Why are some songs much louder than others?

Different releases and masters can target different dynamics and perceived loudness. Playback normalization may reduce, but not eliminate, those differences.

What does Spotify audio normalization do?

Spotify says it balances soft and loud songs for a more uniform listening experience. Availability and controls vary by device.［1］

What is Apple Sound Check?

Apple describes Sound Check as adjusting loudness between songs.［2］ Check it separately on each playback device.

Should normalization make every peak identical?

No. It targets perceived program loudness; musical dynamics, short peaks, frequency balance, and different mixes can remain distinct.

Why is an album different from the same songs on shuffle?

Album-aware processing may preserve relationships intended across an album, while shuffled tracks may be handled individually.

Can EQ make one song seem louder?

Yes. Bass, treble, loudness, or enhancement boosts interact differently with each master and can trigger limiting.

Why is volume different on a smart speaker and phone?

They may use separate normalization support, EQ, spatial formats, volume levelling, and output gain. Compare each route with the same pair.

Can a VPN equalize music volume?

No. Song masters, loudness metadata, player settings, and device processing determine the result, not the network exit route.

Sources:

Spotify Support - Audio normalization — https://support.spotify.com/gm/article/audio-normalization/
Apple Support - Change the way music sounds on iPhone — https://support.apple.com/guide/iphone/change-the-way-music-sounds-iph5643d2c85/ios
ITU-R - Recommendation BS.1770-5 — https://www.itu.int/rec/R-REC-BS.1770-5-202311-I/en

Sources checked 6 September 2026.

Related Articles:

Music Streaming Volume Changes Between Songs: What to Check