Streaming service audio quality settings: what you're actually sending to your DAC

Last month I watched a bloke spend twenty minutes on an audio forum debating whether his new streamer sounded "more resolved" after switching from Wi-Fi to Ethernet — fair enough, I've been in those threads — but when I asked what quality setting he had Spotify set to, he went quiet. It was on "Automatic". The app had been throttling his audio for three months.

This is more common than you'd think. People invest real money in streamers, DACs, and cables, then leave their streaming app's output settings at whatever the installer or default install chose. That's not a knock on anyone; the apps bury these settings deliberately, and the documentation from most services is genuinely bad. So let's go through it properly — what each setting actually does to the bit stream, where the quality floor sits per service, and when you should care.

What the quality setting actually controls

The short version: on lossy services it controls codec, bitrate, and sometimes the codec variant. On lossless services it controls whether the app serves a compressed or lossless stream, and at what resolution. Your DAC receives whatever the app sends — it cannot reconstruct information that was discarded upstream.

On a lossy stream (Spotify, YouTube Music in their standard tiers), the audio goes through an encoder — Ogg Vorbis on Spotify, AAC on Apple Music's standard and Spotify's web player fallback — and is reconstructed by a decoder before it ever touches your DAC. At 320 kbps Ogg Vorbis or AAC, most people can't identify the compression in a controlled blind test. But at 96 kbps, which is what "Low" or "Data Saver" modes typically serve, the artefacts become audible on headphones with real resolution. That's not folklore; it's the reason codec designers publish quality versus bitrate curves in the first place.

On a lossless service (Tidal HiFi Plus, Apple Music with Lossless enabled, Qobuz), the app is serving a FLAC or ALAC file. At CD quality (16-bit/44.1 kHz), that's an uncompressed 1,411 kbps data rate, though FLAC typically compresses it to around 900 kbps without any audio information loss. Hi-res tiers push that to 24-bit/96 kHz or higher, which is a very different conversation — I covered the perceptual case for hi-res in our DACs and streamers guide and won't relitigate it here.

Spotify: three settings, one that matters

Spotify's quality settings in the desktop and mobile app run from Automatic through Low (24 kbps), Normal (96 kbps), High (160 kbps), and Very High (320 kbps Ogg Vorbis). The "Automatic" setting adjusts based on connection quality and, critically, will drop below Very High if Spotify's servers think your connection is marginal — even when it isn't.

For any serious listening on a real system: pin it to Very High. Full stop. On mobile, remember that the app has separate settings for Wi-Fi and cellular, and both need to be set explicitly. I've seen plenty of setups where someone set Very High at home on Wi-Fi and forgot the cellular setting was still on Normal — then they'd take their headphones out, stream on the go, and wonder why it sounded worse.

One thing Spotify does do well: Ogg Vorbis at 320 kbps is a genuinely good codec implementation, arguably slightly more transparent than MP3 at the same bitrate. You're not going to unseat lossless with it, but it's not the weak link it was five years ago. If Spotify is your service, make sure your DAC is receiving 320 kbps before you draw any conclusions about anything else in the chain. Connect a Chord Mojo 2 (check price) to a laptop and the signal quality difference between 96 kbps and 320 kbps is immediately obvious — that's the setting's fault, not the hardware's.

Apple Music: lossless doesn't turn itself on

This is the one that trips people up most often. Apple Music's subscription includes CD-quality lossless and hi-res lossless at no extra cost — but lossless is disabled by default. You have to manually enable it in Settings > Music > Audio Quality and select the Lossless tier for each connection type (Wi-Fi, cellular, and when downloading).

Once enabled, Apple Music streams ALAC (Apple Lossless Audio Codec) at 16-bit/44.1 kHz for standard lossless, up to 24-bit/192 kHz for hi-res. The catch — and this is worth understanding — is that Apple's own hardware (iPhone, iPad, Mac) handles the decoding natively, but getting hi-res to a USB DAC requires the right USB driver stack and, on iOS, the Apple USB-C to USB 3 Camera Adapter or the Lightning equivalent. The built-in headphone output on current iPhones is limited to 24-bit/48 kHz regardless of what the app is trying to send.

On a Mac, Apple Music with lossless enabled and a quality USB DAC connected is genuinely a capable transport. ALAC decodes natively in macOS, the USB audio stack is stable, and you're getting bit-perfect output if you've set your Audio MIDI Setup correctly. I'll write a full piece on the Mac-as-streamer setup at some point, but the short version is: check Audio MIDI Setup, match the sample rate to your content, and you're probably in better shape than you realise.

Tidal: tier confusion, then it gets cleaner

Tidal's tier structure has been a moving target. The current relevant distinction is between their standard tier (AAC, up to 320 kbps) and HiFi Plus (FLAC at CD quality, plus their Max tier with hi-res FLAC and Dolby Atmos). MQA has been deprecated and is mostly irrelevant to new subscribers — I won't miss it.

