Convert WAV to WEM

A Wwise-based game, mod, or sound-bank build may require encoded Wwise media instead of source WAV files. The conversion is normally performed inside the matching Audiokinetic Wwise project so the media uses the project’s codec, platform settings, and sound-bank identifiers.

What the WAV format is

WAV is a RIFF/WAVE audio container widely used for uncompressed PCM recordings. Digital audio workstations and editors such as Audacity, Adobe Audition, REAPER, Pro Tools, and Windows Sound Recorder use it for recording, editing, interchange, and archival masters.

The .wav extension does not guarantee PCM or a particular quality level: WAV can contain several audio encodings. A PCM WAV with the sample rate, bit depth, and channel layout expected by the Wwise project is the safest source.

What the WEM format is

WEM is the usual filename extension for media encoded by Audiokinetic Wwise. It is not one universal codec. Depending on the Wwise release, target platform, and project settings, the encoded media can use codecs such as Vorbis, Opus, ADPCM, or PCM.

WEM is intended for playback through the Wwise sound engine rather than ordinary media players or audio editors. The Wwise pipeline can provide platform-specific compression, streaming or prefetch behavior, memory controls, and integration with events, buses, effects, and sound banks.

How to convert WAV to WEM

Use the Wwise version required by the target project. A file generated by another Wwise release, project, platform, or codec configuration may not work even if it has the .wem extension.

1. Install the required Wwise release through the Audiokinetic Launcher and open the target project. If no project exists, create one with the required platform configured.
2. Import the WAV into the project’s Actor-Mixer Hierarchy by dragging it there or using Wwise’s audio-file import command. Wwise creates a sound object linked to the source file.
3. Open the sound’s conversion settings, select the target platform, and choose a codec and quality setting supported by that project. Check sample-rate conversion, channel configuration, and mono or stereo handling instead of relying on defaults.
4. Assign the sound to the required event and SoundBank when the game uses events and banks. A standalone sound object is not necessarily included in a game build.
5. Generate the SoundBank for the target platform. Wwise performs the media conversion during this process or during the project’s equivalent audio-generation workflow.
6. Check the generated SoundBanks directory, commonly a path such as GeneratedSoundBanks/<platform>. Wwise may produce numeric or hashed names such as 123456789.wem; the original WAV filename is not guaranteed to remain.

Some projects embed encoded media inside SoundBanks rather than writing separate WEM files. In that case, generating the bank creates the package required by the game, but there may be no standalone file to copy.

For batch builds, use the Wwise command-line tools supplied with the same Wwise release, commonly through WwiseConsole, and invoke that release’s documented SoundBank-generation workflow. Command names and options vary between releases, so do not reuse arguments from an unrelated version.

Quality and compatibility limits

Do not rename a WAV to .wem; changing the extension does not encode the audio. A WEM’s compatibility depends on the Wwise version, target platform, codec support, SoundBank layout, media identifier, and any project-specific packaging or encryption.

Keep the original PCM WAV as the archival master. Converting a lossy source into Vorbis or Opus adds another lossy-generation step. Wwise can resample, downmix, or otherwise transform the source, so verify those settings when pitch, timing, phase, or channel placement matters.

There is no generally suitable online WAV-to-WEM converter. Generic services can create common formats such as MP3 or OGG, but they normally cannot reproduce a project’s Wwise conversion settings, media IDs, or SoundBank structure; uploading unreleased game assets may also disclose proprietary content. Use Wwise locally unless the target project explicitly supplies another compatible encoder.