A WAV file is audio, not a complete YouTube video stream. To broadcast it live, use OBS Studio to place the WAV in a scene alongside a still image or another visual source, then send that scene to YouTube with an encoder stream.
The reliable part of this workflow is checking each link in the chain before you publish: the file must play in OBS, the scene must contain a visible picture, YouTube must receive the encoder feed, and the Live Control Room preview must show both audio and video.
What you need before starting
You need a finished podcast WAV file, OBS Studio installed on the computer that will run the broadcast, and a visual source such as podcast cover art. A local image is enough for a straightforward episode stream. You can add motion or a visualiser later, but it introduces another part of the setup that needs testing.
You also need a YouTube channel that can live stream. YouTube's live-streaming eligibility guidance says the channel must be verified, must not have had a live-streaming restriction during the previous 90 days, and the creator must be at least 16 years old. Check the current official page rather than assuming an old channel is still eligible.
Before opening OBS, decide how the episode should behave:
| Choice | What it means | Suitable when |
|---|---|---|
| Play once | The WAV reaches its end and stops producing that audio source | You are broadcasting one scheduled episode |
| Loop the WAV | The same episode starts again after it ends | Repetition is intentional and clearly communicated |
| Several files | Episodes advance through a playlist or another arrangement | You are building a continuing programme |
| Still image | The viewer sees one cover image while listening | The podcast is the main content |
| Moving visual | The scene includes animation, a waveform or video | You have prepared and tested an additional visual layer |
This decision affects the scene and the test. A single WAV with a still image is the smallest setup. If you want several episodes to run continuously, OBS documents a VLC Video source for playlists, but that requires the VLC component and is a different arrangement from adding one WAV as a Media Source. For a broader discussion of continuous podcast programming, see how to stream podcast episodes 24/7 on YouTube using OBS.
Prepare the file and image in a location that will remain available while OBS is running. Do not move, rename or disconnect them after adding them to the scene unless you are ready to update the source and test it again. Keep the YouTube stream key private. Anyone who obtains it may be able to send a feed to your channel.
Create an OBS scene for the podcast
Open OBS and create a new scene for this broadcast. Give it a useful name such as Podcast - Episode 01, rather than leaving several similarly named scenes to sort through later. A scene is the arrangement that OBS sends to the encoder. The WAV alone is not a video scene, so the first job is to create a canvas that can contain both the audio source and a visible source.
In the Scenes area, add a scene, then use the Sources area to add the sources described in the following sections. OBS labels and menus can vary between versions, operating systems and translations. The official OBS documentation describes the relevant source types, but it does not mean that every installed version will present identical wording or layout. If a label differs, look for the equivalent Media Source or Image Source control in your version.
Keep the source order in mind. Visual sources are normally placed where they can be seen in the preview, while the Media Source supplies audio even if it has no visible picture of its own. If you add text, a logo or a visualiser later, place it above the background image and check that it is not hidden behind another source.
Use the preview as your first practical confirmation. You should eventually see the intended picture at the correct size, while the Audio Mixer should show activity when the WAV is playing. A quiet mixer and a blank preview are different problems, so check them separately rather than changing several settings at once.
If your podcast will become a long-running music or spoken-word channel, the planning questions are similar to those covered in running a 24/7 radio of your own tracks on YouTube. For this article, however, the core example remains one podcast WAV paired with one visual source.
Add the podcast WAV as a Media Source
In the Sources area, add a Media Source. Choose the option to create a new source and give it a descriptive name, such as Episode 01 WAV. In the source properties, select the local WAV file. OBS's Media Sources documentation identifies WAV as a supported audio format and documents the Media Source controls used for file playback.
The exact property names may differ in your OBS version. Look for the file selection control and the playback options associated with the source. Do not infer that a setting exists simply because a tutorial from another version shows it in a particular position. The useful preflight check is simple: select the file, return to the main OBS window, and start playback while watching the Audio Mixer.
When the episode is playing, the mixer should show level movement. Listen through the monitoring arrangement you normally use, but remember that local monitoring and the sound received by YouTube are not identical checks. The later Live Control Room preview confirms what YouTube is receiving.
If the mixer shows no activity, first check that the correct file is selected and that the source is not hidden or disabled in the Sources list. Then check the file itself in a local audio player. A file that is silent outside OBS needs attention before you investigate streaming settings.
Avoid changing the WAV unnecessarily just to make it fit the scene. The important requirements here are that OBS can read it and that the resulting audio is suitable for the stream. YouTube's encoder guidance lists AAC or MP3 for RTMP and RTMPS audio feeds, so OBS must encode the source into the selected stream output rather than sending the original WAV as a raw YouTube stream format. See the current YouTube encoder settings when choosing output settings.
If the source is an episode that should play only once, leave looping disabled if your version presents that control. Watch what happens at the end during testing. A source that stops is not necessarily broken: it may simply have reached the end of the file.
Decide whether the WAV should loop
A loop is a behaviour choice, not a repair for a failed stream. Enable the Media Source's Loop option only when you want the episode to begin again after it finishes. OBS documents this control for Media Sources, but the label and exact placement should be confirmed in your installed version.
For a one-off live episode, looping is usually the wrong choice. It can cause the same introduction, advert or closing message to repeat without warning. If the stream is intended to remain available after one broadcast, it is clearer to let the episode finish and end the event, or to prepare a sequence of episodes rather than repeating one programme.
For a station that deliberately repeats a short programme, looping may be appropriate. Tell viewers what they are hearing in the title or description, and test the transition at the end of the WAV. Some files include silence at the beginning or end, so the repeat may not happen at the point you expect from looking at the duration alone.
If you have multiple episodes, a playlist-based workflow may be more suitable than putting each file into a separate scene. OBS documents VLC Video as a source for playlist playback, but it is optional and has its own dependency. If your aim is simply to concatenate prepared videos rather than operate an OBS scene, compare that approach with streaming multiple videos continuously with FFmpeg concat. The two workflows have different setup and monitoring requirements.
After changing Loop, restart the source or perform a controlled test so you know the setting is active. Do not wait until a public broadcast has been running for the length of the episode to discover that it stops or repeats unexpectedly.
Add a still image or another visual source
Add an Image Source to the same scene and choose your podcast artwork. OBS's Image Sources guide describes using a local image file as a source. Resize or crop it in the preview so it fills the intended canvas without important text being cut off.
A still image is often the most dependable visual for a spoken podcast. It has no separate playback clock, no moving parts and no need to keep a video file running. That does not make it universally best: an animated waveform, a camera feed or a video background may suit your programme, but each additional source creates another item to check for visibility, performance and content suitability.
Use artwork that remains readable at the output resolution. A small square cover placed in the middle of a large frame may be technically visible but unhelpful on a phone. You can use a full-frame background, a larger cover, episode details or a restrained border, provided those elements do not obscure one another.
If you add a text source, type the episode title and any information that must remain on screen. Check spelling and contrast in the OBS preview. Text that looks clear on your desktop may be difficult to read after YouTube's compression or on a smaller screen.
The visual source is not an afterthought. YouTube live video requires a video feed even when the programme is audio-led. The still image gives OBS a picture to encode while the Media Source supplies the podcast sound. WAV playback by itself does not create a complete video stream.
Do not assume that a motion visualiser is active merely because it has been added to the scene. Play it during the test and look for movement in the preview. For a static podcast stream, the still image should remain visible throughout the episode, including during any silence at the beginning or end.
Connect OBS to YouTube
In YouTube Studio, open the live creation workflow and choose the Stream option for an encoder stream. You can create the event immediately or schedule it. YouTube's encoder setup instructions explain where to find the stream URL and stream key, how scheduling works and how to start the broadcast from the Live Control Room.
In OBS, open the stream settings and select the YouTube service if it is available in your version. Alternatively, enter the server URL and stream key supplied by YouTube. YouTube recommends RTMPS, its encrypted extension to RTMP, so use the secure server option when the workflow presents it.
Treat the stream key like a password. Paste it carefully, do not publish it in screenshots and do not put it in a public document. If you think it has been exposed, use YouTube's current controls to reset or replace it before the next broadcast.
Set the YouTube event's visibility deliberately. Public is appropriate for an event ready for viewers. Unlisted can be useful for sharing the link with a limited audience, while private is useful for access-controlled testing. Scheduling provides a shareable URL and can help viewers receive reminders, but it does not replace the technical test.
When the connection details are saved, start OBS streaming, but do not assume that pressing Start Streaming has made the YouTube event public. Wait for the incoming preview in YouTube Studio and follow the Live Control Room controls for starting and ending the event. The sequence can vary with the current YouTube interface, so use the official workflow if the buttons in your account differ.
Choose output settings that match the connection
YouTube publishes encoder recommendations rather than a podcast-specific preset. For H.264 video, its current table lists 4 Mbps as a recommended bitrate for 720p at 30 frames per second, 10 Mbps for 1080p at 30 frames per second and 14 Mbps for 1080p at 60 frames per second. The table also lists minimum values for some modes. These are ingest recommendations, not a promise that a particular computer or internet connection will sustain them.
For a podcast with a still image, a lower-complexity visual may not require a high frame rate, but the official guidance does not define a special podcast setting. Choose a resolution and bitrate that fit the available upload capacity, and check the current YouTube table before publishing. YouTube recommends leaving 20% upload bandwidth headroom, so do not plan to consume every bit of a connection's measured upload speed.
For stereo audio, YouTube's encoder settings page lists 44.1 kHz and 128 kbps. These settings apply to the encoded stream output, not to a claim that the source WAV must have those exact properties. If your WAV has a different sample rate or channel layout, let OBS encode it according to the output configuration and confirm the result in the test.
If your connection is shared with other people or devices, run the test under the same conditions you expect during the broadcast. A speed test taken when the network is quiet cannot establish how the stream will behave while someone else is uploading files or using a video call.
Run a preflight test before going live
YouTube's practical advice is to test before starting and to include audio and movement similar to the real broadcast. For this podcast workflow, the test should cover the start of the WAV, the picture, the connection and the end-of-file behaviour. A short test using the complete episode is not always necessary, but the points you care about must be exercised.
Use this order:
- Open the intended OBS scene and confirm the correct WAV and visual files are selected.
- Start the source and watch the Audio Mixer for level movement.
- Check the preview for the cover art, text and any other visual element.
- Start streaming from OBS and wait for YouTube's incoming preview.
- Listen to the YouTube preview or a controlled private or unlisted test, not only to local monitoring.
- Watch the stream health indicators for warnings and allow enough time to identify an unstable connection.
- If looping is enabled, test the transition at the file's end. If looping is disabled, confirm the expected stop behaviour.
- Stop the test cleanly and review what YouTube recorded or displayed.
If YouTube shows a picture but no sound, return to the OBS mixer and confirm that the Media Source is producing level. If OBS shows level but YouTube does not, check the selected audio output and encoder settings rather than replacing the WAV immediately. If sound is present but the picture is blank, inspect the Image Source visibility, file path and source order.
A warning about stream health is a reason to investigate, not a diagnosis by itself. Check upload capacity, the selected bitrate and whether another device is using the connection. YouTube's network guidance and streaming tips are the appropriate references for current recommendations.
Start the public event only after the preview shows the intended audio and video. Keep OBS open and monitor the mixer, preview and stream health during the broadcast. A preflight reduces avoidable mistakes, but it cannot guarantee uninterrupted broadcasting or prevent every later network, software or account problem.
Once the scene is stable, remove unnecessary changes. A simple scene with one tested WAV and one tested image is easier to recover than a collection of untested sources. If the channel is intended to run for long periods, consider whether a computer that must remain switched on is practical for your routine. StreamNeo removes the need to leave that computer running by taking an uploaded video and sending it to YouTube after you provide the stream key, with monitoring and automatic restart for drops. It remains a YouTube-only workflow, so YouTube's account and content rules still apply.
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
Can I upload a WAV directly to YouTube Live?
No. A WAV is an audio file, while a YouTube live encoder feed needs video and encoded audio. Use OBS or another encoder to combine the WAV with a visual source and send the resulting stream to YouTube.
Does the WAV have to be converted before OBS can use it?
OBS documents WAV support for its Media Source, so conversion is not automatically required. Check the file in your installed OBS version and test playback in the Audio Mixer. The stream output is encoded separately according to the settings selected for YouTube.
Should I enable Loop for a podcast episode?
Enable Loop only when repeating the episode is intentional. For a scheduled one-off broadcast, leaving it disabled avoids repeating the introduction or closing message after the file ends. Test the end-of-file behaviour before going public.
Is a still image enough for a YouTube podcast live stream?
A still image can provide the video part of a simple audio-led stream while the WAV supplies the programme sound. It is not a guarantee of uninterrupted broadcasting, so confirm the image, audio and stream health in YouTube's preview before and during the event.