Initializing... drag & drop files here
Supports: CAF
.caf audio. Logic Pro bounces, GarageBand exports, Soundtrack Pro renders, and iOS field recordings are all accepted. Batch is supported — drop a whole session folder at once.CAF (Core Audio Format) is Apple's audio container, released with Mac OS X 10.4 Tiger in 2005. It uses 64-bit file offsets, so unlike WAV and AIFF — which both cap at 4 GB — a CAF file can hold practically unlimited audio (Apple's spec literally allows hundreds of years at 16-bit/44.1 kHz). MOV is Apple's QuickTime container, introduced in December 1991, and went on to become the basis for the MPEG-4 file format and the ISO Base Media File Format that underpins MP4, 3GP, and many modern containers. Converting CAF → MOV rewraps the audio into a QuickTime stream so video tools can ingest it.
| Property | CAF (source) | MOV (output) |
|---|---|---|
| Type | Audio-only container | Multimedia container (audio + video + text tracks) |
| Released | 2005 (Mac OS X 10.4 Tiger) | 1991 (QuickTime 1.0) |
| File-size cap | None (64-bit offsets) | None (64-bit offsets) |
| Default audio codec on xconvert | n/a (already encoded) | AAC |
| Audio codecs supported | PCM, ALAC, AAC, MP3, IMA4, μ-law, A-law, more | PCM, AAC, ALAC, AC-3, MP3, others |
| Native macOS apps | Logic Pro, GarageBand, Soundtrack Pro | Final Cut Pro, iMovie, QuickTime Player, Motion |
| Cross-platform support | Mac-centric; limited Windows playback | Broad — Mac, Windows (via QuickTime / players), most NLEs |
| Best for | Long recordings, surround stems, Apple-only workflows | Delivering audio into video editors, NLE timelines |
| Mode | What it controls | Pick when |
|---|---|---|
| Quality Preset (Very High default) | A simple Highest → Lowest dial; encoder targets a quality band | You want a one-click "sounds great" result without thinking about numbers |
| Constant Bitrate (CBR) | Encoder holds a fixed bitrate (e.g. 192 / 256 kbps) | You need predictable file size for streaming or broadcast spec |
| Variable Bitrate (VBR) | Encoder spends bits where audio is complex, fewer in silence | You want better quality-per-byte for music and dialogue mixes |
| Constant Quality (CRF-style) | You set a perceptual quality target; bitrate floats | You want consistent perceived quality across files of varying complexity |
| Constraint Quality | Quality target with min/max bitrate guardrails | You need quality-driven encoding but with a hard ceiling for delivery limits |
No real video, no. CAF is audio-only, so the resulting MOV is functionally an audio-only QuickTime file. Some editors render a black or background-color frame for visual placeholder so the audio track lines up against video timelines, but no source imagery is added. If you only need audio without any video container, CAF to M4A or CAF to AAC are smaller and simpler.
Both work for moving audio into a video editor, but MOV is the native QuickTime container — Final Cut Pro, Motion, and Compressor were built around it, and it preserves a few QuickTime-specific atoms (timecode tracks, edit-decision markers) that strict MP4 doesn't. MP4 is more portable for Windows / Android / web. If your destination is Final Cut or another macOS-native tool, MOV; if it's a general-purpose video pipeline, CAF to MP4 is often easier downstream.
xconvert re-encodes to AAC by default in this conversion (so the MOV plays cleanly across players that don't support every CAF interior codec). If your CAF interior codec is already AAC, that's a transparent transcode at the bitrate you choose. If the interior is PCM or ALAC, expect a quality step at the encoder (set 256-320 kbps to keep that step inaudible) — or convert to CAF to WAV first if you need a lossless intermediate.
For music and full-band content, 256 kbps AAC is effectively transparent vs the source — most listeners can't ABX it. 192 kbps is the standard "good music" target. 128 kbps is fine for spoken-word, podcasts, and lecture audio. AAC is roughly 30% more efficient than MP3 at the same perceived quality, so don't reach for 320 kbps unless you need it.
Partially. CAF can carry rich metadata — markers, channel layouts, region info, text annotations — but MOV's audio track structure stores only a subset (channel layout and basic metadata). Punch markers and Logic-specific region annotations generally do not survive the rewrap. If marker preservation matters, export from Logic Pro directly to MOV using its built-in bounce-to-movie option instead.
Yes — that's actually the case CAF was designed for. Files larger than 4 GB and recordings several hours long are processed normally. Be aware that very large source files take proportionally longer to upload and encode in the browser; for multi-gigabyte files a wired connection helps.
Final Cut Pro X usually accepts CAF, but older Final Cut versions and Premiere on Windows can choke on certain CAF interior codecs (especially Apple-only ones like IMA4 or ALAC variants). Rewrapping to MOV with AAC audio is the universally-imported path — the same logic editors use when sending audio between Mac and Windows post houses.
Yes. Use Trim → Time Range with start time and duration. Both accept seconds (e.g. 12.5) or HH:MM:SS.sss (e.g. 00:01:30.500). Useful for pulling a single take from a long Logic bounce or extracting a section of a multi-hour live capture without sending the whole CAF through.
The reverse direction is MOV to MP3 — extract the audio track from any MOV into a stand-alone MP3 file.