← Blog16 Jul 20264 min read

OBS Settings for Indian Internet

Streaming on a 20Mbps upload with an unstable line. Encoder choice, bitrate, and why your stream looks worse than your recording.

OBS Settings for Indian Internet

Most OBS guides assume a fibre connection with a rock-solid 50Mbps upload. Plenty of Indian connections are not that, and the correct settings are different.

Measure your upload first, properly

Not once. Run a speed test at the time you actually stream — evening upload speeds are frequently a fraction of the advertised figure.

Test three or four times across a week at your streaming hour and use the lowest number you see. That’s your real budget.

The 70% rule

Never set your bitrate above 70% of your measured upload.

The remaining 30% absorbs jitter, other devices on the network, and the general unreliability of a shared line. A stream that drops frames looks dramatically worse than one at a lower bitrate — viewers forgive softness, they leave over stuttering.

The stream bitrate calculator works this out for you.

Resolution and bitrate, matched

Output Bitrate Needs upload of
720p 30 3,000 kbps ~4.5 Mbps
720p 60 4,500 kbps ~6.5 Mbps
1080p 30 4,500 kbps ~6.5 Mbps
1080p 60 6,000 kbps ~9 Mbps
1440p 60 9,000 kbps ~13 Mbps

The important insight: a clean 720p60 looks better than a starved 1080p60. Under-bitrated 1080p is a blocky mess in exactly the fast-motion scenes that make up a shooter.

If your budget lands between two tiers, take the lower resolution at full bitrate.

Encoder choice

NVENC (NVIDIA) / AV1 or HEVC where supported — use this if you have a modern NVIDIA card. Modern NVENC is essentially free performance-wise and the quality is excellent.

AMD AMF — much improved on recent cards. Use it if you have one.

Intel QuickSync — decent, useful if you have an Intel iGPU sitting idle.

x264 (CPU) — only if you have no hardware encoder, or you have a genuinely high core count CPU doing nothing else. On a 6-core gaming CPU it will cost you frames.

The rule: encode on the GPU, game on the GPU, and let the CPU run the game. The old advice to use x264 for quality is outdated — hardware encoders caught up years ago.

Newer codecs, if your platform accepts them

HEVC and AV1 deliver similar visual quality at roughly 30% less bitrate. On a constrained upload that’s the difference between 720p and 1080p.

Support varies by platform and by viewer device, so check what your destination accepts before committing.

Keyframe interval and rate control

  • Rate control: CBR for streaming. Constant bitrate is what platforms expect.
  • Keyframe interval: 2 seconds. Required by most platforms.
  • Preset: quality, unless you’re seeing encoder lag.
  • Profile: high.
  • B-frames: 2 on NVENC.

These are set-and-forget. There’s very little to gain from tuning beyond this.

Downscaling correctly

If your base canvas is 1440p and you’re outputting 1080p, use Lanczos for the downscale filter. Bicubic is fine and slightly cheaper. Bilinear is soft.

Better still: set your base canvas to the output resolution and avoid scaling entirely, if you don’t need the extra canvas space for overlays.

Diagnosing a bad stream

OBS shows dropped frames in the status bar. Learn which number means what:

  • Dropped frames (network) — your upload can’t keep up. Lower the bitrate.
  • Skipped frames (encoding) — the encoder can’t keep up. Lower the preset, or switch encoder.
  • Missed frames (rendering) — your GPU is saturated. Lower game settings, or cap the game’s frame rate.

People frequently lower bitrate to fix an encoding problem, which does nothing. Read which counter is climbing.

Cap your game frame rate

Counter-intuitive but important: capping the game at, say, 120fps when your monitor is 144Hz leaves GPU headroom for the encoder.

An uncapped game consuming 100% of the GPU starves the encoder, which produces missed frames and a stuttering stream while your local gameplay looks perfect.

Record locally at higher quality

Your stream is bandwidth-limited. Your recording isn’t.

Set up a separate recording output at high bitrate — that’s the footage you’ll cut clips and videos from later. There’s no reason to archive the compressed stream when local storage is cheap.

Audio matters more than video

If you have limited resources to spend on quality, spend them here. Viewers tolerate a soft picture and leave over bad audio.

160kbps AAC, a decent microphone, and levels that don’t clip. That’s most of it.


Bottom line: measure your real evening upload, use 70% of it, prefer clean 720p60 over starved 1080p60, encode on the GPU, cap your game’s frame rate to leave encoder headroom, and record locally at higher quality than you stream.

NewerBGMI Settings and Control Layout That Actually HelpOlderStarting a Gaming Channel: The First Fifty Videos
Subscribe for more
Keep reading

Related guides