How to Master a Suno Song for Spotify, Apple Music, and Streaming

You finish your Suno song, prepare it for release, and then run into one of the most confusing parts of modern mastering: streaming loudness. Should you master the track to -14 LUFS because Spotify uses loudness normalization? Should Apple Music receive a different master? Do you need another version for YouTube? How much true-peak headroom should you leave, and what happens if your song is considerably louder than the normalization reference?

The answers are more nuanced than many online mastering guides suggest. I have been mixing and mastering music for more than 15 years, and I do not master a song by choosing a streaming platform first and forcing the audio toward one number. I master the music first, then make sure the finished master behaves properly when streaming services normalize and encode it.

Streaming Mastering Is Not the Same as Mastering to -14 LUFS

This is the first misunderstanding I would clear up. Spotify currently uses -14 LUFS as the loudness reference for its Normal playback setting. If your master is louder, Spotify generally turns playback down. If the track is quieter, Spotify may increase playback level when sufficient headroom exists.

That describes playback normalization. It does not mean Spotify rejects masters louder than -14 LUFS, and it does not mean every song should be limited until the integrated loudness meter reads exactly -14.0.

A streaming platform and a mastering engineer solve different problems. The platform wants listeners to move between songs without extreme volume jumps.

The mastering engineer wants the song to sound balanced, controlled, musical, and appropriate for its genre. Those goals interact, but they are not identical. I cover this distinction in more detail in my guide to mastering at -14 LUFS.

What Spotify Actually Does to Your Master

Spotify measures the loudness of the uploaded track and applies gain compensation during playback.

At the Normal setting, Spotify currently targets -14 LUFS according to the ITU-R BS.1770 measurement standard.

Imagine that your Suno master measures -9 LUFS integrated.

Spotify does not need to compress or limit that master simply because it is louder than -14 LUFS. Under Normal playback, it can reduce the playback gain by roughly 5 dB.

Your mastering dynamics remain part of the file. Spotify simply plays the song at a lower level.

This is important because it means that pushing a master from -10 LUFS to -7 LUFS does not automatically make it sound louder to someone listening with normalization enabled.

You may simply create a denser, more distorted, or less dynamic master that Spotify later turns down further.

Spotify Also Has Different Playback Settings

Spotify currently offers several normalization levels to Premium users.

Normal playback targets -14 LUFS, Quiet targets -19 LUFS, and Loud targets -11 LUFS. Spotify uses additional limiting for the Loud setting when necessary.

This is another reason I do not treat one LUFS number as an absolute mastering law.

You cannot control every listener’s playback configuration.

You can control the quality of the master you deliver.

Does Spotify Recommend -14 LUFS?

Yes.

Spotify’s current artist guidance recommends targeting -14 LUFS integrated and keeping the master below -1 dBTP when optimizing specifically for Spotify.

Spotify also gives separate guidance for louder masters. If the master exceeds -14 LUFS integrated, Spotify recommends keeping the true peak below -2 dBTP to reduce the risk of additional distortion during encoding.

I take that guidance seriously. I simply distinguish a platform recommendation from a universal mastering target.

There are many professionally released tracks mastered louder than -14 LUFS. The question is not whether a louder master is allowed. The question is whether the additional loudness genuinely improves the music after you account for playback normalization.

How Loud Should a Suno Song Be for Spotify?

I would not choose a number until I hear the song.

A dense electronic production with controlled transients may tolerate significantly more limiting than an acoustic ballad with large dynamic contrasts.

A powerful rock track may feel better with greater average density than an ambient composition where dynamics create most of the emotional impact.

That means two Suno tracks can require completely different mastering strategies even though both are going to Spotify.

When deciding how far to push a master, I listen for:

• loss of drum impact,
• vocal harshness,
• low-end distortion,
• pumping,
• loss of depth,
• increased AI-generated artifacts,
• and listener fatigue.

When another decibel of loudness makes the track worse, I stop. The number on the meter does not get the final vote.

What About Apple Music?

Apple Music also uses loudness normalization through a feature called Sound Check.

Apple describes Sound Check as a system that adjusts the loudness between songs so they play at a more consistent volume.

What Apple does not do in its public consumer guidance is tell mastering engineers that every stereo master must hit one specific integrated LUFS number.

That difference is worth understanding. I would not create a separate Apple Music master simply because I saw an unofficial website claim that Apple wants one exact LUFS value.

For a conventional stereo release, I would create one strong lossless master that translates correctly, controls peaks appropriately, and survives normalization well.

Apple Digital Masters Are a Different Subject

