Start with the loudest part of the actual playlist, not a quiet introduction. Find the source OBS is capturing, watch that source’s meter while the audio plays, and reduce level upstream before adjusting the OBS fader.
If peaks still approach full scale, a Limiter on the captured source can cap them. It cannot make separate songs equally loud or repair distortion already baked into a file, so make a test recording and listen to it before leaving the playlist running.
Find the audio source OBS is capturing
First identify the route the sound takes into OBS. A playlist loaded as an OBS Media Source or VLC Video source has a dedicated mixer entry. If you play music in a browser, OBS may capture that application specifically, or it may capture desktop audio that includes the browser and other computer sounds. Those routes can look similar while behaving differently when another notification, tab, or application makes noise.
In the OBS Audio Mixer, locate the entry that responds when the playlist plays. Pause the playlist briefly, then resume it and watch which meter moves. If several meters respond, determine which one contains the music and whether another source is also contributing to the final mix. Do not assume that the visible player volume is the same as the level OBS receives.
A dedicated source is usually easier to inspect because its meter and fader refer to the playlist itself. VLC Video supports a playlist and provides loop and shuffle controls; it requires VLC to be available to OBS. A regular Media Source is intended for an individual media file. The comparison of OBS and VLC playlist approaches can help you choose a route based on how you want to arrange files, but either setup still needs a level check.
For browser playback, check whether the source is application audio capture, desktop audio, or a combination. If desktop audio is carrying the playlist plus system sounds, a notification can enter the stream even though the music source itself looked fine. Keep the mixer visible while testing, and mute unrelated sources temporarily if you need to isolate the path. Restore only the sources the programme actually needs once you know which one is carrying the playlist.
The OBS Audio Mixer Guide describes the mixer and its controls. Follow its guidance for the OBS version you use, since labels and controls can change. The important practical point is to monitor the source that actually reaches the recording or stream, rather than a different player or device that happens to show a volume slider.
Play the loudest sections and watch the meter
Do not judge a playlist by its first minute. Find the loudest expected song, chorus, drum hit, prayer bell, transition, or other peak, then let that section play while watching the meter for the captured source. Include any introduction or transition that is unusually loud. If your playlist contains several files, sample the loudest ones rather than assuming the first track represents the rest.
OBS meters show signal level, and their peak-hold indicator can help expose a brief transient that passes too quickly to notice by eye. The OBS Audio Mixer Guide describes the top indicator as showing the loudest level in the previous 20 seconds. Red is close to clipping; do not treat reaching red as a useful target. Give the output some margin rather than trying to use every bit of available level.
Digital full scale is 0 dBFS. A signal that reaches or exceeds the final digital ceiling can distort, though OBS can process floating-point audio above 0 dBFS internally in parts of its signal path. That means a value shown at one point is not, by itself, proof of what the final recorded output sounds like. You need to inspect the relevant captured source and listen to a test of the actual output.
Observe the meter over a representative section, not just one glance. A sustained passage and a sharp transient are different things: the former may sound too loud overall, while the latter may cross the ceiling for an instant. Peak hold is useful for spotting brief peaks, but it cannot tell you whether the song is balanced against the next track or whether the original file is already distorted.
If the source meter remains comfortable but the final mix sounds harsh, check the combined output as well. Two individually modest sources can add together when mixed. A browser playlist plus another audio source, for example, may sum higher than either source alone. Your test needs to include the combination you intend to broadcast, not only each source in isolation.
Lower gain at the earliest controllable point
When the captured source peaks too high, begin at the earliest place you can control its level. For a local file, lower the media playback level if that control is available. For a browser playlist, adjust the browser or application level where practical. If the source file itself is unusually hot, an audio editor can reduce its level before it enters OBS. Then play the loud section again and observe what arrives in the mixer.
The point of changing level early is to avoid feeding an unnecessarily hot signal into later stages. If the original file is already clipped, though, turning it down only makes the damaged audio quieter. It does not reconstruct waveform detail that was lost before OBS received it. Find a clean master or replace the track if the distortion is present in ordinary playback before OBS is involved.
If source-level controls are unavailable or not enough, reduce the OBS fader next. Make a small adjustment, replay the peak, and check the meter again. Keep track of which control you changed; changing a player volume, an operating-system volume, and the OBS fader all at once makes it harder to understand the result. The useful sequence is to reduce upstream gain first, then use the fader to set the source’s level in the OBS mix.
Listen at the earliest output you can access as well as through OBS. If the sound distorts before it reaches OBS, look upstream: lowering the OBS fader cannot undo clipping that has already occurred in a device or file. If it sounds clean at the source but distorts in the recording, inspect OBS levels, other sources, and processing in the path. This distinction saves time because it points you towards the stage where the problem begins.
For a playlist whose tracks differ substantially, avoid using a high track to set every track’s level by ear. Reduce the hot source as a temporary safeguard, then consider level-matching the individual files in an audio editor. Recheck the loudest peaks through OBS afterwards. A limiter can contain peaks, but it will not bring a quiet devotional track up to the perceived loudness of a heavily mastered recording.
Set the OBS source fader
Once upstream level is sensible, set the OBS source fader for the captured playlist. The fader changes how strongly that source contributes to the OBS mix. Adjust it while the loudest relevant material is playing, then check quieter sections too. The aim is a usable source level with headroom, not a meter that sits at the top of its range.
If you use multiple audio sources, test the fader setting with the whole intended mix. A quiet music source may appear harmless alone, but another programme source can add to it. Conversely, lowering a shared desktop source may reduce unrelated audio that you still need. For that reason, dedicated capture is easier to manage when the playlist must be controlled independently from notifications or other applications.
Do not infer a universal target from a single meter number. OBS documentation discusses alignment and permitted maximum levels as part of meter design, but those figures are not a target for every programme source or playlist. Your usable level depends on the material, the rest of the mix, and what the recorded output sounds like. Keep enough margin below full scale to accommodate peaks and later changes, then verify by listening.
A separate issue is continuity between tracks. If one song is much quieter than the next, raising the common fader may cause the loud song to peak while leaving the quiet one relatively low. In that case, the fader is not a track-by-track balancing tool. Level-match the files before playback, or accept that the playlist will have audible changes in loudness. The article on fixing audio gaps in a 24/7 playlist stream addresses gaps between files; level jumps are a different problem, even though both are easier to judge with a representative test.
Add and position a Limiter filter if needed
Use a Limiter only if upstream gain reduction and the source fader still leave occasional peaks too close to the ceiling. In OBS, open the captured source’s filter controls and add the built-in Limiter. Apply it to the source whose peaks you are trying to contain, not to a different meter simply because it is convenient. Then replay the loud passage and check the output again.
Set its threshold below 0 dBFS to leave headroom. OBS documents a default threshold of -6.00 dB and a release of 60 ms; these are software defaults, not instructions that they suit every playlist. Start from an appropriate setting, then listen and measure your own material. A threshold that catches occasional peaks may behave differently on a track with frequent, dense peaks.
Put the Limiter last in that source’s filter chain. The OBS Project Limiter Filter documentation says that a Limiter should be the last filter in the chain. If another gain-raising filter follows it, that later processing can undo the ceiling you expected. Also check whether other sources are summed later in the mix: a limiter on one source does not by itself control the combined level of every source at the final output.
A limiter caps peaks that reach it; it does not level-match songs or repair already-clipped audio. Compression is a separate kind of processing that reduces dynamic peaks, and it can change how a source behaves. A compressor on a programme mix can also duck desktop or other audio when a microphone speaks, so do not add one without a clear need and a listening test. Neither processor automatically makes separately mastered tracks equally loud overall.
If peaks still appear to overload after adding a limiter, confirm that it is attached to the correct captured source, enabled, and last in its filter chain. Then make a recording and check the combined output. A meter on one source cannot tell you whether later summing or processing has caused the final mix to overload. If the track sounds distorted before OBS, replace or repair the source material rather than expecting a filter to restore missing audio detail.
Make a test recording and listen back
Before relying on the setup for a long stream, record a representative segment using the same OBS audio path and settings you plan to use live. Include the loudest section, a quieter passage, a transition between tracks, and any other source that will be mixed with the playlist. If the playlist is long, you do not need to listen to every minute to discover a peak problem, but the sample should represent the parts most likely to expose it.
Listen to the file from beginning to end at a sensible monitoring level. Check for crackle, harshness, flattened transients, sudden jumps between tracks, silence at transitions, and unwanted desktop sounds. Compare suspicious moments with the original file played outside OBS. If both sound distorted, the source may be clipped already; if the original sounds clean but the test recording does not, trace the OBS capture and mix path again.
Use the test to distinguish two questions: are the peaks controlled, and is the playlist consistent enough for its purpose? A Limiter may help with the first while leaving the second unchanged. If a quiet track is difficult to hear after a loud one, process or replace the individual files and then repeat the peak check. Do not respond by raising the whole playlist until the loudest song reaches full scale.
Once you are satisfied, save the OBS scene or profile state you tested and avoid making untested level changes immediately before leaving the stream unattended. If you do change a file, source route, fader, filter order, or other audio setting, record another short sample. This is especially useful when a playlist runs overnight: a quick test catches a misplaced source or unexpected peak before it becomes hours of distorted output.
For a continuous channel, audio checks sit alongside stream continuity checks. The guide to checking whether a YouTube live stream is actually looping covers a separate operational question: whether the broadcast continues as intended. A successful loop does not prove the audio is clean, just as a clean test recording does not prove that a live stream will remain connected.
When the repeated work of keeping a computer awake and checking a long-running broadcast is itself a problem, StreamNeo removes that specific burden by letting you upload a video and run its YouTube broadcast with your computer switched off; you still need to prepare clean audio and verify the result.
When your audio path and test file are ready, compare the operating choices and decide how you want to run the channel.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Why does OBS show a peak even when the player volume is low?
The player’s volume setting does not map directly to a particular OBS meter level. OBS may capture application audio, desktop audio, or another route, and the level can be affected by controls along that path. Watch the meter for the source OBS actually records and test the captured output.
Will a Limiter make every playlist track the same volume?
No. A Limiter constrains peaks that reach it; it does not raise quieter tracks to match louder ones. If the difference is distracting, level-match the files individually and check their peaks again through OBS.
Can lowering the OBS fader fix a file that is already distorted?
It can make the distorted audio quieter, but it cannot restore detail clipped in the original file. Compare ordinary playback of the file with an OBS test recording. Replace it with a clean source if the distortion is already present.
Do I need a Limiter if the meter stays out of red?
Not necessarily. The meter helps you spot peaks, but it cannot guarantee that playback is free of distortion or that the final combined output is safe. Start by controlling gain upstream and with the fader, then make and listen to a representative test recording before deciding whether a Limiter is needed.