ENGLISH | 简体中文
- About
- Download
- Installation
- Support
- Config Folder
- Input and context menu
- Command Line Interface
- Terminal
- mpv.net specific commands
- mpv.net specific options
- External Tools
- Scripting
- Extensions
- Color Theme
- Advanced Features
- Differences compared to mpv
- Environment Variables
- user-data
- Contributing
- Context Menu Commands
mpv.net is a media player for Windows that has a modern GUI.
The player is based on the popular mpv media player. mpv.net is designed to be mpv compatible, almost all mpv features are available, this means the official mpv manual applies to mpv.net, differences are documented in this manual under Differences compared to mpv.
- Stable and beta portable and setup via GitHub download
- Stable via command line with winget:
winget install mpv.net - Automated nightly portable builds
- Windows 10 or higher.
- .NET Desktop Runtime 6.0
Internet streaming requires:
- Downloading yt-dlp and adding its folder to the user environment variable PATH. Alternativly the yt-dlp executable can be saved in the mpv.net executable folder.
- In case of proxy server usage, manual configuration.
File Associations can be registered using the context menu under Config > Setup.
After the file associations were registered, it might still be necessary to change the default app in the Windows settings.
Another way to register file associations is using Windows File Explorer,
select a media file and select Open with > Choose another app in the context menu.
Open with++ can be used to extend the File Explorer context menu
to get menu items for Play with mpv.net and
Add to mpv.net playlist.
Alternativly the Send To feature of Windows File Explorer can be used.
In order to use mpv.net in a terminal for advanced use cases,
mpv.net can be added to the Path environment variable, it allows
to run mpv.net in a terminal by typing mpvnet. The easiest way
to add mpv.net to path is:
Context Menu > Config > Setup > Add mpv.net to Path environment variable
For more information see the terminal section.
It's recommended to install the Command Palette user script, the installer script can be invoked from:
Context Menu > Config > Setup > Install Command Palette
Before making a support request, please try the newest beta version first.
Support can be requested here:
mpv.net bug reports, feature requests and advanced questions:
https://github.com/mpvnet-player/mpv.net/issues
Beginner mpv questions:
https://www.reddit.com/r/mpv
Advanced mpv questions:
https://github.com/mpv-player/mpv/issues
https://github.com/mpv-player/mpv/discussions
mpv.net searches the config folder at:
- Folder defined via MPVNET_HOME environment variable.
- startup\portable_config (startup means the directory containing mpvnet.exe)
%APPDATA%\mpv.net(C:\Users\Username\AppData\Roaming\mpv.net)
The config folder can be easily opened with:
Context Menu > Config > Open Config Folder
The most important files and folders in the config folder are:
mpv.conffile containing the mpv configuration.mpvnet.conffile containing the mpv.net configuration.input.conffile containing mpv key and mouse input bindings.scriptsfolder containing mpv user scripts.script-optsfolder containing user scripts configuration files.
Global keyboard shortcuts are supported via global-input.conf file.
The config folder can be opened from the context menu: Config > Open Config Folder
A input and config editor can be found in the context menu under Config.
The input test mode can be started via command line: --input-test
The input key list can be printed with --input-keylist.
mpv input.conf defaults:
https://github.com/mpv-player/mpv/blob/master/etc/input.conf
mpv input commands:
https://mpv.io/manual/master/#list-of-input-commands
mpv input options:
https://mpv.io/manual/master/#input
Before version v7 all bindings and the context menu definition were defined in the input.conf file, which mpv.net created in case it didn't exist. This had the disadvantage that mpv.net lost control over all default bindings and context menu defaults. This was unfortunate, v7 introduces a new bindings and context menu design fixing it.
In v7 no input.conf file is created, the default bindings and context menu is defined internally. input.conf only contains what is different from the internally defined defaults, so it works the same as it works in mpv.
For backward compatibility the old input.conf context menu
format with the menu definition using #menu: is still
supported. The new design also allows for a menu customization,
in a sub section called Custom. In input.conf it can be
defined like so:
Ctrl+a show-text Test #custom-menu: Test > Test
Users that have their bindings and context menu customized
before v7 can easily migrate to the new design by deleting
bindings they don't use and remember the shortcut and remove
#menu: everywhere, it's important to remove #menu:
everywhere in order to enable the new mode/design.
mpvnet [options] [file|URL|PLAYLIST|-]
mpvnet [options] files
mpv properties can be set with the same syntax as mpv, that is:
To enable the border property:
--border or --border=yes
To disable the border property:
--no-boder or --border=no
Supported are all mpv properties, they are documented here:
https://mpv.io/manual/master/#properties
mpv has a few non property based switches which are generally not supported in mpv.net.
When mpv.net is started from a terminal it will output status, error and debug messages to the terminal and accept input keys from the terminal.
script-message-to mpvnet <command> <arguments>
Adds mpv.net to the Path environment variable.
Removes mpv.net from the Path environment variable.
Opens mpv.conf or input.conf in a text editor.
Shows a file browser dialog to open external audio files.
For automatic detection of external audio files based on the file name,
use the mpv option audio-file-auto, it can be found it the config dialog:
Context Menu > Config > Show Config Editor > Audio > audio-file-auto
Shows a file browser dialog to open external subtitle files.
For automatic detection of external subtitle files based on the file name,
use the mpv option sub-auto, it can be found it the config dialog:
Context Menu > Config > Show Config Editor > Subtitles > sub-auto
Moves the Window to the screen edge (Alt+Arrow) or center (Alt+BS).
Opens the config folder with Windows File Explorer.
append
Appends files to the playlist.
Opens a file browser dialog in order to select files to be opened. The file browser dialog supports multiselect to load multiple files at once.
Supported are media files and Blu-ray and DVD ISO image files.
Shows a folder browser dialog to open a DVD or BD folder. ISO images don't have to be mounted, but instead can be opened directly with the open-files command.
Opens URLs or filepaths from the clipboard, or files in the file clipboard format.
append
Appends files/URLs to the playlist.
Cycles the pause property. In case the playlist is empty, the most recent file from the recent files list is loaded.
Registers the file associations.
Decreases or increases the Window size.
Shell executes a single file or URL.
Shows the about dialog.
Shows available audio devices in a message box.
Shows available mpv input commands.
Shows available properties.
Shows available input keys.
Shows available protocols.
Shows available decoders.
Shows available demuxers.
Shows the conf editor.
Shows the input editor.
msgbox
Shows media info in a messsage box.
editor
Shows media info in a text editor.
osd Shows media info on screen.
full
Shows fully detailed media info.
raw
Shows media info with raw property names.
Shows the context menu.
Shows available profiles with a message box.
Shows a OSD message with given text, duration and font size.
Shows a menu to select the stream quality.
Works similar as the window-scale mpv property.
mpv.net specific options can be found in the conf editor searching for 'mpv.net'.
The options are saved in the mpvnet.conf file.
Initial window height in percent for audio files. Default: 70
Initial window height in percent for image files. Default: 80
Adds files to the playlist, requires --process-instance=single. Open with++ can be used to add files to the playlist using File Explorer.
Sends a input command to a running mpv.net instance via command line, for instance to create global keyboard shortcuts with AutoHotkey. Requires process-instance=single.
Save and restore the audio device chosen in the context menu. Default: yes
Save volume and mute on exit and restore it on start. Default: yes
Setting to remember the window size.
width-session
Width is remembered in the current session.
width-always
Width is always remembered.
height-session
Height is remembered in the current session. Default
height-always
Height is always remembered.
video
Window size is set to video resolution.
session
Window size is remembered in the current session.
always
Window size is always remembered.
Minimum aspect ratio of the window. Useful to force a wider window and therefore a larger OSC.
Same as minimum-aspect-ratio but used for audio files.
Save the window position on exit. Default: no
Threshold in milliseconds to wait for libmpv returning the video resolution before the window is shown, otherwise default dimensions are used as defined by autofit and start-size. Default: 1500
For single files automatically load the entire directory
into the playlist. This option by default is disabled.
The option is deprecated because mpv now has native
support for it using autocreate-playlist,
which by default mpv.net sets to autocreate-playlist=filter.
Used menu syntax for defining the context menu in input.conf.
mpv.net by default uses #menu:, uosc uses #! by default.
Defines if more then one mpv.net process is allowed.
Whenever the CTRL key is pressed when files or URLs are opened, the playlist is not cleared but the files or URLs are appended to the playlist. This not only works on process startup but in all mpv.net features that open files and URLs.
Multi can alternatively be enabled by pressing the SHIFT key.
multi
Create a new process everytime the shell starts mpv.net.
single
Force a single process everytime the shell starts mpv.net. Default
queue
Force a single process and add files to playlist.
Amount of recent files to be remembered. Default: 15
Usage of the media info library instead of mpv to access media information. Default: yes (mpv.net specific option)
Enable this only when a developer asks for it. Default: no
User interface display language. mpv.net must be restarted after a change.
Work on the translation is done with transifex:
https://app.transifex.com/stax76/teams/
Enables a dark theme.
always
Default
system
Available on Windows 10 or higher.
never
Color theme used in dark mode. Default: dark
Color theme used in light mode. Default: light
In order to play videos from sites such as YouTube the Chrome Extension Play with mpv can be used.
Due to Chrome Extensions not being able to start a app, another app that communicates with the extension is required, this app can be downloaded here. The extension works only when the app is running, to have the app always running a link can be created in the auto start folder located at:
C:\Users\%username%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
This will start the app on system start and have it running in the background. When the file association registration of mpv.net was executed then the app should find the location of mpv.net, alternativly the mpv.net folder can be added to the Path environment variable.
Alternatively the Chrome/Firefox extension Open With can be used.
Open with++ can be used to extend the File Explorer context menu to get menu items for Play with mpv.net and Add to mpv.net playlist.
Videos can be streamed or downloaded easily with the Chrome extension External Application Launcher, for download (recommended):
path: wt
args: -- powershell -NoLogo -Command "yt-dlp --ignore-errors --download-archive 'C:\External Application Button.txt' --output 'C:\YouTube\%(channel)s - %(title)s.%(ext)s' ('[HREF]' -replace '&list=.+','')"
A very large collection of user scripts can be found in the GitHub repository awesome-mpv.
Lua scripting is documented in the mpv.net wiki here.
.NET Extensions are located in a subfolder extensions in the config folder, the filename must have the same name as the directory:
<config folder>\extensions\ExampleExtension\ExampleExtension.dll
mpv.net supports custom color themes, the definition of the built-in themes can be found at:
Custom themes can be saved at:
<conf folder>\theme.conf
The theme.conf file may contain multiple themes.
In the config editor under UI there are the options dark-theme and light-theme to define the themes used in dark and in light mode.
vpy files are supported with following mpv.conf configuration:
[extension.vpy]
demuxer-lavf-format = vapoursynth
Python and VapourSynth must be in the path environment variable.
mpv.net is designed to work exactly like mpv, there are a few differences and limitations:
The configuration folder is named mpv.net instead of mpv:
C:\Users\username\AppData\Roaming\mpv.net
mpv.net implements an own main window which means only mpv window features are supported that have an own implementation in mpv.net.
A window free mode is currently not supported, the main window is always visible, even when mpv.net is started from the terminal and music is played.
For mpv.net it's currently not possible to find out where OSC menus are located, but there are 3 features that require this information, therefore mpv.net makes the assumption that near the window borders might be OSC menus. As a result the following three features, work only when invoked from the center of the window:
- Window dragging (moving the window with the mouse).
- Showing the context menu.
- Auto hiding the mouse cursor.
When the mouse is near a window border, these 3 features are not available. The dead zone sizes are 10% left, top, right and 22% bottom.
The documentation of mpv's window features can be found here:
https://mpv.io/manual/master/#window
mpv.net has currently implemented the following window properties:
- border
- cursor-autohide
- fullscreen
- keepaspect-window
- ontop
- screen
- snap-window
- title-bar
- title
- window-maximized
- window-minimized
- window-scale
Partly implemented or modified:
<int> Initial window height in percent. Default: 60
<int> Minimum window height in percent. Default: 10
<int> Maximum window height in percent. Default: 80
Initial window location in percent. Default: 50:50 (centered)
Requires Windows 11, on Windows 10 it works slightly incorrect due to invisible borders.
x=0 docks the window to the left side.
x=100 docks the window to the right side.
y=0 docks the window to the top side.
y=100 docks the window to the bottom side.
Shows the window title bar. Default: yes
mpv.net specific window features:
mpv.net specific window features are documented in the screen section.
mpv.net supports property based mpv command line options which means it supports almost all mpv command line options.
What is not supported are non property bases options. Non property based options need an own implementation in mpv.net, so far implemented are:
--ad=help
--audio-device=help
--input-keylist
--profile=help
--vd=help
--version
The mpv property idle can be
used and mpv.net functions accordingly, but Lua scripts always see idle=yes
because mpv.net has to set it to function correctly, this is a difficult
to overcome libmpv limitation.
Options that are specific to mpv.net can be found by entering mpv.net in the search field of the config editor, in the mpv.net manual they are documented here.
mpv.net specific options are saved in the file mpvnet.conf and are just as mpv properties available on the command line.
Directory where mpv.net looks for the user configuration.
Script authors can access the following user-data properties:
user-data/frontend/name
user-data/frontend/version
user-data/frontend/process-path
Work on the translation is done with transifex, translators have to create a transifex account:
https://app.transifex.com/stax76/teams/
For translation questions visit: