Start with the output you want

Open OBS Settings with streaming and recording stopped. Use a separate named profile for the destination so changing a rehearsal does not overwrite your working output. Keep a copy of the scene collection as well: a profile stores output settings, while scenes describe what appears and sounds in the program.

Write down the destination, video codec, output size, frame rate and sustained upload. If you arrived from a tool, the selected output appears below. These are planning inputs, not a claim that your computer or destination has accepted them. Field names here were checked against OBS documentation on September 7, 2026; available encoder options depend on your OBS build, operating system, drivers and hardware.

Run the bandwidth calculation for your selected output before entering video bitrate. A source-camera mode, an HDMI display mode and the stream output are three different choices. A 4K passthrough display does not establish 4K capture or 4K upload capability.

    Set Video: canvas, scaled output and FPS

    In Settings → Video, Base (Canvas) Resolution is the space in which you arrange the scene. Output (Scaled) Resolution is the frame sent to the encoder. Set the output to the intended stream size; keep its aspect ratio consistent with your layout or deliberately crop and inspect the result. A smaller input cannot gain captured detail by being enlarged.

    Choose Common FPS Values to match the planned output. Check motion in the source before increasing the stream frame rate; sending more frames cannot repair a camera or capture device that is delivering fewer. Leave an extra rescale in Output disabled unless you intentionally need a different encoded size, so the Video output remains the single scaling decision.

    The field map is an original schematic, not an OBS screenshot. Follow the arrows from the choice you made to the setting it controls.

      Scene and destination

      Composition area ↓
      Video: Base (Canvas) Resolution
      Stream size and movement ↓
      Video: Output (Scaled) Resolution
      Video: Common FPS Values

      Encoded stream

      Destination codec ↓
      Output → Streaming: Video Encoder
      Upload budget + service profile ↓
      Rate Control · Bitrate · Keyframe Interval
      Sources assigned to stream track ↓
      Streaming: Audio Track
      Output → Audio: track bitrate
      Video defines the frame; Output defines how it is compressed and sent. Review both panels when changing profiles.

      Choose the available encoder and rate control

      In Settings → Output, switch Output Mode to Advanced and open Streaming. Select a Video Encoder that implements the codec accepted by your destination. H.264 may appear as a hardware option associated with NVIDIA, AMD, Intel or Apple, or as the software encoder x264. The presence of a GPU model in a shopping list does not prove which options this host exposes.

      Keep the encoder’s normal service-compatible preset for the first rehearsal. Save its exact name in your notes. Hardware encoding can move compression work away from x264’s CPU path, but OBS still needs resources to compose the scene. Do not copy another machine’s preset, multipass or quality settings as a performance guarantee.

      For the conventional live profiles below, Rate Control is CBR. Enter video bitrate in Kbps, not Mbps: multiply the Mbps figure by 1,000. A recording quality control such as CQP, CRF or a quality slider is not the same field. Enter an explicit Keyframe Interval in seconds. Keep the service’s limits enabled; do not bypass them to force an unsupported profile.

        YouTube example: 1080p60 with H.264

        For an SDR stereo stream, YouTube’s encoder table currently recommends 12 Mbps video for 1080p60 H.264, CBR and a 2-second keyframe interval (no more than 4 seconds). Its stereo guidance is AAC or MP3, 128 Kbps and 44.1 kHz. Use AAC here. This example follows that published profile; it is not a hardware benchmark.

        Set Base Canvas to your composition size, for example 1920 × 1080; Output Scaled to 1920 × 1080; FPS to 60; Video Encoder to an available H.264 implementation; Rate Control to CBR; Bitrate to 12000 Kbps; Keyframe Interval to 2 seconds. In Audio choose Stereo and 44.1 kHz; in Output → Audio set the selected stream track to 128 Kbps and use AAC.

        Worked upload check: one stream at (12 + 0.128) ÷ 0.80 + 2 = 17.16 Mbps, using this site’s 20% capacity margin and a reader-chosen 2 Mbps household reserve. A measured 20 Mbps leaves 2.84 Mbps above that plan. The margin and reserve are planning assumptions; a green calculation still needs a destination test. If it fails, select a lower output in the calculator and carry its resulting bitrate back here.

          Twitch example: carry a tested profile into OBS

          Open Twitch Inspector and the current Twitch broadcasting guidance. Use the OBS Twitch service integration for the current account. If Enhanced Broadcasting is enabled, its negotiated encodes and bandwidth budget are a different path from this single-encode example; do not overwrite that configuration with a universal bitrate.

          Example chosen by a reader: 1280 × 720 at 30 fps, H.264, CBR, 3000 Kbps video, keyframes every 2 seconds, AAC stereo at 128 Kbps and 44.1 kHz. These are explicit example inputs to validate in Inspector, not a claim that every account, content type or connection should use them. Set Output Scaled to 1280 × 720 and FPS to 30, then enter the codec, rate control, video bitrate and keyframe values in Output → Streaming. Set the chosen stream track’s audio bitrate in Output → Audio.

          Before adopting that example, confirm that current account/service guidance permits the chosen profile. Follow Inspector’s test instructions, compare its received resolution, FPS and stable bitrate against your note, and check for reported errors. If the service requests a change, update the named field and repeat. A test that has not been run remains unvalidated; this page never marks your Twitch account as checked.

          For a capacity estimate using the same planning margin, (3 + 0.128) ÷ 0.80 + 2 = 5.91 Mbps. This is arithmetic for the example, not the calculator issuing a Twitch recommendation. Keep concurrent encodes, household traffic and actual Inspector observations in the final decision.

            Choose the stream track and verify its contents

            Output → Streaming selects the audio track broadcast to the service. Advanced Audio Properties determines which sources feed that track. Confirm the microphone, game, alerts and any guest are assigned once. Listen to the destination, because hearing a source in headphones does not establish that it is on the stream track.

            Use the OBS audio-routing steps to assign sources and monitoring. If the live mix and archive must differ, follow the separate stream and VOD track procedure; selecting another track number alone does not remove a sound from the live program. Check sample-rate settings across OBS and the audio device if you hear clicks or drift.

              Test recording and streaming together

              For the first comparison, use the stream encoder for recording (Same as stream in Simple mode, or the equivalent stream-encoder choice in Advanced). OBS notes that a separate recording quality or encoder adds resource demand. MKV is a resilient recording container if a session stops unexpectedly; remux a copy afterward when your editor needs MP4. Verify free disk space before the rehearsal.

              Play the actual saved file in another player. Check a scene transition, a movement-heavy segment, speech, alerts and any camera cut. A good recording verifies part of the local path, not the upload path. If you later choose a separate high-quality recording encoder, repeat the test while streaming and recording together.

                Confirm the received stream before saving the profile

                Use a private or unlisted test where your destination supports it, or the destination’s documented test mode. Confirm its visibility before starting. Watch the destination preview on another device, with headphones or the preview muted locally to prevent a feedback loop. Check the received output size/FPS and audio, not only the OBS preview.

                Open View → Stats and compare the counters before and after a representative rehearsal. Save the profile only after output, sound and destination health match the plan. Record the OBS version, encoder name/preset, date, stream profile and result so the next rehearsal has a baseline.

                If motion breaks up, the encoder warns, or viewers buffer, separate network drops, rendering lag and encoding lag in OBS Stats before changing equipment. The repair guide supplies a worksheet and a distinct first check for each symptom.

                  Sources