Hi folks, here are some tools to play with your NKX files (and NICNT, NKR, NKS) whitout using Total Commander or Double Commander. NkxTool is 64-bit command-line utility for managing Native Instruments Kontakt archives. It acts as a specialized wrapper around the inNKX.wcx64 plugin, allowing you to list files, extract, and seamlessly pack libraries. Key Features - Multi-Format Support: Read and write .nkx (Audio/Samples), .nkr (Resources/Scripts), and .nicnt (Library Info) containers. - Smart Packing (Auto-Split): Automatically handles the strict 1.95 GB (2,090,000,000 bytes) size limit of the NKX format. If a source folder exceeds this limit, NkxTool automatically splits the output into _00.nkx, _01.nkx, etc. - Filelist Support: Pack archives dynamically using a text file containing relative paths (@filelist.txt), perfect for scripted audio conversions or selective repacking. - Update function for internal database: synced with system NativeAccess.xml with exotic / old libraries unique support. - Modern Architecture: Built with C# on .NET 10 (win-x64), completely standalone. NKXTool-UI is a lightweight desktop interface for NkxTool.exe, allowing to browse, create, and extract NKX and other NI archives format on Windows. The application focuses on a clean native workflow: pack a folder, pack from a @filelist.txt, unpack one or more archives, browse archive contents, switch light/dark theme, and run batch multi-pack operations from a single window. .Net 10.0 download page Liens vers les pages https://github.com/manzing/NKXTool https://github.com/manzing/NKXTool-UI I will update my LiTE Converter script very soon, with full NKX unpacking/packing support and batch mode relying on NKXTool. I hope you will find these tools useful, feel free to leave some feedback here. Last edited: Jul 12, 2026 at 6:38 PM
hey, stumbled accross this and wanted to ask does this help add kontakt libraries in windows? I recently switched to windows from mac and apparently there is no KLU for windows and I tried to make one but still no luck so I'd be very glad if you pointed me in the right direction
Very cool! I just took this for a spin to automate packing up some old Dan Dean instruments. Worked flawlessly. Two feature requests: - A flag (or even default) to use the current working directory instead of having to write out absolute paths would feel more natural. - A "-y" flag that prompts the user before overwriting samples when unpacking would be nice.
No sorry, this tool is moslty for advanced users who want to modifiy Kontakt library: packing or unpacking samples archives, edit nicnt files... I think you don't really need a tool for what you want, or maybe the kontakt_button small app from Bobdule can help you to add your library, depending on your Kontakt version (Legit, R2R, Bobdule...) Not sure of what you mean for current working directory, could you put an example of the command line you would like with a small explanation? I thought I implemented a basic file collision handling but I guess I forgot! I think I would add it the other way: no flag -> ask/warn user, flag -y -> overwrite existing files without asking. I will add it soon.
