Mixing Jingles for Streaming Radio vs. Traditional Broadcast

Jingles remain one of the most powerful branding tools in radio—they carve out a station’s identity, cue listeners emotionally, and smooth transitions between songs and ads. But the way a jingle is mixed determines whether it cuts through the clutter or gets lost. Mixing for streaming platforms like TuneIn, iHeartRadio, or station websites demands a fundamentally different approach than mixing for FM, AM, or DAB. Streaming audio goes through lossy codecs, loudness normalization algorithms, and a wide variety of playback devices—from budget smartphone speakers to high-end headphones. Traditional broadcast, on the other hand, passes through analog transmission chains, heavy processing, and often mono summing. An engineer who understands these technical and creative differences can deliver jingles that sound punchy, clear, and emotionally engaging on every platform.

Technical Foundations of Jingle Mixing

Audio Codecs and Bitrates

The most immediate difference lies in how the audio is encoded. Streaming services use lossy compression codecs such as MP3 (64–320 kbps) or AAC (typically 128–256 kbps). Even platforms that offer lossless files (FLAC, ALAC) often transcode to a lossy format before streaming to save bandwidth. These encoders truncate high frequencies above 16 kHz, smear transient attacks, and introduce quantization noise that can make a jingle’s vocals and percussion sound dull or gritty. The artifact known as “pre-echo” is particularly damaging to short, percussive jingle hits—the codec spreads energy before the transient, blurring the punch.

Traditional broadcast uses analog transmission for FM and AM, with digital options like DAB+ gaining ground. FM stereo has a theoretical frequency response up to about 15 kHz due to pre-emphasis/de-emphasis curves (50 µs or 75 µs time constants). AM is severely bandwidth-limited, rolling off sharply above 5 kHz and lacking stereo separation. DAB+ uses HE-AAC at bitrates of 48–128 kbps, which is similar to streaming but with a different processing chain before the encoder. The station’s studio-transmitter link (STL) can be analog or digital, each adding its own coloration.

Practical takeaway: When mixing for streaming, assume the final encode will be AAC at 128 kbps or MP3 at 192 kbps. Avoid relying on extreme high-frequency content above 15 kHz for musical impact—those frequencies will be heavily reduced or aliased. Keep transients clean and avoid excessive high-frequency sibilance that the codec will exaggerate. For broadcast (especially AM), focus energy in the mid-range (500 Hz–4 kHz) where intelligibility and impact live. Sub-bass below 60 Hz should be used sparingly; on AM it will be lost, and on FM it can cause distortion in the station’s limiter.

Additional nuance: The AAC codec (used by most streaming platforms) is generally more efficient than MP3, but it introduces a different type of artifact—spectral band replication can make hats and cymbals sound “swirly.” Listen to your jingle encoded with the platform’s actual codec during the QC stage. Free tools like FFmpeg or online encoders allow you to test this quickly.

Loudness Normalization and Standards

Streaming platforms apply loudness normalization to maintain consistent listening levels. Spotify, Apple Music, and YouTube all target an integrated loudness of approximately –14 LUFS (Loudness Units relative to Full Scale) with a true peak ceiling of –1 dBTP or –2 dBTP. If your jingle is louder than the target, the platform will turn it down, potentially crushing dynamics and making it sound flat. If it’s too quiet, the platform will boost it, raising the noise floor and exposing hiss, rumble, or even low-level digital artifacts.

Traditional broadcast is governed by stricter loudness regulations. The EBU R128 standard (used by many European and network broadcasters) specifies a target of –23 LUFS (±0.5 LU) with a true peak of –1 dBTP. In the U.S., the ITU‑R BS.1770 recommendation is often followed, though some stations use their own internal targets. The broadcast chain also includes a multiband processor (like an Orban Optimod or Omnia) that further shapes loudness and consistency. If the jingle is delivered too hot, the processor will clamp down hard, causing audible pumping and distortion. If it’s too quiet, the processor will boost gain excessively, raising noise and making the jingle sound thin.

