ERASYOpen App

AI Music

How to Master AI Music in 2026: Four Routes to a Release-Ready Track

By Eddie Mathews··12 min read
How to Master AI Music in 2026: Four Routes to a Release-Ready Track — Erasy

Your track sounds finished in the generator and then sits half a step behind everything else in the playlist. The usual advice is to master AI music to a platform loudness target, and the usual page gives you a table of targets for six platforms. We went and read what those six actually publish. One of them publishes a number.

So this is the version of the mastering guide that separates the documented from the repeated, and then walks the four routes people are actually using in 2026 — Suno’s own Remaster button, an LLM with a Python sandbox, a free meter you run yourself, and paying somebody. Every figure below was read at its source on 21 October 2026, and where a source says nothing, this page says that instead of filling the gap.

The short version

Spotify is the only major platform that publishes a mastering target — -14 dB integrated LUFS, true peak below -1 dBTP. Apple’s own guide has no LUFS figure in it at all; TIDAL’s and Deezer’s help centres return nothing for “loudness”.

Suno’s Remaster re-generates the song instead of mastering the file, so it is not route one for a track you already like.

Mastering does not change how a platform labels your release. YouTube’s own guidance puts automated AI mastering under “No Gen AI” — the generated audio underneath is what gets declared.

Why an AI export is not a master

A generator is solving for a convincing two-and-a-half minutes, not for a delivery spec. The file it hands back is a finished-sounding mix with none of the decisions a mastering pass exists to make, and the symptoms are consistent enough to list.

Why AI music needs mastering: off-spec loudness, inconsistent levels, and a thin and flat mix
The three problems a master fixes on an AI export.

Loudness is unpredictable from render to render, so an album assembled out of twelve generations steps up and down between tracks. Headroom is wherever the model left it, which matters because lossy encoding adds peaks that were not in your file. And the balance is a statistical average of the training material rather than a choice — loud in the middle, soft at the edges, with transients already squashed by whatever the model learned a mastered record sounds like.

That last one is why mastering an AI track is not the same job as mastering a mix. You are not adding the final 10% to something that was built with headroom; you are working on a file that has already been through something that behaves like a limiter, with no stems behind it unless you paid for them. Keep the goal modest: in spec, consistent, and undamaged.

Which loudness numbers are actually published

Every mastering guide in the search results carries the same table: Spotify -14, Apple -16, YouTube -14, Amazon -14, TIDAL -14, Deezer -15. We tried to source each cell from the platform itself. Here is what came back.

PlatformPublished for people making records?What the source actually saysChecked
SpotifyYesSpotify for Artists: target “-14dB integrated LUFS” and keep true peak “below -1dB TP”, or below -2dB if the master is louder than -14.21 Oct 2026
Apple MusicNoThe Apple Digital Masters guide contains no LUFS or LKFS value. It asks you to “leave at least 1 dB of headroom” and to master so the track “captures your intended sound, regardless of playback volume”. Sound Check sets level at playback, per track or per album.21 Oct 2026
YouTube / YouTube MusicNoNo loudness specification for music uploads in the help centre; playback is normalised, the figure is not documented for creators.21 Oct 2026
TIDALNoIts help centre search returns zero articles for “loudness” and zero for “normalization”.21 Oct 2026
DeezerNoZero articles for “loudness” in its help centre. The -15 figure circulating online traces to a forum post, not a specification.21 Oct 2026
Amazon MusicNoNo published mastering target found in Amazon Music for Artists.21 Oct 2026
Table of six streaming platforms and whether each publishes a mastering target for people making records: Spotify yes, at -14dB integrated LUFS with true peak below -1dB TP, highlighted; Apple Music no, its Apple Digital Masters guide contains no LUFS or LKFS value and asks only for at least 1 dB of headroom; YouTube and YouTube Music no, with no loudness specification for music uploads in the help centre; TIDAL no, its help centre returning zero articles for loudness and zero for normalization; Deezer no, with zero articles for loudness and the -15 figure tracing to a forum post; and Amazon Music no, with no published mastering target found
Every mastering guide carries the same six numbers. Only the first of them comes from the platform.

The difference matters more than it looks. A published target is a submission guideline you can master to; an undocumented one is a measurement of what a player did on the day somebody measured it. Those numbers are not useless — they are roughly right, and we keep the working set on our LUFS targets for Spotify and streaming page — but you should know which one you are obeying. Both ends of the table are one click away: read Spotify’s loudness normalisation page and then search Apple’s own Apple Digital Masters guide for the string “LUFS”. It is not in there.

