Where Does Kontakt Store Libraries? Windows & Mac Paths, NICNT, and Relocation

Libraries vs. the Kontakt Plugin: Two Different Folders

Kontakt splits into two storage jobs that beginners often conflate. The Kontakt application — the standalone app and VST/AU plug-in binary — installs to your system Applications folder. The library content — multi-gigabyte sample pools, instrument presets (.nki), and the .nicnt registration file — installs wherever Native Access points its Content Location^[1].

Searching Program Files\Native Instruments\Kontakt 8 for Alicia's Keys samples will fail. The plug-in is a host; libraries are separate folders that Kontakt indexes through Native Access or the Library Browser. If you need a primer on plug-in formats before diving into paths, read plugin formats VST, AU, and AAX.

• Kontakt app (plugin binary) Windows: C:\Program Files\Native Instruments\Kontakt 8 (or Kontakt 7). macOS: /Applications/Native Instruments/Kontakt 8^[8].
• NI-managed VST2 folders (Windows only) C:\Program Files\Native Instruments\VSTPlugins 64 bit and VSTPlugins 32 bit — separate from library content^[1].
• Library content (samples + NICNT) Installed to Native Access Content Location — one top-level folder per library, never inside the Kontakt app directory.
• User snapshots / custom presets Saved inside each library's Snapshots subfolder on modern Powered-by-Kontakt libraries — do not move individual subfolders, only the entire library root^[4].

Default Library Paths: Windows vs macOS

Native Access controls where every NI Kontakt library lands on disk. Out of the box, the Content Location points to shared public folders — not your personal user Documents on macOS, and on Windows the path that Explorer often labels Public Documents^[1]. Each installed product creates its own named folder (for example Session Strings Pro 2) directly inside that Content Location.

If you previously set a custom Content path — common choices include D:\NI Libraries on Windows or an external SSD — all libraries sit there instead. Check the live path in Native Access: Preferences → File Management → Content Location → Browse.

The NICNT File and Library Folder Anatomy

Every Native Instruments and licensed third-party Kontakt library ships with a .nicnt file in its root folder. This small registration file tells Kontakt and Native Access which product the folder belongs to, where snapshots live, and how to build the Library Browser entry^[2]. When Native Access throws path is invalid, the cause is almost always selecting a parent directory or an Instruments subfolder instead of the folder that actually contains the .nicnt.

Powered-by-Kontakt libraries from NI use a predefined internal structure — Instruments, Samples, Snapshots, and more — that you must not rename or rearrange^[4]. You can move the entire library folder to another drive; you cannot split samples across locations without breaking paths.

• .nicnt Library identity file — required in the folder you point Native Access or Kontakt to^[2].
• .nki Individual instrument preset files, sometimes nested in subfolders under Instruments^[8].
• Older libraries (pre-NICNT) Some legacy folders use libraryname_info.nkc and libraryname_info.nkx instead of .nicnt^[4].
• Snapshots folder Stores user and factory snapshots on modern libraries — part of the fixed structure; do not delete or relocate alone^[4].

Setting and Checking Content Location in Native Access

All future Kontakt library installs follow whatever Content Location Native Access has on file. Changing it does not automatically move existing libraries — you relocate those separately^[1]. Before installing a 30 GB orchestral pack, point Content to a drive with room for both the download cache and the final library folder.

NI also separates Download Location (temporary installer files, auto-deleted after install) from Content Location (permanent library storage). Both need free space during installation^[1].

1. Open Native Access
   Launch Native Access and sign in with your NI account.
2. Open Preferences
   Click Preferences (lower-left in Native Access 2) and select File Management^[1].
3. Set Content Location
   Click Browse next to Content and choose your target folder — NI suggests creating a dedicated folder like NI Libraries on an external drive^[1].
4. Install or verify
   New libraries from Library → Available → Install land in that Content path. Already-installed libraries stay at their old path until you relocate them^[3].

How to Move a Kontakt Library and Relocate It

Copying or cutting a library folder to a bigger drive is safe — as long as you move the entire root folder intact and then tell Native Access where it went^[4][3]. Never drag individual Samples or Instruments subfolders out of the library tree.

Close Kontakt and your DAW before moving files. On Kontakt 7 / 8, Native Access handles relocation through Repair → Relocate. On Kontakt 6 and earlier, Kontakt's own Locate button in the Libraries browser points to the new folder^[3].

1. Close audio software
   Quit Kontakt, your DAW, and any other audio/MIDI apps^[3].
2. Move the library folder
   Drag the complete library root (the folder containing .nicnt) to the new drive or directory. Wait for the copy to finish before deleting the original.
3. Open Native Access → Repair
   Go to Library → Installed → Kontakt, find the library, and click Repair^[3].
4. Click Relocate
   In the Repair window, choose Relocate, then browse to the library's new root folder and confirm^[3].
5. Verify in Kontakt
   Launch Kontakt standalone, open the LIBRARY browser, and confirm the instrument presets load without a Library content not found error^[3].

Kontakt 6 and earlier: Locate inside the plug-in

If you still run Kontakt 6, move the folder first, then open Kontakt. The Libraries tab shows Library content not found. Click Locate to set the content. Click Locate → Browse for folder, select the library root, and click Choose / OK^[3].

Third-Party and Free Libraries: Different Registration Rules

Not every Kontakt instrument follows the same install path. NI distinguishes three third-party categories: webshop libraries installed through Native Access, serial-number libraries activated then installed or located in Native Access, and unlicensed libraries that only work in full Kontakt (not Kontakt Player)^[7].

Free community libraries often fall into the last group. They still live wherever you unzip them on disk — there is no NI default folder for them. In Kontakt 7 / 8 you can add them to the Library Browser via the cogwheel → Add → select the library root folder^[6]. For a curated list of free instruments and what Kontakt Player can load, see free Kontakt libraries guide.

Library Missing from Kontakt? Fix the Path, Not the Plug-in

A library that vanishes from the browser is usually a path or visibility issue — not a broken Kontakt install. Work through the checks below before reinstalling 40 GB of samples^[5][2].

• Library hidden in Preferences Open Kontakt Preferences (Mac) / Options (Windows) → Libraries tab. Tick the checkbox beside each library you want visible in the browser (available in Kontakt 5.6.8+)^[5].
• Wrong folder selected When locating or adding a library, choose the folder that contains .nicnt — not a parent directory or the Instruments subfolder^[2].
• Content Location mismatch If Native Access Content Location changed but old libraries were not relocated, run Repair → Relocate per library^[3].
• External drive offline Libraries on USB or Thunderbolt drives disappear when the drive is unplugged. Reconnect the drive, then relocate or let Kontakt find the path again.
• Case-sensitive or unsupported format NI products require NTFS on Windows and APFS or Mac OS Extended (Journaled) on macOS. Case-sensitive volumes are not supported^[2].
• Demo mode after restart Update Kontakt via Native Access, relaunch Native Access to refresh the product database, then open Kontakt standalone — licensed libraries should return to full mode^[5].

Folder Hygiene and Free Library Sources

Treat your Content Location like a sample vault: one root per library, descriptive top-level folder names, and backups before OS migrations. The same filing discipline that keeps Kontakt paths stable applies to WAV one-shots and loops — see sample organization for a cross-format system.

Kontakt Player is free but locks you to licensed libraries; full Kontakt unlocks the free NKI ecosystem. If you are still deciding whether paid instruments are worth the disk space, compare trade-offs in free vs paid VST plugins 2026. When you are ready to audition free Kontakt instruments without hunting random forums, browse /libraries on Plugg Supply or read the free Kontakt libraries guide for Player-compatible picks.