Key action: Use a reliable loudness meter (Youlean Loudness Meter, iZotope Insight, or mloudness) to measure integrated LUFS and true peak. For streaming jingles, aim for –14 LUFS integrated with a true peak no higher than –1 dBTP. For broadcast, deliver jingles at –23 LUFS (±0.5) or according to the station’s specific spec. Many production houses now provide both a streaming mix and a broadcast mix, clearly labeled.

Platform-specific notes: YouTube may apply additional loudness normalization and also uses a –14 LUFS target, but its encoder can introduce artifacts on highly compressed material. Apple Music uses Sound Check, which can shift the perceived balance if the jingle has a wide dynamic range. Always test on the actual platform if possible.

Dynamic Range and Compression

Dynamic range handling is where streaming and broadcast mixes diverge most sharply. Streaming encoders struggle with sudden loud transients—a snare hit that peaks 12 dB above the average level can cause pre-echo or spectral spreading in the encoded audio. To mitigate this, use gentle, transparent compression on the mix bus with a ratio of 1.5:1 to 2:1, a low threshold, and a fast attack (10–20 ms) to catch the peaks without pumping the musical feel. Follow with a brickwall limiter that catches only the highest peaks (1–2 dB of gain reduction) and set the output ceiling at –1 dBTP.

Traditional broadcast transmission includes heavy processing designed to maximize coverage and perceived loudness. The station’s multiband compressor will react differently to different frequency bands—if the jingle has a wide dynamic range, the processor can squash it unpredictably, causing audible pumping on kick drums or sibilance on vocals. For broadcast jingles, a more aggressive compression approach is beneficial: ratio 3:1 to 4:1, attack 5–10 ms, release 100–200 ms, aiming for 3–5 dB of gain reduction on the mix bus. This pre-processes the jingle so that the station’s processor doesn’t have to work as hard, preserving the intended punch and clarity.

Tip for consistency: If the station uses an Orban Optimod 8700i or Omnia.9, ask for the processing preset or at least the average “dial loudness” value. You can then run your jingle through a plugin that emulates broadcast processing (like the Orban Loudness Meter with a processing simulation, or the free iZotope Ozone with a multiband compressor set to similar parameters). This audition step can reveal issues before delivery.

Creative Approaches for Each Platform

Frequency Balance and EQ Strategies

While every jingle should sound musical and well-balanced, the optimal EQ curve shifts depending on the destination. For streaming, the lossy codec tends to exaggerate artifacts in the 5–7 kHz range (sibilance and harshness) and rolls off energy above 15 kHz. Use a de-esser set to around 6 kHz with 2–3 dB of reduction, and apply a gentle low-pass filter at 15–16 kHz to prevent aliasing. Boost the upper mids (2–4 kHz) slightly to maintain vocal clarity through the codec.

For FM broadcast, the pre-emphasis curve boosts high frequencies at the transmitter, which is then de-emphasized at the receiver. This theoretically results in a flat response, but if the jingle has strong content around 10 kHz, it can cause distortion or listener fatigue after processing. Apply a gentle high-frequency shelf cut of 1–2 dB at 10 kHz to compensate. AM broadcast demands a completely different approach: boost the mid-range (1–4 kHz) for intelligibility, high-pass filter at 60–80 Hz to remove sub-bass, and use a tight low-pass filter at 5 kHz to avoid out-of-band interference. Some AM stations also use a bandwidth filter that further restricts the signal—know your client’s transmitter setup.

Pro tip: For a jingle that will air on multiple platforms, create two separate mixes. The time investment is small compared to the improvement in clarity and impact. If a single mix must serve both, compromise with a broadcast-friendly EQ (moderate high-frequency roll-off) and a streaming-friendly compression profile (less aggressive).

Stereo Imaging and Mono Compatibility

A large percentage of radio listening is in mono—car radios with marginal FM reception, AM broadcasts, and many streaming listeners using a single Bluetooth speaker. A jingle that sounds wide in stereo can collapse to a thin, phasey mess when summed to mono. Essential elements—vocals, kick drum, snare, bass—must remain centered. Avoid stereo-widening plugins that rely on polarity inversion or mid-side delay tricks; they create cancellation when summed. Use tools like the iZotope Ozone Imager in “Stereoize” mode with caution, and always check mono compatibility by summing the left and right channels.

