Convert WTV to AIF — Free Online Tool
Convert WTV recorded TV files to AIF, extracting the audio track as uncompressed PCM and discarding the video stream. This is ideal for pulling high-fidelity audio from Windows Media Center recordings into a lossless format natively compatible with Apple tools like Logic Pro and GarageBand.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your WTV 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
WTV files produced by Windows Media Center typically contain an H.264 video stream alongside an AAC or MP3 audio track. During this conversion, FFmpeg discards the video stream entirely and decodes the compressed audio (commonly AAC) from the WTV container, then re-encodes it as 16-bit big-endian signed PCM (pcm_s16be) — the standard codec for AIF files. Because AIF is a purely audio container with no video support, only the first audio track is extracted. The result is an uncompressed AIFF file: larger than the original audio but with no generation loss beyond the initial decode of the lossy source.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary, the open-source multimedia processing engine that handles demuxing the WTV container, decoding the compressed audio stream, and encoding the uncompressed PCM output into the AIF file. |
-i input.wtv
|
Specifies the input file — a WTV recording produced by Windows Media Center. FFmpeg automatically detects the ASF-derived WTV container and identifies the available video and audio streams within it. |
-c:a pcm_s16be
|
Sets the audio codec for the output to 16-bit signed big-endian PCM, which is the standard uncompressed audio encoding required by the AIF format specification. FFmpeg decodes the lossy source audio (typically AAC or MP3 from the WTV file) and re-encodes it into this uncompressed representation. |
output.aif
|
Defines the output filename with the .aif extension, which tells FFmpeg to write an Audio Interchange File Format container. Because AIF is audio-only, FFmpeg automatically drops the video stream from the WTV source without requiring an explicit '-vn' flag. |
Common Use Cases
- Pulling the audio commentary or narration from a recorded TV documentary to edit in Logic Pro or GarageBand on a Mac
- Extracting a live musical performance broadcast recorded with Windows Media Center to import into a DAW as a lossless working file
- Archiving the audio from a sports broadcast recording in an uncompressed format for long-term preservation before the WTV file is deleted
- Isolating dialogue or interviews from a recorded news segment to use as high-quality audio clips in a video production project
- Converting recorded TV audio to AIF for import into Final Cut Pro, which handles AIF natively for audio-only timeline tracks
- Preparing broadcast audio extracted from a WTV recording for further processing or mastering where an uncompressed intermediate format is required
Frequently Asked Questions
No. WTV recordings typically store audio as AAC or MP3, which are lossy formats. This conversion decodes that compressed audio and stores it as uncompressed PCM in the AIF file, but any quality lost during the original broadcast compression cannot be recovered. The AIF file will be lossless in the sense that no further quality degradation occurs during the FFmpeg conversion itself, but it is not truly lossless end-to-end because the source was lossy.
The video stream is completely discarded. AIF is a pure audio container and has no capability to store video data. FFmpeg implicitly drops the video track when writing to an AIF output. If you need to keep the video, you should convert to a format like MKV or MP4 instead.
By default, FFmpeg selects the first audio track it identifies in the WTV file. WTV supports multiple audio tracks (for example, secondary audio programming used in broadcast TV), but AIF does not support multiple audio tracks in a single file. If you need a specific non-default track, you can modify the command by adding '-map 0:a:1' (for the second audio track) before the output filename to select it explicitly.
AIF stores audio as uncompressed PCM, meaning every sample is stored as raw data with no compression. A typical AAC audio track inside a WTV file might be encoded at 128–192 kbps, while the equivalent pcm_s16be stream in AIF at CD quality (44.1 kHz stereo) uses approximately 1,411 kbps. A one-hour recording could produce an AIF file of 600 MB or more, compared to a much smaller compressed source audio track.
Replace 'pcm_s16be' with 'pcm_s24be' in the command: 'ffmpeg -i input.wtv -c:a pcm_s24be output.aif'. AIF supports 16-bit, 24-bit, and 32-bit signed big-endian PCM as well as 32-bit and 64-bit floating-point variants. Choosing pcm_s24be gives you 24-bit depth, which is commonly preferred in professional audio workflows, though note that the source audio from a broadcast WTV recording is unlikely to contain content that genuinely benefits from depth beyond 16-bit.
Largely no. WTV files embed rich DVR metadata including program title, channel name, broadcast time, and episode descriptions using Windows-specific metadata fields. AIF supports only a limited set of standard audio metadata fields (such as artist and title via AIFF chunk structures), and FFmpeg does not automatically map WTV-specific broadcast metadata to AIF fields. You should expect most recording metadata to be lost in the output file.
Technical Notes
The FFmpeg command targets pcm_s16be — 16-bit signed big-endian PCM — which is the canonical default codec for AIF files and ensures compatibility with virtually all Apple software including Logic Pro, GarageBand, Final Cut Pro, and QuickTime. The big-endian byte order is intrinsic to the AIFF format specification (as opposed to AIFF-C, which permits little-endian PCM). WTV files created by Windows Vista and later Media Center versions use an ASF-derived container and may contain H.264 (libx264) or MJPEG video alongside AAC or MP3 audio; FFmpeg's WTV demuxer handles all of these combinations reliably. Because the tool extracts only one audio track, users with WTV recordings that contain secondary audio programming (SAP) must manually specify an alternate audio stream mapping if needed. Subtitles and chapter data present in the WTV file are not transferred, as AIF supports neither. The sample rate of the output will match whatever sample rate is present in the source audio stream — FFmpeg does not resample unless explicitly instructed — so broadcast audio at 48 kHz will produce a 48 kHz AIF file rather than the 44.1 kHz CD standard.