Convert VOC to AIF — Free Online Tool
Convert VOC audio files — the classic Creative Labs format used in DOS-era games and Sound Blaster applications — to AIF (Audio Interchange File Format), Apple's lossless uncompressed audio standard. The conversion transcodes from VOC's 8-bit unsigned PCM (pcm_u8) to AIF's 16-bit big-endian PCM (pcm_s16be), upgrading the bit depth and byte order to produce a high-fidelity file compatible with macOS, Logic Pro, and professional audio tools.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your VOC file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
VOC files store raw PCM audio using 8-bit unsigned samples (pcm_u8) or occasionally 16-bit signed little-endian samples (pcm_s16le), in a container format designed for Creative Labs' Sound Blaster hardware in the DOS era. AIF, by contrast, uses big-endian byte ordering (a legacy of Motorola-based Macintosh hardware) and typically stores 16-bit signed PCM samples. During this conversion, FFmpeg reads the VOC container, decodes the raw PCM audio data, and re-encodes it as pcm_s16be — converting from unsigned 8-bit to signed 16-bit representation and flipping the byte order from little-endian to big-endian. The bit depth increase from 8-bit to 16-bit means the output file will be larger and will have a wider dynamic range headroom, though the original 8-bit source limits the actual fidelity ceiling. No quality is lost beyond what the 8-bit source inherently restricts.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg command-line tool, which handles the reading, decoding, re-encoding, and writing of audio containers. This is the same underlying engine used in the browser-based tool via FFmpeg.wasm. |
-i input.voc
|
Specifies the input file — a VOC audio file created by Creative Labs' Sound Blaster tools or DOS-era game software. FFmpeg reads the VOC container header to determine the sample rate, channel count, and PCM codec (typically pcm_u8 or pcm_s16le). |
-c:a pcm_s16be
|
Sets the audio codec for the output to 16-bit signed big-endian PCM, which is the standard encoding used inside AIF files. This transcodes from VOC's 8-bit unsigned little-endian PCM to the big-endian format required by the AIF container and expected by Apple software like Logic Pro and macOS's Core Audio. |
output.aif
|
Specifies the output filename with the .aif extension, which tells FFmpeg to wrap the pcm_s16be audio stream in an Audio Interchange File Format container — Apple's lossless uncompressed audio format compatible with macOS, Logic Pro, GarageBand, and Final Cut Pro. |
Common Use Cases
- Extracting sound effects from retro DOS games to use in modern audio projects or remakes on macOS
- Archiving a Sound Blaster VOC sound library into AIF for long-term preservation and use in Apple's Logic Pro or GarageBand
- Importing legacy multimedia CD-ROM audio assets into a macOS-based audio production workflow that requires AIF or AIFF format
- Converting VOC voice lines or music from classic 1990s DOS titles for use in video essays or documentary productions edited on Final Cut Pro
- Preparing retro game audio samples for use in Ableton Live or other DAWs on macOS that natively prefer AIF over raw PCM containers
- Digitally restoring a collection of Sound Blaster demo files into a lossless format compatible with modern high-resolution audio players and archival storage
Frequently Asked Questions
No — the audio quality is fundamentally capped by the original VOC source. Most VOC files use 8-bit unsigned PCM, which has a dynamic range of only about 48 dB and audible quantization noise. While the output AIF file uses 16-bit signed PCM (which supports up to ~96 dB dynamic range), the extra bit depth simply provides headroom around the original 8-bit data — it does not add detail that was never captured. The conversion is lossless in the sense that no further degradation occurs, but it cannot recover quality that the 8-bit source never had.
This can happen because VOC uses unsigned 8-bit PCM (values from 0–255, with silence at 128), while AIF uses signed 16-bit PCM (values from -32768 to 32767, with silence at 0). FFmpeg handles this conversion correctly by mapping the unsigned 8-bit values to their signed 16-bit equivalents, but some older VOC files with unusual encoding or non-standard headers may have their silence offset interpreted differently. If the output sounds offset or DC-biased, you may need to apply a high-pass filter or DC offset correction in a DAW after conversion.
Yes — FFmpeg reads the sample rate declared in the VOC file header and preserves it in the AIF output without resampling. Many DOS-era VOC files were recorded at non-standard sample rates like 11025 Hz, 22050 Hz, or even unusual rates like 8000 Hz, and all of these will be faithfully preserved. If you need the output at a specific sample rate for your project (such as 44100 Hz or 48000 Hz), you can add the -ar flag to the FFmpeg command, for example: ffmpeg -i input.voc -c:a pcm_s16be -ar 44100 output.aif.
Yes — AIF supports multiple bit depths including pcm_s24be, pcm_s32be, pcm_f32be, and pcm_f64be. You can change the codec flag in the command to use one of these, for example: ffmpeg -i input.voc -c:a pcm_s24be output.aif. However, given that the source is an 8-bit VOC file, using anything above 16-bit will not recover additional audio information — it will simply store the upsampled data in a larger word size. For archival purposes some prefer 24-bit for future-proofing, but 16-bit (pcm_s16be) is the practical and standard choice.
On macOS or Linux, you can use a shell loop to process all VOC files in a folder: for f in *.voc; do ffmpeg -i "$f" -c:a pcm_s16be "${f%.voc}.aif"; done. On Windows Command Prompt, use: for %f in (*.voc) do ffmpeg -i "%f" -c:a pcm_s16be "%~nf.aif". This is especially useful when working with a DOS game's entire audio asset library, which may contain dozens of individual VOC sound effect files.
VOC files have extremely minimal metadata support — the format was designed for raw hardware audio playback in the DOS era and stores virtually no tags beyond basic header information like sample rate and codec type. AIF supports metadata fields such as artist, title, and comment chunks, but since VOC carries none of this information, the AIF output will have no embedded metadata tags. If you want to add metadata to the AIF file for library management, you can do so in a DAW or with a tagging tool after conversion.
Technical Notes
VOC is a block-based format where audio data is stored in typed chunks, with the most common chunk type containing raw 8-bit unsigned PCM sampled at rates that Creative Labs' Sound Blaster hardware supported. AIF uses big-endian byte ordering inherited from Motorola 68000-based Macs, which is the opposite of the little-endian architecture that VOC was designed for on x86 DOS machines — this is why the target codec is specifically pcm_s16be (signed 16-bit big-endian) rather than pcm_s16le. One known limitation is that some VOC files contain multiple audio blocks with different sample rates or codec types (a feature used in certain DOS games), and FFmpeg will decode the first audio stream it encounters; multi-block VOC files may require manual inspection with ffprobe before conversion. VOC also supports a looping mechanism (via block type 6) used in game music, but this loop metadata has no equivalent in AIF and will be silently discarded. File sizes will increase significantly — an 8-bit VOC at 22050 Hz will produce an AIF that is roughly twice as large in raw bytes due to the expansion from 8-bit to 16-bit sample storage.