SoundCloud Says Your Upload Is Not Broken When the Spectrogram Drops at 17 kHz
SoundCloud explained why its newer AAC encoder can show a hard rolloff near 17 kHz. The platform says the change spends bits where listeners are more likely to hear them.
Short answer
On June 18, 2026, SoundCloud's engineering team explained why some artists see a steep high-frequency rolloff when they download and inspect SoundCloud's AAC transcodes. SoundCloud says it moved to Fraunhofer's libfdk_aac encoder, which can cut or roll off very high frequencies around 17 kHz so more bits are available for the audible midrange. The practical artist takeaway: upload the best lossless master you have, but do not judge SoundCloud delivery only from a spectrogram. Compare the original and platform version by listening, and keep a local lossless master for distribution, pitching, sync, and archive use.
SoundCloud says some AAC transcodes now show a visible high-frequency rolloff around 17 kHz because the encoder is spending bits where people are more likely to hear detail. Your upload is not broken just because the spectrogram looks clipped at the top.
Key takeaways
- SoundCloud says it upgraded its AAC encoder to Fraunhofer's libfdk_aac.
- Some downloaded or inspected transcodes can show a hard rolloff near 17 kHz.
- SoundCloud says the tradeoff gives the encoder more room to preserve the range listeners hear most clearly.
- Artists should still upload lossless masters, but should judge platform playback by listening as well as by graphs.
What happened?
SoundCloud published an engineering note explaining why uploaded tracks can look different after platform transcoding. If you upload a lossless master, then download or inspect the SoundCloud AAC version, you may see a steep drop near 17 kHz. SoundCloud says that is part of how its newer AAC encoder allocates bits.
The platform’s explanation is technical, but the artist version is plain: lossy audio has to throw something away. SoundCloud says the encoder sacrifices very high frequencies so the midrange and other more audible parts of the file can stay cleaner.
Why independent artists should care
Mastering conversations can get weird fast when someone opens a spectrogram and sees a shelf. The graph may be real, but it does not automatically mean the upload failed, your master is bad, or SoundCloud damaged the track in the way the image suggests.
| Useful check | Bad conclusion | |
|---|---|---|
| Spectrogram | Can show how the platform transcode changed the file | Does not tell the whole listening story by itself |
| Upload file | Use a clean WAV or FLAC export from your final master | Do not upload a lower-quality file because the platform will transcode anyway |
| Review process | Compare the original and SoundCloud playback on real speakers and headphones | Do not panic from a 17 kHz visual cutoff alone |
The graph can tell you what changed. Your ears still have to tell you whether it matters.
What to do now
Keep your master clean
Upload the best lossless master you have. Keep the final WAV or FLAC in your own archive for distribution, sync, pitching, and future re-delivery. The platform transcode should never be your only copy.
Check playback, not only pixels
Listen to the SoundCloud version next to the original at matched volume. If the vocal, drums, bass, and top-end feel right in normal listening, a visible high-frequency rolloff is not automatically a release problem.
What is still unclear?
Open questions
SoundCloud is explaining AAC playback behavior, not promising that every upload will sound identical to your master. Different platforms use different encoders and bitrates, and the transcode you inspect may not represent every playback context. The practical rule stays the same: upload clean source audio and keep the platform copy in perspective.
Sources
Related Velveteen guides
Get music industry updates without the noise
Short notes on platform changes, royalty issues, and release marketing moves that actually affect independent artists.
Was this useful? Send a signal or flag a correction.