Softwr

Entertainment · head to head

mpv vs RetroArch

mpv logo

mpv

Entertainment

Free open source command line video player with no graphical interface, built for scripting and precision

From
Free
Rated
-
Full reviewWebsite
R

RetroArch

Gaming

Open source frontend running dozens of emulators as interchangeable cores behind one interface

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: mpv there is no graphical interface at all by default, so a typical non-technical user will find it unusable without significant setup.; RetroArch the menu system is dense and unintuitive, and first-time setup defeats a meaningful number of users before they launch anything.
  • They diverge on capability: mpv covers Command line control, RetroArch covers Core-based architecture.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which mpv and RetroArch actually diverge.

Attributes where mpv and RetroArch differ
AttributempvRetroArch
PlatformsMac, Windows, LinuxWindows, Linux, macOS, Android, iOS
CategoryEntertainmentGaming

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in mpv

  • Command line control
  • Lua and JavaScript scripting
  • Plain text configuration
  • Minimal on-screen overlay
  • Embeddable engine

Only in RetroArch

  • Core-based architecture
  • Run-ahead latency reduction
  • Shader pipeline
  • Netplay
  • Save states and rewind

Both cover

  • Cross-platform

What people use each for

The jobs each tool is most often brought in to do.

mpv

  • A developer who wants to script or automate media playback rather than click through a graphical appnot RetroArch
  • A Linux user who wants a lightweight player without the overhead of a full desktop application shellnot RetroArch
  • Someone embedding video playback into another tool or workflow rather than using it as a standalone appnot RetroArch
  • A power user who prefers editing a text config file over navigating a settings panelnot RetroArch

RetroArch

  • Running several console emulators with one controller configuration instead of configuring each separatelynot mpv
  • Reducing input lag on a modern display where standalone emulators feel unresponsivenot mpv
  • Building a handheld or single-board retro machine with a consistent interfacenot mpv
  • Playing with period-accurate display shaders rather than raw upscaled outputnot mpv

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

mpv

  • There is no graphical interface at all by default, so a typical non-technical user will find it unusable without significant setup.
  • It has no library browser, artwork fetching or organised media collection view, unlike IINA or Infuse.
  • There is no Apple TV, iOS or Android version, so it cannot be used for a living room or mobile streaming setup.
  • Configuration is entirely file and flag based, so getting a specific behaviour set up correctly has a real learning curve compared with a settings panel.
  • Because it is a general-purpose engine rather than a consumer product, there is no dedicated support channel beyond community forums and documentation.

RetroArch

  • The menu system is dense and unintuitive, and first-time setup defeats a meaningful number of users before they launch anything.
  • Core quality varies widely because each is maintained separately, so accuracy, performance and update frequency differ from system to system with no clear signal of which is which.
  • Several systems need BIOS files that the project does not and will not supply, so those cores do nothing until the user sources files whose legality depends entirely on their origin.
  • Controller configuration is the most common point of failure, particularly with multiple controllers or a mix of wired and wireless devices.
  • Project governance has been publicly contentious and some emulator authors decline to have their work distributed as cores, so certain systems are better served by standalone emulators.

Pricing, plan by plan

mpv

Free
  • mpvFree
    • Free and open source under GPL or LGPL depending on build
    • No account, subscription or paid tier
    • Cross-platform, same engine on every OS

RetroArch

Free
  • RetroArchFree
    • Full functionality
    • All cores free
    • No games or BIOS included

Which should you pick?

Choose mpv if

  • You need command line control.
  • You want to start without paying.
  • You work on Mac, Windows, Linux.
  • You also want lua and javascript scripting.
mpv review

Choose RetroArch if

  • You need core-based architecture.
  • You want to start without paying.
  • You work on Windows, Linux, macOS, Android, iOS.
  • You also want run-ahead latency reduction.
RetroArch review

Questions people ask

Is mpv or RetroArch better?
Neither clearly leads. mpv starts at Free and RetroArch at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, mpv or RetroArch?
mpv starts at Free and RetroArch at Free.
Does mpv or RetroArch run on more platforms?
mpv runs on Mac, Windows, Linux. RetroArch runs on Windows, Linux, macOS, Android, iOS.
Can I use mpv for free?
Both have a free tier, so you can try either at no cost before committing.
What is mpv best used for?
mpv is most often used for a developer who wants to script or automate media playback rather than click through a graphical app, a linux user who wants a lightweight player without the overhead of a full desktop application shell, someone embedding video playback into another tool or workflow rather than using it as a standalone app, a power user who prefers editing a text config file over navigating a settings panel. Of those, a developer who wants to script or automate media playback rather than click through a graphical app and a linux user who wants a lightweight player without the overhead of a full desktop application shell are not what RetroArch is typically brought in for.
What can mpv do that RetroArch cannot?
mpv covers Command line control, Lua and JavaScript scripting, Plain text configuration, Minimal on-screen overlay. RetroArch covers Core-based architecture, Run-ahead latency reduction, Shader pipeline, Netplay. Both handle Cross-platform.

Answered from the vendors’ own pages

mpv: Is mpv free?

Yes, entirely, and it is open source with no paid tier of any kind.

RetroArch: Does RetroArch come with games?

No. It ships no game content and no BIOS images. Whether your setup is lawful depends on what you supply and where it came from.

mpv: Does mpv have a GUI?

Not by default. It shows the video and a minimal overlay, but there are no menus, library or settings panel; IINA is the graphical Mac interface built on the same engine.

RetroArch: Why does it feel more responsive than a standalone emulator?

Run-ahead computes frames in advance to remove input lag, which most standalone emulators do not implement.

mpv: Can mpv play from network shares or cloud storage?

It can play many stream types via command line arguments, but it has no built in browsable network or cloud library the way Infuse does.

RetroArch: Is it hard to set up?

The first hour is the hard part, mostly downloading cores and configuring controllers. After that it is consistent across every system it runs.

Share

Related pages

More on mpv

More on RetroArch

Keep looking

Other head to heads