Apple Digital Masters have additional source requirements. Apple currently requires qualifying Apple Digital Masters sources to be delivered at 24-bit resolution using an approved format, with accepted sample rates ranging from 44.1 kHz through 192 kHz.

That does not mean every independent Apple Music release automatically needs a separate Apple Digital Masters file. It is a specific delivery program with its own technical workflow.

Do You Need a Different Master for Spotify and Apple Music?

In most independent release situations, no. I normally prefer one excellent stereo master over several nearly identical masters built around different normalization references.

A single master also makes release management easier. You keep one approved version, your distributor delivers it, and each platform handles the playback format and normalization according to its own system.

There are exceptions. You may create different masters for vinyl, CD, club playback, broadcast, Dolby Atmos, or other specialized delivery formats.

But creating “Spotify -14 LUFS,” “Apple -16 LUFS,” and “YouTube -14 LUFS” versions of the same stereo single usually adds complexity without solving an important musical problem.

What About YouTube?

YouTube also processes uploaded audio, but I would again avoid mastering toward an unofficial magic LUFS number.

For conventional video uploads, YouTube currently recommends high-quality audio, with 48 kHz as its preferred sample rate for the video upload workflow.

YouTube then creates its own playback encodes. If you are uploading your Suno song as a video, give YouTube a high-quality source rather than deliberately compressing it into a low-bitrate MP3 first.

YouTube itself advises uploading the highest-quality audio possible. If you release through a music distributor to YouTube Music, follow the distributor’s delivery requirements rather than assuming the same specifications as a manually uploaded YouTube video.

Start With the Best Suno Source Available

Streaming mastering begins with the source file. If you have the original WAV, use it. I would not intentionally master the MP3 when the WAV exists.

The reason is straightforward. Streaming services will create their own delivery encodes later, so there is little benefit in adding another lossy encoding stage before mastering.

If you are unsure which format to use, I have a dedicated guide comparing Suno WAV vs MP3 for mastering.

If MP3 is genuinely the only source you have, you can still master it. I simply become more conservative about processing that may exaggerate existing encoding artifacts.

Fix the Sound Before You Fix the Loudness

This is probably the most important practical advice in this article. Do not load a limiter onto the Suno export and start pushing toward a target LUFS number before fixing obvious tonal or dynamic problems.

If the track has excessive low-mid energy, limiting can make that congestion feel even denser. If the vocal already sounds brittle, pushing the master harder can make the upper mids more tiring.

If the drums already have weak transients, aggressive limiting can flatten them further.

Correct the master first. Then decide how loud it can become. My broader guide on making Suno songs sound professional explains how I separate source, mix, and mastering problems before processing the final file.

Do Not Assume Every Suno Track Needs the Same EQ

I would avoid fixed recipes such as:

• always cut 300 Hz,
• always reduce 4 kHz,
• always boost the air band,
• and always widen the stereo image.

Those moves can solve real problems on the right track.

They can also damage a track that did not have those problems.

I listen first, then use EQ, dynamic EQ, or resonance suppression only where the song actually needs it.

This becomes particularly important before streaming loudness processing because limiting tends to expose tonal problems that were easier to ignore at a lower level.

Understand LUFS Before You Chase It

LUFS measures perceived loudness over time rather than simply measuring the highest sample peak.

Integrated LUFS describes the average perceptual loudness across the measured program, while short-term and momentary measurements show shorter windows.

Two songs can reach the same peak level and still have very different integrated loudness.

A highly dynamic track can reach close to full scale while remaining relatively quiet overall. A heavily compressed track can maintain a much higher average loudness without producing higher sample peaks.

If you want a deeper technical explanation, read my guide to RMS and LUFS in audio mastering.

True Peak Matters as Much as LUFS

A master can remain below 0 dBFS on a conventional sample peak meter and still generate higher reconstructed peaks when converted or played back.

These inter-sample peaks become particularly relevant when streaming services create compressed delivery formats.

That is why I monitor true peak during final limiting.

Spotify currently recommends keeping a master optimized around -14 LUFS below -1 dBTP. For louder masters, Spotify recommends staying below -2 dBTP because hotter masters can produce additional distortion when encoded.

You do not necessarily need to treat those values as immutable laws for every platform, but true-peak management should absolutely be part of a streaming master.

Should You Use a -1 dBTP Ceiling?

A -1 dBTP ceiling is a sensible conservative starting point for many streaming masters.

It leaves some margin for encoding and playback reconstruction.

However, the exact ceiling should be considered alongside the loudness and source.

If you push the master substantially louder, leaving additional true-peak margin can be worthwhile.

