A 4K video file can stay at 4K while your streaming software sends a 1920×1080 live feed to YouTube. Set the outgoing resolution in the streaming software; you do not need to make a separate 1080p copy first if your playback path can scale the picture reliably.
These are three different stages: the resolution of your source file, the resolution your encoder sends to YouTube, and the versions YouTube makes available to viewers. The live encoder must still be configured for 1080p. YouTube’s viewer-side transcoding does not replace that setting.
Keep the source and live output separate
Think of the 4K file as the input, not as a declaration of what the live stream must be. Your playback software reads its frames, and the streaming encoder can resize those frames to 1920×1080 before sending them. The file on disk remains unchanged; only the live output is scaled.
For a 16:9 source, 3840×2160 scales evenly to 1920×1080: each output dimension is half the input dimension. The image has fewer pixels in the outgoing feed, but the original file is still available for later editing or a higher-resolution version. If you have a 4K clip in another aspect ratio, resizing alone will not make it fit a 16:9 canvas without a choice: you may crop part of the image, or preserve all of it with bars. Check faces, captions and edge details after choosing.
YouTube then processes the incoming live feed into formats suitable for viewers and their devices. That processing happens after your encoder has sent its configured output. If the event is set up for 1080p, send a 1080p feed rather than assuming YouTube will infer the desired resolution from the 4K file playing inside your software. The YouTube live encoder settings guide describes the encoder settings YouTube expects and its own processing of live streams.
This distinction can spare an unnecessary export. For example, if a 4K devotional programme already plays smoothly in your chosen streaming software, output scaling lets you use the original file directly. On the other hand, if playback stutters or the computer cannot decode the file consistently, a prepared 1080p copy may help; test that possibility rather than treating conversion as a rule.
Check the frame rate and playback path
Before adjusting the canvas, inspect the source file’s frame rate and note how it will reach the encoder. A 4K file may be 24, 25, 30 or 60 frames per second, among other possibilities. Choose the output cadence deliberately: matching the source is a straightforward starting point, while changing it means the playback path must repeat or drop frames. For a still-image ambience loop, 60 fps is not automatically an improvement; for footage with quick movement, the difference may be more visible.
The playback source and the stream encoder have separate jobs. Add the pre-recorded file as a media source in your streaming software, confirm that it opens at the intended start point, and make sure its sound is included in the programme audio. If the file should run continuously, establish how it will behave at its end: restart the file, move to another item, or show a planned holding scene. Do not assume a player will loop simply because the channel is meant to run all day.
Check for variable frame rate or unusual frame dimensions if timing or smoothness is inconsistent. A programme that looks normal in an editing application can behave differently in a live playback path, particularly if the file is high-bitrate or the machine is already busy. Test the same file, scene layout and audio route you intend to use, not a short low-motion sample that hides the difficult parts.
For an always-on programme, decide whether the local machine should remain part of the operating plan. A dedicated spare PC can be practical where you want direct access to the file and encoder, but it needs power, a stable connection and monitoring; see the spare-PC setup considerations. If your file plays correctly but keeping a computer awake overnight is the recurring problem, StreamNeo removes that specific need by letting you upload a file and run the YouTube broadcast without leaving your own computer on.
Set the outgoing size to 1920×1080
In OBS, open Settings > Video and set Output (Scaled) Resolution to 1920×1080. The Base (Canvas) Resolution describes the working canvas used to arrange sources; it can remain at the source or layout resolution where that suits the scene. What matters for the transmitted 1080p feed is the scaled output setting. OBS’s official scaling and performance guidance. explains the output resolution and scaling filters.
After setting the dimensions, inspect the preview. A full-frame 16:9 video should fill a 16:9 canvas. If it appears stretched, cropped, or surrounded by unexpected bars, correct the source transform or decide explicitly how bars should look. Do not distort the image to fill the canvas: circles becoming ovals or faces appearing wide are signs that the aspect ratio has not been preserved.
Choose a scaling filter as a practical trade-off rather than a universal quality setting. OBS offers bilinear, bicubic and Lanczos. Bilinear is the lightest on system resources; Lanczos uses more resources and can preserve a sharper impression of fine detail; bicubic sits between them. The visible difference depends on the footage, and the heavier filter may be unhelpful on a machine already close to its limits.
Use representative material to decide. A still shot of text, a face, tree leaves, or temple ornament can reveal softness and ringing around edges; a moving shot can show whether detail flickers. If you see encoding or rendering lag while using a sharper filter, compare a lighter option. A clean, steady picture is more useful than a theoretically sharper frame that cannot be processed consistently.
If you are using a different application, find its outgoing or canvas resolution controls and confirm that the encoder output—not merely the preview or source properties—is 1920×1080. The names vary by product. A 4K preview window does not prove that the stream is 4K, and a 1080p project canvas does not prove that the transmitted feed is 1080p either; verify the encoder’s actual output settings.
Choose codec, bitrate and keyframe interval
YouTube’s live encoder recommendations depend on the output resolution, frame rate and codec. For 1080p at 30 fps, its recommended bitrate is 14 Mbps for H.264 and 10 Mbps for AV1 or H.265. At 1080p and 60 fps, the recommendations are 17 Mbps for H.264 and 12 Mbps for AV1 or H.265. These are starting points from YouTube’s current encoder settings, not a guarantee that your connection or chosen encoder can sustain them.
| Output choice | YouTube recommended video bitrate | Consider it when |
|---|---|---|
| 1080p, 30 fps, H.264 | 14 Mbps | You want the broadly familiar H.264 workflow and the source cadence suits 30 fps |
| 1080p, 60 fps, H.264 | 17 Mbps | The source has useful motion detail at 60 fps and upload capacity is sufficient |
| 1080p, 30 fps, AV1 or H.265 | 10 Mbps | Your encoder and end-to-end workflow support the chosen codec |
| 1080p, 60 fps, AV1 or H.265 | 12 Mbps | You want 60 fps and have confirmed support for that codec combination |
The same YouTube table lists minimum values below these recommendations, but those are not sensible targets for routine quality planning. Start from the recommended figure for your selected combination, then check whether your upload connection can hold it steadily with room for normal variation. YouTube advises running an upload-speed test. If your available connection is marginal, reducing the stream’s demands—such as choosing 30 fps where it suits the source—is preferable to picking settings that repeatedly exceed what the connection can carry.
YouTube supports H.264, H.265 (HEVC) and AV1 for live ingestion, but your chosen streaming application and encoder must also support the particular combination you intend to use. H.264 is often the simpler compatibility choice; the supported codecs and bitrate recommendations are platform facts, not a claim that every software package exposes each option. For details on the encrypted transport choice, the RTMP, RTMPS and SRT overview explains why transport protocol is a separate question from resolution and codec.
Set rate control to constant bitrate (CBR), as YouTube recommends, and use a two-second keyframe interval. YouTube says not to exceed four seconds. A keyframe interval is not the same as frame rate: at 30 fps, a two-second interval means keyframes are spaced across the stream according to time, not that the video is running at two frames per second. Keep the audio settings in view too; YouTube lists AAC or MP3 as supported and recommends stereo audio at 128 Kbps and 44.1 kHz in its advanced recommendations.
For SDR, YouTube specifies Rec. 709 and 8-bit depth. Keep those colour settings consistent across the playback and output path where your software exposes them. If colours look washed out or unexpectedly saturated, verify the source and output colour settings rather than trying to correct the issue only with a scaling filter.
Configure the YouTube event and encoder
Create or schedule the live event in YouTube Studio and choose the normal workflow for an encoder-based broadcast. The event’s configuration and the software encoder must agree about the outgoing resolution and frame rate. If your software sends 1920×1080 at 30 fps, use those values when YouTube asks for the encoder’s settings; do not enter the 4K source file’s dimensions as though they describe the transmitted signal.
Copy the stream key into the encoder carefully and keep it private. YouTube recommends RTMPS, its encrypted extension of RTMP. Select the server address and protocol supplied by YouTube for the event, then verify the encoder is connected before starting the public broadcast. If you are changing an existing setup from RTMP, use the RTMPS changeover guide to keep the transport change distinct from a change in video settings.
Check that the event is set up as intended for live playback, including visibility and any scheduled start time. If the stream is meant to become an archive, review the relevant archive settings separately; they do not change the incoming encoder resolution. This is also a good moment to verify the title, description and thumbnail so that technical testing does not accidentally turn into a rushed public launch.
Test scaling, playback and stream health
Run a private or unlisted test before relying on the setup for a long broadcast. YouTube’s guidance is to test with audio and movement similar to the planned stream. A test with only a static title card will not reveal whether detailed motion overwhelms the encoder, whether the sound is routed correctly, or whether a particular clip drops frames.
Watch the YouTube Live Control Room’s stream health messages while the test runs. Check for dropped frames, connection warnings and any indications that the incoming settings differ from the event configuration. Also check what a viewer actually sees: confirm the visible image is correctly framed, the sound is audible, and the picture is not unexpectedly soft or distorted. A connected encoder icon alone does not confirm that the whole programme is behaving as expected.
For a prerecorded file, include a check near the beginning and the end. Confirm that playback starts at the right point, that the file’s audio stays in sync with the picture, and that the planned next action happens when the clip ends. If you are joining files or routing audio through a separate process, timing deserves particular attention; the guide to fixing audio drift in an FFmpeg YouTube stream covers one such failure mode.
Keep notes on the actual settings that worked: source frame rate, output size, codec, bitrate, filter and any warnings shown in the control room. Change one setting at a time when troubleshooting. If you change resolution, frame rate and bitrate together, a better or worse result will not tell you which change mattered. During the live event, continue to monitor stream health and messages rather than assuming that a successful initial connection means the rest of the night is settled.
When an offline conversion may help
A separate 1080p export is optional, not a prerequisite. Live scaling is usually the simpler route when the playback software decodes the 4K file smoothly, the output is correctly framed, and the machine can encode the chosen stream settings without lag. It avoids keeping two near-identical programme files and an extra export step in the workflow.
Offline conversion is worth testing if the 4K source is unusually demanding for the playback machine, if the decoder or playback application struggles, or if your chosen live software cannot reliably scale that source. It can also be useful when you need a prepared 1080p master for several workflows, or when you want to inspect and approve the scaled picture before the broadcast. These are operational reasons, not a YouTube requirement.
If you do convert, preserve the original and check the export’s dimensions, frame rate, audio sync and aspect ratio before replacing anything in the live playlist. Avoid changing frame rate casually: converting a 60 fps source to 30 fps discards temporal detail, while converting the other way cannot create motion that was not present in the source. A conversion does not automatically improve quality; it adds an encode generation and may soften detail or introduce artefacts if poorly configured.
The practical comparison is straightforward: live scaling saves preparation and retains the original untouched, while an offline copy can reduce live decoding work and gives you a fixed output to inspect in advance. Test both only if the live path gives you a real problem. Do not add a conversion stage merely because the source filename says 4K.
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 my 4K file need to be converted before a 1080p YouTube Live stream?
No. If your streaming software can play the file and scale its outgoing feed, leave the source as it is and set the encoder output to 1920×1080. Convert a copy only if it solves a playback, compatibility or preparation problem.
Will YouTube downscale the 4K file for me?
YouTube processes an incoming live stream into viewer formats, but it does not configure your encoder’s outgoing feed. Set the live output to 1920×1080 yourself if that is the resolution you intend to send.
Should I stream at 30 fps or 60 fps?
Choose a cadence the source supports and that suits the movement in the programme. YouTube’s recommended bitrate is higher for 1080p60 than for 1080p30, so consider upload capacity as well as the visual difference.
Which downscaling filter should I use?
Start with a filter your machine can process steadily, then compare the actual footage. Bilinear is lighter on resources, while Lanczos can retain a sharper impression of detail at greater cost; neither is best for every source or computer.