Save AIFF with Tags 💿

Save AIFF with Tags 💿 is the comfy-audio-tagger node you'll probably scroll past, and for most people that's correct. AIFF is the 1988-era uncompressed audio format that Apple never quite let die, and its only real stronghold today is pro audio - old DAWs, broadcast workflows, and a surprising amount of Mac-native audio software that still treats it as the safe interchange format. If your generated track is heading into that world, this is the node that gets it there with tags intact.

Same node, different container

The input schema is the pack standard - audio, filename_prefix (default audio/ComfyUI_AIFF), all the tag strings, the license dropdown, multiline comment/lyrics, optional cover_image - and the outputs are audio passthrough plus file_path. Functionally it's the MP3 node's twin, because AIFF tags with the same standard: ID3v2. The source literally imports the same ID3 frame types (TIT2, TPE1, USLT, APIC, TXXX for license) and writes them the same way. If you've used Save MP3 with Tags, this requires zero new learning.

One important correction to how it's usually pitched: the README calls AIFF "Uncompressed Apple Lossless," which is a contradiction in terms. AIFF is plain uncompressed PCM - the audio equivalent of a BMP. It's the opposite of lossless compression, and it's why files are enormous. (There's a compressed variant, AIFF-C, but this node doesn't write it.) So the actual reason to use AIFF is not quality - FLAC preserves every bit at a fraction of the size - it's compatibility with old pro-audio tools that only take AIFF.

The gotchas

• File size is the headline problem. Uncompressed stereo at 44.1kHz runs about 10 MB per minute. A five-minute generated track is 50MB for no quality benefit over FLAC. If you're not sending to a legacy tool, you're paying disk space for nothing.
• Tagging is ID3v2.3, not AIFF-native. ID3 support in AIFF is a de-facto convention rather than a deep standard. Modern music players that read ID3 will show your tags fine; a bare-bones broadcast tool that reads only the AIFF chunks won't see them at all. If tags are the whole point, test the destination before you trust it.
• Encode failure is silent. Like MP3 and M4A, the save wraps the torchaudio encode in a try/except - if it fails, the node warns in the console and passes the audio through with an empty file_path. AIFF is one of the more portable formats for torchaudio, so this is unlikely to trigger, but know the tell.

Install

Same single-repo, single-dependency story as the whole pack:

cd ComfyUI/custom_nodes
git clone https://github.com/lakeconstance78/comfy-audio-tagger
cd comfy-audio-tagger
pip install -r requirements.txt   # Windows portable: ..\..\..\python_embeded\python.exe -m pip install -r requirements.txt

or search "ComfyUI Audio Tagger" in ComfyUI Manager, then restart.

The verdict

Reach for this node exactly when a DAW, a broadcast suite, or an old Mac app demands AIFF and won't take anything else. For every other use, FLAC is strictly better - same losslessness, a tenth of the size, and better tag support. It's the most ignorable node in this pack, but if you've ever been stuck with a tool that "only does AIFF," you'll be glad it's there.