For traditional broadcast, the station often sums to mono for AM or weak FM areas. Extreme panning—hard-left guitar, hard-right vocals—can cause the vocal to drop 6 dB in the mono sum, creating a “hole” in the mix. Keep lead vocals, snare, and bass centered. Use stereo spread only for background pads, harmonies, or percussion that is not critical to the core identity. Streaming, by contrast, can preserve true stereo width because the codec encodes stereo separation efficiently. Moderate stereo enhancement—Haas delays on background elements, chorus on synth pads—can add depth without compromising mono fold-down, as long as you verify the mono sum sounds full.

Testing method: Export a 30-second loop of your jingle and load it into an audio editor. Sum to mono and listen at a moderate level. If the vocal becomes noticeably quieter or the kick loses punch, go back and adjust panning or use mid-side EQ to narrow the sides.

Branding and Listener Engagement Through Production Style

Jingles are not just audio filler—they are sonic logos. In the broadcast world, a jingle often serves as a station ID, a sweep, or a drop-in that must grab attention in a high-energy environment. The mix should be punchy, with a clear vocal that cuts through the station’s dense processing. Layered harmonies, sound effects, and a tail that blends seamlessly into the next song are common. Because broadcast jingles are played through heavy compression, they need to be “finished” and robust; subtle dynamics will be lost.

Streaming jingles, on the other hand, are heard in a less processed context—as part of a podcast, an ad break, or a curated playlist. They can afford to be more transparent and dynamic. You can include nuanced production details like reverb tails, harmonic complexity, and gentle stereo width that would be squashed on broadcast. However, keep in mind that many streaming listeners are on mobile devices or laptops with limited bass response. Vocal clarity and a strong mid-range remain paramount. A jingle that sounds too hot or over-compressed on streaming can feel fatiguing on headphones.

Psychological consideration: Listeners on streaming platforms often have the option to skip—jingle length and impact are critical. A well-mixed jingle that stands out in a playlist can reinforce station brand recall. For broadcast, the jingle must grab attention in a noisy frequency band and overcome listener dial-twisting. A bright, upfront vocal with a strong hook works best.

Practical Workflow Tips for Jingle Mixing

Source Material Preparation

Start with the highest quality source files: 24-bit, 48 kHz WAV or AIFF. This sample rate is standard for both broadcast and streaming. If the jingle includes voice-over, record in a treated booth with a high-quality condenser microphone and a clean preamp; any room tone or hiss will be magnified by lossy encoding or broadcast processing. For music elements, request stems or multitracks instead of a pre-mixed stereo file. This gives you the flexibility to adjust individual instrument levels, apply EQ per stem, and fine-tune the blend for the target platform.

For voice-over, use a pop filter and maintain a consistent mouth-to-mic distance. Record at 24-bit/48 kHz. Apply a high-pass filter at 80 Hz to remove low-end rumble, and a gentle de-esser around 6 kHz before adding compression. Leave some headroom (peaks around –12 dBFS) to allow for processing later.

Mixing Chain for Streaming

Set up your DAW with a chain tailored to streaming codecs. Start with a high-pass filter at 30–40 Hz to remove sub-sonic rumbles that waste headroom. Add a low-pass filter at 15–16 kHz to prevent aliasing. Use a de-esser at 5–7 kHz with 2–3 dB reduction on vocal and sibilant elements. Follow with a gentle bus compressor (SSL-style or similar) with a ratio of 2:1, attack 10–30 ms, release 100 ms, aiming for 1–2 dB of gain reduction. Then a brickwall limiter with the output ceiling at –1 dBTP and enough input gain to catch only the loudest peaks (1–2 dB GR). Finally, measure integrated LUFS with a loudness meter; adjust the limiter output or use makeup gain to hit –14 LUFS. For platforms like YouTube that use a lower target (–14 LUFS), this works directly. For Spotify or Apple Music, the jingle will be normalized to –14 LUFS but may benefit from a slightly louder mix (around –12 LUFS) if the platform allows, though that risks the platform turning it down and reducing dynamics.

