mpv Volume Too Low: How to Fix It

When mpv sounds much quieter than your browser, music player, or another video application, the cause is usually not a broken speaker or missing codec. The most likely causes are mpv's current volume setting, a restrictive volume-max value, ReplayGain metadata, an audio filter, multichannel downmixing, a profile or script, the selected audio track, or an operating system volume control. Use the tests below in order. After each change, compare the same section of the same media file. Once mpv matches the expected loudness without distortion, stop changing settings.

1. Confirm the Symptom With a Minimal Clean mpv Command

Start by separating an mpv configuration problem from a media, operating system, or audio-device problem. The --no-config option tells mpv not to load its normal configuration files. This temporarily excludes most custom options, profiles, scripts, shaders, and input bindings without deleting anything.

1.1 Test a known local file without configuration

Close other mpv instances, open a terminal, and run one of these commands. Replace the example path with a local file you know plays correctly in another application.

On Windows:

mpv.exe --no-config --volume=100 "C:\Media\test-video.mkv"

On Linux or macOS:

mpv --no-config --volume=100 "/path/to/test-video.mkv"

Use quotes around paths containing spaces. Do not test an online URL first because network delivery, yt-dlp, website formats, and stream-specific audio tracks introduce extra variables.

Success means the clean mpv session is approximately as loud as other players using the same output device. If it is, mpv itself and the media file are probably functional. Your normal configuration, a profile, an input binding, or a script is the likely cause. Stop investigating drivers and operating system permissions at this stage.

If the clean session remains quiet, play the same local file and exact audio track in another trusted player. If every player is quiet, the file may have a low-level mix. If only mpv is quiet, continue with the mpv and operating system checks below.

1.2 Verify the displayed volume

While the file plays, press 9 and 0 using mpv's default bindings to lower and raise volume. The on-screen display should report the volume. If these keys do nothing in your normal session but work with --no-config, a custom input.conf, script, or input section is overriding them.

A displayed value of 100 does not guarantee equal perceived loudness across applications. Different players can apply normalization, downmixing, or system-level gain. It does establish a useful baseline for mpv troubleshooting.

2. Check mpv Volume Options and Configuration

2.1 Understand volume and volume-max

The volume option sets mpv's starting software volume. The volume-max option controls how high that software volume is allowed to go. If volume-max is set to 100, mpv cannot be raised above 100 through its normal volume control. A higher ceiling allows amplification, but it does not make playback louder by itself.

Test a moderate increase temporarily:

mpv --no-config --volume=120 --volume-max=150 "test-video.mkv"

Listen for harshness, crackling, or flattened peaks. Software amplification can clip when the source already approaches digital maximum. If 120 solves the problem cleanly, you can adopt a conservative value. If distortion appears, return to 100 and investigate ReplayGain, filters, downmixing, or the operating system mixer instead of continually increasing gain.

For a persistent setting, add options to mpv.conf without leading double hyphens:

Do not assume that setting volume-max=200 automatically provides safe headroom. It merely permits greater gain. Success means normal material reaches a comfortable level with no clipping. Stop increasing the limit when that condition is met.

2.2 Find duplicate or profile-specific settings

Search your mpv configuration files for these terms:

• volume=
• volume-max=
• replaygain
• af= or af-add
• audio-normalize-downmix
• profile=

A later option can replace an earlier one, and profiles may apply only to particular file types, protocols, resolutions, or paths. That explains why local files may sound normal while playlists or network streams are quiet.

Run mpv --show-profile=profile_name to print the contents of a named profile. Substitute the actual profile name from your configuration. You can also launch mpv from a terminal and inspect its startup messages to see which profiles are applied.

Comment out one suspicious line at a time by placing # at its beginning, then repeat the same playback test. Do not delete the entire configuration directory. Success is a single identified option or profile whose removal restores expected loudness.

2.3 Inspect input bindings and scripts

Open input.conf and search for bindings containing volume, af, audio, cycle-values, or script messages. A binding can set volume to a fixed value or toggle an audio filter without making the change obvious.

User scripts can also remember volume, load profiles, modify filters, or communicate through IPC. Because --no-config normally prevents the usual user configuration and scripts from loading, a successful clean test strongly points here. Disable suspected scripts individually by moving one script temporarily outside the scripts directory, then retest. Preserve the original file so the change is reversible.

3. Check ReplayGain, Normalization, Filters, and Downmixing

3.1 Review ReplayGain behavior

ReplayGain metadata describes recommended gain adjustments for compatible audio. Depending on the metadata and selected ReplayGain mode, mpv may reduce gain to maintain consistent loudness or avoid peaks. This can make a tagged music file sound quieter than an untagged video or another player that ignores the tags.

