For a YouTube fireplace stream, start with 1080p at 30 frames per second if your upload connection can hold the bitrate reliably. YouTube currently recommends 14 Mbps for 1080p30 H.264 input.
If that leaves too little capacity for normal network variation, use 720p at 30 fps instead. YouTube recommends 8 Mbps for 720p30 H.264, and a stable 720p stream is more useful than a higher-resolution stream that repeatedly buffers, drops frames or disconnects.
Start with the source, not the output menu
Resolution describes the size of the video you send to YouTube. It does not describe every quality option that viewers will later see. For a fireplace stream, the useful starting point is the quality of the original material: a live camera, a rendered loop, or a prerecorded video file.
If your source is 1920×1080 at 30 fps, sending it as 1080p30 preserves the detail available in that source. If the source is 1280×720 at 30 fps, enlarging it to 1080p does not create new detail. It can increase the amount of data you need to send without making the logs, flames or room texture genuinely sharper.
The same principle applies to frame rate. A locked-off fireplace scene usually does not need 60 fps simply because YouTube supports it. If the source was made at 30 fps, keep the stream at 30 fps unless there is a clear reason to change it. YouTube’s published bitrate recommendations are tied to both resolution and frame rate, so a 30 fps recommendation should not be applied to a 60 fps stream.
For a prerecorded file, check its actual properties before choosing encoder settings. You can use the file’s dimensions and frame rate as the baseline. If you are building the loop yourself, the guide on looping a fireplace stream without black frames covers a separate problem that can otherwise look like a resolution failure.
A source can also be visually simple but technically demanding. A still image with a small flame overlay may compress easily, while a close-up of turbulent flames, glowing coals and moving shadows contains more changing detail. Resolution remains important, but it is only one part of the result. The encoder, codec, bitrate and consistency of the upload all affect what reaches YouTube.
A practical 1080p30 starting point
For a 1920×1080 source at 30 fps, use 1080p30 as the first setting to test. YouTube’s current live encoder guidance recommends 14 Mbps for H.264 at 1080p30, accessed on 3 October 2026. Treat that as an ingestion recommendation for YouTube, not as a special requirement for fireplace content or a universal rule for every platform.
A sensible H.264 starting profile is therefore:
- Resolution: 1920×1080
- Frame rate: 30 fps
- Bitrate: 14 Mbps, using YouTube’s recommended H.264 input figure
- Rate control: constant bitrate, or CBR
- Keyframe interval: two seconds, and not over four seconds
- Transport: RTMPS where your encoder provides it
The bitrate is the amount of video data you are asking the connection to carry. It is not the same as the resolution, and increasing one does not automatically repair a weak source. If the video was produced at 720p, encoding it as 1080p at 14 Mbps can still leave it looking like enlarged 720p footage.
CBR is useful because a long-running broadcast is easier to monitor when its output is predictable. A variable bitrate can be appropriate in other delivery workflows, but for this YouTube ingest test, follow the platform’s published encoder guidance rather than choosing settings because they sound more advanced.
Audio also consumes part of the connection and should be included in your planning. A fireplace stream may use crackling audio, quiet ambience or no audio at all, but the complete outbound stream still needs room for all enabled tracks and any other traffic using the connection.
Do not judge the setting only from a short preview. A connection can look fine during a quiet part of the day and become unreliable when another person starts a video call, a cloud backup begins or the local network becomes busy. For a useful test, use movement and audio similar to the planned stream, then watch the stream health while it runs.
If your 1080p file is ready but the computer cannot be left running continuously, the workflow question is separate from the resolution question. A 24/7 radio livestream schedule may help you think through timing and handover, while the encoder still needs to be tested at the chosen resolution.
When 720p30 is the safer choice
Choose 720p30 when 1080p would consume too much of the upload capacity or make the stream sensitive to ordinary network use. YouTube currently recommends 8 Mbps for 1280×720 at 30 fps with H.264, accessed on 3 October 2026.
That is not a failure or an improper setting. It is a reasonable fallback for a small channel, a home connection shared with other people, or a source that is already 720p. For a simple fireplace scene, reliable motion and clean continuity can matter more than sending a larger frame.
The comparison is practical rather than absolute:
| Input choice | YouTube H.264 recommendation | YouTube AV1 or H.265 recommendation | Use it when |
|---|---|---|---|
| 1080p30 | 14 Mbps | 10 Mbps | The source has useful 1080p detail and upload capacity is stable |
| 720p30 | 8 Mbps | 6 Mbps | Bandwidth, shared use or recovery risk is the main constraint |
| 1440p30 | 21 Mbps | 15 Mbps | The source and delivery connection genuinely justify more detail |
| 2160p30 | 42 Mbps | 30 Mbps | A high-detail 4K source and ample delivery capacity are deliberate goals |
The figures in this table are YouTube’s published live-ingest recommendations, accessed on 3 October 2026. They are not fireplace-specific requirements. They also apply to 30 fps entries only. Do not use the 1080p30 figure for a 60 fps stream and assume the result is equivalent.
A useful decision is to compare the source detail, the required bitrate and the headroom left after other traffic. If 1080p uses nearly all of the measured upload capacity, moving to 720p may produce a better night-long result even though each frame contains fewer pixels.
Viewers may also watch on small mobile screens, older televisions or connections that vary during the day. You cannot control their network, but you can avoid making your own ingest unnecessarily fragile. YouTube will create viewer-side versions from the stream, so your input does not need to match every quality choice available in the playback menu.
If the stream is a loop rather than a camera feed, inspect the rendered file before changing resolution. The guide to making a 24/7 YouTube music stream with a static image explains why a simple visual source can still require careful handling of the file and audio.
H.264, AV1 and H.265 are different inputs
Do not mix codec recommendations. YouTube’s current table lists 14 Mbps for 1080p30 H.264 and 10 Mbps for 1080p30 AV1 or H.265. For 720p30, it lists 8 Mbps for H.264 and 6 Mbps for AV1 or H.265. These are YouTube ingestion recommendations, accessed on 3 October 2026.
The lower listed figure for AV1 or H.265 does not mean you should enter 10 Mbps into an H.264 encoder. The codec changes how the video is compressed, so the setting must match the encoder output. If your software says H.264, use the H.264 row. If it says AV1 or H.265, use the corresponding row only after confirming that your complete YouTube workflow supports that codec.
H.264 is often the straightforward baseline because it is widely supported by streaming software and hardware. That does not make it automatically best in every setup. AV1 or H.265 may offer a different compression trade-off, but the practical benefit depends on whether your encoder can produce it reliably, whether the computer has enough capacity, and whether the workflow remains easy to recover when something goes wrong.
For a 24/7 stream, complexity has a cost. A codec that looks efficient on paper is not useful if the encoder drops frames, overheats, fails after a restart or cannot be configured consistently. You should test the actual output rather than comparing only the bitrate numbers.
The same caution applies to 1440p and 2160p. YouTube’s table lists 21 Mbps H.264 or 15 Mbps AV1/H.265 for 1440p30, and 42 Mbps H.264 or 30 Mbps AV1/H.265 for 2160p30. Those figures may be appropriate for a detailed source and a connection with ample capacity, but a simple, fixed fireplace scene does not automatically benefit from sending 4K.
Higher source resolution is useful when the original material contains detail that viewers can notice and when the encoder and connection can sustain it. It is not useful merely because a larger number appears in the settings menu. Begin with the simplest codec your setup can operate reliably, then change one variable at a time if testing shows a real benefit.
Check upload stability before choosing the final setting
Measure upload capacity, not just download speed. YouTube’s network guidance says to leave room for variation, with 20% recommended. That means the total stream bitrate should not be planned right up against the connection’s measured maximum.
For example, if you intend to send a 14 Mbps H.264 video stream, the connection needs more than 14 Mbps of dependable outbound capacity. Audio, protocol overhead, competing devices and short interruptions all need consideration. The exact spare capacity available to you will depend on the connection and the traffic sharing it, so do not turn the 20% guidance into a promise that a particular internet plan will work.
Write down what else uses the network. A second livestream, security camera uploads, cloud synchronisation, large file transfers and video calls can all reduce the margin. If the fireplace stream is important overnight, schedule backups outside the test window or place them on a different connection where practical.
Watch for dropped frames, reconnects and changing stream-health messages rather than relying on a single speed-test result. YouTube’s streaming tips recommends accounting for competing network use and leaving room in the connection. YouTube also recommends testing with similar audio and movement to the intended broadcast.
For a 24/7 operation, let the test run long enough to expose the behaviour you actually care about. Check what happens after the encoder is restarted, after the network briefly disappears and after the source reaches the end of a loop. This is a practical application of YouTube’s general advice to test and monitor; it is not a published YouTube-specific resolution requirement.
If you are running the stream from a small computer, monitor its temperature and throttling as well as the network. The Raspberry Pi temperature and throttling checks are relevant when local hardware is doing the encoding. A network that is fast enough cannot compensate for an encoder that stops producing frames.
Select the lower resolution when the test shows a repeatable stability problem at the higher one. Changing from 1080p30 to 720p30 reduces the recommended H.264 video bitrate from 14 Mbps to 8 Mbps, but it will not repair every fault. Bad cabling, an unstable router, a failing source file or encoder overload may need a different remedy.
YouTube creates the viewer-side versions
You do not need to ingest 1440p, 1080p, 720p and every smaller playback format separately. YouTube Help states that YouTube automatically transcodes a live stream to create different output formats for viewers on different devices and networks.
Your input is the material from which those versions are made. A 1080p source can provide more original detail to the transcode than a 720p source, but the larger input only helps when that detail exists and can be delivered consistently. Upscaling a low-detail file does not restore information that was never captured.
This is why choosing 1080p is not a guarantee that every viewer will see 1080p. A viewer’s device, connection and YouTube playback conditions affect the format offered or selected. Conversely, sending 720p does not mean the stream is unusable for viewers who watch on smaller screens.
You can also make the playback experience more forgiving by avoiding unnecessarily low latency for an ambient channel. YouTube notes that lower latency can increase buffering and matters less when the streamer is not interacting with viewers. A fireplace stream normally has no need for instant conversation, so prioritise dependable playback over a latency setting chosen for interactive broadcasts.
DVR, if enabled, can let viewers pause and rewind a live stream. That may be useful for an ambience channel, but confirm the current choices in YouTube’s live stream settings guidance rather than assuming every account or broadcast configuration behaves identically.
The important distinction is between input quality and viewer selection. You choose one source resolution and one encoder output. YouTube handles the creation of multiple playback formats, while each viewer receives a version suitable for the conditions available to them.
A simple decision process for your fireplace stream
Start by identifying the source dimensions and frame rate. If the source is 1920×1080 at 30 fps, test 1080p30. If it is 1280×720 at 30 fps, test 720p30 rather than enlarging it without a clear reason.
Next, choose the codec row that matches the encoder. For H.264, begin with YouTube’s 14 Mbps recommendation at 1080p30 or 8 Mbps at 720p30. For AV1 or H.265, use the corresponding 10 Mbps or 6 Mbps figures from YouTube’s table. Keep the frame rate at 30 fps when that matches the source.
Then measure the upload connection during the time you expect to operate. Leave the recommended 20% room, include audio and count other traffic. If there is not enough dependable capacity for 1080p30, move to 720p30 before adding more complexity elsewhere.
Configure CBR, a two-second keyframe interval and RTMPS where available. Test with the same kind of movement and audio that your public stream will use. Watch for dropped frames, reconnects and changes in stream health.
Finally, let the chosen setup run for a representative period and test recovery. If a loop reaches its end, verify that it starts again without a black frame. If the connection drops briefly, verify what the encoder does. If the computer restarts, verify whether the broadcast resumes as intended. Resolution is only one part of a 24/7 workflow.
For many fireplace channels, the final answer will be 1080p30 H.264 when the source is genuinely 1080p and the upload has room to spare. For a constrained connection or a 720p source, 720p30 H.264 is the sensible fallback. Use the higher setting because it survives your test and preserves useful source detail, not because the number is larger.
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 1080p required for a 24/7 fireplace stream?
No. 1080p30 is a practical starting point when the source contains 1080p detail and the upload can sustain YouTube’s recommended 14 Mbps H.264 input with headroom. If that makes the stream unstable, 720p30 at YouTube’s recommended 8 Mbps H.264 input is a valid choice.
Should I stream a fireplace video at 60 fps?
Usually not if the source is 30 fps. Match the source frame rate where practical, because YouTube’s bitrate recommendations differ by frame rate and a higher setting does not automatically create smoother original footage.
Do I need to send every resolution viewers can select?
No. YouTube automatically transcodes a live input into multiple output formats. Send one suitable source resolution, then let YouTube create the viewer-side versions.
Is AV1 or H.265 better than H.264 for this use?
Not automatically. YouTube lists lower recommended input figures for AV1 or H.265 than for H.264 at the same 30 fps resolution, but the best choice depends on encoder support, processing stability and how reliably the complete setup runs. Use the recommendation for the codec you are actually sending, and test it over a representative run.