Mixing Chain for Broadcast

For FM or AM jingles, use a more aggressive chain. High-pass filter at 40–50 Hz (FM) or 60–80 Hz (AM). Low-pass filter at 14–15 kHz (FM) or 5–6 kHz (AM). Insert a multiband compressor (3-band) to even out the mix: tighten the low end with a slower attack, control mid-range presence, tame high-frequency sibilance. Follow with a wideband compressor with ratio 3:1 to 4:1, attack 5 ms, release 200 ms, aiming for 3–4 dB of gain reduction. Then a brickwall limiter with output ceiling at –1 dBTP and 2–4 dB of gain reduction. Deliver the final jingle at an integrated loudness of –16 LUFS (or –14 LUFS if the station specifies) to leave headroom for the station’s processor. Many production houses deliver broadcast jingles at –16 LUFS as a safe middle ground.

For DAB+: DAB+ uses HE-AAC at bitrates around 48–128 kbps. The mixing chain should be similar to streaming but with a lower low-pass filter (14 kHz) to avoid artifacts from spectral band replication. Deliver at –14 LUFS or per client spec.

Latency and Synchronization Considerations

One often-overlooked difference is latency. Streaming services introduce buffering delays of 2–10 seconds or more, depending on the connection. This delay is irrelevant for the jingle’s audio quality, but it affects how the jingle integrates with live elements. For example, if a DJ talks over the jingle, the timing may be off for streaming listeners. When mixing jingles for streaming, avoid tight synchronization that relies on real-time cues—make the jingle self-contained with clear starts and ends. For broadcast, near-zero latency is typical, so jingles can interact with live voice or ad breaks in real time. If the jingle includes a tail that fades into the next element, ensure the fade is long enough to accommodate both environments.

Quality Control and Testing

Before finalizing, test the jingle through realistic listening scenarios. Export a 30-second loop and listen through consumer earbuds (Apple EarPods or similar) to check for harshness. Downsample to a 128 kbps MP3 using an encoder like Fraunhofer or FFmpeg to hear what a typical streaming listener experiences. Play the jingle through a car stereo system (or a simulator like Waves Greg Wells VoiceCentric) to approximate broadcast reception. Check mono compatibility by summing left and right channels—phase issues become obvious. Use a loudness meter to confirm compliance with target standards.

Additionally, listen at low volume—a good jingle mix should still sound balanced and clear even when played softly. Streaming listeners may be in quiet environments, while broadcast listeners often have the radio on as background noise. A mix that relies on loudness alone will disappoint at lower levels.

Delivering to Clients

Provide both a streaming-optimized version (labeled “-stream”) and a broadcast-optimized version (labeled “-broadcast”). Use 24-bit/48 kHz WAV files for broadcast (they can handle the station’s processing), and 16-bit/44.1 kHz WAV or FLAC for streaming. Include a simple PDF note specifying the integrated LUFS and true peak values. Many stations now appreciate receiving both versions so they can choose based on their workflow. If the client doesn’t specify, default to streaming specs as the safer choice.

Conclusion

Mixing jingles for streaming radio versus traditional broadcast is not a one-size-fits-all job. Streaming demands a mix that withstands lossy compression, adheres to loudness normalization targets, and works well on mono mobile speakers while offering stereo width for headphones. Traditional broadcast requires a mix that can survive heavy processing, mono summing, and the frequency limitations of FM and AM transmission, all while maintaining impact and vocal clarity.

By understanding the technical differences—codecs, loudness standards, dynamic range, EQ strategies, and stereo behavior—you can craft jingles that sound their best on each platform. The extra investment of building two separate mixes is rewarded with a cleaner, more professional end product that strengthens the station’s brand across every listening environment. Whether your jingle airs on a car radio, a streaming app, or a digital audio stream, the right mixing approach ensures that listeners hear it exactly as the creative team intended.

Resources: