For a single fireplace video, the simplest OBS setup is one scene with a local Media Source set to Loop and fitted to the canvas. You do not need VLC for one file; use VLC Video when you want OBS to play a playlist.
A practical YouTube starting profile is 1080p at 30 fps, H.264, CBR, a two-second keyframe interval and 14 Mbps video bitrate. Treat 14 Mbps as a test target, not a universal requirement: the connection and encoder must sustain it, so check stream health and dropped frames before relying on the profile for a long broadcast.
Prepare a fireplace video you may use
Start with a video file you have permission to broadcast. A fireplace clip found online is not automatically available for reuse just because it can be downloaded or viewed. Check the licence and its conditions, including whether live streaming is covered. Keep a copy of that information with the project so you can refer to it later. OBS settings cannot establish whether a video is cleared for your use.
Choose footage that works as a loop rather than merely as a short scene. Watch the beginning and end in sequence: a sudden change in flame position, a jump in room brightness or a brief black frame can make a repeating clip noticeable. Do the same with the sound. A fireplace crackle that stops or spikes at the seam may be distracting when the viewer hears it for hours. If the file is silent by design, check that OBS will not add desktop sound or a microphone unintentionally.
Use a file format your local playback setup can open reliably, then test that exact file in OBS. Keep its location stable after you build the scene; moving or renaming it can leave the source unable to find the media. Give it a clear name, such as fireplace-loop.mp4, and store it somewhere that will remain available while the computer is streaming. That is an operational choice, not a guarantee of uninterrupted playback.
A 24/7 broadcast also raises a separate question: what happens to a YouTube live stream after it has run for a long time? Do not assume that an always-on broadcast will necessarily produce the archive you expect. Check YouTube’s current guidance if a replay matters to you, and make any local recording or archive plan separately from the OBS scene.
Add and loop an OBS Media Source
Create one scene for the broadcast, with a recognisable name such as “Fireplace”. Add a Media Source and point it to the local video. In the source properties, enable Loop. OBS documents Media Source playback and its loop option in its Media Sources guide. For a single video that should repeat, this is the direct route: OBS plays that file again when it reaches the end.
Keep the source list deliberately short. The video is the main visual, and an audio source should be present only if you need one beyond the file’s own sound. Extra browser panels, animated overlays and additional video layers increase the number of things to inspect without improving a quiet fireplace scene by default. If you do add a clock, logo or other element, check that it does not cover the fire or create a visual change that feels out of place.
After adding the source, preview it for longer than a brief glance. Confirm it starts at the expected point, runs, reaches the end and begins again. Look for a freeze or black frame at the transition. Listen across the same boundary for a gap, abrupt change in loudness or unintended sound. OBS’s source controls allow you to manage playback and visibility; do not assume a scene preview alone has proved the full loop is clean.
Save the scene collection after the source is working. If you need to move the file to another computer, verify the source path on that machine rather than assuming the old path will resolve. A scene can look correct in OBS while its media file is missing or unavailable, so check the preview again after any file move or system restart.
If you are still setting up the channel itself, make sure live access is ready before spending time troubleshooting the scene. For example, see the steps in YouTube Live streaming activation when phone verification is stuck. Access and scene setup are separate tasks; a correctly configured Media Source does not resolve an account-level restriction.
Fit the video to the canvas
Set the canvas and output to the dimensions you intend to send to YouTube, then size the fireplace source to match. In OBS, select the source and use the transform options to fit it to the canvas. Inspect the preview rather than relying on the label of the command: confirm that the whole intended picture is visible, that there are no unintended borders, and that the flames or fireplace are not stretched.
Aspect ratio is the key check. If the source and canvas have different shapes, fitting the entire video may leave unused space around it; filling the canvas may crop part of the picture. Neither is automatically correct. Choose the framing that preserves the scene you want viewers to see. Avoid stretching the image to force a match, as that alters the shape of the fireplace and flame. OBS explains source positioning, scaling and cropping in its Sources guide.
Look at the preview at the final output size and at the edges. A thin border can be easy to miss when the preview is small. Check that no source is accidentally hidden under another layer and that the fire is composed sensibly within the frame. If a static text element is part of the design, make sure it stays legible without dominating a relaxation stream.
A low-motion scene usually does not need 60 fps simply because the setting exists. YouTube’s guidance offers profiles by resolution and frame rate, while OBS notes that higher frame rates can increase system load. For gentle flame movement, 1080p30 is a reasonable place to begin; choose 60 fps only if the smoother motion matters for your source and your system can sustain it. If you are comparing other prerecorded formats, how to rotate product comparison videos in a nonstop YouTube stream illustrates a different kind of multi-clip scene, not a requirement for a single fireplace loop.
Use VLC Video only for a playlist
A single file that repeats is well served by Media Source. VLC Video is useful when the show needs a sequence of clips, such as several fireplace views, or a playlist that should move from one file to another. OBS’s documentation says VLC must be installed for the VLC Video source type to be available. If it does not appear in your source menu, check that prerequisite rather than treating VLC as mandatory for basic looping.
For a playlist, add the VLC Video source and select the files in the intended order. Check the playlist settings and playback in the preview. OBS documents Loop Playlist as enabled by default, but verify the behaviour in your own scene rather than relying on a remembered setting. Play through clip changes and the end of the list: differences in brightness, aspect ratio, audio level or length can make transitions more noticeable than the individual videos.
A playlist offers variety, but it adds more places to check. Confirm that every file opens, that the ordering is right and that the intended loop behaviour persists after reopening OBS. Consider whether the change between clips fits a relaxing channel. If one clip is much louder or framed differently, adjust the media before using it in a continuous broadcast. A single Media Source is simpler when one carefully chosen loop is sufficient.
Do not choose VLC merely because the channel is meant to be continuous. Continuity comes from the playback and broadcast arrangement, not from using a particular source type. If your real requirement is a scheduled sequence of distinct videos, a playlist may fit better; for one fireplace file, the Media Source keeps the scene easier to understand and test.
Set a YouTube Live starting profile
For a 1080p, 30 fps H.264 test, a workable starting profile is CBR with a two-second keyframe interval and 14 Mbps video bitrate. YouTube Help lists 14 Mbps as its recommended H.264 video bitrate for 1080p30, and recommends a two-second keyframe frequency, with a maximum of four seconds. These are platform recommendations, not a promise that every computer or internet connection can deliver them consistently. See YouTube’s current live encoder settings and bitrates before you go live, because platform guidance can change.
In OBS, select an encoder and output settings appropriate to your machine and the stream’s resolution. H.264 with CBR is a broadly documented starting configuration for RTMP/RTMPS. YouTube also documents HEVC and AV1 compatibility, but availability depends on the encoder and ingest setup you actually use. Do not switch codecs just because an option is listed: first confirm that your selected output path supports it and test the result.
For a lower-motion fireplace scene, 30 fps is a practical starting point. At 60 fps, YouTube lists a different H.264 recommendation, 17 Mbps, for 1080p60. That does not mean 60 fps is automatically better for a fire, or that your connection should be pushed to that figure. More frames can increase encoding and upload demands; use them when the visual difference is useful and the setup can sustain the load.
Set audio intentionally as well. YouTube’s RTMP/RTMPS guidance lists AAC or MP3 and recommends 128 Kbps for stereo. The source file may already contain the crackling sound, so check the OBS audio mixer and avoid capturing desktop audio on top of it. Listen for clipping, silence and a sudden level change where the video loops. The desired sound is a creative choice; the platform recommendation is not a prescribed fireplace mix.
| Starting choice | When it makes sense | What to check |
|---|---|---|
| 1080p30, H.264, CBR, 14 Mbps | A first test for a 1080p low-motion scene | Sustained upload, encoder load and YouTube stream health |
| 1080p60, H.264, 17 Mbps | If smoother flame movement is worth the extra demand | Whether the source benefits from 60 fps and the system can maintain it |
| Lower output demand | If tests show the connection or encoder cannot hold the target | Picture quality, dropped frames and stream-health messages |
The figures in the first two rows are YouTube Help’s recommendations for the stated H.264 profiles, accessed in 2026; the captured guidance does not state a publication date. They are comparison points for testing, not mandatory settings. For other resolution, frame-rate or codec combinations, use YouTube’s current table rather than inferring a bitrate from these examples.
Test bitrate against connection and encoder
A number entered in OBS is not evidence that your connection can sustain it. YouTube recommends running a speed test to test upload bitrate, but a speed test is only one check: the stream also depends on what your internet connection does over time and what the computer can encode. YouTube recommends RTMPS; use the current instructions in its live encoder guidance to check the ingest and stream settings for your channel.
Test privately or otherwise without making the broadcast public before relying on the scene. Use the actual fireplace video and sound, at the intended resolution and frame rate. Let the video reach its loop seam, then watch the YouTube stream health display and messages while OBS is sending. This tests the movement and audio you will really use, as YouTube advises, rather than an unrelated static test screen.
Watch OBS’s dropped-frame indicator during the test. OBS explains that increasing dropped frames can indicate that the connection cannot keep up with the configured bitrate or is unstable. If frames are dropping, first work out whether the issue is network, encoder load or both. Reduce the output demand and test again; do not keep a high bitrate merely because it appears in a platform table. If practical, a wired connection can remove one variable, but it does not guarantee a stable route or sustained upload.
Also watch encoder performance and the rendered picture. A computer that cannot encode smoothly may show rendering or encoding strain even when the network seems adequate. Close unnecessary applications, check the encoder options available on your machine, and repeat the same test after changing one setting at a time. Changing resolution, frame rate and bitrate all at once makes it harder to tell which change helped.
If the stream-health messages identify a problem, follow the current YouTube or OBS guidance and test again. A successful short test is useful evidence, not a guarantee for a 24/7 run: network conditions and system load can change. Keep a realistic plan for checking the stream after it begins, especially if you are not in the same room as the computer.
Keep the scene simple and monitor playback
A static relaxation stream benefits from a scene you can inspect quickly. Keep the intended video visible, check the audio meter, and remove sources that do not contribute to the broadcast. The fewer moving parts, the easier it is to diagnose a frozen image, missing file or unexpected audio. This does not eliminate failures; it narrows the places you need to inspect when something looks wrong.
In OBS, confirm automatic reconnect is enabled if that suits your setup, and choose retry behaviour appropriate to the machine and connection. OBS identifies automatic reconnect as an advanced setting, but there is no single retry value that fits every network. Reconnect behaviour can help OBS attempt to resume a dropped broadcast; it cannot make an unstable connection reliable or guarantee that YouTube will retain a particular stream state.
For a computer-based 24/7 stream, the machine, OBS, source file and network all need to remain available. Consider power settings, operating system restarts and whether the computer will sleep, but test those conditions rather than assuming a setting has the effect you intend. After a restart, verify that OBS opens the correct scene, the local media is found and the audio remains as expected. A test after a reboot is more useful than assuming a previously working scene will recover unchanged.
If keeping a computer running and checking local playback is the part that makes the plan difficult, StreamNeo can remove that specific burden by taking an uploaded video and running the YouTube broadcast with your computer switched off. It is for YouTube, not a replacement for an OBS workflow when you need interactive scenes, live camera inputs or control over a changing production. Whichever approach you use, you remain responsible for checking that the video, sound and channel are ready.
For a single-file loop, you can also read how to restart a looping ASMR stream automatically on YouTube for related continuity considerations. A restart strategy and a looping scene solve different problems: the first addresses what happens after a stream drops, while the second repeats the media inside a working scene. If you need to operate the channel without a PC, the guide to running a prerecorded YouTube live stream without a PC covers that decision from the operating side.
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
How do I loop a fireplace video in OBS?
Add the local file as a Media Source, enable Loop in its properties and preview it through the end and back to the beginning. Check both the picture and audio at the seam. VLC Video is not required for a single file.
Should I use 14 Mbps for every fireplace stream?
No. YouTube lists 14 Mbps as its recommended H.264 video bitrate for 1080p30, but your encoder and sustained upload connection may not support it. Test that target with the intended scene, inspect stream health and dropped frames, then reduce output demand if needed.
When should I use VLC Video instead of Media Source?
Use VLC Video when you want a playlist of multiple clips and have VLC installed so OBS can provide that source type. For one video that should repeat, Media Source with Loop is the simpler choice. In either case, verify clip order, loop behaviour and sound transitions in the preview.
Does a successful test guarantee a continuous broadcast?
No. A test can reveal problems with the file, scene, connection or encoder, but operating conditions can change during a long stream. Keep the computer and network available if you are using OBS, and check playback and stream health after going live.