From ArchWiki
Jump to: navigation, search

mpv is a media player based on MPlayer and MPlayer2. It supports a wide variety of video file formats, audio and video codecs, and subtitle types. A comprehensive (although admittedly incomplete) list of differences between mpv and the aforementioned players can be found here.


Install the mpv package or mpv-gitAUR for the development version.

Front ends

mpv comes with a minimal GUI called On Screen Controller (OSC), that appears when moving the mouse. There are also other front ends available:

  • Baka MPlayer — Free and open source, cross-platform, libmpv based multimedia player (Qt 5). || baka-mplayer, baka-mplayer-gitAUR
  • GNOME MPV — A simple frontend for mpv (GTK+ 3). || gnome-mpvAUR, gnome-mpv-gitAUR || mpc-qt-gitAUR
  • SMPlayer — Qt multimedia player with extra features (CSS themes, YouTube integration, etc.) (Qt 5). || smplayer
  • xt7-player-mpv — Qt/Gambas GUI to mpv with a rich set of configurable options including filters and drivers, ladspa plugins support as well as library/playlist managment, YouTube, online radios, podcasts, DVB-T and more. || xt7-player-mpv-gitAUR


Though mpv comes with good all-around defaults that should work well on computers with weaker/older video cards. However, if you have a computer with a more modern video card then mpv allows you to do a great deal of configuration to achieve better video quality (limited only by the power of your video card). To do this one only needs to create a few configuration files (they do not exist by default).

Note: Configuration files are read system-wide from /etc/mpv and per-user from ~/.config/mpv (unless the environment variable XDG_CONFIG_HOME is set), where per-user settings override system-wide settings, all of which are overridden by the command line. User specific configuration is suggested since it may require some trial and error.

First create the ~/.config/mpv directory if it does not already exist.

$ mkdir ~/.config/mpv

To help you get you started mpv provides a couple empty sample configuration files with a lot of options commented out, they are located at /usr/share/doc/mpv/.

  • mpv.conf will contain the majority of mpv's settings.
  • input.conf will just contain key bindings.

Read through both of them to get an idea of how they work and what options are available. You may copy them to your config folder to use as a starting point if you like:

$ cp /usr/share/doc/mpv/mpv.conf ~/.config/mpv/mpv.conf
$ cp /usr/share/doc/mpv/input.conf ~/.config/mpv/input.conf

General settings - mpv.conf

High quality configurations

This loads high quality OpenGL options. Most users can run these without any problems, but they are not enabled by default to avoid causing problems for the few users who cannot run them.


The opengl-hq profile defaults to the spline36 scaling filter for mid quality and speed. For the best quality video output, the manual states that if your hardware can run it, ewa_lanczossharp is probably what you should use.


These last three options are a little more complicated. The first option makes it so that if audio and video go out of sync then instead of dropping video frames it will resample the audio (a slight change in audio pitch is often less noticeable than dropped frames). The mpv wiki has an in depth article on it titled Display Synchronization. The remaining two essentially make motion appear smoother on your display by changing the way that frames are shown so that the source framerate jives better with your display's refresh rate (not to be confused with SVP's technique which actually converts video to 60fps). The mpv wiki has an in depth article on it titled Interpolation though it is also commonly known as smoothmotion.


Beyond this there is still a lot you can do but things become more complicated, require more powerful video cards, and are in constant development. As a brief overview, it is possible to load special shaders that perform exotic scaling and sharpening techniques including some that actually use deep neural networks trained on images (for both real world and animated content). To learn more about this take a look around the mpv wiki, particularly the user shader's section.

There are also plenty of other options you may find desirable as well. It is worthwhile taking a look at mpv(1). It's also helpful to run mpv from the command line to check for error messages about the config.


In mpv.conf it is possible to create profiles which are essentially just "groups of options" with which you can:

  • Quickly switch between different configurations without having to rewrite the file.
  • Create special profiles for special content.
  • nest profiles so that you can make more complicated profiles out of simpler ones.

Creating a profile is easy. The area at the top of mpv.conf is called the top level, any options you write there will kick into effect once mpv is started. However, once you define a profile by writing its name in brackets then every option you write below it (until you define a new profile) is considered part of that profile. Here is an example mpv.conf:

profile=myprofile2        #Top level area, load myprofile2
ontop=yes                 #Always on top

[myprofile1]              #A simple profile, top level area ends here
profile-desc="a profile"  #Optional description for profile
fs=yes                    #Start in full screen

