Most people will never hear your mix on a pair of studio monitors. They'll hear it through a phone speaker while doing dishes, through AirPods on the subway, through a Bluetooth speaker in a hotel room. If your mix doesn't hold up on those devices, the work you put in on your monitors doesn't fully matter.

Using your phone as a reference monitor isn't a compromise. It's a discipline — one that working engineers have practiced since the days of the Auratone "horror-tone" cube. The tools have just gotten better.

What a Phone Speaker Actually Does to Your Mix

Understanding why phone checks matter starts with understanding what phone speakers physically can and cannot do.

A typical smartphone speaker attenuates significantly below 200–300 Hz. Sub-bass below 80–100 Hz is essentially inaudible on most phones; what bass you hear comes from upper harmonics and midrange energy. Real-world measurements across common smartphones show significant attenuation starting anywhere from ~150 Hz on the high end to ~65 Hz on flagship devices — with most mid-range phones losing meaningful output below ~200–300 Hz. What this means in practice:

  • Sub-heavy bass disappears entirely. A kick or bass that's all fundamental energy below 80 Hz will sound thin or absent.
  • Mud in the 200–400 Hz range becomes very obvious. Energy that felt "warm" on monitors sounds boxy or cluttered on a phone.
  • The 1–4 kHz presence region is emphasized. Harshness in vocals, guitars, or synths that you've been tolerating will jump forward.
  • Stereo width collapses. Most phone speakers play at close enough proximity that stereo imaging effectively disappears. Wide elements that rely on hard panning lose their sense of space. If your stereo bus has phase issues, they'll surface immediately as comb filtering or as elements that feel hollow.

None of this is a flaw — it's physics. Small drivers in a small enclosure can't move enough air to reproduce low frequencies. The upside: these constraints are exactly what make a phone check useful. If your mix survives a phone speaker, it's been tested against the most common playback condition in the world.

The Loudness Normalization Factor

There's a second layer of phone-era reality that many engineers underweight: streaming platforms normalize loudness before playback. When a listener hits play on Spotify or Apple Music, they're not hearing your master at the level you delivered it — they're hearing it scaled to a platform target.

Platform Integrated LUFS Target True Peak Limit
Spotify −14 LUFS −1 dBTP
Apple Music −16 LUFS −1 dBTP
YouTube −14 LUFS −1 dBTP
Tidal / Amazon Music −14 LUFS −1 dBTP

If your master is significantly louder than the platform target, it gets turned down. An over-compressed master that reads hot on a limiter can sound perfectly fine before delivery — and then arrive at the listener at lower perceived volume than an uncompressed version would have, once platform normalization does its work. A phone check at realistic listening levels helps you hear what your listener actually hears.

Simulation vs. Real Device: Two Different Answers

The software industry has built tools specifically for this problem. Sonarworks SoundID Reference (around $99–$199 depending on tier) applies headphone and speaker calibration profiles, and includes consumer device simulation modes via its Virtual Monitoring add-on. Waves NX offers similar simulated speaker environments. These tools are legitimate and useful — they let you hear a rough approximation of consumer playback without leaving your mix position.

But simulation has a ceiling. Here's what a simulated phone curve cannot tell you:

  • Actual driver distortion at loud levels. Real phone speakers distort in non-linear ways that an EQ curve approximation won't reproduce.
  • Room interaction. Your phone sitting on a desk, in your hand, or propped against a coffee cup changes how the sound couples with the surface. That's real-world listening.
  • Normalization behavior. When a listener streams music on a real device, normalization is applied. A simulation plugin in your DAW is playing back audio before any of that happens.
  • Your own perceptual shift. Listening to the same mix in a different physical space, on a different transducer, trips different perceptual circuits. Engineers have trusted this for decades — the car check, the kitchen check, the hallway check. A real device produces a genuine context shift that a simulated curve on the same studio monitors does not.

The smart approach is both: use simulation tools for in-session micro-decisions, use a real device for go/no-go checks at key moments.

Setting Up Your Phone as a Monitor with Auxfeed

Auxfeed is a free plugin and app that streams audio from your DAW to your phone in real time over Wi-Fi. No account required, no IP address to configure — it uses Bonjour auto-discovery, so the app finds the plugin automatically when they're on the same network.

