SampleRipper gathers every sample from your tracker modules (XM, IT, MOD, S3M) and your folders of audio files into one library you browse in your web browser. It keeps one copy of each sample, groups near-duplicates, and lets you play, label and rate every sample. The cloud lays out the whole library by how the samples sound, and the morph plays the sounds between any two of them.
Download the file for your system from the Releases page:
- Windows (64-bit): run
SampleRipper-<version>-windows-x64-setup.exe. It installs SampleRipper for you alone and adds it to the Start menu. If Windows warns about an unrecognized app, click More info, then Run anyway. - macOS (Apple silicon): open
SampleRipper-<version>-macos-arm64.dmgand drag SampleRipper into Applications. The first time you open it, macOS asks you to confirm an app from outside the App Store: go to System Settings → Privacy & Security and click Open Anyway. - Linux (64-bit): allow
SampleRipper-<version>-linux-x64.AppImageto run as a program, in its file properties or withchmod +x, then open it.
The first start downloads Python and the packages SampleRipper runs on, about 2 GB on disk, which takes several minutes. On Windows and Linux with an NVIDIA graphics card, it takes the packages that let the card do the heavy listening instead, several gigabytes more. Later starts take a few seconds. SampleRipper then opens in your browser on its setup page:
- Under Folders, choose your module folder, your sample folders, or both.
- Choose where the library keeps its files. Pick a drive with free space: a large collection takes several gigabytes.
- Click Save and open the library.
- Under Library, click Build my library. The build lists its steps with the time each took, and a long step shows the time it has left. Once it finishes, click Open the library beside it.
Build the cloud, on until you switch it off, has the build listen to every sample and lay out the cloud. The first time, it downloads a listening model of about 1 GB. An NVIDIA graphics card makes this much faster, and the setup page names the card it uses. Without one, a large collection takes a day or more, so the page asks before it starts.
- Open SampleRipper from the Start menu, from Applications, or from its AppImage. A start while it already runs opens it in your browser again. A new version closes the old one as it starts, and so does any start when the running one has stopped responding.
- A build keeps going when you close the browser tab.
- To add folders, or to build again after your collection grows, open Library → Setup.
- Library → Quit SampleRipper, or Quit on the setup page, stops SampleRipper.
Using SampleRipper explains the cloud, the morph, every click and key, and using the app on a phone or tablet. The app shows the same list under Help → Keyboard and mouse.
If the first start stops before SampleRipper opens, a download was interrupted. Start SampleRipper again: it reuses every file it finished downloading.
SampleRipper keeps a log you can read or attach to a report:
| System | Log folder |
|---|---|
| Windows | %LOCALAPPDATA%\SampleRipper\Logs |
| macOS | ~/Library/Logs/SampleRipper |
| Linux | ~/.local/state/SampleRipper/log |
Report a problem on the issue tracker, with the log attached.
SampleRipper keeps every change to your labels, ratings and favorites. If some were changed by
mistake, running SampleRipper from source brings them back to how they were at a given time:
sampleripper annotations restore --at "2026-09-26 21:30" shows what it would change, and adding
--confirm carries it out.
Uninstalling SampleRipper on Windows removes the program and the packages it downloaded. Your library stays in the folder you chose for it.
- Using SampleRipper: the cloud, the morph, keys and gestures, phones and tablets.
- Putting your library online: publishing your library as a site on Railway.
- Running from source: running SampleRipper from a checkout, with its commands and every setting.
- Development: checks, tests and the sandbox library, for contributors.
- Building and releasing: building the executable and the installers, and publishing a release.
- Architecture: how the code is organized, and why.