File inspector

What this does

Sampler instrument files are mostly opaque. A preset either loads or it does not, and when it does not the message rarely says why. This reads the file and tells you what is actually in it: how many zones, which keys they cover, where it expects its audio to be and whether the fields a sampler checks are filled in.

It also flags the specific ways these files fail. An .exs with an empty folder path can take Logic down instead of reporting a missing sample. An .sfz with an unquoted # in a filename silently loses that region. An .xpm with more than four layers on a key is going to lose some of them on the hardware.

Nothing is uploaded

The file is read in your browser and never sent anywhere. This page contains no fetch, no XMLHttpRequest and no analytics, so there is nothing here capable of sending it.

Check it in the network tab if you like. You will see two requests, both for the web font, both made before you drop anything. Turn the wifi off and the tool still works.

Sample Miner works the same way. The app is local, your library is local and it stays that way: no upload, no cloud, no telemetry.

What it reads

• .wav and .aif chunk list, sample rate, bit depth, and the root note and loop points if the file carries them
• .exs block structure, zone key ranges, sample folder, and the three fields that decide whether Logic loads it
• .xpm keygroup and layer counts, root notes shown both as played and as stored
• .sfz regions, groups, opcodes in use and unquoted hash characters
• .dspreset groups, samples, note ranges and absolute paths that will not travel
• .X7L identifier and version