While MakeMKV primarily uses its own internal system of "hashed keys" to decrypt Blu-ray and UHD discs, it can also use an external KEYDB.cfg file—a community-maintained database of decryption keys—as a secondary source. This is particularly useful for discs that MakeMKV hasn't yet added to its own server or if you are working offline. What is KEYDB.cfg?
KEYDB.cfg is a text-based database containing Volume Unique Keys (VUKs) and unit keys for thousands of Blu-ray and UHD titles. While MakeMKV normally downloads updates automatically, adding a manual KEYDB.cfg file acts as a backup to ensure your drive can open specific discs immediately. Where to Place KEYDB.cfg
For MakeMKV to recognize the file, it must be placed in the MakeMKV Data Directory. You can find your specific path by opening MakeMKV and going to Preferences > General > MakeMKV Data Directory. Default locations by operating system: Windows: C:\Users\[YourUsername]\.MakeMKV\ macOS: ~/Library/MakeMKV/ Linux: ~/.MakeMKV/
Important: Make sure the filename is exactly KEYDB.cfg (case-sensitive on some systems). How to Get the Latest Keys
Because new movies are released constantly, the database needs frequent updates. [SOLVED] Seems makemkv don't see the KEYDB.cfg file
Unlocking Your Media: How to Use KEYDB.cfg with MakeMKV If you’ve ever tried to rip a brand-new 4K UHD Blu-ray only to have MakeMKV tell you the disc is "unknown," you aren’t alone. While MakeMKV usually downloads its own "hashed keys" automatically, there is often a lag between a movie's release and the official update.
This is where the KEYDB.cfg file comes in. It’s a community-maintained database of Volume Unique Keys (VUKs) that can get your discs ripping weeks before the official software catches up. What is KEYDB.cfg? keydbcfg makemkv
It is a simple text file containing decryption keys for thousands of Blu-ray and UHD titles. Think of it as a "cheat sheet" for your disc drive. When MakeMKV doesn't recognize a disc, it can look at this local file to see if the community has already found the key. Step-by-Step Guide: Setting Up Your Key Database 1. Download the Latest Key Database
The most reliable source for this file is the FindVUK Online Database. Download the keydb.cfg file (usually provided as a .zip). Extract the file so you have the raw .cfg file ready. 2. Locate Your MakeMKV Data Directory
MakeMKV looks for this file in its specific data folder, not the installation folder. To find yours: Open MakeMKV. Go to View > Preferences > General.
Look for "MakeMKV data directory" at the top. This is where you need to place the file.
Pro Tip: Common default paths include %USERPROFILE%\.MakeMKV on Windows or ~/Library/MakeMKV on macOS. 3. Install and Restart Copy your downloaded KEYDB.cfg into that data directory.
Restart MakeMKV entirely to ensure it initializes the new database. Troubleshooting Tips While MakeMKV primarily uses its own internal system
Edit /etc/keydb/keydb.conf:
# Persist job state (optional — RDB is fine for queue)
save 60 1000
Step 3: Create the Configuration File (Important!)
MakeMKV does not read KEYDB.cfg directly by default. It relies on a specific integration file.
Inside the .MakeMKV folder, you need to create a new text file named: keys_hashed.txt
Why keys_hashed.txt? MakeMKV expects a hashed key format. The raw KEYDB.cfg uses a different standard (VUK). However, modern ripping utilities (like FindVUK or DVDFab) include a "Hasher" tool. Alternatively, you can rename the file, but it is safer to copy the contents:
- Open the downloaded
KEYDB.cfg in Notepad++ or VS Code.
- Select all the lines that contain
0x (hexadecimal values).
- Paste them into your new
keys_hashed.txt file in the .MakeMKV folder.
Part 1: What is MakeMKV?
Before we tackle the configuration file, let's establish the primary software. MakeMKV is a commercial (but currently free while in beta) application designed to convert video discs into MKV containers.
Core Functions:
- Decryption: It includes on-the-fly decryption for DVD, Blu-ray, and 4K UHD Blu-ray.
- Remuxing: It copies video/audio streams into an MKV file without re-encoding (lossless quality).
- Backup Mode: It creates a full folder structure of the disc on your hard drive.
The Limitation: While MakeMKV has built-in decryption keys, 4K UHD discs constantly introduce new "AACS 2.0" encryption methods. Sometimes, MakeMKV’s internal database hasn't been updated yet. This is where keydbcfg enters the scene.
A Basic Example
To illustrate, let's assume you want to store information about your media rips in KeyDB:
-
Install KeyDB and MakeMKV: Ensure both are installed on your system.
-
Start KeyDB: Begin the KeyDB server.
-
Use a Script to Rip and Store Info:
- You could write a script (in Python, for example) that uses the
subprocess module to run MakeMKV commands.
- Use the
redis or keydb Python client to connect to your KeyDB instance and store or retrieve information.
Example Python Snippet (for illustration purposes): You see frequent decryption errors in MakeMKV (e
import subprocess
import redis
# KeyDB Connection
r = redis.Redis(host='localhost', port=6379, db=0)
def rip_disc(disc_info):
# Example MakeMKV command
mkv_command = f"makemkv disc_info['source'] disc_info['output']"
subprocess.run(mkv_command, shell=True)
# Store info in KeyDB
r.hset("media:rips", disc_info['title'], disc_info['output'])
# Example usage
disc_info =
'source': '/dev/sr0',
'output': '/path/to/output.mkv',
'title': 'My Movie'
rip_disc(disc_info)
Step 5: Testing the Integration
Insert a problematic disc. Open MakeMKV. Watch the Log window (usually at the bottom).
- If successful, you will see a line reading: "Loaded content hash table, will verify integrity of M2TS files."
- If you see "Failed to load keys_hashed.txt" – you have a syntax error or wrong path.