Screenshot of Spotify for Artists' Loudness normalization on Spotify help page captured on 21 October 2026, stating that Spotify adjusts tracks to -14 dB LUFS according to the ITU 1770 standard, that normalization applies to all playback formats including lossless audio, and that the web player and third-party devices do not use it
The one published target, on the one platform that publishes it.

What normalisation does, and what it does not

Normalisation is a volume change, applied at playback, to the whole track. It is not processing. Nothing is compressed, nothing is re-balanced, and your file is not modified — the player simply decides how much gain to put in front of it.

Which means the thing people fear — “Spotify will crush my master” — is not what happens. What happens is subtler and worse: a track squashed to -7 LUFS gets turned down seven or eight dB to sit beside everything else, and arrives with all of its dynamic range already spent and none of the loudness it paid for. The master that was made quieter and cleaner arrives at the same level with its transients intact. That is the whole argument against chasing loudness on a streaming release, and it is why the limiter is the last place to look for impact.

The one asymmetry to know: platforms are cautious about turning quiet tracks up, because gain applied to a file that already peaks near zero would clip it. Spotify documents exactly that behaviour — a quiet track with little headroom gets only as much gain as its peaks allow. So a master at -20 LUFS does not reliably arrive at -14. Leaving real headroom is what lets the platform do its job.

Key-value panel on what loudness normalisation does: a track squashed to -7 LUFS is turned down seven or eight dB to sit beside everything else and arrives with its dynamic range already spent; a quieter, cleaner master arrives at the same level with its transients intact; and a master at -20 LUFS does not reliably arrive at -14, because platforms are cautious about turning quiet tracks up when gain on a file peaking near zero would clip it
Normalisation is a volume change at playback. Nothing is compressed and your file is not modified.

Four routes to a mastered AI track

Once you accept the generator will not do it, there are four things people actually do, and they are not interchangeable. They differ in what they change about the file and in what they can never change.

RouteWhat it changesWhat it cannot doWhat to check afterwards
Suno RemasterNothing about your file — it generates a new render of the song on a current modelPreserve the take you liked; raise the loudness of an existing exportWhether the new render is the same song you wanted
ChatGPT / an LLM sandboxReal DSP: gain, EQ, compression, limiting, loudness measurement, written as code and run on the fileHear the result; make a judgement call; know whether it helpedThe measured integrated loudness and true peak of the file it hands back
A meter plus ffmpeg or a DAWExactly what you tell it to, with a number on the before and the afterMake taste decisions for youNothing — the measurement is the output
A service, or a personA finished master; a person also makes judgements about the recordFix the arrangement or the performance underneathThat the return is in spec and that you can still hear the top end

Notice what the column headings do to the question. “Which is best” is unanswerable without the track in front of you. “Which one can do the thing I need” usually has one answer, and for a track you already like it is never the first row.

Route 1: Suno’s Remaster button

The name is the problem. In audio, remastering means going back to the source and preparing it again. Suno’s Remaster re-generates the song on a current model — it is a new performance of the same prompt and lyrics, not a new treatment of the file you downloaded. If what you liked was a particular vocal phrase or a particular drum fill, there is no guarantee it survives.

It is also metered. A remaster is a generation and a download, and downloads are the thing Suno counts. We went through the mechanics, the costs and the model-retirement catch in Suno Remaster: what it actually does to an old song, and the short version is that it is a good tool for the problem it solves — an old track rendered on a model that no longer exists — and the wrong tool for the problem people reach for it with, which is loudness.

The editing environment is no help here either: the reporting on Suno Studio 2.0 counts seven effects — compressor, convolution, delay, distortion, EQ, gate, reverb — with no limiter and no loudness meter. You cannot master inside a room with no meter in it.

Route 2: handing it to ChatGPT

This is the route that has arrived in the last few weeks, and it is worth being precise about, because two completely different things get described with the same sentence.

What the person doesWhat actually happensWhere it goes wrong
Describes the track and asks for mastering settingsThe model writes a plausible chain — EQ moves, compressor ratios, a limiter ceiling — from the description aloneIt has not heard the track. The advice is a genre average, and it will be stated with the same confidence whether or not it fits
Uploads the file and asks for it to be masteredCode runs in a sandbox: the audio is read as samples, filters and gain are applied, a new file comes back. This is real processingThe model still cannot hear the output. It reports success from the code completing, not from the result sounding right
Uploads the file and asks for it to be measuredA loudness and true-peak measurement, which is arithmetic and reliableVery little — this is the use that plays to the tool’s strengths

The second row is the one people argue about, and both sides are half right. It genuinely processes the file — a gain stage written in Python is as real as a gain stage in a DAW. But every judgement in mastering is a listening judgement, and that is the one faculty the sandbox does not have. The honest framing is that you are using a very fast assistant who writes competent DSP code and then describes the result from the log rather than the speakers.