If the song remains dynamic and relatively quiet, you may have plenty of natural peak margin without asking the limiter to do much at all.

The important point is to use a true-peak limiter or meter rather than assuming that a sample peak reading tells you everything.

Headroom Before Mastering vs True-Peak Headroom After Mastering

These concepts are often confused.

Premaster headroom refers to the level available before the mastering stage.

Final true-peak margin refers to the finished master’s peak behavior after mastering.

You do not need to artificially turn a clean premaster down to a magical number if it is not clipping and gives the mastering chain sufficient room to work.

Likewise, a final master with good premaster headroom can still be limited too close to 0 dBTP.

I explain the premaster side of this topic in my guide to headroom for mastering.

Do Not Let the Limiter Destroy the Suno Track

AI-generated audio can already arrive with dense dynamics.

This makes aggressive limiting particularly risky.

As you increase limiter gain, listen to what happens to:

• kick attack,
• snare impact,
• bass definition,
• vocal texture,
• cymbal harshness,
• reverb tails,
• and stereo depth.

If the track becomes smaller, harsher, or flatter while the meter gets louder, the limiter is not improving the music.

A good streaming master should remain musical after normalization turns it down.

Why a Louder Master Can Sound Worse After Normalization

Consider two versions of the same song.

Master A reaches -9 LUFS and retains strong transients.

Master B reaches -6 LUFS but requires much heavier limiting.

With normalization enabled, Spotify may turn Master B down roughly 3 dB more than Master A.

The listener no longer receives much of the loudness advantage that encouraged you to push the limiter harder.

What remains is the difference in dynamics, distortion, punch, and tone.

If Master B lost drum impact and became harsher, the extra loudness may have bought you nothing useful.

Does This Mean Loud Masters Are Bad?

No.

A loud master can sound excellent.

Genres such as modern pop, electronic music, hip-hop, metal, and other dense productions can support substantial average loudness when the mix is built for it.

The mistake is treating loudness as the goal instead of one characteristic of the finished record.

I have no problem delivering a loud master when the song benefits from it.

I simply do not sacrifice the record to reach a number that the streaming service may later normalize anyway.

Compare at Matched Loudness

This matters when choosing your final limiter settings.

Create one version with moderate limiting and another pushed harder.

Then reduce the playback level of the louder version until both sound approximately equal in perceived loudness.

Now compare them.

Which version has the stronger kick?

Which one has better vocal clarity?

Does the louder master become tiring?

Does the quieter master suddenly feel deeper and more open once the level difference disappears?

This is one of the reasons reference-track comparison works best when loudness is matched. I explain that process in my guide to using reference tracks in mixing and mastering.

Should You Master a Suno Album Differently From a Single?

Potentially, yes.

A single only needs to work as one record.

An EP or album also needs internal consistency.

You may have one dense electronic track, one quieter ballad, and one mid-tempo song. Forcing all three to the same integrated LUFS value can damage the natural relationship between them.

Spotify also treats albums differently in some playback contexts. It can normalize an album as a group so that intentional level relationships between tracks remain intact.

That means album mastering should consider the project as a whole, not only individual loudness numbers.

Do You Need a Separate Loud Master for Social Media?

Usually not as your primary release master.

Short-form platforms, social networks, and user-generated content systems may apply their own encoding and playback processing.

If you need a specialized promotional edit, create it from the high-quality master rather than compromising the main streaming master.

Keep one approved lossless master as your source of truth.

You can create shorter edits, video files, and compressed promotional versions from it later.

What File Should You Deliver?

For release, follow your distributor’s current technical specifications.

I generally prefer delivering the best lossless stereo master accepted by the distributor rather than creating a low-quality compressed version myself.

The distributor and streaming platforms can then create the delivery formats they require.

This also gives you a high-quality archival master for future releases, compilations, sync uses, and remastering.

Should Your Streaming Master Be 44.1 kHz or 48 kHz?

Do not change sample rate simply because a larger number appears more professional.

If your Suno source and mastering session are already working correctly at one sample rate, unnecessary conversion does not create additional musical information.

Follow the requirements of the final delivery workflow.

YouTube’s direct video upload guidance currently prefers 48 kHz audio, while music distributors may accept several standard sample rates for streaming delivery.

I cover the broader technical differences in my guide to 44.1 kHz vs 48 kHz for music production.

Should You Export a 24-Bit Master?

For a modern lossless master, 24-bit delivery is a sensible choice when your distributor accepts it.

It provides ample resolution and is also part of Apple’s current Apple Digital Masters source requirements.