What You Need

  • macOS or Windows computer running your DAW
  • iPhone (iOS 16 or later) or Android phone (Android 8 or later)
  • Both devices on the same Wi-Fi network

Setup

  1. Download and install the Auxfeed plugin from auxfeed.com. It installs as AU, VST3, and AAX on macOS; VST3 and AAX on Windows.
  2. Insert the plugin on your master bus (or any bus you want to monitor). It sits at the end of your chain, post-fader.
  3. Install the Auxfeed app on your phone — available on the App Store and Google Play.
  4. Open the app. Your session appears automatically. Tap to connect, then press play in your DAW.

Audio is now playing through your phone in real time — latency is low enough that you can scrub and loop normally. The plugin supports PCM lossless, Opus, and AAC (iOS) codecs, so you can choose the codec that matches your bandwidth situation.

If you need to send audio to a client who isn't in the studio, Auxfeed Pro adds remote streaming over the internet — they connect from anywhere and hear your session live.

Where the Phone Check Fits in Your Workflow

Using your phone as a studio monitor doesn't mean mixing on it. You're not replacing your monitors — you're adding a reference checkpoint. Here's where it pays off most:

Before a Client Call

Ten minutes before you play a rough for a client, do a quick phone check. Listen on the phone speaker, then through AirPods or earbuds. Anything that's going to raise questions will surface here. Better to catch it now than mid-conversation.

After a Long Session

Ear fatigue is real. After three or four hours on studio monitors, your perception of the low-mid region shifts. A phone check gives you a hard reset — different transducer, different room, different context. Things that were hiding often reveal themselves.

Before Printing a Rough Mix

Before you bounce a file and send it anywhere, listen on the phone. Check that the vocal sits where it should, that the kick and bass have perceptual weight from upper harmonics (since the fundamental is mostly gone on phone speakers), and that nothing harsh is jumping out in the 2–4 kHz band.

Low-End Reality Check

Sub-bass is notoriously hard to judge in imperfect rooms. If your room has a bass buildup, you may be compensating in ways that don't translate. Play the track on your phone. If the bass groove disappears entirely — if the song feels rhythmically thin — you've over-relied on fundamentals below 80 Hz. Add harmonic content in the 150–300 Hz range so the bass speaks on small speakers.

Going Further: AirPods, Bluetooth, and Multi-Device Monitoring

Once Auxfeed is streaming to your phone, the phone becomes a router for all your mobile listening options.

AirPods and Earbuds

AirPods and most in-ear earbuds have more low-frequency extension than phone speakers, but pronounced peaks in the upper midrange. Listening through AirPods while Auxfeed streams catches a third reference point that's highly relevant: earbuds are how a large share of streaming listeners actually hear music.

Bluetooth Speakers

A Bluetooth speaker connected to your phone while Auxfeed streams is a quick check of how your mix sounds on a kitchen or bathroom speaker — another extremely common playback environment. Note: Bluetooth adds its own latency and codec processing, so use this for impression checks rather than precise A/B comparisons.

Multi-Device Workflow

A practical three-point reference system during a session:

  • Studio monitors — primary mixing environment, detail and imaging work
  • Closed-back headphones — stereo detail, low-level elements, late-night work
  • Phone (via Auxfeed) — consumer reality check at key moments

The phone check is a brief circuit-breaker, not a continuous monitor. You don't need to be on all three simultaneously.

Checking LUFS on Your Phone

Auxfeed's free tier shows momentary and short-term LUFS (EBU R128) in the app. For a full breakdown of what LUFS means and how streaming platforms use it, see What Is LUFS? A Mixing Engineer's Guide to Loudness. Auxfeed Pro adds integrated LUFS, true peak (dBTP), and LRA, plus platform targets for Spotify, Apple Music, YouTube, and Netflix — so you can confirm delivery levels without leaving your session.

Step-by-Step Setup Guides by DAW

The steps are the same across every host: install the plugin, insert it on your master bus, open the Auxfeed app, and press play. These guides cover the exact procedure for each DAW:

The Bottom Line

Simulation tools are useful. Calibrated monitors are necessary. But there is no substitute for actually playing your mix through the same hardware your listeners use.

Other tools simulate what your mix will sound like on a phone. Auxfeed just plays it there.

Setup takes under two minutes. The plugin is free, the app is free, and no account is required for same-network use.

Download Auxfeed free and add a phone check to your mix workflow today.