Which makes it usable, with a rule: never accept a described outcome, only a measured one. Ask for the integrated loudness and true peak of the input, the same two numbers for the output, and listen to both files yourself. If those numbers are not in the reply, you have been told a story about your track.

Route 3: the free route you can check yourself

Everything in the previous section is available directly, for nothing, with the measurement built in. ffmpeg implements the EBU R128 loudness standard in its loudnorm filter, which both measures and normalises. Measuring first is the step people skip:

# 1. Measure what you actually have
ffmpeg -i song.wav -af loudnorm=I=-14:TP=-1:LRA=11:print_format=summary -f null -

# 2. Normalise to the one published target, writing a new file
ffmpeg -i song.wav -af loudnorm=I=-14:TP=-1:LRA=11 -ar 48000 song-master.wav

The first command prints input integrated loudness, input true peak and loudness range, then the same figures for what the output would be. That is the before-and-after nobody in the tool roundups publishes, and it takes about two seconds. If you would rather not touch a terminal, a free loudness meter plugin in any DAW gives you the same reading.

What this route does not give you is tone. Loudness normalisation makes a quiet track the right loudness; it does not fix a dull top end or a boxy low-mid, which is the actual complaint behind most “my AI track sounds flat” posts. For that you need an EQ decision, which means either learning to make one or paying someone who already has. Run the measurement anyway: knowing you are at -9 LUFS with -0.2 dBTP changes what you ask for next.

Route 4: a service, or a human

Automated mastering services do the thing route three does plus the tone decision, by matching your track against a model of finished records. They are quick, consistent and genuinely fine for a single-track release. We are not printing a price table here, because every vendor’s pricing moves and we could not read a single one of their pricing pages from source this week — check the number on the vendor’s own page rather than in anyone’s roundup, including the roundups that rank them.

A human engineer is the other end, and the live question in the forums is not price but disclosure: do you tell them the track came out of a generator? Tell them. An engineer prices by how much work a file needs, and a generated master is an unusual job — no stems unless you bought them, reverb baked into the vocal, and transients already shaved. Some engineers decline AI work on principle, and finding that out in the first message costs nothing, while finding it out after a deposit costs the deposit.

If the complaints are about the record rather than the file — a vocal that never commits, drums with no room — mastering is the wrong department entirely. That is a rebuild, and we walk through pulling stems into a DAW in why labels reject Suno tracks.

Does mastering change how a platform labels you?

This became a real question on 14 October 2026, when YouTube Music began labelling AI-generated songs. It is worth answering precisely, because the fear — that running a track through an AI mastering tool is itself an act of AI generation that gets you flagged — is backwards. YouTube’s own guidance on Gen AI designations answers it with worked examples.

StepHow YouTube's guidance treats itWho decides
Prompting a generator and downloading the resultFully Gen AIYour distributor’s declaration on delivery
Automated AI mastering of the finished trackNo Gen AINamed in YouTube’s own worked examples
Standard pitch correction on a sung vocalNo Gen AINamed in YouTube’s own worked examples
Delivering with no declaration at allYouTube may designate it for youYouTube’s own detection signals

Read the second and third rows together with the first and the logic is clear: the designation is about how the content was created, not how it was finished. Mastering — by hand, by a service, or by an AI mastering tool — is post-production, and YouTube says so in as many words. The generated audio underneath is what gets declared, and the declaration travels in the delivery metadata from your distributor.

Which is the boundary to hold on to, because plenty of marketing implies otherwise: no audio processing changes a label that is driven by a declaration. Not mastering, not watermark removal, not re-rendering. Those steps address screening and artifacts, which is a different gate with a different owner — we separate the two on distributing AI music without getting flagged.

The order of operations before you upload

Mastering sits in the middle of a sequence, and running the steps out of order is how people end up mastering twice. Clean first, because anything you strip or repair afterwards changes the level you just set.

01
Export the best file you can

WAV over MP3 where your plan allows it — more to work with, and no encoder artifacts stacked under the ones already there.

02
Clean before you master

Artifact repair and marker removal change the signal. Do them while there is still headroom, not after limiting.

03
Master to -14 LUFS, -1 dBTP

The one published target. Hitting it keeps every other platform's normalisation out of your way.

04
Measure, do not assume

Print the integrated loudness and true peak of the finished file. A master you have not measured is a guess.

05
Declare on delivery

Answer your distributor's AI questions accurately. That field, not your processing chain, is what sets the label.

