Corneta guides
Upload, bitrate, encoders, resolution, and computer load.
Guide
Use 720p30 for stability and low-motion content, 720p60 for motion with limited bandwidth and 1080p60 when text, detail, upload and encoder can keep up. The best setting is the one that stays stable in your heaviest scene.
Guide
Copy when the same H.264, resolution, FPS and bitrate work for every platform. Transcode only the destination that requires a different limit or format.
Guide
“Dropped frames” usually points to the network, but OBS also measures rendering lag and encoding lag. Open Stats and fix the counter that actually went up.
Guide
For local multistream, add up the video and audio bitrate of every output. As a starting point, look for a stable connection of 1.5 to 2 times that total.
Guide
First cap the game's FPS and copy the compatible signal instead of transcoding it. If there is still lag, simplify scenes, cut transcoded outputs and go from 60 to 30 FPS before you touch the OBS base resolution.
Guide
Start with the hardware encoder you have: NVENC on NVIDIA, QSV on Intel or AMF on AMD. Use x264 when there is no compatible hardware or when the CPU has proven headroom.
Guide
RTMP is the protocol that carries your stream to an ingest server; the stream key identifies your channel. Bitrate measures data per second, a keyframe starts over with a complete image and transcoding creates another version of the video.
Guide
There is no perfect bitrate for all three platforms. In H.264, 1080p60 calls for 6 Mbps on Twitch, 17 Mbps recommended on YouTube (6 minimum) and up to 8 Mbps on Kick; use the lowest common profile or transcode only the destinations that need it.
Guide
A lagging stream can come from the network, rendering or the encoder. Check which counter went up before you lower quality or restart everything — each cause needs a different fix.