Free online SF2 to SFZ converter

Source format: sf2

SF2 is the common shorthand for SoundFont 2, a file format used to store sampled instruments and drum kits for MIDI playback. It is widely used in software synthesizers, samplers, and some hardware devices that support SoundFont banks. An SF2 file typically contains multiple presets, sample data, envelopes, loops, and playback parameters for realistic MIDI sound generation.

Target format: sfz

SFZ is a text-based sampler instrument format used by many software samplers and virtual instruments. Instead of storing samples and instrument definitions in one binary container, SFZ uses a readable plain-text definition file that points to external sample files. Its main advantages are flexibility, easy editing, and broad support in sampler software. SFZ is commonly used for custom sample libraries, instrument mapping, and detailed articulation control.

How sf2 to sfz conversion works

Converting SF2 to SFZ usually means extracting the samples from the SoundFont and recreating the instrument mapping in an SFZ definition file. Because SF2 and SFZ are structurally different, the result is often a best-effort translation rather than a perfect one.

In practice, the conversion may involve two parts:

• Sample extraction from the SF2 file to WAV or another sampler-friendly format.
• Mapping recreation in an SFZ file using opcodes such as sample=, lokey=, hikey=, and lovel=/hivel=.

How to convert sf2 to sfz

1. Open the SF2 file in a tool that can inspect SoundFont instruments and export or rebuild them for SFZ use.
2. Check the presets, key ranges, velocity layers, loop points, and sample names so you know what must be preserved.
3. Export the samples if needed, usually as WAV files.
4. Create or export an SFZ file that references those samples with the correct relative paths.
5. Save the SFZ file and its sample folder together so the sampler can find the audio files.
6. Test the result in an SFZ-compatible sampler and adjust the mapping if necessary.

Recommended software

• Polyphone (Windows, macOS, Linux): A free and open-source SoundFont editor that can open SF2 files, inspect instruments, and help with sample export and SFZ-oriented rebuilding.
• sforzando (Windows, macOS): A free SFZ player that is useful for testing converted instruments.
• ARIA Player (Windows, macOS): Another sampler that supports SFZ playback and can help verify compatibility.

Polyphone is the most practical desktop tool for this workflow, but direct one-click SF2-to-SFZ export may not always be available depending on the file and version. In some cases, you may need to export samples and build the SFZ mapping manually.

Step-by-step conversion with Polyphone

1. Open your SF2 file in Polyphone.
2. Inspect the instrument structure and confirm the samples, zones, and key ranges.
3. If needed, export the samples as WAV files using the export options in File → Export.
4. Create a new SFZ file in a text editor, or use Polyphone features if your version supports SFZ-oriented export.
5. Map each sample to the correct key and velocity range using SFZ opcodes.
6. Place the SFZ file and samples in the same project folder or use correct relative paths.
7. Open the SFZ in sforzando or another compatible sampler and verify playback.

Limitations to expect

SF2 to SFZ conversion is not always lossless. SF2 presets may use features that do not map perfectly to SFZ, such as complex modulation, built-in effects, or generator settings that depend on a specific SoundFont player. Some velocity layers, loop points, tuning data, and articulation behavior may require manual adjustment after conversion.

Because SFZ is text-based, the converted instrument is often easier to edit and maintain, but it depends on external sample files that must remain in the correct relative paths. Also, different SFZ players support different subsets of the specification, so a file that works in one sampler may need tweaks in another.

You can also convert the file on 101convert.com for free, without installing any software.

Tips for better results

• Preserve the original folder structure when possible so sample paths stay valid.
• Check loop points carefully, especially for sustained instruments.
• Verify velocity layers and key ranges after conversion.
• Test the SFZ in more than one sampler if compatibility matters.
• Refer to the SFZ format documentation for opcode details and advanced mapping options.