Indexed by TopGit from live GitHub metadata: mpv-player/mpv has 37.4k stars, written primarily in C. 🎥 Command line media player
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
mpv is a free (as in freedom) media player for the command line. It supports
a wide variety of media file formats, audio and video codecs, and subtitle types.
There is a FAQ.
Releases can be found on the release list.
System requirements
A not too ancient Linux (usually, only the latest releases of distributions
are actively supported), Windows 10 1607 or later, or macOS 10.15 or later.
A somewhat capable CPU. Hardware decoding might help if the CPU is too slow to
decode video in realtime, but must be explicitly enabled with the --hwdec
option.
A not too crappy GPU. mpv's focus is not on power-efficient playback on
embedded or integrated GPUs (for example, hardware decoding is not even
enabled by default). Low power GPUs may cause issues like tearing, stutter,
etc. On such GPUs, it's recommended to use --profile=fast for smooth playback.
The main video output uses shaders for video rendering and scaling,
rather than GPU fixed function hardware. On Windows, you might want to make
sure the graphics drivers are current. In some cases, ancient fallback video
output methods can help (such as --vo=xv on Linux), but this use is not
recommended or supported.
mpv does not go out of its way to break on older hardware or old, unsupported
operating systems, but development is not done with them in mind. Keeping
compatibility with such setups is not guaranteed. If things work, consider it
a happy accident.
Downloads
For semi-official builds and third-party packages please see
mpv.io/installation.
Changelog
There is no complete changelog; however, changes to the player core interface
are listed in the interface changelog.
Changes to the C API are documented in the client API changelog.
The release list has a summary of most of the important changes
on every release.
Changes to the default key bindings are indicated in
restore-old-bindings.conf.
Changes to the default OSC bindings are indicated in
restore-osc-bindings.conf.
Compilation
Compiling with full features requires development files for several
external libraries. Mpv requires meson
to build. Meson can be obtained from your distro or PyPI.
After creating your build directory (e.g. meson setup build), you can view a list
of all the build options via meson configure build. You could also just simply
look at the meson_options.txt file. Logs are stored in meson-logs within
your build directory.
For libplacebo, meson can use a git check out as a subproject for a convenient
way to compile mpv if a sufficient libplacebo version is not easily available
in the build environment. It will be statically linked with mpv. Example:
X development headers (xlib, xrandr, xext, xscrnsaver, xpresent, libvdpau,
libGL, GLX, EGL, xv, ...)
Audio output development headers (libasound/ALSA, pulseaudio)
FFmpeg libraries (libavutil libavcodec libavformat libswscale libavfilter
and either libswresample or libavresample)
libplacebo
zlib
iconv (normally provided by the system libc)
libass (OSD, OSC, text subtitles)
Lua (optional, required for the OSC pseudo-GUI and youtube-dl integration)
libjpeg (optional, used for screenshots only)
uchardet (optional, for subtitle charset detection)
nvdec and vaapi libraries for hardware decoding on Linux (optional)
Libass dependencies (when building libass):
gcc or clang, nasm on x86 and x86_64
fribidi, freetype, fontconfig development headers (for libass)
harfbuzz (required for correct rendering of combining characters, particularly
for correct rendering of non-English text on macOS, and Arabic/Indic scripts on
any platform)
FFmpeg dependencies (when building FFmpeg):
gcc or clang, nasm on x86 and x86_64
OpenSSL or GnuTLS (have to be explicitly enabled when compiling FFmpeg)
libx264/libmp3lame/libfdk-aac if you want to use encoding (have to be
explicitly enabled when compiling FFmpeg)
For native DASH playback, FFmpeg needs to be built with --enable-libxml2
(although there are security implications, and DASH support has lots of bugs).
AV1 decoding support requires dav1d.
For good nvidia support on Linux, make sure nv-codec-headers is installed
and can be found by configure.
Most of the above libraries are available in suitable versions on normal
Linux distributions. For ease of compiling the latest git master of everything,
you may wish to use the separately available build wrapper (mpv-build)
which first compiles FFmpeg libraries and libass, and then compiles the player
statically linked against those.
If you want to build a Windows binary, see Windows compilation.
Release cycle
Once or twice a year, a release is cut off from the current development state
and is assigned a 0.X.0 version number. No further maintenance is done, except
in the event of security issues.
The goal of releases is to make Linux distributions happy. Linux distributions
are also expected to apply their own patches in case of bugs.
Releases other than the latest release are unsupported and unmaintained.
See the release policy document for more information.
Bug reports
Please use the issue tracker provided by GitHub to send us bug
reports or feature requests. Follow the template's instructions or the issue
will likely be ignored or closed as invalid.
Questions can be asked in the discussions or on IRC (see
Contact below).
Contributing
Please read contribute.md.
For small changes you can just send us pull requests through GitHub. For bigger
changes come and talk to us on IRC before you start working on them. It will
make code review easier for both parties later on.
You can check the wiki
or the issue tracker
for ideas on what you could contribute with.
License
GPLv2 "or later" by default, LGPLv2.1 "or later" with -Dgpl=false.
See details.
History
This software is based on the MPlayer project. Before mpv existed as a project,
the code base was briefly developed under the mplayer2 project. For details,
see the FAQ.
Contact
Most activity happens on the IRC channel and the GitHub issue tracker.
The most recent commit recorded on mpv-player/mpv was 2 months ago, based on the GitHub push timestamp. The repository has 3.6k forks — one of the better signals of community interest.
How many stars does mpv-player/mpv have?
mpv-player/mpv has 37.4k GitHub stars — refresh the page for the live number, or check github.com/mpv-player/mpv. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is mpv-player/mpv open source?
TopGit's metadata for mpv-player/mpv does not record a license. Most public repositories on GitHub ARE open source, but the exact terms vary — verify by opening the LICENSE file directly.
What else is in the Image Tools space?
mpv-player/mpv is tracked by TopGit under the Image Tools category, alongside 7 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What is mpv-player/mpv?
mpv-player/mpv (mpv-player/mpv) is a C project on GitHub. From the project's own README: 🎥 Command line media player
What language is mpv-player/mpv written in?
mpv-player/mpv is written primarily in C. GitHub's language field is based on the largest share of bytes in the default branch.
Where do I read more about mpv-player/mpv?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/mpv-player/mpv is the definitive source.
Read full README in the tab above.
Want a second opinion on mpv?
Ask an AI that can read this page — one click and you get its take on mpv.
/mpv