[myprofile2]              #Another simple profile
profile=opengl-hq         #A built in profile that comes with mpv
log-file=~~/log           #Sets a location for writing a log file, ~~/ translates to ~/.config/mpv

There are only two lines within the top level area and there are two separate profiles defined below it. When mpv starts it sees the first line, loads the options in myprofile2 (which means it loads the options in opengl-hq and log-file=~~/log) finally it loads ontop=yes and finishes starting up. Note, myprofile1 is never loaded because it's never called in the top level area.

Alternatively one could call mpv from the command line with

$ mpv --profile=myprofile1 video.mkv

and it would ignore all options except the ones in myprofile1.

Key bindings - input.conf

Key bindings are actually fairly straightforward given the examples in /usr/share/doc/mpv/input.conf and the relevant section in the manual.

Here is an input.conf file that attempts to reproduce MPC-HC keybindings in mpv.

Here are some more fun examples:

Alt+RIGHT add video-rotate 90
Alt+LEFT add video-rotate -90
Alt+- add video-zoom -0.25
Alt+= add video-zoom 0.25
Alt+j add video-pan-x -0.05
Alt+l add video-pan-x 0.05
Alt+i add video-pan-y 0.05
Alt+k add video-pan-y -0.05

Additional configuration files

In addition there are a few more configuration files one can create:

  • ~/.config/mpv/lua-settings/osc.conf manages the On Screen Controller
  • If you are using any Lua scripts then you can create a corresponding conf file for each one here: ~/.config/mpv/lua-settings/scriptname.conf
  • lots more


mpv has a large variety of scripts that extend the functionality of the player. To this end, it has internal bindings for both Lua and JavaScript (added recently).

Scripts are typically installed by putting them in the ~/.config/mpv/scripts/ directory (you may have to create it first). After that they will be automatically loaded when mpv starts (this behavior can be altered with other mpv options). Some scripts come with their own installation and configuration instructions, so make sure to have a look. In addition some scripts are old, broken, and unmaintained.


Since JavaScript support is still fairly new, there is currently very little in the way of scripts, but documentation exists for anyone interested in making their own.

JavaScript support isn't currently available in the mpv build, but is supported by several AUR packages, including mpv-fullAUR and mpv-build-gitAUR.


There are a lot of interesting Lua scripts for mpv. If you would like to make your own, the relevant documentation may be found here.


mpv-stats (or simply stats) is a Lua script that outputs a lot of live statistics showing how well mpv is currently doing. It is very useful for making sure that your hardware can keep up with your configuration and for comparing different configurations. Since it is very actively maintained you may have to install mpv-gitAUR in order to use it.


mpv-webm (or simply webm) is a very easy to use Lua script that allows one to create WebM files while watching videos. It includes several features and does not have any extra dependencies (relies entirely on mpv).


Vapoursynth is an alternative to AviSynth that can be used on Linux and allows for Video manipulation via python scripts. Vapoursynths python scripts can be used as video filters for mpv.

To use vapoursynth filters you have to install the vapoursynth package (or vapoursynth-gitAUR) and compile mpv with the --enable-vapoursynth build flag.

