Initializing... drag & drop files here
Supports: CAF
This conversion is a crossing between two ecosystems that never much cared about each other. CAF is Apple's Core Audio Format, a container that macOS and iOS read natively and almost nothing else does. WMA is Windows Media Audio, Microsoft's lossy codec from 1999, carried inside an ASF container and read natively by the Windows Media stack. Pick WMA when a specific destination demands it — an older Windows Media Player setup, a legacy car head unit, a piece of Windows software that accepts .wma and little else. If nothing is forcing the format, CAF to MP3 or CAF to AAC will play in far more places.
| Property | Value |
|---|---|
| Full name | Core Audio Format |
| Developer | Apple, part of the Core Audio framework |
| Type | Container — it does not fix the codec inside |
| Payloads it can hold | Linear PCM, Apple Lossless, IMA ADPCM, AAC and others |
| Size ceiling | None in practice: Apple's spec notes AIFF, AIFF-C and WAV "are limited in size to 4 gigabytes, which might represent as little as 15 minutes of audio", whereas CAF uses 64-bit file offsets |
| Extra data it can carry | Markers, regions, edit comments, MIDI, channel layout, peak and overview chunks, UMID |
| Native support | macOS and iOS |
| Property | Value |
|---|---|
| Full name | Windows Media Audio |
| Developer | Microsoft, introduced in 1999 |
| Container | ASF (Advanced Systems Format), which is what a .wma file actually is |
| Family members | Microsoft's audio encoder documents three output categories: Windows Media Audio Standard (format tag WAVE_FORMAT_WMAUDIO2, 0x0161), Professional (0x0162) and Lossless (0x0163) |
| What this converter writes | The Standard codec — offered as WMA v2, with WMA v1 available for very old decoders |
| Compression | Lossy, perceptual |
| Channels | Two, maximum |
| Sample rate | Up to 48 kHz |
| Bitrate | Clamped to 32-320 kbps for constant and custom bitrates |
| Native support | Windows Media Player and the Windows media stack; VLC and FFmpeg-based players elsewhere |
WMA Standard is a narrow target compared with the CAF it is reading, so a high-resolution master needs one setting changed before it will encode at all.
| Your CAF | What happens | What to do |
|---|---|---|
| 44.1 or 48 kHz, mono or stereo | Encodes directly | Nothing — leave the rate and channel on "Original" |
| 88.2 or 96 kHz high-resolution master | The Standard WMA encoder does not accept sample rates above 48 kHz | Set Audio Sample Rate to 48000 Hz before converting |
| Multichannel or surround | Folded down to stereo automatically, because the codec allows at most two channels | Nothing, unless the channel layout matters — then pick a different target |
| 24-bit or 32-bit PCM | Re-encoded to a lossy stream; bit depth is not a WMA concept | Use CAF to FLAC if depth must survive |
| Already lossy (AAC inside the CAF) | Decoded and re-encoded — a second lossy generation | Set the WMA bitrate at or above the source's |
.caf onto the page or click "+ Add Files" to browse. Several recordings can be queued and converted with the same settings in one pass.Convert to WMA when something concrete requires it: an old Windows Media Player workflow, a legacy in-car or hi-fi component that lists .wma on the box, or Windows software that will not accept anything else. WMA was Microsoft's answer to MP3 at the end of the 1990s and it never won broad support outside Windows — modern phones, browsers and streaming tools handle MP3 and AAC far more reliably. If the destination is not dictating the format, use CAF to MP3 for maximum compatibility or CAF to AAC for better quality per megabyte.
They are two generations of the same Standard codec. WMA v2 is the one in general use — Microsoft's encoder documentation lists it as Windows Media Audio Standard with the format tag WAVE_FORMAT_WMAUDIO2 (0x0161) — and it is what this converter writes unless you pick otherwise. WMA v1 is the original 1999 revision, kept available only because a handful of very old hardware decoders were built before v2 existed. If you are not troubleshooting such a device, leave it on v2.
No. Microsoft's audio encoder documents three separate output categories — Standard, Professional and Lossless — and this converter writes the Standard codec. That is the variant with the broadest decoder support, which is usually the entire reason someone wants a .wma in the first place. Professional's multichannel and high-resolution modes and Lossless's bit-exact mode are not produced here; for a genuinely lossless result, CAF to FLAC is the portable choice.
Because the Standard WMA codec does not encode above 48 kHz. Set Audio Sample Rate to 48000 Hz and the conversion proceeds normally; 48 kHz still covers the whole audible range, so this is a non-issue for playback. It is only a problem if you intended the WMA to be an archival transfer of a high-resolution master, which is not a job this format was designed for — keep the CAF, or make a lossless copy with CAF to WAV, and use the WMA purely for distribution.
It is downmixed to stereo automatically, because the codec accepts at most two channels. Nothing fails and nothing needs configuring, but the discrete channel layout is gone from the output. If the layout is the point of the file, convert to a format that can carry it — FLAC handles up to eight channels losslessly.
Yes, WMA is a lossy codec. If the CAF held uncompressed PCM or Apple Lossless, which is typical of a Logic Pro or GarageBand bounce, this is a clean first-generation encode and 192 kbps and above is hard to fault on ordinary playback gear. If the CAF already held a lossy payload you are on the second generation; the audio is decoded and re-encoded either way, since there is no repackage-only path.
Core Audio Format is implemented by Apple's Core Audio framework, and Windows has no native equivalent — most Windows players will not even recognize the container, let alone decode the payload inside it. That is the whole reason this conversion exists. Note that a converted WMA is playable by the built-in Windows stack, but MP3 is playable by that same stack and by everything else, which is why it is the safer default target.
Yes, and it is usually worth doing. CAF uses 64-bit file offsets specifically so it can hold very long recordings, so these files run to hours more often than you would expect. The Trim option takes a start time and a duration and exports only that region, which keeps the WMA small and skips encoding audio you were going to throw away. For finer editing before conversion, use the dedicated audio cutter. Whatever you upload travels over an encrypted connection, is converted on our servers, and is deleted automatically a few hours later — no sign-up, no watermark, never shared.