Within HiFi Plus, the app setting to watch is whether you've set streaming quality to "HiFi" (CD quality FLAC) or "Max" (hi-res FLAC where available). The Max setting serves 24-bit/96 kHz or 24-bit/192 kHz tracks when the catalogue has them, which is genuinely useful if your DAC supports those sample rates. The Cambridge Audio CXN100 I reviewed handles Tidal Max directly through its own app implementation without needing a separate device — if you're considering a network streamer that handles Tidal natively, that's worth reading (check price).

One honest note: Tidal's app-based streaming quality on Android and iOS can be inconsistent between firmware versions. I've had the app revert quality settings after updates on at least two occasions. Worth checking after every major app update.

Qobuz: arguably the most transparent implementation

Qobuz streams FLAC, serves hi-res where available, and doesn't add processing layers or codec wrappers that complicate the signal. Their quality settings are straightforward: MP3 320 kbps, CD quality FLAC, or Hi-Res FLAC (up to 24-bit/192 kHz depending on the track). If you're on the Studio tier, hi-res is included.

Qobuz's catalogue depth in classical and jazz is strong — arguably stronger than Tidal in those genres. For pure hi-res coverage across contemporary music, both are competitive. I'd encourage anyone serious about lossless streaming to run both for a month and compare catalogue coverage against their actual listening habits rather than picking based on marketing claims.

The Qobuz desktop app on Windows and macOS outputs to whatever audio device is selected and respects WASAPI Exclusive Mode (Windows) and Core Audio (macOS), which matters for bit-perfect output. On mobile, it's the same pattern as Tidal — check whether your connection is providing hi-res or dropping to CD quality based on bandwidth detection.

What your DAC actually sees: the transport chain problem

Here's something the streaming services don't explain and that's worth spending a minute on. Even if your streaming app is set to lossless and your DAC supports 24-bit/96 kHz, there are several places in the chain where the signal can be intercepted, resampled, or mixed — all silently.

On Windows, any audio going through the Windows Audio Session API (WASAPI) shared mode is mixed by the Windows audio engine and resampled to whatever the system sample rate is set to. If your DAC is set to 48 kHz in Windows and your Qobuz track is 44.1 kHz FLAC, Windows is resampling before the signal reaches the DAC. The fix is WASAPI Exclusive Mode, which lets the app claim the audio device and bypass the mixer entirely. Most serious playback apps (Roon, JRiver, foobar2000 with the right components) support exclusive mode. Qobuz's desktop app does too, via settings.

On macOS, the equivalent is ensuring the Core Audio device sample rate matches your content, or using an app that sets it automatically. Roon does this well. The native Apple Music app does not — it locks Core Audio to whatever rate you've set in Audio MIDI Setup, which means 44.1 kHz content plays correctly if you've set 44.1 kHz there, but 96 kHz content will be resampled down. This is why Roon users who care about this stuff tend to route everything through Roon even if they also use Apple Music for casual listening.

I've written about this in the context of network audio clocking and jitter, and the same logic applies here. The signal chain matters end to end. If you're serious enough about streaming to use a dedicated streamer and DAC — something in the class covered in our streamers and DACs guide — then getting the app's quality settings right is the first step, not an afterthought.

Bluetooth streaming: a different conversation entirely

If you're streaming to a Bluetooth speaker or wireless headphones, the codec negotiation between your phone and the device overrides everything above. aptX HD, LDAC, and AAC each have their own bitrate and quality characteristics, and whether your phone actually uses LDAC or falls back to SBC depends on both the phone's OS version and the specific Bluetooth implementation.

I'll cover Bluetooth codec negotiation in depth in a separate piece because it deserves its own treatment. The short version: on Android with LDAC-capable headphones, force LDAC at maximum quality in developer settings. On iOS with AirPods, you're in AAC at Apple's implementation, which is genuinely fine for casual listening but nowhere near lossless. Don't conflate Bluetooth streaming quality with what you're sending over USB or Ethernet to a dedicated DAC — they're not comparable.

Where to actually start

Go into your streaming app right now. Find the audio quality settings. On every service, set them to the highest quality available for your tier on every connection type — Wi-Fi, cellular, downloaded content, all of them. If you're on a lossless tier and lossless isn't enabled, enable it. If you're on a lossy service, confirm you're at the maximum bitrate.

Then, if you're on Windows, check whether your playback app is using WASAPI Exclusive Mode. On macOS, open Audio MIDI Setup and check what sample rate your DAC is set to. These two steps will resolve more sonic issues than swapping cables, and they're free.

Honestly, it's a bit embarrassing how much of the streaming quality conversation happens around hardware when the software settings are this easy to misconfigure and this rarely discussed. The room and the transducers matter most, yes — but an incorrectly configured streaming app is the equivalent of a dirty stylus: it's upstream of everything else, and no amount of good hardware downstream corrects it.

If you're building out a serious streaming chain with a dedicated network streamer, the streaming amplifiers guide and our existing piece on network streamers and DACs are good next steps. Get your signal clean first, then start upgrading boxes.

— Theo Mensah, Digital, DACs & Streaming Editor