SampleStack can turn a folder of samples into a playable instrument and export it as a SoundFont 2 file. Of all the formats SampleStack writes, SF2 is the one that packs everything, samples included, into a single file you can move anywhere.
This guide covers what SF2 is, when it’s the right choice, and how to build one in SampleStack. There’s a plain-language FAQ at the end.
What is SoundFont 2?
SoundFont 2 (.sf2) is a file format for sampled instruments that dates back to the 1990s. Its defining trait is that it’s self-contained: the audio, the key and velocity zones, the loop points, and the envelopes all live inside one binary file. There are no loose WAV files sitting next to it, which is what makes an SF2 so easy to hand off or archive.
That single-file design is the opposite of a format like SFZ, which keeps the mapping in a text file and the audio in separate WAVs. Both describe the same kind of instrument. They just package it differently.
When to reach for SF2
SF2 is the format to choose when portability matters most:
- One file, nothing to lose. Because the audio is embedded, you can email an SF2, drop it on a USB stick, or file it away without worrying about keeping a samples folder alongside it.
- It plays almost everywhere. SF2 has been around long enough that support is nearly universal across software samplers, and it turns up in some hardware too.
- It’s a public format. The SoundFont specification is documented and not controlled by a single vendor, so files stay readable by many tools.
The trade-off is age. SF2 was built around General MIDI-style instruments, so its modulation and layering options are simpler than newer formats, and it uses a single envelope curve shape rather than the range some other formats allow. For a straightforward multisampled instrument, none of that gets in the way. For elaborate, deeply-modulated instruments, a format like SFZ or Decent Sampler has more room.
How to create an SF2 in SampleStack
The workflow is the same as for any multisample export, right up to the final step. Multisample support shipped in SampleStack 1.2, so it’s in the current release.
- Create a new instrument in the sidebar and drop in your samples, usually pitched one-shots with a clear fundamental.
- Let SampleStack map them. It detects each sample’s pitch and assigns it a zone across the keyboard. More samples across the range means narrower zones and a more natural sound.
- Stack velocity layers. Load several samples per note at different strengths and SampleStack maps them to velocity ranges.
- Tune the zones and check the root notes, adjusting anything the auto-detection didn’t nail.
- Shape the amp envelope with the ADSR controls and preview as you play.
- Preview over MIDI, the computer keyboard, or the mouse before you commit.
- Export as SoundFont 2. SampleStack builds the single
.sf2file, embedding the audio and writing the zones, velocities, loops, and envelope into it.
The result is one file, ready to load in any SoundFont-compatible player.
What SF2 preserves
SampleStack’s built-in export matrix shows exactly what each format keeps. For SF2, the important points:
- Key zones, velocity layers, root notes, and fine tuning all carry over.
- Loop points are preserved for sustaining sounds.
- The amp envelope (ADSR) carries, though SF2 uses a single envelope curve shape rather than a choice of curves.
- Stereo samples are stored as linked, hard-panned left and right samples, which SF2’s design requires. SampleStack handles that packing for you.
- The audio is embedded, so the file is fully self-contained.
Artwork and custom controls are not part of SF2. If you want an instrument with its own interface, that’s what the Decent Sampler format is for.
Helpful tips
- Use SF2 when you want one file. If the reason you’re exporting is to hand the instrument to someone or store it simply, SF2’s self-contained file is the cleanest option.
- Keep source samples clean. As with any multisample export, pitched one-shots with a steady fundamental map most accurately, and more sample points across the range sound more natural.
- Expect a single envelope shape. If your instrument leans on a specific envelope curve, preview it after export, since SF2 flattens curve shapes to one type.
- Check very large instruments. Because SF2 embeds all its audio, a big multisampled instrument becomes a big file. That’s usually fine, but worth knowing if you’re working with a huge sample set.
FAQ
What is a SoundFont (SF2) file? A single file that contains both a sampled instrument’s audio and how it plays: which samples cover which notes and velocities, plus loops and envelopes. The audio is embedded, so there are no separate WAV files.
What plays SF2 files? A wide range of software samplers, including sforzando, Polyphone, and many DAW SoundFont players, plus some hardware. Support is nearly universal.
What’s the difference between SF2 and SFZ? SF2 packs samples and mapping into one self-contained binary file, easy to move but not readable. SFZ is plain text that references separate audio, more flexible and editable but travels as a folder.
Is SF2 self-contained? Yes. It’s the one common multisample format that embeds its audio, so a single .sf2 is the whole instrument.
How does SF2 handle stereo samples? It stores stereo as two linked mono samples, hard-panned left and right, played together. SampleStack handles this automatically.
Can hardware read SF2 files? Some hardware supports SoundFont playback, though it varies by device. SF2’s long history means it shows up in more places than newer formats.