Test the same file with ReplayGain disabled:

mpv --no-config --replaygain=no "tagged-audio-file.flac"

If this restores the expected level, inspect your normal configuration for replaygain options. Decide whether you prefer consistent album or track loudness, or no ReplayGain processing. Do not automatically compensate by adding large global volume gain, because that also affects files that were already loud.

Success means tagged and untagged files behave according to your chosen policy without audible clipping. Once ReplayGain is confirmed as the cause, there is no need to change video, subtitle, hardware-decoding, or network options.

3.2 Inspect audio filters and normalization

Audio filters can reduce gain intentionally or as part of a larger processing chain. Common examples include equalizers, compressors, limiters, channel remapping, loudness normalization, and filters inserted by scripts. Test without the configured filter chain:

mpv --no-config --volume=100 "test-video.mkv"

If you need your remaining configuration but want to clear filters for one test, launch mpv with an empty audio-filter setting appropriate to your shell, such as --af=. Shell parsing differs, so quote the argument if your shell treats it specially.

Normalization is not always the same as amplification. Some normalization or peak-protection methods lower loud passages to create headroom. Filters can also alter perceived loudness while preserving peak level. Reintroduce filters one at a time and compare at the same timestamp.

3.3 Test multichannel downmixing

A common low-volume symptom occurs when 5.1 or 7.1 audio is played through stereo speakers or headphones. Dialogue may be concentrated in the center channel, and the downmix must combine channels without clipping. Safe downmixing can reduce overall gain to preserve headroom.

Use mpv's track information or stats display to determine whether the source is multichannel and the output is stereo. Then compare with another audio track, such as a native stereo track, if the file contains one. You can cycle audio tracks using the default # binding or select a track explicitly with --aid=ID.

Check whether your configuration changes audio-normalize-downmix or adds channel-layout filters. Test both the clean configuration and your normal configuration before changing this option. Disabling protective normalization may raise volume but can cause clipping when channels combine. A better solution may be a carefully designed downmix filter or a modest post-downmix gain that you have tested on loud scenes.

Success means dialogue and effects are balanced at a useful level without crackling during peaks. Stop changing settings if selecting the correct stereo track solves the problem.

4. Check the Operating System and Audio Backend

4.1 Windows app volume mixer

Windows can store a separate volume level for each application and output device. Start playback in mpv, open Settings, navigate to the volume mixer, and find the active mpv process. Confirm that it is not muted or set substantially below the system and other application levels. Also verify that mpv is routed to the intended speakers, headphones, HDMI display, or audio interface.

If you switch between packaged builds or executable locations, Windows may treat them as distinct application entries. Check the mixer while the exact mpv process is running. Success means the mpv app slider and output route match your intended baseline. If that fixes the level, leave mpv's software volume near 100 rather than stacking unnecessary amplification.

4.2 Linux and macOS output controls

On Linux, inspect the per-application stream in your desktop sound panel or the control utility associated with PipeWire or PulseAudio. Confirm that mpv is connected to the correct sink and that its stream is not reduced. If you use ALSA directly, check the relevant hardware mixer controls and ensure that mpv is not opening a different device than other applications.

On macOS, verify the selected output device and its volume in System Settings or Control Center. HDMI, USB interfaces, aggregate devices, and external displays can have separate controls. Some digital outputs expose fixed software volume, leaving level control to the receiving device.

4.3 Compare audio output drivers carefully

mpv normally chooses an available audio output automatically. A forced ao setting can select an unexpected backend or device. Search mpv.conf for ao= and audio-device=. Temporarily remove or comment out forced values and let mpv auto-select.

Use terminal output to identify the selected audio output and channel layout. GPU drivers, display servers, HDR settings, shaders, and hardware video decoding generally do not control audio loudness. They become relevant only when the audio is carried over HDMI or DisplayPort and a different display or device is selected. Do not change hwdec, HDR tone mapping, or shaders merely because volume is low.

5. Verify Tracks, Streams, URLs, and External Tools

5.1 Confirm the selected audio track

Files and streams may contain several audio tracks with different languages, mixes, channel counts, or loudness. Open mpv's track list through the on-screen interface if available, inspect terminal output, or use the stats overlay. Select each plausible audio track and compare it at the same scene.

Subtitle settings do not change audio volume. However, a profile triggered by subtitle language, filename, or track selection could also contain audio options. Treat subtitles as a profile trigger to investigate, not as a direct audio cause.

5.2 Separate online extraction from playback

For online URLs handled through yt-dlp, mpv may receive a different format or audio stream than a browser. First test a local file. Next, inspect the available tracks and terminal output for the URL. Ensure yt-dlp comes from its official project or your trusted package manager and that mpv can find it.

