Hardware decisions

Headphones are quiet on an interface: check more than impedance

Separate output routing, headphone connection, source level and model-specific drive capability before buying an amplifier.

OUR TAKE

Check the headphone output, routing and source level before blaming impedance. Focusrite's guidance is model-specific and notes that sensitivity, source loudness and listening conditions also affect usable level. An impedance number alone is not a complete compatibility test.

A clear distinction between a routing/connection issue and an output-capability limitation.

In this guide
Before you start
  • The exact headphones and interface models, including generation.
  • A familiar recording at a comfortable listening level and a correctly wired headphone adapter.

Before you change the setup

Quiet headphones can result from several small problems that look like one. The source may be quiet, the interface may be feeding a different mix, a partly seated adapter may lose a channel or the headphones may need more drive than the output comfortably provides. Start with the first three before adding equipment.

Focusrite publishes different headphone-impedance guidance for different interface generations, but it also warns that the number is not a guaranteed listening-level result. Sensitivity and source material matter. Compare the exact models and use a controlled listening test instead of assuming all headphones with the same impedance behave identically.

Run a controlled check

  1. Check the correct output

    Connect to the interface's headphone socket using the intended adapter, not a rear line output. Inspect the connection at low volume and confirm that both channels are present with a familiar stereo recording.

    Look for: You establish a proper headphone path before judging the amplifier's capability.

  2. Inspect the headphone mix

    Check which playback or monitor mix feeds the headphone output. Compare ordinary computer playback with the microphone monitor feed separately. Keep any blend control in a deliberate position.

    Look for: A quiet microphone monitor is not confused with a globally weak headphone output.

  3. Compare source levels sensibly

    Use the same known recording and application volume for each test. Begin quietly and raise the headphone control only to a comfortable level. Note whether the source itself was recorded unusually low.

    Look for: The comparison is based on consistent material rather than different songs or applications with different loudness.

  4. Read the model-specific guidance

    Check the interface generation's headphone recommendation and the headphone's sensitivity/impedance specification. Treat published guidance as a compatibility aid, not a promise about your preferred listening level.

    Look for: Any suspected output limitation is tied to the actual equipment rather than a generic brand claim.

  5. Make one controlled alternative test

    If available, compare another suitable pair of headphones on the same output, or the same headphones on another documented compatible output at a comfortable level. Keep the source recording unchanged.

    Look for: You obtain evidence about the pairing before deciding whether an additional headphone amplifier is useful.

Read the result and keep a working setup

If one channel disappears or the sound becomes thin when the plug moves, resolve the connector or adapter first. If computer playback is normal but direct monitoring is faint, investigate the microphone level and monitor routing. If everything is clean but lacks the required comfortable level only with one headphone pair, the pairing's drive requirements become a more plausible explanation.

An extra amplifier adds another powered device, cable path and volume control to the desk. It may be appropriate, but it should answer a demonstrated need. Check how it would connect to the interface's intended output and how you would prevent accidental excessive level when switching sources.

No maximum sound-pressure level or amplifier performance is claimed here. Listening should remain comfortable, and a control position near its maximum is not by itself proof of failure. Keep the source, route and headphone model in your notes so later comparisons remain meaningful rather than turning into a contest of volume-knob positions.

Keep these distinctions clear

Keep these distinctions clear
ObservationInvestigate first
Only microphone monitoring is quietMonitor blend, routing and mic input level.
One side missing or intermittentPlug, adapter and cable.
All sources quiet with one pairExact headphone/output pairing.
Playback quiet in one appApp and source level.

Try it on your own setup

Start small: try the free files or continue with a guide for the part you’re working on.

Open or Closed Headphones When You Stream with a Separate Mic? ↗

Sources & references

Documentation review checked 4 November 2026 using the primary sources listed below. This is not a hands-on product test: the diagnostic sequence and rehearsal suggestions are Foxdip editorial guidance. No measured performance, search volume, price or universal compatibility result is claimed.

  1. Focusrite — Headphone impedance and interfaces ↗Checked 2026-11-04
  2. Focusrite — System Science: Analogue Connections ↗Checked 2026-11-04

Spotted something out of date? Let Alex know.

How we put our guides together ↗
READ NEXT

A few places to go from here.

All stories

Open or Closed Headphones When You Stream with a Separate Mic?

Compare DT 700 PRO X and DT 900 PRO X around room noise, microphone pickup and your listening output rather than assuming open backs improve a stream.

Direct Monitoring vs OBS Monitoring: Why Your Headphones Sound Different

Find out which microphone path you’re hearing, remove an unwanted doubled voice and check what OBS actually records.