If the game or screen runs on the same computer as your encoder, you can capture it in software and send a 2160p60 stream to YouTube without a capture card. The computer still needs enough performance to run the source, capture it and encode the stream at the same time.
A console or separate device is different. You need a supported way for the streaming computer to access that source, and no general method guarantees 4K60 without a capture card. Check the source path before changing encoder settings.
Identify where the game or screen runs
Start by drawing the signal path in plain language. Ask three questions: where is the game or screen being produced, which computer can see it, and which device will run the encoder?
If the game runs on the same Windows or macOS computer as the encoder, the path is direct:
game or desktop → capture source → encoder → YouTube
This is the simplest capture-card-free arrangement. OBS or another encoder can capture a game window, a display, or a supported application on that computer. YouTube describes encoder software as a way to share a screen and broadcast gameplay, but that does not mean every game behaves identically. A game may use a display mode, graphics API or anti-cheat system that affects which capture source works reliably.
If the game runs on a console, a second computer or another device, the path is different:
source device → supported connection or software path → encoder computer → YouTube
The encoder must receive usable video and audio before it can send anything to YouTube. A television displaying the console output does not automatically make that output available to OBS on a laptop. A remote or built-in streaming feature may work for a particular device, but you must verify its resolution, frame rate, audio behaviour and reliability yourself.
For a channel that will run continuously, source planning matters as much as picture quality. If you are recording a live game session, decide who will watch the source, who will monitor the stream and what happens when the game closes. If you are building a fixed visual loop, the more dependable approach may be to prepare a video file and use a cloud service that keeps the channel running while your computer is switched off. StreamNeo is designed for that specific uploaded-file-to-YouTube workflow, so it removes the need to leave the source computer running overnight.
Use direct capture on the encoder computer
For a computer game, open the game on the same machine that will encode the broadcast. In OBS, add a Game Capture source if the game is supported and visible to that source. If that does not behave properly, try Window Capture or Display Capture, accepting that each method has different performance and privacy consequences.
Game Capture usually targets the game rather than the whole desktop. That can reduce the risk of showing notifications, browser tabs or private messages. Display Capture is broader: it records what appears on a selected monitor, which is useful for a presentation or a desktop demonstration but requires more care before going live.
Capture the audio path at the same time. Check that the game or application audio reaches the encoder mixer, and add a microphone only if the broadcast needs one. Watch the mixer while the source is producing sound. A picture that looks correct but has silent or distorted audio is still a failed test.
The encoder computer now has several jobs. It must run the game or application, render the image, copy or capture frames, scale them if necessary, encode the video, encode audio and upload the resulting stream. Raising the output to 2160p60 does not create detail that the source does not contain. It also increases the work required at each stage.
Capture-card-free does not mean resource-free. A computer may run a game at 4K while struggling to encode a separate 4K60 stream. Conversely, an encoder may produce a smooth stream while the game itself drops frames. Test the actual title, scene and overlays you intend to use rather than relying on a desktop specification or a short menu screen.
If you are choosing a general setup for a long-running channel rather than occasional gameplay, compare the trade-offs in this guide to running a 24/7 YouTube stream without OBS. A direct computer capture path is useful when the source is active on that computer; it is not automatically the best arrangement for a fixed loop.
Check whether a console or other source needs a capture path
A console-only source cannot be treated as a computer screen simply because both devices are connected to the same home network. The streaming computer needs a supported input path that exposes the console's video and audio to the encoder.
Possible paths vary by device and software. A console may offer its own streaming feature, a remote-play application may expose gameplay to a computer, or a network application may provide a source. These paths have their own limits. They may change the resolution, add delay, compress the picture, omit audio or depend on a stable network connection. The official material used for this guide does not establish one universal console-to-PC method that preserves native 4K60 without a capture card.
Before committing to a console workflow, answer these practical questions:
| Check | Why it matters |
|---|---|
| Can the encoder computer receive the console's video? | A console connected only to a television is not an encoder source. |
| What resolution and frame rate arrive at the computer? | A 4K console output does not prove that the received source is 2160p60. |
| Does the audio arrive with the video? | Some paths need separate audio routing or produce delay between picture and sound. |
| Does the method remain stable during a long test? | A short successful connection may not survive a full broadcast. |
| Can the computer encode while receiving the source? | Receiving, displaying and encoding all consume resources. |
If the answer to the first question is no, changing OBS to 2160p will not solve the problem. You need to change the source path first. If the answer to the second question is 1080p or 30fps, the encoder cannot honestly turn that input into native 4K60. It can scale the image, but scaling is not the same as capturing more detail or more motion.
The same reasoning applies to cameras, phones, another laptop and set-top boxes. Identify the signal that reaches the encoder, then configure the output around what the complete system can sustain.
Set the OBS canvas and output to 4K60
In OBS, set the Base (Canvas) Resolution to 3840×2160 when the source and layout are designed for 4K. Set the Common FPS Value to 60. The canvas is the workspace in which OBS arranges sources; it is not, by itself, proof that the source or final stream is 4K60.
Set the Output (Scaled) Resolution to 3840×2160 when you want the encoder to send 2160p. Keep the output at the canvas size if your source is already composed at 4K. If the computer cannot sustain that arrangement, reduce the output resolution or frame rate rather than allowing a persistently overloaded stream.
Use a supported hardware or software encoder available in your OBS installation. The appropriate choice depends on the computer, graphics hardware, operating system and codec support. YouTube accepts H.264, H.265/HEVC and AV1 for live ingest, but your encoder may not offer all three, and a codec that is available may not be suitable for your source or hardware.
Set the rate control to CBR. YouTube recommends a two-second keyframe interval and says the interval should not exceed four seconds. These are ingest settings, not visual-quality guarantees. A correct keyframe interval cannot compensate for dropped frames, an overloaded encoder or insufficient upload capacity.
Use progressive output rather than assuming that an interlaced or unusual source mode will be handled as expected. Check the OBS statistics window during testing. Look for rendering lag, encoding lag, dropped frames and CPU or GPU pressure. The names and presentation of these counters can vary by version, but the principle is the same: find out which stage is falling behind.
For a further discussion of resolution and frame-rate decisions in always-on broadcasts, see this guide to OBS resolution and frame rate for a 24/7 YouTube stream. The useful lesson is not that 4K60 is always better, but that the output should match the source, hardware and purpose of the channel.
Configure YouTube encoder settings
Enable live streaming in YouTube Studio and prepare the event in Live Control Room. YouTube says first-time live-streaming enablement may take up to 24 hours, so do not begin this process immediately before an important broadcast. Create the event, select the encoder route and copy the stream URL and stream key into OBS or your chosen encoder. Keep the key private.
YouTube's current English settings table lists these figures for 2160p60:
| Codec | Listed minimum video bitrate | Listed recommended video bitrate |
|---|---|---|
| AV1 or H.265/HEVC | 10 Mbps | 35 Mbps |
| H.264 | 14 Mbps | 50 Mbps |
These are YouTube Help recommendations for live ingest, not results from an independent test and not a promise that every viewer will receive a 4K60 playback rendition. Use the current YouTube encoder settings page when you configure the stream, because platform guidance can change.
Choose a bitrate that the encoder and connection can sustain. The recommended figure is a sensible target when your hardware supports the selected codec and your upload service has room around it. If the connection cannot maintain the video bitrate, lowering the bitrate, resolution or frame rate is more useful than repeatedly reconnecting at an unstable setting.
YouTube recommends RTMPS for the connection protocol. Use the protocol and codec combination supported by your encoder and the current YouTube table. For ordinary stereo audio, YouTube lists AAC or MP3 support; AAC is also listed for 5.1 audio over RTMP or RTMPS. Keep the audio configuration straightforward unless you have a reason to test a more complex arrangement.
For SDR, YouTube's guidance includes Rec. 709 and 8-bit settings. HDR is a separate workflow. YouTube recommends H.265/HEVC for HDR and does not list AV1 as supported for HDR in the encoder settings table. HDR requires the source, colour settings and encoder output to agree, so do not label a stream HDR merely because the game or monitor is capable of displaying it.
At 2160p, YouTube says the low-latency option is unavailable and the stream uses normal latency. That makes 4K useful for image detail, but it is not the setting to choose if immediate audience interaction is the main requirement.
Test source performance and upload capacity
Run a private or unlisted test with the same movement, overlays and audio that the public broadcast will contain. A still desktop is an easy test and a poor representation of a fast game. Include camera movement, text, transitions, music or speech, and the busiest scene you expect to use.
Watch the encoder while the test runs. If the game itself stutters, lower game quality or frame rate before assuming the encoder is at fault. If OBS reports rendering or encoding lag, reduce scene complexity, change the encoder workload or lower the output target. If the picture is smooth locally but YouTube reports dropped frames, inspect the network path.
YouTube advises leaving about 20% headroom above the total stream bitrate. For example, a stream configured at 35 Mbps needs more upload capacity than a connection that measures exactly 35 Mbps. The recommendation concerns available outbound capacity, not the download speed shown in an internet package or speed test. Other users, cloud backups, security cameras and software updates can consume the same upload path.
Use a wired Ethernet connection if it is practical. It can remove one variable associated with wireless interference and signal changes, but it cannot increase the upload capacity supplied by your internet service. Test at the time and location in which you will actually stream, especially if the connection is shared.
If upload capacity is not sufficient, change one thing at a time and test again. A lower bitrate may preserve 4K resolution with less motion detail. A lower resolution may produce a cleaner result when the source is not truly 4K. A lower frame rate reduces motion smoothness but also reduces the amount of video data and processing required. There is no setting that makes an inadequate connection simultaneously carry the same data without compromise.
Do not confuse YouTube's live ingest table with recommendations for uploading recorded videos. They describe different workflows. Likewise, do not promise that viewers will all see 2160p60: YouTube transcodes the input for different playback formats, and the available rendition depends on the viewer's device, connection and playback conditions.
Verify YouTube stream health
Start the test stream before announcing it. In Live Control Room, check the preview, incoming signal and stream-health messages. YouTube recommends monitoring stream health and messages during the event, not only checking whether the encoder says it is connected. A connected encoder can still be sending dropped frames, incorrect audio or an input that does not match the intended output.
Compare what OBS reports with what YouTube receives. If OBS shows 3840×2160 at 60fps but YouTube identifies a different input, investigate the output profile, scaling settings and source path. If YouTube reports network problems, check upload saturation and competing traffic. If the source is smooth locally but the received stream is not, the fault may be between encoding and ingest rather than in the game.
Listen on another device as well as watching the preview. This can reveal a muted track, audio delay, clipping or a problem that is hidden by monitoring on the encoder computer. Use headphones when checking, and keep the test unlisted if you do not want an unfinished broadcast to be public.
Before a long session, write down the working settings and the recovery steps. Include the stream key location, the scene to start, the source to reopen, the audio devices to select and the person who can check the channel if the stream stops. For a fixed channel, also decide whether the broadcast should restart after a source failure or whether someone must intervene.
If your content is devotional, music-based or built from repeated media, picture quality is only one part of the risk. Review the separate guidance on avoiding copyright claims on a devotional YouTube Live stream before publishing material you do not own or have permission to use. A technically stable stream can still face an interruption or claim if its content rights are unclear.
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
Can I stream a PC game in 4K60 without a capture card?
Yes, if the game runs on the same capable computer as the encoder and that computer can capture, render and encode the source at 2160p60. You still need to test the particular game, scene and upload connection. A 4K display or game setting alone does not guarantee a 4K60 broadcast.
Can I stream a PS5 or Xbox in 4K60 without a capture card?
Not as a universal method. The console's video and audio must reach the encoder through a device-specific supported path, and that path may change the resolution, frame rate, audio or reliability. Verify the complete source route before treating it as a 4K60 setup.
What bitrate should I use for YouTube 2160p60?
YouTube's current English encoder table lists 35 Mbps as the recommended bitrate for AV1 or H.265/HEVC, and 50 Mbps for H.264, with lower listed minimums. Leave additional upload headroom, test the actual stream and check the current YouTube live settings guidance before publishing.
Will every viewer receive 4K60?
No. YouTube processes the incoming stream into playback versions, and the viewer's device, connection and available rendition affect what they receive. Configure and verify a clean 2160p60 input, but do not present that as a promise about every viewer's playback.