This is easier to do by first installing Vapoursynth and then installing (or re-installing if it's already installed) mpv-gitAUR. The configure script for mpv-gitAUR will auto-detect Vapoursynth (as long as it has already been installed) and it will automatically compile mpv with support for Vapoursynth without having to manually change any configure options or anything (this makes it very easy to update mpv as well).

SVP 4 Linux (SmoothVideoProject)

SmoothVideoProject SVP is a program that's primarily known for converting video to 60fps. It's free [as in beer] and full featured for 64bit Linux (costs money for Windows and OS X and is incompatible with 32bit Linux).

It has three main features and each one can be disabled/enabled as one chooses (you are not forced to use motion interpolation).

  1. Motion interpolation (youtube video) - An algorithm that converts video to 60fps. This creates the somewhat controversial "soap opera effect" that some people love and others hate. Unfortunately the algorithm is not perfect and it also introduces more than its share of weird artifacts. The algorithm can be tuned (via a slider) for either performance or quality. It also has some artifact reduction settings that interpolate actual frames with the generated frames reducing the noticeability of the artifacts. The framerate detection can be set to automatic or manual (manual seems to resolve performance issues for some users).
  2. Black bar lighting (youtube video) - If the image has an aspect ratio that produces black bars on your display then SVP will illuminate the black bars with "lights" generated by the content on the screen. It has some amount of customization but the defaults are pretty close to optimal.
  3. LED ambient lighting control (youtube video) - Has the ability to control LED ambient lighting attached to your television.

Once you have mpv compiled with Vapoursynth support it's fairly easy to get SVP working with mpv. Simply install svpAUR, open the SVP program to let it assess your system performance (you may want to close other programs first so that it gets an accurate reading), and finally add the following mpv profile to your mpv.conf (taken from here):

input-ipc-server=/tmp/mpvsocket     # Receives input from SVP
hr-seek-framedrop=no                # Fixes audio desync
resume-playback=no                  # Not compatible with SVP

# Can fix stuttering in some cases, in other cases probably causes it. Try it if you experience stuttering.

Then, in order to use SVP you must have the SVP program running in the background before opening the file using mpv with that profile. Either do:

$ mpv --profile=svp video.mkv

or set profile=svp in the top-level portion of the mpv config.

If you want to use hardware decoding then you must use a copy-back decoder since normal decoders are not compatible with Vapoursynth (choose a hwdec option that ends in -copy). For instance:


Either way, hardware decoding is discouraged by mpv devs and is not likely to make a significant difference in performance.

Tips and Tricks

Hardware decoding

See Hardware video acceleration.

Warning: Hardware decoding is known to sometimes cause problems and as such it is considered "usually a bad idea unless absolutely needed" by the developers. For that reason and because it typically offers very similar performance to software decoding it is disabled by default. Moreover, depending on the video card, drivers installed, and file being decoded hardware decoding may perform differently or may not even be used at all leading to inconsistent behavior that can be difficult to debug.
Note: The main difference between hardware decoding and software decoding is that in software decoding the file will be decompressed and then moved onto the video card whereas with hardware decoding it will be moved to the video card first and then decompressed. In either case, video playback will still be hardware accelerated via the video card.

Unlike mplayer and mplayer2, mpv has both VA-API and VDPAU support built-in. To enable it, run mpv with the --hwdec='method' option. You can find list of all available methods looking in the mpv(1) manual. To make this persistent, add the line hwdec=method to your configuration file. If hardware decoding cannot be used, mpv will automatically fall back to software decoding.

The default video output driver, opengl, is the preferred video output driver and all others are offered only for compatibility purposes. If one encounters problems they may choose to use either vo=vdpau (if using hwdec=vdpau) or vo=vaapi (if using hwdec=vaapi) instead. This can affect the framedrop code used and cause other small differences.

Even with hardware decoding enabled, it will only be used for some codecs by default (at the time of writing this list includes: h264, vc1, wmv3, hevc, mpeg2video, vp9). In order to use hardware decoding with all codecs set hwdec-codecs=all. It is also possible to specify an exact list of codecs for which you want hardware decoding to be used (provided it has been enabled) by setting --hwdec-codecs=h264,mpeg2video.

In GNOME Wayland

Because GNOME in Wayland mode also runs an Xorg server, video acceleration will fail with [vaapi] libva: va_getDriverName() failed with unknown libva error,driver_name=(null). To make mpv use the Wayland compositor, add the mpv option opengl-backend=wayland [1].

Save position on quit

By default you can save the position and quit by pressing Shift+q. The shortcut can be changed by setting quit_watch_later in the key bindings configuration file.

To automatically save the current playback position on quit, start mpv with --save-position-on-quit, or add save-position-on-quit to the configuration file.

Volume is too low

Set volume-max=value in your configuration file to a reasonable amount, such as volume-max=600. Additionally (or alternatively), you can utilize dynamic range compression with af=acompressor.

Quickly cycle between aspect ratios

You can cycle between aspect ratios using Shift+a from version 0.8.0 onwards.

Ignoring aspect ratio

You can ignore aspect ratio using --keepaspect=no. To make option permanent, add line keepaspect=no to configuration file.

Draw to the root window

Run mpv with --wid=0. mpv will draw to the window with a window ID of 0.

Always show GUI

It may be useful to always show the GUI window, even for audio files, especially when mpv is not started from terminal. This can be done by using --force-window option.

Hide GUI for video files

It may be useful to hide the GUI window for video files. This can be done by using --no-video option.

Restoring old OSC

Since version 0.21.0, mpv has replaced the on-screen controls by a bottombar. In case you want on-screen controls back, you can edit the mpv configuration as described here.

Use as a browser plugin

With the help of mozpluggerAUR, mpv can be used in a supported browser to play video. See Browser plugins#MozPlugger for configuration details. This coupled with a user script such as ViewTube, allows you to use mpv in place of a site's integrated video player.

It may be needed to specify a valid user agent for HTTP streaming, e.g. user-agent="Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0".

Browser plugins#Multimedia playback page shows other easy ways to watch videos.

Improving mpv as a music player with Lua scripts

The development of mpv's Lua scripts are documented in DOCS/man/lua.rst and examples are shown in TOOLS/lua of the mpv repository. This blog post introduces the music.lua script, which shows how Lua scripts can be used to improve mpv as a music player. streaming over mpv

If youtube-dl is installed, mpv can directly open a Twitch livestream.

Alternatively, streamlink can be used to stream Twitch. If you want a GUI for launching these streams use streamlink-twitch-guiAUR. See Livestreamer#Twitch.

Another alternative based on Livestreamer is this Lua script:

youtube-dl and choosing formats

The default --ytdl-format is bestvideo+bestaudio/best. For youtube videos that have 4K resolutions available, this may mean that your device will struggle to decode 4K VP9 encoded video in software even if the attached monitor is much lower resolution.

Setting the right youtube-dl format selectors can fix this easily though. In the following configuration example, only videos with a vertical resolution of 1080 pixels or less will be considered.


If you wish to avoid a certain codec altogether because you cannot hardware-decode it, you can add this to the format selector. For example, we can additionally choose to ignore VP9 as follows:


If you prefer best quality open codecs (VP9 and Opus), use:


youtube-dl audio with search

To find and play audio straight from your terminal with mm "search terms" put the following function in your .bashrc:

function mm() {
    mpv --no-video --ytdl-format=bestaudio ytdl://ytsearch:"$@"

Use mpv with a compositor

If you are using a compositor (e.g. in KDE Plasma 5) and find that composition is disabled (e.g. in Plasma this would make you unable to present windows or see window thumbnails in the default app switcher) when mpv is playing a video, try x11-bypass-compositor=no

Creating a single screenshot

An example of creating a single screenshot, by using a start time (HH:MM:SS):

$ mpv --no-audio --start=00:01:30 --frames=1 /path/to/video/file --o=/path/to/screenshot.png

Screenshots will be saved in /path/to/screenshot.png.

GNOME Blank screen (Wayland)

MPV may not suspend GNOME's Power Saving Settings if using Wayland (resulting in screen saver turning off the monitor while video is playing for example). A workaround is to add gnome-session-inhibit to the beginning of the Exec= line in mpv.desktop.


General debugging

If you are having trouble with mpv's playback (or if it's flat out failing to run) then the first three things you should do are:

  1. Run mpv from the command line. If you are lucky there will be an error message there telling you what is wrong.
    $ mpv video.mkv
  2. Have mpv output a log file. The log file might be difficult to sift through but if something is broken you might see it there.
    $ mpv --log-file=./log video.mkv
  3. Run mpv without a configuration. If this runs well then the problem is somewhere in your configuration (perhaps your hardware cannot keep up with your settings).
    $ mpv --no-config video.mkv

If mpv runs but it just does not run well then a fourth thing that might be worth taking a look at is installing the mpv-stats script and using it to see exactly how it's performing.

Fix jerky playback and tearing

mpv defaults to using the OpenGL video output device setting on hardware that supports it. In cases such as trying to play video back on a 4K display using a Intel HD4XXX series card or similar, you will find video playback unreliable, jerky to the point of stopping entirely at times and with major tearing when using any opengl output setting. If you experience any of these issues, using the XV (XVideo) video output device may help:


This VO is deprecated and will cause issues in recent versions of mpv, most noticeably is the osd looking very blurry.

It is possible to increase playback performance even more (especially on lower hardware), but this decreases the video quality dramatically in most cases.

The following options may be considered to increase the video playback performance:


Problems with window compositors

Window compositors such as KWin or Mutter can cause trouble for playback smoothness. In such cases, it may help to set x11-bypass-compositor=yes to make mpv also disable window compositing when playing in windowed mode (if supported by the compositor).

With KWin compositing and hardware decoding, you may also want to set x11-bypass-compositor=no to keep compositing enabled in fullscreen, since reanabling compositing after leaving fullscreen may introduce stutter for a period of time.

No volume bar, cannot change volume

Spin the mouse wheel over the volume icon.