For those who need the raw, decrypted binary data to analyze shaders.
Step 1: Extracting the XOR key.
Almost all standard KN5 files use a static 16-byte XOR key: 0x6B, 0x6E, 0x35, 0x20, 0x50, 0x52, 0x4F, 0x54 ("kn5 PROT").
Step 2: Using kn5_decryptor.exe (Verified build)
kn5_decryptor.exe input.kn5 output.dec
This removes the XOR obfuscation and decompresses the node blocks.
Step 3: Parsing the decrypted output.
The output (.dec) is now a raw binary stream of node data. You still need a parser (like kn5dump.exe) to convert this into a readable .ini or .csv structure.
| File Type | Decrypt Possible? | “Verified” Removal Possible? | |-----------|------------------|-------------------------------| | Kunos original KN5 | No (AES-128 + proprietary key) | No – requires breaking encryption | | User-made unencrypted KN5 | Yes – just rename/use standard tools | Not applicable | | User-made encrypted KN5 | Yes – if you know the key (some modders share it) | Yes – but you can rebuild without verify |
Bottom line:
You cannot decrypt original Kunos KN5 files (like from the base game or DLCs) because the encryption key is not public and brute-force is infeasible. Attempts to do so violate the EULA and copyright laws.
A: Common false positive because tools hook into game processes. Verify by scanning the source code (if open source) or using VirusTotal.
If you are a modder, 3D artist, or sim racing enthusiast, you have likely encountered KN5 files. These proprietary encrypted container files are native to Kunos Simulazioni’s game engine, most famously used in Assetto Corsa and Assetto Corsa Competizione. They store 3D models, textures, shaders, and collision data.
However, a common question arises: How do you decrypt KN5 files to extract or inspect their contents?
Before proceeding, it is critical to understand the legal and ethical landscape. This guide provides verified, technical methods for decryption, focusing on legitimate use cases (e.g., recovering your own lost work, studying file structures for compatibility, or non-commercial modding with permission).
If you distribute decrypted official KN5 assets:
A KN5 file is not a standard 3D format like FBX or OBJ. It is a compiled, proprietary binary format that can be encrypted using AES-128 or custom XOR-based obfuscation. Kunos designed it to:
KN5 files can exist in two states:
Thus, “decrypting” means reversing KN5 back to editable source files (FBX, DDS, KN5 raw).
First, let's clear up a myth: The .kn5 format is not encrypted in the traditional sense (like AES-256). It is compiled and hashed.
You cannot "decrypt" a DLC-locked ACC KN5 file without valid Steam authentication. If you try, you will get a hash mismatch error. The "verified" methods below only work for standard, unprotected, or community-modded KN5 files.
This tool decrypts the file on-the-fly into memory without permanently writing an unencrypted file to disk. This is the safest method.