You can sell an original Kontakt sample library directly, but the listing must say whether it requires the paid full version of Kontakt or is officially licensed for the free Kontakt Player. Package the exact NKI instruments, samples, resources, documentation and licence that passed a clean-machine test, then release that version only after payment succeeds.
This workflow is for independent instrument developers, not people reselling third-party samples. Its original asset is a four-host release matrix that makes compatibility and missing-file failures visible before launch.
Set the Player Boundary Before You Price the Library
Native Instruments explains that only officially licensed libraries run fully in Kontakt Player; an unlicensed indie library generally requires the full version. Its current NKS licensing information also describes encoding, serials and Native Access deployment for licensed products.
Never describe an unlicensed product as “Kontakt Player compatible.” Put the minimum Kontakt version, full-versus-Player requirement, operating systems, plug-in formats tested, storage size after extraction and required third-party content beside the price.
Build a Four-Host Release Matrix
Test the retail download, not your development folder:
| Host | Test | Pass condition |
|---|---|---|
| Kontakt standalone | Browse, load and play every NKI | No missing samples or demo timeout |
| DAW instrument track | Save, close and reopen a project | Patch and automation restore correctly |
| Second computer/profile | Extract to a new location | No absolute path to the build machine |
| Lowest promised version | Load every instrument and snapshot | No newer-version warning or broken script |
Run the matrix on each operating system you advertise. If you did not test a host or version, label it untested rather than inferring compatibility.
Freeze a Buyer Archive Manifest
Create one versioned archive with a manifest containing product version, release date, minimum Kontakt version, Player/full requirement, sample format and rate, installed size, instrument count, presets, licence, checksum and support route. Use Kontakt's batch re-save or sample-management tools carefully, then retest from the final archive.
The manifest is the release contract between listing and download. A beautiful demo cannot repair an archive whose NKI files still point to a private sample drive.
Audit the Recording and Software Rights
Use recordings and source material you own or are permitted to redistribute inside a sample instrument. Native Instruments' current EULA distinguishes using factory content in music from repackaging content as a sound library. Review every source licence and obtain specialist advice when ownership is unclear.
Define what the buyer may do in finished music, games and client work, and what they may not do with raw samples, instruments, presets or shared team copies. This is a practical checklist, not legal advice.
Deliver the Tested Release After Payment
Create a music and audio digital product, upload the exact approved archive and use protected file delivery. Buy it once with a separate email, download to a clean folder and repeat the standalone and DAW tests.
Start with one instrument and one honestly supported host matrix. Publish only when the product page, manifest, licence, archive and support answer all name the same release.