A yt-dlp path problem usually causes extraction errors rather than merely low volume. A stream can still be quieter because the selected format, commentary track, surround mix, or source master differs. Compare the actual track and format instead of increasing global volume immediately.

Network access, shell quoting, and URL signatures matter when playback fails, stalls, or selects an unexpected resource. They are not primary explanations when a correctly identified stream plays continuously but sounds quiet. Screenshot settings do not affect playback volume and should not be changed for this symptom.

6. Use Logs and Runtime Information

6.1 Capture a focused log

Run mpv from a terminal so warnings and selected audio details remain visible. For a reusable log, use:

mpv --log-file=mpv-volume-test.log --msg-level=ao=debug,af=debug "test-video.mkv"

The exact amount of output varies by build and backend. Look for the selected audio device, channel layout, sample format, filters, audio-track selection, and errors opening an output. Avoid publishing logs without checking them for local paths, usernames, URLs, tokens, or other sensitive information.

6.2 Use stats and profile inspection

Press i for mpv's default stats display, if that binding has not been replaced. The pages can provide track and audio details useful for confirming the codec, channels, and selected stream. The track list and terminal output are often more useful for loudness than video performance statistics.

Use --show-profile=NAME for profiles you suspect. Compare the profile's options with a clean --no-config launch. Logs are most useful for proving what mpv actually selected, not for judging subjective loudness by themselves.

7. Run a Clean Temporary Test Before Making Permanent Changes

Use this controlled sequence so that several changes do not hide the real cause:

1. Choose one local file and one timestamp with clear dialogue and louder peaks.
2. Play it with --no-config --volume=100.
3. Confirm the operating system's per-application volume and output device.
4. Confirm the selected audio track and channel layout.
5. Run your normal configuration and compare the same timestamp.
6. Add back the suspected profile, filter, ReplayGain behavior, or script individually.
7. Only after identifying the cause, make one persistent configuration change.

This process preserves your customized setup and avoids unnecessary changes to hardware decoding, HDR, subtitle styling, screenshots, IPC, shaders, and unrelated video settings. Success is repeatable playback at the expected level after restarting mpv. Once the result repeats, stop troubleshooting.

8. Quick Fix Checklist

• Test a known local file with mpv --no-config --volume=100.
• Check that mpv's displayed volume is not unexpectedly low.
• Confirm volume-max is not preventing the increase you intend.
• Raise software volume moderately and stop if clipping appears.
• Disable ReplayGain temporarily to test tagged audio.
• Remove audio filters temporarily and reintroduce them one at a time.
• Compare surround and native stereo tracks.
• Check Windows Volume Mixer or the Linux and macOS per-app output controls.
• Remove forced ao or audio-device settings for a test.
• Inspect profiles, input bindings, scripts, and IPC automation.
• Use logs and stats to verify the actual device, track, channels, and filters.
• Make only the smallest permanent change that reproduces the successful test.

9. Frequently Asked Questions

9.1 Why is mpv quieter than VLC or my browser?

The applications may use different per-app operating system levels, normalization policies, ReplayGain behavior, audio tracks, or surround-to-stereo downmixing. Compare the same file and track, check the system mixer, and test mpv with --no-config --volume=100. If clean mpv sounds normal, the difference comes from your configuration or scripts.

9.2 Is it safe to set mpv volume above 100?

It can be useful for genuinely quiet material, but software gain above the baseline can clip loud peaks. Increase it moderately, listen to the loudest sections, and stop if you hear distortion. Setting a higher volume-max only raises the permitted ceiling and does not prevent clipping.

9.3 Why is dialogue quiet but music and effects are loud?

The likely cause is a multichannel mix being played through stereo equipment, the wrong audio track, or the source's intentional dynamic range. Select a native stereo track when available and inspect downmix options or filters. A large global volume boost may make effects uncomfortably loud without fixing the mix balance.

9.4 Does hardware decoding affect mpv volume?

Normally, no. Hardware decoding handles video. It is indirectly relevant only if changing displays or video outputs also changes the HDMI or DisplayPort audio device. Verify the selected audio output before modifying hwdec or GPU settings.

9.5 Can yt-dlp cause low mpv volume?

yt-dlp can influence which online format or stream mpv receives, but extraction failures more commonly produce errors than low volume. Inspect the selected online audio track and compare it with a local file. Use official yt-dlp releases or a trusted package manager rather than random binaries.

9.6 Should I delete my mpv configuration folder?

No. Use --no-config for a reversible clean test, then disable individual options, profiles, scripts, or bindings. Deleting the whole folder can erase valuable customization while providing little information about which setting caused the mpv player issue.