By Dylan Owen, VP Streaming & CTV Solutions, JWX
On July 1, California became the first state to make it illegal for streaming services to play ads louder than the content around them. Loud ad breaks have been one of the most persistent viewer complaints in ad-supported streaming for years; they are now a compliance obligation for any service reaching the country's largest market.
California's SB 576 prohibits streaming services from transmitting ads at a louder volume than the content they accompany, extending into streaming the standard broadcast and cable have followed under the federal CALM Act since 2010. It applies to any ad-supported service reaching viewers in California, on any device.
The law specifies exactly how compliance is measured: loudness is assessed in LUFS, the same industry-standard unit that underpins the CALM Act's broadcast rules. And its reach extends well beyond state lines: California is too large a market for any streamer to carve out, and states like Illinois are already following with their own versions. In practice, this is a national standard arriving state by state.
So the question for every ad-supported streamer is simple: can you guarantee that every ad in every break sits at the same level as your content? For most, the honest answer is no. Ads arrive from a long chain of buyers, exchanges, and ad servers, each spot mastered to a different loudness target - and by the time they reach the viewer's device, there is no opportunity left to correct them. Your library can be perfect and your ad breaks can still break the law.
For JWX customers, the building blocks were already in the stack.
Ad loudness normalization is built directly into our server-side ad insertion (SSAI). Because JWX stitches ads server-side, every single spot passes through our infrastructure before it reaches the viewer - which makes SSAI the only point in the delivery chain where loudness can be guaranteed rather than hoped for. Client-side insertion hands the ad to the device exactly as it arrived.
We brought those capabilities together into a single workflow. Streamers set their target loudness levels once, in LUFS, to the exact specification of the legislation, and JWX aligns everything to that target: the content and the ads, across both VOD and FAST channels. There is no dependency on advertisers mastering their spots correctly, no reliance on loudness metadata surviving the programmatic supply chain, no additional content mastering workflows and no device-level fixes downstream. You define the number; the stream that leaves meets it.
The workflow is live in production today, and because it is part of the JWX streaming stack any current or future customer can switch it on without re-engineering their ad path or content pipeline.
It would be easy to frame this purely as a legal checkbox. That undersells it.
Loud ads are one of the most cited frustrations in ad-supported streaming, and every jarring volume spike is a micro-incentive to mute, skip, or open a competitor's app. Ads that sit at the same level as the content get watched rather than muted, which is better for viewers, better for advertisers, and better for the yield on every impression. The streamers who treat SB 576 as a floor will do the minimum. The ones who treat consistent loudness as part of the viewing experience will quietly earn more attention per ad break.
If you stream ad-supported content to viewers in the US, this legislation already applies to you, and the map is only going to fill in from here.
If you are a JWX customer, the path to compliance is short: set your target levels, and the stack does the rest. If you are not yet a JWX customer and July 1 arrived faster than your roadmap did, we should talk.
The loud ad era is over. Our customers are ready for the quiet one.