For a relaxing fireplace loop, start with 1080p at 30 fps, H.264 video, constant bitrate (CBR), a 2-second keyframe interval and AAC audio. YouTube’s recommended H.264 video bitrate for 1080p30 is 5 Mbps; that is a practical starting point for a mostly static scene, not a fireplace preset prescribed by YouTube.
The settings only work if your upload connection can carry the whole stream steadily. If the flame detail benefits from smoother motion and your connection has enough spare capacity, consider 1080p60 instead. Test the actual loop, including its audio and the transition back to the beginning, before you rely on it overnight.
A practical starting profile for a fireplace loop
Use this as a starting configuration in your encoder, then check the result in YouTube’s Live Control Room. It is an editorial recommendation for a calm, largely static picture. YouTube publishes general encoder settings and bitrate recommendations, rather than a special profile for fireplace videos.
| Setting | Starting point | Why it suits this use |
|---|---|---|
| Resolution and frame rate | 1920 × 1080 at 30 fps | Full HD detail without sending twice as many frames as a 60 fps stream |
| Video codec | H.264 | A widely supported choice for YouTube encoder ingestion |
| Rate control | CBR | Keeps the video bitrate at a consistent target |
| Video bitrate | 5 Mbps | YouTube’s recommended H.264 video bitrate for 1080p30 |
| Keyframe interval | 2 seconds | Matches YouTube’s recommendation |
| Audio | AAC, stereo, 44.1 kHz | A suitable format for the loop’s crackle or background ambience |
| Ingest protocol | RTMPS, if the encoder supports it | YouTube recommends RTMPS for general streaming |
Treat the table as a configuration to test, not a guarantee of picture quality or uninterrupted playback. The source file matters: a compressed or soft-looking video cannot gain detail just because you choose a higher stream bitrate. Conversely, tiny flame movement, smoke and glowing embers can make a scene less static than it first appears, so inspect the result rather than assuming the picture will encode effortlessly.
If you already have a reliable, appropriately configured encoder, there is no need to change every control at once. Set the resolution, frame rate and video bitrate first; check YouTube’s stream health; then adjust only if you see a specific problem. If you need a broader explanation of keeping long-running videos moving between one another, the guide to preventing gaps when switching videos on a 24/7 YouTube stream covers a related but separate production issue.
Why 1080p30 is a sensible first test
A fireplace loop usually has no presenter, fast camera movement or changing scene every few seconds. The flame itself moves, but much of the frame—the hearth, wall and surrounding room—may remain still. That makes 1080p30 a reasonable first test for a calm ambience channel: it preserves Full HD resolution while using a lower recommended H.264 bitrate than 1080p60.
The distinction is about the source and the viewing experience, not a special YouTube rule. At 60 frames per second, the stream can show more frequent changes in the flame’s movement. That may look more fluid if the original video was recorded at 60 fps and the motion is prominent. It also raises the recommended H.264 video bitrate for 1080p from 5 Mbps at 30 fps to 14 Mbps at 60 fps. Audio and other network use sit alongside that video traffic, so plan for the total rather than just the video number.
For a mostly static composition, the extra motion sampling may not be worth the additional upload demand. Start at 30 fps if your source is 30 fps, if the flame looks natural at that rate, or if your internet connection needs more room for stability. Do not convert a 30 fps source to 60 fps expecting it to create genuine new motion detail. If your source is 60 fps, compare both settings with a short test and keep the one that looks good without straining upload capacity.
A stable picture is more useful for an ambience channel than a nominally higher frame rate that produces recurring warnings or dropped frames. If the channel runs for long periods, take continuity seriously too: a loop can be encoded well and still feel broken if the last frame jumps sharply to the first. For a different kind of recorded-video channel, building a 24/7 study stream from recorded videos offers useful context for thinking about repeated playback as a channel format.
YouTube bitrate recommendations by resolution and frame rate
YouTube’s encoder guidance provides recommended bitrates by codec, resolution and frame rate. The values below are H.264 video recommendations relevant to common HD choices; they are reference points, not a promise that a given upload connection will sustain them. Check the current YouTube encoder settings and bitrate guidance when configuring a new stream, because that official page is the source of the recommendations.
| Resolution and frame rate | YouTube-recommended H.264 video bitrate |
|---|---|
| 720p30 | 4 Mbps |
| 720p60 | 6 Mbps |
| 1080p30 | 5 Mbps |
| 1080p60 | 14 Mbps |
The 720p values can be useful if your connection does not leave enough headroom for a steady 1080p stream, or if the source itself is only 720p. Choosing a lower resolution is not a failure: it can be preferable to a higher-resolution stream that repeatedly buffers or loses frames. The right setting depends on what your connection can actually sustain while the stream is running.
Keep the comparison narrow. These figures concern recommended video bitrate for H.264, not your complete network requirement. Add the audio stream and account for other traffic, including a second stream or household use. YouTube’s separate streaming tips on bandwidth and connection reliability recommend leaving 20% headroom beyond the total streaming bitrate. That margin is intended to help accommodate fluctuations; it is not a guarantee against internet outages or congestion.
For a practical choice, compare the source at the intended frame rate, then measure upload speed at the location and time you plan to stream. If 1080p60 does not fit comfortably within available upload capacity after headroom and competing use, choose 1080p30 or 720p rather than setting a target the connection cannot maintain. Use upload speed, not a download result, for this decision.
Choose H.264 and CBR for a straightforward setup
H.264 is a useful first codec because it is widely supported by encoders and is covered by YouTube’s published bitrate table. YouTube also lists H.265/HEVC and AV1 for RTMP/RTMPS ingestion, but codec availability and encoder controls vary. If you are using an encoder you already know, choose a codec it can reliably produce and that YouTube supports. For a first fireplace stream, changing codecs offers little value if the basic stream has not yet been tested.
Set rate control to CBR when that option is available. A constant bitrate gives the encoder a steady target to send, which makes it easier to budget upload capacity over a long broadcast. A scene with mostly still surroundings can sometimes look acceptable at a lower rate than footage with rapid movement, but CBR does not make the bitrate adapt automatically to your connection. If your upload service cannot sustain the selected target, the encoder cannot fix that by using CBR.
Avoid confusing video bitrate with total stream bitrate. The video target is only one part of the outgoing feed; audio and protocol overhead also use capacity. Leave the headroom YouTube recommends and check whether other devices are uploading at the same time. A cloud backup, camera upload or another live stream can affect the connection even if the encoder settings themselves are unchanged.
H.264 and CBR are not a substitute for a sound source file. If the original fireplace footage is low resolution, heavily compressed or has banding in dark areas, a larger bitrate may not remove those defects. Watch a representative sample on the kind of screen your audience is likely to use. For a channel mixing ambience with music or narration, review ways to improve audio quality on a live stream as a separate part of preparation.
Set the keyframe interval to two seconds
Set the keyframe interval to 2 seconds. YouTube recommends a 2-second interval and says not to exceed 4 seconds. In some encoders the control is called keyframe interval; in others it may be expressed as a GOP length or a number of frames. If it asks for frames, the frame count depends on frame rate: use the encoder’s documentation to translate the interval rather than entering the number 2 blindly.
A keyframe is a complete reference frame from which following frames can be decoded. Between keyframes, the encoder can describe changes rather than repeatedly sending a full frame. A regular interval helps keep the stream in line with YouTube’s ingest guidance and makes the stream easier to process. It is not a control for how long the fireplace video plays before looping, and it does not repair a visible cut between the end and beginning of the source clip.
Do not lengthen the interval in an attempt to save bandwidth unless you have a specific reason and have checked the consequences. YouTube’s upper limit in its guidance is 4 seconds; use 2 seconds for the simple starting profile. If your encoder has a separate setting for automatic keyframes, verify that it does not override the interval you intended.
Configure audio and RTMPS
For RTMP or RTMPS ingestion, YouTube lists AAC or MP3 audio. AAC stereo at 44.1 kHz is a practical starting point for a fireplace recording with crackle, soft music or other ambience. Keep the level comfortable and consistent, and listen to the actual file rather than relying only on the encoder’s meters. A steady visual loop can still be tiring if the audio has a sudden jump, a clipped crackle or a brief silence each time it repeats.
Check the source file at the join. Listen through the end and beginning several times: a slight change in room tone may be more noticeable after an hour than during a quick preview. If the fire sound is meant to continue underneath the visual, make sure the audio loop is aligned or edited to avoid an abrupt cut. YouTube’s guidance is to test with audio and movement similar to what you will stream; the loop-join check is an additional practical step for this format.
Use RTMPS when your encoder supports it. YouTube recommends RTMPS for general live streaming, and its encoder guidance lists H.264, H.265/HEVC and AV1 for RTMP/RTMPS ingestion. HLS is another workflow in YouTube’s documentation, but its segmented delivery has higher latency; for a quiet fireplace loop with little audience interaction, that is not an obvious advantage. Follow the protocol options that your chosen encoder and YouTube workflow support.
Create or schedule the stream in YouTube Studio’s Live Control Room and enter the stream URL and stream key in the encoder. Treat the key as private: YouTube describes it as the credential that lets the encoder send a feed to the channel. Set visibility intentionally—public, unlisted or private according to your plan—and check the correct stream is selected before starting. If this is your first time enabling live streaming, allow time for YouTube’s activation process; consult its current encoder setup instructions rather than scheduling a first broadcast at the last minute.
Test stream health and match the settings to upload capacity
Test before the planned broadcast, using the same video, audio, encoder and network arrangement you expect to use. YouTube recommends testing with audio and movement similar to the real stream. For a fireplace loop, that means letting the fire move naturally, listening for the full audio cycle and watching at least one transition from the end of the file to its beginning. A short test of a still frame alone will not reveal a loop seam or recurring audio gap.
In Live Control Room, check stream health and read any messages rather than treating a successful connection as proof that everything is fine. Watch for dropped frames, a bitrate that fluctuates unexpectedly, warnings about the incoming feed or audio that is missing or out of sync. If you see a problem, change one thing at a time. Lowering frame rate or resolution may reduce upload demand; lowering a bitrate target may also help, but compare the resulting picture with your source before deciding.
Measure upload speed on the actual connection, preferably under conditions similar to the intended broadcast. Do not use the headline download speed from a broadband plan as a substitute. Leave at least the headroom YouTube recommends—20% beyond the total streaming bitrate—and include other ongoing uploads in the calculation. If the connection is shared, ask whether other devices can pause large uploads during the stream. An Ethernet cable is an optional way to remove a weak Wi-Fi link from the setup, but it cannot fix congestion or an unreliable internet service upstream.
A repeated stream can be affected by the computer as well as the internet connection. During a test, check that the encoder remains active, the machine does not sleep, and the source continues to play after the loop returns to its first frame. Keep the test long enough to expose a problem that appears only after repeated playback, not just one clean start. A guide to managing a 24/7 YouTube stream remotely is relevant if you need to think through what happens when you are not beside the setup.
For a channel where the computer would otherwise need to stay on all night, StreamNeo removes that specific operational burden by running an uploaded video as a YouTube live stream without keeping your own computer on. That does not remove the need to prepare a suitable file, check the channel and review the stream’s health. YouTube remains the platform in this workflow.
For a fireplace stream with little live conversation, prioritise continuity and a stable picture over low latency. YouTube notes that lower latency can mean more buffering; it is more important when you need to interact with viewers in near real time. DVR is optional: when enabled, viewers can pause, rewind and resume the live stream. Decide whether that viewer control suits the channel rather than turning it on automatically.
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
Is 5 Mbps a YouTube-prescribed bitrate for a fireplace stream?
No. YouTube recommends 5 Mbps for H.264 video at 1080p30 generally; it does not prescribe that value as a fireplace-specific preset. It is a practical starting point for a calm loop, provided your upload connection can carry the total stream with headroom.
Should I use 1080p60 for flames?
Use 1080p60 if the source is 60 fps, the flame motion benefits from the smoother presentation, and the upload connection can sustain the higher recommended bitrate. YouTube’s recommended H.264 video bitrate for 1080p60 is 14 Mbps, compared with 5 Mbps for 1080p30. If that leaves too little room for the rest of the stream and normal connection variation, 1080p30 is the more sensible test.
How do I loop a fireplace video on YouTube Live without an obvious jump?
Prepare the video so its final image and audio join cleanly to their starting points, then test that transition in the actual playback setup. Check more than one repeat and listen for silence, a sudden change in ambience or an abrupt sound at the seam. YouTube’s stream-health checks can help identify feed issues, but the loop edit itself is your responsibility.
Is low latency important for a fireplace ambience stream?
Usually not, unless you plan to interact with viewers in near real time. A fireplace loop has little need for a rapid audience response, while YouTube notes that lower latency can increase buffering. Consider DVR separately if you want viewers to pause or rewind the live stream.