YouTube normally detects the resolution and frame rate arriving from a custom stream key. You can choose them manually by creating a custom key with manual stream-resolution settings, then matching your encoder settings to the connection available at the property.
There is no universally best resolution for a continuous real-estate showcase. More detail can help viewers inspect rooms and finishes, but it also calls for a connection that can sustain the matching bitrate; test the actual venue and choose reliability over a setting the upload cannot hold.
How YouTube handles resolution by default
YouTube’s default for streams using custom stream keys is automatic detection of incoming resolution and frame rate. In practice, your encoder sends a video signal to YouTube, and the platform identifies the format it receives. If you have no specific reason to override this behaviour, leaving detection on is a reasonable starting point.
In YouTube Studio, open Go Live and prepare a stream. The encoder workflow provides a stream URL and a stream key: the URL tells the encoder where to send the feed, and the key authorises its acceptance. YouTube describes this setup in its live streaming encoder instructions.
Automatic detection does not mean that any camera output will be sustainable. The encoder still has to send a consistent feed over the property’s internet connection. A setting that works in an office may falter in a sales suite, a newly built home, or a venue whose connection is shared with guests and staff. The resolution seen by the encoder and the upload conditions at the venue both matter.
For a showcase, think about how the picture will be used. A room tour with slow pans may call for clear detail, especially where viewers are examining finishes or layout. A long-running static view may not need the same visual treatment as a camera moving through a property. Those are production choices, not YouTube rules, and the right choice depends on what viewers need to see and what the connection can sustain.
If you are using OBS, the stream can also be affected by media-source or scene behaviour, not just resolution. The practical checks in keeping a YouTube stream running when OBS loses its media source are relevant when your showcase depends on a prepared loop rather than continuous camera operation.
When to set resolution manually
Manual selection is useful when you want a defined output format and have tested that format at the venue. For example, you might want to keep a camera and encoder on one known resolution and frame rate throughout a property tour, rather than allowing automatic detection to follow changes in the incoming signal. A consistent configuration also makes it easier to compare tests from one visit to another.
It is not a shortcut to higher quality. Selecting a higher resolution increases the data the encoder needs to send when paired with the corresponding bitrate settings. If the upload connection cannot sustain the feed, the picture may become unstable or the stream may report health problems. A nominal speed result from a single test does not establish that a connection will hold for a continuous broadcast.
YouTube’s recommended live encoder settings and bitrates are organised by codec, resolution and frame rate. Use the row that matches the incoming format rather than choosing a bitrate from a general video-upload guide. These values describe live ingestion settings; they are not a promise of stability at a venue with variable upload capacity.
Manual control is also worth considering when you have a specific workflow constraint. Perhaps the camera only outputs one format, or you have a controlled encoder profile that must be repeated for each showcase. If neither applies, automatic detection avoids adding a setting you do not need to manage. The decision is about control and repeatability, not about a platform preference for one resolution.
Create a custom key with manual settings
In YouTube Studio, go to Go Live and prepare the stream. Create a custom stream key, then look for the manual-settings option under Stream resolution. Turn it on and choose the resolution and frame rate you intend to send. The exact interface can change, so check the current YouTube Help instructions for encoder settings if the labels differ from what you see.
Then configure the encoder to send the same combination. If the key is set for a particular resolution and frame rate but the encoder is outputting something else, your setup is no longer the clean, repeatable configuration you intended. Check both sides before going live: the stream settings in YouTube Studio and the video output profile in the encoder.
YouTube’s guidance lists RTMP or RTMPS as supported protocols, and lists H.264, H.265 (HEVC) and AV1 video codecs. It also specifies constant bitrate (CBR), up to 60 frames per second, and a recommended two-second keyframe interval that should not exceed four seconds. These are encoder compatibility recommendations, not reasons to buy a particular device. You do not need dedicated encoder hardware simply because you are setting a manual resolution.
Before the showcase, write down the selected key and the encoder profile associated with it. That small note helps if another person needs to restart the stream or you return to the same property for a second session. If the output changes—for instance, because a different camera or encoder profile is used—recheck the selected resolution, frame rate and bitrate together.
A video loop can create its own continuity issues, particularly if the media source disappears or a scene changes unexpectedly. For a pre-recorded property walkthrough, review the relevant OBS scene and media-source troubleshooting steps as part of the setup, alongside resolution testing.
Match resolution, frame rate, and bitrate
Resolution, frame rate and bitrate form one configuration. A resolution describes the picture dimensions; frame rate describes how many frames are sent each second; bitrate is the amount of video data being sent. The codec also affects which YouTube bitrate row applies. Set the encoder to a supported combination and consult the matching row in YouTube’s live-ingestion table.
The examples below reproduce YouTube Help’s minimum and recommended bitrate values in megabits per second (Mbps). The table distinguishes AV1/H.265 from H.264 because the listed figures differ. Values are for the incoming live stream, not a recorded file that you upload later.
| Incoming resolution and frame rate | AV1/H.265 minimum | AV1/H.265 recommended | H.264 minimum | H.264 recommended |
|---|---|---|---|---|
| 2160p (4K) at 60 fps | 10 | 35 | 14 | 50 |
| 2160p (4K) at 30 fps | 8 | 30 | 11 | 42 |
| 1440p at 60 fps | 6 | 24 | 8 | 34 |
| 1440p at 30 fps | 5 | 15 | 7 | 21 |
| 1080p at 60 fps | 4 | 12 | 6 | 17 |
| 1080p at 30 fps | 4 | 10 | 5 | 14 |
| 720p at 60 fps | 2 | 6 | 3 | 8 |
| 720p at 30 fps | 2 | 6 | 3 | 8 |
| 480p at 30 fps | 0.3 | 3 | 0.4 | 4 |
| 360p at 30 fps | 0.3 | 3 | 0.4 | 4 |
As listed in YouTube Help in September 2026, H.264 at 1080p30 has a minimum of 5 Mbps and a recommended bitrate of 14 Mbps; H.264 at 1080p60 has a minimum of 6 Mbps and a recommendation of 17 Mbps. Match the row to your actual codec and frame rate. Do not treat the minimum as a practical guarantee, or assume that a connection measuring the recommended bitrate once will deliver it continuously.
A higher frame rate also changes the relevant recommendation. If a slow property tour does not benefit from the extra motion detail of a higher frame rate, testing a lower frame rate may be a sensible way to reduce the bitrate demand. That is an option to evaluate rather than a rule that one frame rate suits every camera movement. For a tour with quick pans, compare the resulting picture in a test before deciding.
The venue’s usable upload capacity must leave room for variation. The connection may be shared, or performance may change during the day. The table tells you what YouTube recommends at ingestion; it does not account for every local network condition. Choose an output that works with observed capacity during realistic tests, rather than aiming at the highest row the connection briefly reaches.
Test upload capacity before the showcase
Start with an upload speed test on the connection you plan to use. YouTube recommends testing before a live stream and checking that the connection can support the bitrate for the selected format. A test is a useful baseline, but it is only a snapshot. If possible, repeat it at the time of day you expect to broadcast and while normal venue devices are using the network.
Then run a private or otherwise controlled stream test using the real camera, encoder, audio and movement. YouTube specifically advises that tests include audio and movement similar to the planned stream. A static test screen can miss problems that appear when a camera pans through a room or when the audio feed is enabled. Keep the camera moving as it will during the showcase and check the stream health messages in YouTube Studio.
Use a simple comparison rather than changing several variables at once. Test a candidate resolution and frame rate with its matching bitrate, note whether the feed remains stable, then make one adjustment and test again. If you change resolution, frame rate and codec all together, it becomes harder to identify which change helped or hurt. Record the connection conditions as well, such as whether the property Wi-Fi was busy.
If the stream health warning appears, do not assume that a higher resolution is still acceptable because the picture looks sharp on your own monitor. Viewers receive the stream after encoding and delivery, and a short local preview cannot show what will happen over a longer session. Check the platform’s messages, review the encoder output settings, and repeat the test under the same conditions.
For a remote or temporary property, plan a fallback before the day of the showcase. That might mean preparing a lower-resolution profile to use if the test shows the preferred setting cannot be sustained. It is more useful to have a tested alternative than to make a hurried change after the live broadcast has begun. A fallback is not a promise that the connection will stay up; it is a way to make a measured choice if conditions differ.
Choose a stable setting for the venue
The best setting for a particular showcase is the one that gives viewers useful detail while remaining sustainable on that venue’s connection. YouTube does not publish a resolution specifically for real-estate interiors, exteriors or tours. Assess the property, the camera movement, the network and the audience’s likely use of the picture rather than treating 4K, 1440p or 1080p as a universal answer.
A practical decision can be made in stages. First, decide what details viewers need to see: the overall layout, surface finishes, signage, or a slow walkthrough. Next, choose a candidate resolution and frame rate, then use YouTube’s matching codec row to set bitrate. Finally, test under realistic conditions and keep the highest-detail candidate only if it remains stable. If a stable 1080p feed proves more reliable than a higher-resolution feed, reliability is the sensible choice for a continuous showcase. That conclusion applies YouTube’s general reliability guidance; it is not a real-estate-specific platform rule.
Also consider what “continuous” means for the property and its replay. YouTube says it can automatically archive streams under 12 hours, but warns that a stream longer than 12 hours may not be captured at all; it recommends keeping a local recording if the archive matters. Its archive guidance also says streams at 1440p and 2160p are automatically archived, but that does not remove the explicit warning about exceeding 12 hours. Check the current YouTube archive guidance before relying on an automatic replay.
YouTube says DVR, which lets viewers pause and rewind a live stream, may be limited or unavailable for streams longer than 12 hours. Viewers also cannot seek back to before the stream began. If replay and rewind matter to prospective buyers, consider whether the showcase should be broken into shorter sessions and keep a separate recording. Session planning is an operational response to YouTube’s stated archive and DVR limitations, not a guarantee about capture.
A cloud-based route can be useful when the specific problem is leaving a local computer on for a long showcase: StreamNeo turns an uploaded video into a YouTube live stream, so you can switch your computer off after the file and channel are ready. It is YouTube-only, and it does not remove the need to choose an appropriate source file or plan any archive you need independently.
If you are weighing a local encoder workflow against a pre-recorded loop, the guide to streaming pre-recorded videos on YouTube 24/7 can help frame the operational differences. Whichever route you use, resolution remains one part of the stream plan, not a substitute for checking the source, connection and replay requirements.
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
Does YouTube choose the resolution automatically?
For streams using custom stream keys, automatic detection of the incoming resolution and frame rate is the default. If you need manual control, create a custom key and enable manual settings under Stream resolution, then make the encoder output match.
Which resolution is best for a real-estate showcase?
YouTube does not give a real-estate-specific resolution recommendation. Compare the detail your viewers need with the bitrate and upload capacity your venue can sustain, and base the choice on a realistic test rather than a universal preset.
Does the recommended bitrate guarantee a stable stream?
No. YouTube’s figures are encoder-ingestion recommendations for a particular codec, resolution and frame rate, not a guarantee that a connection with that nominal upload speed will remain stable. Test with comparable audio and camera movement, then monitor stream health.
Will YouTube keep the replay of a continuous showcase?
YouTube warns that a stream longer than 12 hours may not be captured at all, and DVR may be limited or unavailable for streams longer than 12 hours. If replay matters, keep a local recording and check the current YouTube guidance before deciding how to schedule the showcase.