mpv
mpv 0.41.0 is a cross-platform command-line media player and embedded playback engine with GPU rendering, subtitles, scripts, configuration files, IPC and libmpv support.
What mpv does
mpv is a command-line media player and embeddable playback engine for local and network media. It combines broad format support with GPU rendering, subtitles, scripts, configuration files, IPC and the libmpv API. Its flexibility comes with a requirement to understand parameters, build options and extension permissions.
Version and rendering changes
Version 0.41.0 makes gpu-next the default video output and favors Vulkan when hardware decoding is explicitly enabled. The result depends on the GPU, driver, display protocol, file encoding, FFmpeg and libplacebo versions, so a clean default configuration is the right baseline after an upgrade.
Builds and optional features
Official CI assets do not include every optional capability, and Linux distributions may compile different features. Do not infer that an individual binary supports encoding, a protocol or a script merely because mpv as a project supports it. Check the build information and package source.
Scripts, network media and IPC
Lua or JavaScript scripts can read files, access networks and run player commands; IPC can control a running player. Use trusted scripts, restrict the socket to the current user and avoid putting tokens, cookies or sensitive paths in configuration and logs.
Maintenance note
Review date: 2026-08-23. The page was checked against mpv 0.41.0, gpu-next and Vulkan changes, hardware-decoding defaults, build differences, scripts, IPC and dual licensing.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave mpv to this cloud drive
Baidu Netdisk
Save mpv to this cloud drive
mpv 0.41.0 installation, gpu-next and configuration guide
Play a local SDR sample with default settings first, then enable hardware decoding, HDR, scripts or network playback one at a time while keeping a commented configuration backup.
Before you start
- Match Windows, macOS or Linux architecture and package source, and record the build information for the 0.41.0 binary.
- Update the graphics driver, prepare SDR, HDR and subtitle samples and note the display protocol and audio device.
- Back up mpv.conf, input.conf and the scripts directory, removing tokens, cookies and network credentials from the backup.
Installation steps
- 01
Install or extract 0.41.0
Use a matching Windows or macOS archive or a trusted Linux package, then run the version command and inspect the compile-time features before copying old settings.
- 02
Play a local sample with no custom configuration
Temporarily move user configuration and scripts aside, test video, subtitles, audio, screenshots and the on-screen controller and keep the result as a baseline.
- 03
Create a minimal configuration
Add low-risk window, subtitle and volume options first. Enable hardware decoding separately and keep comments explaining each non-default choice.
Quick start
- 01
Verify gpu-next and color
Test SDR and HDR with the default gpu-next output. If colors shift, remove custom LUTs, ICC settings and shaders before inspecting the display color path.
- 02
Test hardware decoding
Enable hardware decoding explicitly, observe logs and CPU/GPU usage and check for dropped frames. Restore software decoding before investigating drivers or API support after a failure.
- 03
Isolate scripts and network playback
Add scripts individually and review their permissions. Use yt-dlp only for media you are permitted to access, keep IPC local to the current user and disable it after testing.
Usage tips
- Version 0.41.0 was released on 2025-12-21, makes gpu-next the default output and prefers Vulkan when hardware decoding is enabled.
- This line expects FFmpeg 6.1 or later and a recent libplacebo, while distribution builds can provide different compile-time features.
- Official CI assets do not contain every optional feature, including some encoding capabilities. Verify the actual binary instead of relying on a generic project description.
- Configuration, scripts, protocol handlers and libmpv front ends can change the security boundary. Return to a no-script default profile when troubleshooting.
Troubleshooting and uninstall
Why are HDR colors wrong or the video blank on Wayland?
Remove custom shaders and color options, restore default gpu-next and software decoding, then check ICC data, driver, Wayland color protocol and display mode one variable at a time.
Why does a network URL or yt-dlp source fail?
Confirm a local file still plays, update a trusted yt-dlp build and check whether the site requires login, uses DRM or changed its interface. Keep cookies and scripts out of copied logs.
- Keep a clean configuration recordSave only the mpv.conf, input.conf and script list you understand and need, and remove tokens, cookies, network credentials and IPC endpoints from the archive.
- Remove the program and optional dataUninstall the package or delete the application directory. Remove user configuration, cache and scripts only after confirming that no other libmpv front end depends on them.
Frequently asked questions
Why does mpv have no traditional player interface?
mpv is centered on command-line controls and a compact on-screen controller. Users who need a library view or dialogs can choose a libmpv front end, but each front end has its own version and permission profile.
Is hardware decoding enabled automatically?
Hardware decoding is not enabled by default and should be configured explicitly. GPU, driver, codec, display protocol and build options determine whether a selected path works.
Can mpv scripts and IPC be treated as harmless extensions?
No. Scripts can access files or networks and IPC can control the player. Use trusted code, restrict the socket and remove scripts when they are not required.