Look inside the pack before it ships
Sellers: catch the .DS_Store files, the 128kbps stowaways, and the untitled tracks before a customer does. Buyers: see exactly what you got. One ZIP in, one honest report out.
Nothing is uploaded — your audio never leaves your device.
| File | Type | Size | Notes |
|---|
A clean pack is table stakes. A hosted pack page sells it.
KitDL is building share-ready pack pages — streaming previews, follow buttons, clean delivery. This inspector is the first brick. Sign up for the studio meanwhile: 3 full packs free.
The five-minute audit that separates pro packs from hobby ZIPs
Every experienced pack seller runs the same mental checklist before shipping, and every experienced buyer runs it after downloading. Is there junk in the archive — __MACOSX folders, .DS_Store files, Thumbs.db? Are the WAVs actually the sample rate and bit depth the store page promised? Are there stowaways — a stray project file, an installer, something executable that has no business inside a sample pack? Is the naming consistent enough that the pack feels designed rather than dumped?
None of those questions needs a download to someone's server or a paid audit. A ZIP file's central directory lists every file, its size, and its compression before a single sample is extracted — and a WAV file's first 44 bytes declare its sample rate, bit depth, and channel count. This inspector reads exactly that, locally: the archive is unpacked in your browser's memory, header-checked, catalogued, and released. What comes back is the report a careful seller would have written by hand — junk files named individually, quality flags on any WAV below 44.1 kHz / 16-bit, red flags on dangerous extensions, and the full file table you can save as a text report.
For sellers, the payoff is the export you fix before a customer leaves the one-star "pack is full of Mac trash files" review. For buyers, it's informed consent: you see the real contents — how many one-shots, how many loops, what formats, what sizes — before you unzip 2 GB into your sample library and find out the "royalty-free drum kit" is 40 MP3s and a readme. Either way, the pack tells the truth here first.
Frequently asked questions
What does the pack inspector check?
The ZIP's full file tree: audio formats and counts, per-file sizes, junk files (.DS_Store, Thumbs.db, __MACOSX), suspicious extensions (.exe in a sample pack is a hard red flag), naming consistency, and folder depth. It's the checklist experienced pack sellers run manually.
Can it check audio quality inside the ZIP?
It flags what's knowable without decoding everything: WAV headers reveal sample rate and bit depth instantly. For MP3 true-quality checks, run suspicious files through the MP3 Quality Checker on audioencode.com — same free toolbox.
Why do junk files matter in a pack?
They're the mark of a rushed export and customers notice: __MACOSX folders and .DS_Store files scream 'zipped without care.' The report lists them so your next export excludes them — most OSes have a one-checkbox fix.
Is the ZIP uploaded to inspect it?
No — it's unpacked in your browser's memory, inspected, and released. Unreleased packs stay unreleased.