For a continuous YouTube property tour stream, use 14 Mbps video bitrate at 1080p30 when you are sending H.264. YouTube lists 5 Mbps as the minimum for that combination, but the minimum is a floor rather than a sensible quality target.
If the tour needs 60 frames per second, use 17 Mbps at 1080p60 H.264. Plan for upload capacity above the video bitrate, because YouTube advises leaving 20% of room and other activity on the connection can reduce what the encoder actually receives.
Choose the resolution and frame rate first
Bitrate is not a setting to choose in isolation. Start with the amount of detail viewers need, the speed of the camera movement, and the upload connection available where the stream will run.
A property tour usually contains rooms, façades, gardens, signs, windows and furniture. Fine detail matters, but the camera often moves more slowly than it would in a sports broadcast or gaming stream. For that reason, 1080p30 is a reasonable starting point for many tours. This is a practical production choice, not a property-tour setting prescribed by YouTube.
At 30 frames per second, the encoder sends fewer pictures each second than it does at 60 frames per second. That leaves more data available for each frame at the same overall bitrate, while also reducing the upload requirement. Slow pans and steady walks can work well at 30 fps if the camera and shutter settings are suitable.
Choose 60 fps when movement is a central part of the presentation. A fast walk through a narrow room, a drive-through tour, or quick camera turns may look smoother at 60 fps. The trade-off is a higher recommended bitrate and a greater demand on the upload connection.
Do not select 1440p or 4K simply because the original camera can record it. Higher resolution can preserve more architectural detail, but it also increases the required bitrate and leaves less tolerance for a variable connection. YouTube advises selecting the highest resolution and bitrate that can be streamed reliably, not the highest setting that looks attractive on a camera specification sheet. Its live stream settings guidance explains that reliability remains part of the decision.
If the video is a prepared file rather than a live camera feed, the same incoming bitrate rules still apply when that file is encoded and sent as a live stream. The question is whether the stream will remain stable for the entire broadcast, including overnight periods when nobody is watching the controls.
Set 1080p30 H.264 to 14 Mbps
For 1080p30 H.264, YouTube’s listed recommended live ingestion bitrate is 14 Mbps. Set the video encoder to 14 Mbps with constant bitrate, or CBR, if your encoder uses that wording.
YouTube lists 5 Mbps as the minimum for 1080p30 H.264. That value can help you understand the lower boundary of the published guidance, but it should not be treated as the target for a detailed property tour. At 5 Mbps, movement, foliage, brickwork and fine interior textures have less data available than at the recommended setting. Problems are more likely to show when the camera pans or the scene contains many small edges.
The 14 Mbps setting is for the video stream. It does not mean that the complete connection only needs to support 14 Mbps. Audio uses additional capacity, and the connection needs spare room for the stream to remain viable when conditions change.
Use a two-second keyframe interval where the encoder exposes that control. YouTube’s live encoder guidance recommends a two-second interval and says it should not exceed four seconds. Keep the audio enabled while testing. YouTube lists AAC or MP3 for stereo audio and recommends 128 kbps audio bitrate, which is useful for a host explaining the property while moving between rooms.
The codec matters. The 14 Mbps figure belongs to H.264 at 1080p30. YouTube’s table also lists a different recommended value for AV1 or H.265 at the same resolution and frame rate. Match the row to the codec actually being sent rather than copying a number from a different encoder configuration. You can check the full table in YouTube’s live encoder settings and bitrate guidance.
A practical starting configuration therefore looks like this:
| Setting | 1080p30 H.264 choice |
|---|---|
| Resolution | 1920 × 1080 |
| Frame rate | 30 fps |
| Video bitrate | 14 Mbps recommended |
| Published minimum | 5 Mbps |
| Rate control | CBR |
| Keyframe interval | 2 seconds |
| Audio reference | AAC or MP3, 128 kbps stereo |
These are incoming encoder settings. YouTube transcodes the incoming live stream into different output formats for viewers, so a viewer’s playback quality is not necessarily the same bitrate as the stream you send.
Compare 1080p60 H.264 carefully
For 1080p60 H.264, YouTube lists 17 Mbps as the recommended live ingestion bitrate and 6 Mbps as the minimum. The recommended value is higher than the 1080p30 recommendation because twice as many frames need to be sent each second.
| Incoming stream | H.264 minimum | H.264 recommended | Practical use in a property tour |
|---|---|---|---|
| 1080p30 | 5 Mbps | 14 Mbps | Steady room tours and slower pans |
| 1080p60 | 6 Mbps | 17 Mbps | Faster walking, driving or camera movement |
The 60 fps row is not automatically better. It gives movement more temporal detail, but it also raises the bitrate and upload requirement. If the connection is marginal, a stable 1080p30 stream is preferable to a 1080p60 stream that repeatedly loses data or disconnects.
A fast pan across a room can expose the difference. At 30 fps, a quick turn may appear less smooth, while at 60 fps it can look more continuous. However, the benefit depends on the camera, lighting, shutter settings and the actual movement in the footage. A static property montage may gain little from doubling the frame rate.
Do not use 17 Mbps as a general figure for every 1080p tour. It is YouTube’s recommended H.264 value for 1080p60. If your encoder is set to 1080p30, use the corresponding 14 Mbps recommendation and calculate your upload headroom from that value.
Keep the minimum separate from the recommendation
The distinction between minimum and recommended bitrate is important when planning a stream that may run for many hours. The minimum describes the lower boundary in YouTube’s published encoder table. It is not a promise that the picture will have the detail you want, and it is not the target for a property presentation.
For 1080p30 H.264, the two figures are 5 Mbps minimum and 14 Mbps recommended. For 1080p60 H.264, they are 6 Mbps minimum and 17 Mbps recommended. These are video bitrate figures, not upload-speed requirements for the whole connection.
If the available upload capacity cannot support the recommended 1080p setting with room to spare, do not simply force the encoder to the minimum and assume the problem is solved. Lowering resolution or frame rate may be a more dependable choice. YouTube’s own settings guidance favours the highest resolution and bitrate that can be streamed reliably.
For example, a connection that occasionally reaches the required figure but falls below it during busy periods is not a sound basis for a continuous 1080p60 tour. A lower setting that remains steady can produce a better viewer experience than a higher setting with repeated interruptions. This is especially relevant where the connection is shared with a home, office, shop or property team.
The same principle applies when comparing a local computer with a cloud-based workflow. If the local machine must remain switched on for a prerecorded loop, the main risk is not only encoding quality but also whether the computer, software and connection will continue operating without attention. The discussion in cloud playout versus YouTube Live Control Room covers that operational distinction in another continuous-stream setting. Remove the space after the opening parenthesis in the published link if your editor does not normalise it.
Calculate upload headroom from the stream bitrate
YouTube advises leaving 20% of upload room above the total stream bitrate. For a single 14 Mbps video stream, applying that guidance means:
14 Mbps × 1.25 = 17.5 Mbps
So, plan on approximately 17.5 Mbps of available sustained upload capacity for the 1080p30 stream alone, before allowing for other traffic. This is an arithmetic result based on YouTube’s 20% headroom advice. It is not a separately published YouTube bitrate figure.
For 1080p60 H.264, applying the same calculation to the 17 Mbps recommended video bitrate gives:
17 Mbps × 1.25 = 21.25 Mbps
Again, that is a planning calculation, not a new YouTube recommendation. It does not include the needs of other devices, a backup feed or unrelated upload activity.
The calculation should use the total simultaneous stream bitrate. If you send a primary and backup stream, add their bitrates first, then apply the headroom. If a second operator is uploading large files, a security system is using the connection, or other people are on a video call, the usable capacity left for the tour is lower.
Measure upload capacity rather than download capacity. A fast download result can coexist with an inadequate upload path, and the stream depends on data leaving the encoder. Test from the same location and connection that will carry the broadcast, preferably at a similar time of day to the planned tour.
You can use a bitrate and upload planning guide for a 24/7 YouTube stream alongside this calculation, but do not treat a single speed-test result as a guarantee. A long broadcast tests the connection for much longer than a short measurement does.
Account for shared traffic and camera movement
A dedicated connection makes planning simpler, but many property tours use a shared home broadband line, office connection or mobile connection. Other traffic can consume upload capacity without appearing in the streaming software as a deliberate change.
Common examples include cloud backup, CCTV uploads, large file transfers, video calls and another live broadcast. Even if the average upload speed looks sufficient, bursts of competing traffic can cause the encoder to fall behind. YouTube notes that shared networks can limit an individual connection and that a connectivity disruption can break the stream.
Run the tour without starting large uploads in the background. If other people need the connection, agree a quiet period for the broadcast. Where the equipment supports it, a wired network path may reduce local wireless variability, but a cable does not guarantee that the wider internet connection will remain stable.
Movement affects the picture as well as the connection decision. A slow pan across a furnished room may be easier to encode than a rapid turn through a hallway. Leaves moving outside a window, rain, traffic and patterned wallpaper can also create changing detail. Test representative scenes rather than pointing the camera at a static wall and assuming the result applies to the whole tour.
If you are preparing a prerecorded loop, inspect the sections with the most movement and the most fine detail. If those sections look soft or break up at the chosen bitrate, increasing the bitrate may help only if the upload path can carry it. Otherwise, reduce the resolution or frame rate and test again.
For a tour that must continue while the production computer is off, StreamNeo removes the need to leave that computer running: upload the file once, provide the YouTube stream key, and let the prepared stream continue with automatic monitoring and restart if it drops. The bitrate and network choice still needs testing before the broadcast.
Test stability and watch stream health
YouTube recommends testing before starting the live stream with audio and movement similar to the intended broadcast. For a property tour, walk the route at the expected pace, speak at the expected distance from the microphone, and include the rooms or exterior scenes that contain the most movement.
Test at the actual resolution, frame rate, codec, bitrate and keyframe interval. A test at 720p does not prove that a 1080p60 configuration will work. Likewise, a test with no audio does not show whether the complete encoder configuration behaves properly.
Keep the network load realistic. If the tour will share a connection with a business or household, test while that normal activity is taking place, or set a clear operating plan that prevents competing uploads during the broadcast. Test for long enough to expose gradual instability rather than relying only on an initial connection check.
During the live event, watch YouTube’s stream health messages in Live Control Room. Look for warnings about dropped frames, insufficient bitrate or connection problems. A picture that looks acceptable on the local preview does not prove that YouTube is receiving the stream correctly.
If the stream becomes unstable, make one controlled change at a time. Stop competing uploads, check the upload path, and confirm that the encoder is still using the intended bitrate. If the available capacity is not sufficient, move to a lower resolution or frame-rate choice instead of repeatedly restarting the same overloaded configuration.
For a locally operated loop, FFmpeg versus OBS for a prerecorded YouTube live loop can help you compare the software side of the workflow. If the problem is a machine that must stay available overnight, how much RAM an FFmpeg YouTube loop needs addresses a different part of the operating decision. Neither article replaces an upload test for the actual stream.
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 enough for a 1080p30 property tour?
YouTube lists 5 Mbps as the minimum H.264 live ingestion bitrate for 1080p30, but it is not the recommended quality target. For a detailed tour, start with the listed 14 Mbps recommendation if the upload connection can sustain it with headroom.
Should I use 1080p60 for every property tour?
No. Use 60 fps when faster movement makes smoother motion important and the connection can support the higher requirement. For slower room tours, 1080p30 is a reasonable starting point and requires less upload capacity.
Does 17.5 Mbps mean YouTube recommends 17.5 Mbps video bitrate?
No. YouTube’s recommended H.264 video bitrate for 1080p30 is 14 Mbps. Approximately 17.5 Mbps is the result of applying YouTube’s 20% upload-headroom advice to that stream, before allowing for other traffic.
Should I test download speed or upload speed?
Test sustained upload capacity from the location where the encoder will run. Download speed does not show whether enough data can leave the encoder, and a short result cannot guarantee stability throughout a long broadcast.