Again, follow your distributor’s actual specification rather than converting files unnecessarily because a blog told you every platform requires the same format.

If you later need to reduce bit depth, use proper dithering where appropriate.

What About Mono Compatibility?

Streaming listeners do not all hear music through full stereo systems.

Phones, smart speakers, Bluetooth devices, televisions, and other playback systems can narrow or combine stereo information.

That makes mono compatibility particularly important for a wide Suno generation.

YouTube’s own troubleshooting guidance even points out that poor mono compatibility can cause stereo audio to lose quality or elements when played on some mobile devices.

I always check that important material survives when the master collapses toward mono.

More stereo width does not automatically mean a more professional master.

A Practical Suno Streaming Mastering Workflow

If I were preparing a Suno track for Spotify, Apple Music, YouTube, and other major streaming services, I would use this workflow:

1. Choose the strongest finished Suno generation.
2. Download the original WAV whenever available.
3. Keep an untouched copy of the source.
4. Fix arrangement or generation problems before mastering.
5. Determine whether the stereo mix is ready or whether stems are needed.
6. Correct tonal balance and unwanted resonances.
7. Control dynamics without removing unnecessary punch.
8. Check stereo width and mono compatibility.
9. Set final loudness according to the song.
10. Measure integrated LUFS, true peak, and peak behavior.
11. Compare different limiter settings at matched playback loudness.
12. Check the final master on several playback systems.
13. Export a high-quality lossless master that meets your distributor’s requirements.
14. Keep the final master archived.

This is essentially the same philosophy I use in my complete Suno mastering guide, with extra attention given to normalization, encoding, and delivery.

Common Suno Streaming Mastering Mistakes

Mastering Everything to Exactly -14 LUFS

This treats a playback reference as a creative rule.

Ignoring True Peak

A master can appear safe on a sample peak meter and still create reconstructed peaks that cause trouble after encoding.

Pushing the Limiter Because Commercial Tracks Look Louder

You may be comparing files without matching their playback levels.

Uploading an MP3 When a Lossless Master Exists

Let the distribution workflow handle encoding from the best source you have.

Trying to Fix Mix Problems With the Limiter

Loudness cannot solve a buried vocal or badly balanced bass.

Creating Separate Masters for Every Streaming Platform Without a Reason

One strong stereo master is normally more useful than several versions built around unofficial platform-specific LUFS targets.

Can Automatic Mastering Handle Streaming Loudness?

Yes.

Modern automated mastering systems can measure LUFS, true peak, tonal balance, dynamics, and many other technical characteristics very accurately.

They can also produce masters that meet sensible streaming specifications.

The difference is not whether software can measure -14 LUFS.

The difficult question is whether -14 LUFS is actually where this particular track sounds best.

That requires musical judgment.

I discuss that distinction in more detail in AI mastering vs human mastering for Suno.

When Professional Mastering Makes Sense

You do not need to hire a mastering engineer every time you generate a Suno idea.

If you are testing songs, posting demos, or comparing generations, a quick master may be enough.

Professional mastering becomes more valuable when you have chosen the track you genuinely want to release.

At that stage, you are no longer asking only how to make it louder.

You are asking whether the tonal balance is right, whether the bass translates, whether the vocal becomes tiring, whether the limiter is damaging the transients, and whether the final master survives real playback systems.

Those are listening decisions.

Want Me to Master Your Suno Track for Streaming?

If your song is ready for release, I offer professional Suno mastering by a real mastering engineer.

I personally listen to the track and make the mastering decisions rather than sending it through another automated mastering system.

The goal is not to force your song toward one LUFS number. I want the master to sound balanced, controlled, competitive, and appropriate for the music while remaining suitable for modern streaming delivery.

You can also request a free mastering demo using your own Suno track before deciding whether you want the complete master.

Final Thoughts

Streaming platforms have made loudness more complicated, but they have also removed some of the old pressure to make every master louder than everything around it.

Spotify’s -14 LUFS normalization reference is useful information.

It is not a replacement for mastering judgment.

Apple Music uses Sound Check to reduce disruptive loudness differences between songs, while YouTube and other platforms also process and encode audio for their own playback systems.

You cannot control every playback algorithm.

You can control the quality of the master you give them.

Start with the best Suno source available, solve tonal and dynamic problems before pushing loudness, manage true peaks, compare at matched level, and deliver a high-quality lossless master.

If the song still sounds better when you push it louder, push it. If another decibel makes it flatter, harsher, or smaller, stop.

The song should determine the master, not the normalization number.

Frequently Asked Questions