A large share of the people hearing your music are hearing it through a device with one or two small drivers and no bass response whatsoever. This is not a lesser audience. It is a substantial one, and a mix that only works on good monitors is a mix that does not reach them.
What a phone actually reproduces
Roughly nothing below 200Hz, and the response above that is not flat. Small drivers in small enclosures have resonances that colour what they do reproduce, and they roll off steeply at both ends of their usable range.
The practical consequence is that a mix balanced on monitors is likely to be too bass-heavy on a phone, because you are hearing the low end that the phone will not. And it is likely to lose clarity, because the midrange is being reproduced inaccurately while the low end is simply absent, which usually makes the low-mid region sound more prominent than it is.
Checking on a real device
The most useful test is unglamorous. Play the mix through earphones or the phone speaker at a moderate level, in a normal listening position, and listen for three things.
First, is the kick still doing something? On a phone it will be much weaker than on monitors, and if it disappears entirely, the low end of your mix is doing more work than it appears to be on good speakers. Second, is the vocal still intelligible? If it only works when the low end is present, the arrangement is relying on masking rather than on balance. Third, does it sound thin or does it sound acceptable?
Thin is expected and not a problem. A phone cannot produce low frequencies, so a mix that sounds thin on a phone is playing as well as that device allows. The problem is a mix that sounds congested, which indicates real problems in the low-mid that monitors are hiding from you.
The masking problem
The most common failure on small speakers is masking. A bass line and a kick drum occupying the same region reinforce each other on monitors, where the low end is present in full, and the two read as one strong low end. On a phone, the low end is missing, so what remains is whatever else is in that region, and the result can be a congested midrange where there was a clean low end on the monitors.
This is a genuine argument for treating the low-mid and the sub as separate jobs even when they reinforce each other. If the arrangement works when you solo the sub-bass, it will translate. If it collapses, it depends on the presence of frequencies the phone does not produce.
A translation check
Print or bounce the mix, then close the DAW. Monitoring through the session leaves you able to reach for a plugin, and you will. Work from the file.
Play it on a phone, a laptop speaker and earphones. Three different failure modes. The phone reveals low-end dependence, the laptop reveals midrange congestion, and earphones reveal low-mid imbalance because they leak bass differently depending on fit.
Also play it through good monitors. A mix that only works on a phone is not a solution. You are checking that the core balance survives, not replacing the monitors.
Write down what you had to change. If the fix is always the same, it is a mixing decision rather than a translation problem, and it belongs in the mix rather than in a separate phone master.
What each system reveals
| System | Reveals | Common finding |
|---|---|---|
| Studio monitors | Actual balance across the spectrum | Reference, not truth in every room |
| Headphones | Low-mid imbalance, missing crosstalk | Low end sounds overblown or absent |
| Laptop speakers | Midrange congestion | Low-mid too heavy, vocal unclear |
| Phone speaker | Dependence on absent bass | Kick and bass missing, midrange busy |
| Club system | Low end and headroom | Weak kick, midrange that disappears |
Retuned mixes and small speakers
A retune moves the fundamental of everything down, which pushes more content into the region small speakers cannot reproduce. A mix retuned with 432Hz MASTER may therefore lose slightly more of its audible content on a phone than the same mix at 440Hz, simply because more of it sits below the phone's cutoff.
This is worth checking but is not a reason to avoid retuning. If the midrange and upper content are clear, a phone listener will hear the arrangement, texture and melody, which is most of what they came for.
The bottom line
Check on a phone once per mix. It takes two minutes and it reliably exposes arrangements that depend on frequencies a large share of listeners cannot hear.
Frequently asked questions
Do I really need to check my mix on a phone?
Yes, if a significant share of your listeners use one. It takes two minutes and it reveals arrangements that depend on low-end presence in a way no other single check will. A mix that only works when the bass is audible is relying on masking rather than balance.
Why does my mix sound thin on a phone?
Because a phone cannot produce low frequencies, so everything below roughly 200Hz is missing. A mix that sounds thin on a phone is playing as well as that device allows. The problem is a mix that sounds congested, which indicates real low-mid problems that your monitors are hiding.
Should I make a separate version for phones?
Rarely. If the only thing you need to change is the low end, that is a mixing decision rather than a translation problem, and it belongs in the main mix. A separate version risks the two drifting apart and being maintained inconsistently.
Does retuning affect how a mix sounds on small speakers?
Slightly. A retune moves fundamentals down, which places more content below the cutoff of a small speaker. The midrange and upper content are unaffected, so a retuned mix will still be intelligible on a phone even where more of its low end is inaudible.