Create, modify and inspect Matroska (MKV) files for Windows PC

MKVToolNix (32-bit)

MKVToolNix 33.0.0 (32-bit)

  -  15.29 MB  -  Open Source

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system.

Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of MKVToolNix 33.0.0 (32-bit).


For those interested in downloading the most recent release of MKVToolNix (32-bit) or reading our review, simply click here.


All old versions distributed on our website are completely virus-free and available for download at no cost.


We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

  • MKVToolNix 33.0.0 (32-bit) Screenshots

    The images below have been resized. Click on them to view the screenshots in full size.

    MKVToolNix 33.0.0 (32-bit) Screenshot 1
  • MKVToolNix 33.0.0 (32-bit) Screenshot 2
  • MKVToolNix 33.0.0 (32-bit) Screenshot 3

What's new in this version:

Bug fixes:
- mkvinfo: when using the `--size` option, mkvinfo will now report the correctly if an element has an unknown size
- MKVToolNix GUI: info tool: clusters with an unknown size will now be read and displayed correctly
-  MKVToolNix GUI: multiplexer: Windows: trying to open Blu-ray index or playlist files failed when the path to the files contained symbolic links (e.g. when mounting a drive in a sub-folder via Windows' disk management utility)
- MKVToolNix GUI: multiplexer: if a destination file names ends with a number in parenthesis (e.g. a year such as "(2017)"), that number will not be stripped anymore during the process of ensuring the destination file name is unique. Only those suffixes added automatically in prior attempts to make the file name unique will be removed
- MKVToolNix GUI: multiplexer: Windows: the GUI will let the user change the drive letter part of the destination file name freely again and only verify its validity right before starting to mux/adding to the job queue. Before it tried to force that into something valid, often resulting in unintentional paths (such as "C:users…DCfiles…")