VSTPRESET Files

What is a .VSTPRESET file?

The .vstpreset file extension has been created by Steinberg as a part of the VST 3 file format. It represents the preset configuration of a VST 3 instrument/effect plugin. It includes values of the parameters, program configuration, optional state of any controller, and extra data for the preset browser which displays the preset names, categories/tags, etc. It should be noticed that .vstpreset is neither a regular audio file, MIDI file, nor any type of plugin; its use is possible only when there is a compatible VST 3 plugin and a host that works with the plugin.

The .vstpreset files are most commonly found inside a DAW presets folder, search in MediaBay in Steinberg programs, VST Instrument Library of sounds, soundpacks and exported plugin host presets. This file format is tightly connected with Steinberg software and there are no unrelated formats using the mentioned filename extension.

It should be understood that compatibility of the plugin will be based on the plugin's own ID and its saved state; therefore, preset created on one specific synth/effect is not supposed to work correctly with some other plug-in (because of different configurations saved). To verify the file format it is enough to read the first four bytes and compare the result with "VST3" string (hex 56 53 54 33).

How to open a .VSTPRESET file

Technical details

.vstpreset can be considered a binary wrapper format, which can also carry metadata as an XML chunk. .vstpreset file signature in ASCII contains bytes sequence "VST3", which is located on the very first place of the binary, i.e., byte position 0x0. It has corresponding hexadecimal code 56 53 54 33. Description of the structure given by Steinberg VST3 Software Development Kit starts with the standard header, class ID containing 16 bytes defining plug-in component, offset to a chunk list and finally one or several binary chunks. Byte ordering and interpretation are clearly explained in the VST3 SDK specification, so it needs special decoder that matches specific VST3 plug-in that has created the binary file. Amount of serialized information depends of plug-in itself; therefore, presets created by two different plug-ins or even by two versions of one can differ from each other in binary chunks.

The preset binary can include component state and also could contain controller state, metadata or the list of additional data that would be required from Cubase MediaBay presets browser. .vstpreset is not an archive format like ZIP and rarely can be compressed in bulk. When the compression does happen, it could appear as a part of the specific plug-in data chunk. No public registered MIME type for this extension exists and file would most likely be classified as "application/octet-stream". File size is varied and may take only several kilobytes for simple parameters settings up to several MB, which occurs when the preset stores parameter blocks, big wavetables or specific plug-in metadata. Sample based virtual instruments rarely will have samples embedded into every single preset but most frequently will store the reference of installed libraries, which still should be available while loading presets.

How to convert .VSTPRESET files

For .vstpreset, best “conversion” means loading into the corresponding VST 3 plug-in and saving in the DAW. Since generic file converters can't interpret information specific to the plug-in itself (its private state), Cubase, Nuendo, WaveLab, REAPER, Bitwig Studio, Studio One, or FL Studio have to open the preset file first. In case the objective is to use it exclusively to produce a sample/soundfile, rendering is done via loading the preset, triggering it by MIDI or audio material through the plugin, and creating audio file. At that point no more plug-ins' controls will be able to edit, and no note events or automation tracks will be included anymore.

In order to transfer it to other host, it is better to create in that particular DAW's native file such as Cubase Track Preset file or REAPER FX chain and save it as it is. It might store not only plug-in parameters, but also routing and other automation related information. Migrating .fxp and .fxb files of plug-ins using VST 2 format doesn’t guarantee success for that reason that it can't work without VST3/VST2 translator provided for it by the respective plug-in maker. .vstpreset needs to be archived together with plug-in itself and project of the DAW. Batch conversions are uncommon because hosts can't work with .vstpresets automatically.

Common problems and fixes

"Preset not found" or empty Preset Browser indicates the lack of .vstpreset file inside the folder which host program is scanning for. When loading .vstpreset files in Cubase, Nuendo, HALion, and Groove Agent one should choose the corresponding plugin first and use built-in load/import command, not using file placement in the Finder/Windows Explorer and scanning with MediaBay.

"Cannot load preset" typically suggests a problematic installation of this plugin. It can be caused by the missing, disabled, and only VST 2/2.x/AU installed component of VST 3 plug-in. Loading the preset requires its insertion to a host, and the proper functioning host would be any VST 3 host, for example, Cubase, REAPER, Bitwig Studio, Studio One or FL Studio where there must also be a corresponding VST 3 plug-in installed.

The preset can open successfully but fail the actual sound, since a more updated version of a plug-in changed the mapping of parameters of oscillator, library or presets collection.

If preset requires missing samples, external HALion, Groove Agent and even third party sample collections one should reinstall, relink the folder containing samples or content, or return to initial set.

An error of zero byte or corrupted downloading will cause inability to check VST 3 chunk list of file which size does not satisfy header and length values. One has to retrieve backup version or download once again. If the first four bytes are not 56 53 54 33 - this may be ZIP/RAR/preset from another format file named ".vstpreset".

File association and double clicking on preset files is generally useless feature, especially with presets, because typical procedure includes preset inserting in VST 3 host. Crossplatform loading problem is possible due to absence of certain program either under Windows/Mac or license failure.

Security considerations

The generic .vstpreset file operates on its own as just a binary data format and does not contain any form of scripting macros, JavaScript, or code. In general, there is danger from the VST 3 plugin and/or DAW file parser - if it parses a malformed preset, it can give wrong input state information to the hosts like Cubase, Nuendo, REAPER, Bitwig Studio, Studio One, or FL Studio and this will show vulnerabilities. Do not open unfamiliar presets on outdated DAW/Plugin versions and check your presets on a safe side project before applying them. The dangerous thing here - do not mistake presets for the installer of your plugin. Formats .exe, .pkg, .vst3, and other installers are much more dangerous compared to simple preset (.vstpreset) files. Moreover, presets can hold information related to name, author/companies info, comments, categories, and library.

History and versions

The VST was invented by Steinberg in 1996, whereas VST3 was introduced in 2008 as the replacement for VST 2.x family. VST3 format included the extension .vstpreset, making it possible to preserve a single preset independently of any given host based on its association with a unique VST 3 Component ClassID. Cubase, Nuendo and MediaBay made it popular through indexing of preset's data like tags or categories for more convenient sound exploration. This version of the format became the primary choice for Steinberg, discontinuing distribution of the VST 2 SDK among new clients in 2018. Information about VST 3 format is provided via the VST 3 developer site and SDK by Steinberg, and the format is neither ISO, nor ECMA or IETF. But the importance of this format is still quite evident through inclusion of VST 3 builds in modern DAWs and presets libraries .vstpreset for plugins, along with the compatibility of the VST3 .vstpreset extension with the vendor-defined presets systems.

Related formats

But old VST 2 format presets, .fxp and .fxb are still around in legacy plug-ins though they don’t represent the same thing in relation to the .vstpreset for VST 3. Indeed, a .vst3 format stands for the actual plug-in itself while the .vstpreset merely contains a saved state without ability of outputting anything by its own until you have a plug-in to run together with it. Preset files made for Audio Units in Apple’s host on macOS and iOS are known as .aupreset and stand as close as possible native analogs to VST 3 presets. .nksf is the Native Instruments presets format adding browsing, previewing, and controller configuration information for particular NI instruments. Ableton Live uses the special proprietary format for the similar functions: .adg file for device groups and .adv device presets. They both can do a good job in Live application but aren’t always fully suitable outside Ableton.