Numbered five-step panel: start from the best file you have, WAV over MP3 where your plan allows it; clean before you master, because artifact repair and marker removal change the signal and should happen while there is still headroom; master to -14 LUFS and -1 dBTP, the one published target; measure rather than assume, printing the integrated loudness and true peak of the finished file; and declare on delivery, because the distributor's AI field, not the processing chain, is what sets the label
Cleaning and level-setting belong in the same stage, before the limiter.

Step two is the one unique to an AI release, and it is where Undetectr fits: it is built for the artifacts and the embedded markers that get a generated file bounced by automated screening at a distributor, and it sets level in the same pass. To be exact about what that is and is not — it addresses screening and audible artifacts. It does not change a platform’s AI label, because nothing does; that comes from the declaration, as above.

Our recommended tool

Clear the screening step, then master

Undetectr targets the generation artifacts and embedded markers that get AI tracks bounced by automated distributor screening, and sets level in the same pass. It has no effect on how a platform labels your release.

And when the master is finished

Worth saying plainly, because a mastering guide can imply that loudness is what stands between a track and an audience. It is not. Mastering is finishing work — it removes a reason to skip, it does not create a reason to listen, and the hard problem in AI music remains that nobody can find your release. The routes that do not depend on being discovered are worth more than another dB: a paid sync placement is a person reading a brief and choosing a cue, and selling direct to the listeners you already have keeps all of the money rather than a per-stream fraction of it. A finished master helps with both, which is the honest reason to do it properly.

Frequently asked questions

The Erasy logo mark, shown beside the author byline for Eddie Mathews, Editor

Eddie Mathews — Editor, Erasy

Eddie reads the help-centre article and the specification rather than the roundup, and marks the difference between what a company has documented and what a tutorial has assumed. Where the public record does not settle a question, this site says so.

Does AI music need mastering?+
Yes, in the sense that it arrives unfinished: a generator optimises for a convincing render, not for a delivery spec, so exports tend to be loud in the middle, short of headroom and inconsistent from track to track. What mastering will not do is fix a performance or a structure. If the chorus does not land, a limiter will not make it land.
What LUFS should I master AI music to?+
Spotify is the only major platform that publishes a figure for people making records: -14 dB integrated LUFS with true peak below -1 dBTP, and below -2 dBTP if your master is louder than -14. Master to that and nothing else on the list will punish you, because the rest normalise playback rather than enforce a submission spec.
Is Apple Music really -16 LUFS?+
Apple does not publish that number. Its own Apple Digital Masters guide contains no LUFS or LKFS figure anywhere; what it asks for is at least 1 dB of headroom and a master that captures your intended sound “regardless of playback volume”, with Sound Check handling playback level per track or per album. The -16 you see on every mastering blog is a measurement of playback behaviour that has been repeated until it reads like a spec.
Can ChatGPT master my Suno track?+
It can write and run code that changes the file — gain, EQ curves, compression, a limiter, a loudness measurement — and that is a real edit, not a simulation. What it cannot do is listen to the result and judge it, so the output is only as good as the instructions and the measurements you feed back in. Treat it as a scriptable processor you have to verify, not as an engineer.
Does Suno’s Remaster button master my song?+
No. Remaster re-generates the song on a current model rather than processing the file you already have, so you get a different performance, not a louder or cleaner version of the one you liked. It also costs downloads. We take the feature apart in our piece on Suno Remaster.
Will mastering stop my track being labelled AI?+
No, and nothing else will either. YouTube’s own Gen AI designation guidance lists automated AI mastering as No Gen AI, so the mastering step itself does not trigger a label — but the generated audio underneath it still does, and the designation comes from what your distributor declares on delivery or from the platform’s own detection. No processing of any kind changes a declaration.
Should I tell a mastering engineer the track was AI-generated?+
Yes, and early. Engineers price by how much work a file needs, and a generated master with no stems, baked-in reverb and smeared transients is a different job from a mix handed over from a DAW. Some will decline AI work outright, which is cheaper to find out in the first message than after a deposit.

Read at source on 21 October 2026: Spotify for Artists on loudness normalisation; Apple’s Apple Digital Masters guide, searched in full for LUFS and LKFS, which do not appear in it; YouTube’s help-centre article on Gen AI designations, including its worked examples for automated AI mastering and pitch correction; the TIDAL and Deezer help-centre search APIs, which return no loudness articles; and the ffmpeg filter documentation for loudnorm, whose two-pass output we ran in order to quote what it prints. The count of effects in Suno Studio 2.0 is AI Musicpreneur’s reporting of 10 September 2026, not our own test of the product; that article discloses a paid partnership with one of the tools it ranks. We have not measured a Suno export ourselves and no figure here is presented as one.