Convert VOC to AIFC — Free Online Tool
Convert VOC audio files — the classic Creative Labs Sound Blaster format used in DOS-era games — to AIFC, Apple's compressed/uncompressed audio container. The conversion re-encodes the raw 8-bit or 16-bit little-endian PCM data from VOC into big-endian 16-bit PCM (pcm_s16be), making the audio compatible with professional Apple and macOS workflows.
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 in little-endian byte order, typically as unsigned 8-bit (pcm_u8) or signed 16-bit little-endian (pcm_s16le) samples — a format tied to the x86 architecture of DOS-era PCs. AIFC, by contrast, requires big-endian byte ordering as part of its Apple heritage. During this conversion, FFmpeg reads the VOC container's audio blocks (including its chunk-based structure with optional loop and silence markers) and re-encodes the PCM data as signed 16-bit big-endian samples (pcm_s16be), which is the default uncompressed codec for AIFC. This is a lossless PCM-to-PCM transcode: no audio quality is lost, but the byte order is flipped and the data is repackaged into the AIFC container format. Any VOC-specific metadata such as loop points or silence blocks are not preserved, as AIFC has no equivalent structures for those DOS-era features.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg application, the open-source multimedia processing engine that handles reading the VOC container, decoding the raw PCM audio blocks, and re-encoding them into the AIFC output format. |
-i input.voc
|
Specifies the input VOC file. FFmpeg parses the VOC file header and chunk structure — the Creative Labs container format used by DOS Sound Blaster applications — to locate and decode the raw PCM audio data blocks within the file. |
-c:a pcm_s16be
|
Sets the output audio codec to signed 16-bit big-endian PCM, which is the standard uncompressed audio codec for the AIFC format. This flips the byte order from VOC's little-endian x86 convention to AIFC's big-endian Apple convention while keeping the audio data losslessly intact. |
-b:a 128k
|
Specifies a target audio bitrate of 128 kbps. For uncompressed PCM codecs like pcm_s16be, this flag has no encoding effect since PCM bitrate is fixed by sample rate and bit depth — it is included for command completeness but does not alter the output audio quality or file size. |
output.aifc
|
Defines the output filename and signals FFmpeg to wrap the re-encoded pcm_s16be audio stream in the AIFC container format, producing a file compatible with macOS, Logic Pro, GarageBand, and other Apple audio tools. |
Common Use Cases
- Restoring and archiving sound effects or music ripped from classic DOS games (like those using Sound Blaster audio) into a professionally compatible format for audio editing on macOS.
- Importing vintage game audio into Apple Logic Pro or GarageBand, which natively support AIFC but cannot open VOC files directly.
- Preparing retro game sound assets for use in modern game engines or sample libraries where AIFC is an accepted professional audio format.
- Converting a collection of DOS-era multimedia application sounds from VOC to AIFC for long-term archival, moving from a proprietary 1990s format to a more widely documented container.
- Re-encoding 8-bit unsigned VOC samples into 16-bit signed AIFC to increase dynamic range headroom when upsampling retro audio for modern high-fidelity audio projects.
- Sharing Sound Blaster audio assets with macOS-based audio engineers or musicians who work in Apple-centric toolchains and need a standard big-endian PCM container.
Frequently Asked Questions
No — this specific conversion is lossless. Both the VOC source and the AIFC output in this command use uncompressed PCM audio. The ffmpeg command uses pcm_s16be (signed 16-bit big-endian PCM) for the AIFC output, which is simply a byte-order repackaging of the original PCM samples. If your VOC file uses 8-bit unsigned PCM (pcm_u8), the conversion to 16-bit will actually expand the bit depth, adding headroom without introducing distortion.
VOC was developed by Creative Labs for the Sound Blaster card on x86 DOS PCs, which use little-endian byte ordering — the least significant byte comes first. AIFC (and its parent format AIFF) was developed by Apple for Motorola 68k-based Macintosh computers, which use big-endian byte ordering. The pcm_s16be codec in the output command tells FFmpeg to write each 16-bit audio sample with the most significant byte first, conforming to AIFC's specification. The audio content is identical; only the on-disk representation of each sample changes.
No. The VOC format uses a chunk-based structure that can embed loop markers, silence blocks, and repeat commands — features specific to the Sound Blaster hardware's real-time playback engine. AIFC has no equivalent metadata structures for these DOS-era constructs, so FFmpeg discards them during conversion. If you need to preserve loop behavior, you should note the loop start and end points before converting and re-enter them manually in your audio editor after the conversion.
AIFC supports compressed codecs beyond uncompressed PCM. You can substitute the codec flag to use G.711 compression, for example: replace '-c:a pcm_s16be' with '-c:a pcm_alaw' or '-c:a pcm_mulaw' for telephony-grade compressed audio. For higher bit-depth lossless options, you can use '-c:a pcm_s24be' or '-c:a pcm_s32be'. Note that lossy compressed AIFC codecs like alaw and mulaw are narrow-band formats best suited for voice, so for retro game music or effects, pcm_s16be or pcm_s24be are the recommended choices.
Yes. On Linux or macOS, you can run a shell loop: 'for f in *.voc; do ffmpeg -i "$f" -c:a pcm_s16be -b:a 128k "${f%.voc}.aifc"; done'. On Windows Command Prompt, use: 'for %f in (*.voc) do ffmpeg -i "%f" -c:a pcm_s16be -b:a 128k "%~nf.aifc"'. This processes each VOC file individually and outputs a corresponding AIFC file with the same base filename, which is useful when archiving large DOS game sound asset libraries.
Yes. AIFC with pcm_s16be audio is a native Apple format and is fully supported across macOS, Logic Pro, GarageBand, QuickTime, and Core Audio. The resulting files will be recognized immediately without any additional codecs or plugins. This makes AIFC one of the most seamless delivery formats for Apple-platform audio workflows, which is a primary reason to choose it over alternatives like WAV when working in a macOS environment.
Technical Notes
VOC files consist of a file header followed by typed data blocks (called chunks), which can contain audio data, silence, loop points, and playback markers. FFmpeg extracts only the raw audio data blocks and discards non-audio chunks during muxing into AIFC. The most common VOC codec is pcm_u8 (unsigned 8-bit PCM), which was the native Sound Blaster playback format; some later VOC files use pcm_s16le. In both cases, FFmpeg converts the samples to signed 16-bit big-endian (pcm_s16be) for AIFC output — this is a safe, lossless operation. The '-b:a 128k' flag in the command has no practical effect on uncompressed PCM codecs like pcm_s16be, since PCM bitrate is determined entirely by sample rate and bit depth rather than a compression target; it is included for command consistency but can be safely omitted. The sample rate of the original VOC file (commonly 8000 Hz, 11025 Hz, 22050 Hz, or 44100 Hz) is preserved in the AIFC output without resampling unless explicitly changed. AIFC does not support chapters, subtitle tracks, or multiple audio streams, which aligns with VOC's own single-stream-only design, so no data is lost from those omissions.