MKVToolNix

MKVToolNix is a Docker container that provides a web-based graphical interface to the MKVToolNix suite for creating, altering, and inspecting Matroska files.

  • Media Applications
  • Media Servers
  • Tools & Utilities
MKVToolNix is a Docker container that provides a web-based graphical interface to the MKVToolNix suite for creating, altering, and inspecting Matroska files. The Alpine-based image is resource-efficient and lets homelab users manage tracks, chapters, tags, and attachments from a browser or VNC client without installing desktop tools.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

73/100 Good

Maintained
100last commit 24 days ago
Popular
51334 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
602 GB minimum RAM, runs on ARM
Security check
85no serious findings, CI

Availability: platform listings confirmed today, links checked 8 days ago

GitHub stars
334
Open issues
8
Last commit
2026-10-28
Latest release
v26.10.1
License
MIT
Activity
steady

Checked 22 days ago - source: GitHub (jlesage/docker-mkvtoolnix)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 100 MB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Browser and VNC access After starting the container, open its web port in any modern browser for the full MKVToolNix GUI (no client-side install), or connect with any VNC client. The web interface includes audio playback, clipboard sharing, and an integrated file manager and terminal. source

Fetched 5 days ago - each note links to its source

Alternatives (8)

  • FFmpeg - FFmpeg is an open-source command-line framework for recording, converting, and streaming audio, video, and subtitles.
  • MKVtools - MKVtools was primarily designed for processing mkv files for use in DivX enabled DVD players, it's capabilites have been expanded to allow…
  • Shutter Encoder - Shutter Encoder is a free professional encoding and conversion software for everyone, developed with video editors.
  • Video Transcoder - Video Transcoder is an application which uses the open source program FFmpeg to transcode video files from one format to another.
  • Voukoder Pro
  • makemkv - MakeMKV is a disc-to-MKV format converter that rips proprietary, usually encrypted DVD and Blu-ray discs into patent-unencumbered MKV files…
  • mkvcleaver - MKVCleaver is a lightweight Docker container that provides a browser- or VNC-based GUI for homelabs to extract data from MKV files in batch…
  • tsMuxeR - TsMuxeR is an archived web or VNC front-end for tsMuxer, no longer under development, that remuxes video and audio streams into specificati…

Checked 51 days ago - source: AlternativeTo

Common questions

Which port should I publish to reach the MKVToolNix GUI?

Publish port 5800, as shown in the quick-start docker run example. This is the port used for the web and VNC access in the example.

What should I mount so configuration and media survive container removal?

Mount a config directory, such as /docker/appdata/mkvtoolnix, to /config for configuration, state, logs, and files requiring persistence. The quick-start example also mounts a media folder, such as /home/user, to /storage.

Do I need a VNC client to use the GUI?

No, the full graphical interface can be accessed directly from a modern web browser without client-side downloads, installs, or setup. It can also be accessed with any VNC client if preferred.

Does the browser interface include utilities for files and shell access?

Yes, the web interface provides an integrated file manager and terminal for accessing the container's files and shell. It also supports audio playback, clipboard sharing, and desktop notifications.

Can I protect remote access to the web or VNC interface?

The README documents Web Authentication, Configuring Users Credentials, VNC Password, and certificate options. These sections cover protection for the web interface and VNC access.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads