English
日本語English简体中文暂无翻译，前往中文首页EspañolSin traducción: ir al inicio en español

If this page is not translated, the link opens that language’s home page.

Discord

Discord Stream Stuttering: Broadcaster and Viewer Checks

For Windows 11/10 desktop Discord game streams or screen sharing that freeze or look like a slideshow. Check whose picture stops before changing settings.

Edited by Gemnao Editorial Team (Japanese)Last checked 2026-10-18
Saved articles →
No account needed. Saved only in this browser.

The short answer

Have the broadcaster compare the actual game and, if possible, two viewers report the same scene. For several affected viewers, compare lower stream quality. If the game itself also slows, inspect broadcaster PC load; if only one viewer fails, prioritize that person’s reception/playback conditions.

Different symptom or still not fixed? Find the next check →

Key facts

Compare the actual scene
Broadcaster’s game versus each viewer’s received video
Lower quality as a test
Try available 720p/30fps controls, then repeat the same motion
One viewer differs
Inspect that viewer before blaming every stream setting

Find your symptom

Start with your symptom. Skip steps that do not apply to your setup.

What you seeWhat to checkGo to
Game stays smooth; two viewers see a slideshowCompare lower live quality with both viewers.Step 1
Game stays smooth; only one viewer freezesConfirm another viewer’s result, then inspect the affected viewer.Step 2
The game itself slows only after streaming startsCompare with streaming stopped and inspect PC load.Step 3
All viewers lose both video and speechInspect incidents and the broadcaster’s connection.Step 2
Only a particular game stutters; desktop capture is smoothCompare application and whole-display capture.Step 4

Fixes, in order

Continue this issue

Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.

Step 1｜Compare lower stream quality

Improvement does not by itself identify the network or PC as the limiting factor.

Time: Compare one change at a time

  1. In a safe repeatable game scene, move the camera sideways. The broadcaster checks game motion and viewers report interruptions in that same motion.
  2. While live in a server voice channel, hover the small picture-in-picture and open its gear → Stream Quality. If absent, inspect the active Screen sharing button near the voice panel.
  3. For a DM stream, use the stream’s downward-arrow menu → Stream Quality. Compare 720p and 30fps within the options available to you, recording the original values.
  4. Repeat the same motion for about 10–20 seconds. Ask whether pauses decreased and whether both viewers agree.
  5. If both improve, keep the useful setting. If unchanged, inspect connections in Step 2; if the game itself is also slow, inspect load in Step 3.

The official guide says browser broadcasters cannot adjust stream quality. These controls concern desktop-app broadcasting.

Results that did not fix the problem help the next reader too.

Step 2｜Separate shared failures from one viewer

Several viewers failing together prioritizes shared conditions; one failing viewer needs their own comparison.

Time: Compare one change at a time

  1. Inspect Discord Status for voice/streaming incidents and wait for relevant recovery before retesting.
  2. If several viewers stop together, the broadcaster pauses Steam downloads, cloud sync or another stream/recording one at a time, then repeats the scene for the same viewers.
  3. If the broadcaster uses Wi-Fi, compare wired networking where available without also changing quality. If both viewers improve, investigate the original connection.
  4. If only one viewer fails, that person closes/rejoins the stream, then restarts Discord and compares the same scene.
  5. If still isolated to that person, they pause their downloads/sync and compare a permitted wired/alternate connection if available. Keep other viewers’ successful results in the record.

Record who watched the same scene and on which connection; a speed-test number alone is not a playback diagnosis. Account for data limits and mark unavailable comparisons untested.

Results that did not fix the problem help the next reader too.

Step 3｜If the game also slows, inspect broadcaster load

Do not focus exclusively on viewer networks when local game motion deteriorates.

Time: Compare one change at a time

  1. Compare the same game scene before and during sharing. Ask whether the viewer sees pauses corresponding to the broadcaster’s local pauses.
  2. Open Ctrl+Shift+Esc → Performance and inspect CPU, memory and GPU for sustained changes while streaming. Processes identifies busy apps.
  3. Save work, then stop an unneeded recorder or close unused browser tabs one at a time. Compare both local game and received video again.
  4. If unchanged, record and lower the game’s FPS cap or graphics quality one level. If the game improves but received video still pauses, return to Steps 1–2.

Results that did not fix the problem help the next reader too.

Step 4｜Compare capture method and video processing

For game-specific stutter, retain the same scene and viewer while changing capture.

Time: Compare one change at a time

  1. Compare the game’s window and whole display; hide private windows/notifications before display sharing. If supported, compare borderless mode too, recording the original mode.
  2. Record Hardware Acceleration under User Settings → Voice & Video → Video, switch its state, restart Discord and compare the same scene.
  3. Restore it if unchanged or worse. Inspect Discord/Windows updates and use the GPU/PC manufacturer’s official driver instructions if a driver update is needed.

Labels and placement can vary. Skip absent controls rather than changing a guessed experimental option, and preserve original settings.

Results that did not fix the problem help the next reader too.

Avoid

  • Do not judge viewers’ reception from the broadcaster’s preview alone.
  • Do not change quality, network and graphics settings together or expose private information in display capture.

Important cautions

  • If unresolved, compare the same game window, whole display and another available game with the same viewers. Record whether local game motion also stopped, affected viewers, quality comparison, network/load and time.
  • One viewer is usable if two are unavailable; record that limitation rather than treating an unperformed comparison as success.

FAQ

Where are the live 720p/30fps settings?

For a server stream, hover the broadcaster’s PiP → gear → Stream Quality, or inspect the active Screen button. For a DM stream use the downward-arrow menu → Stream Quality.

Does a smooth local preview prove viewers see smooth video?

No. Compare the game itself with each viewer’s received picture of the same scene.

Does one stuttering viewer prove the broadcaster is at fault?

No. Confirm another viewer can see the same scene, then compare the affected person’s rejoin, app restart and available connection alternatives.

Why are quality controls missing?

The official guide says browser broadcasting cannot adjust quality. Confirm you use the desktop app, then inspect the appropriate live-stream menu.

Sources

English adaptation preserving the Japanese article’s steps, diagnostic branches, precautions and official references. Numerical comparisons are illustrative, not measured results or universal thresholds. Record original settings and restore unhelpful changes.

Discord: Go Live and live quality controlsDiscord: streaming settingsDiscord: voice and video troubleshootingDiscord Status: service incidentsDiscordJapanese version of this page