Skip to content
Download

GuidesPage 04 of 14

Troubleshooting

Diagnose sign-in, launch, stream quality, video, audio, input, and native streaming problems

GitHubOpen in GitHub9 sections
On this page9 sections

Most OpenNOW problems fall into one of four layers: authentication, the GeForce NOW session, the local native stream path, or input. Start with the quick checks below, then use the section that matches what you see.

Check NVIDIA first

OpenNOW depends on NVIDIA's login, catalog, CloudMatch, queue, and streaming services. If the official GeForce NOW client is also failing, wait for the service to recover before changing local settings.

Five-minute check#

Restart OpenNOW. This clears the active session UI and forces the app to rebuild local process state.

Use conservative stream settings. Choose H.264, 1920×1080, 60 FPS, and a lower bitrate. If that works, restore one setting at a time to find the unsupported codec, profile, or bandwidth threshold.

Leave video backend on Auto. In Settings → Stream → Advanced → Video backend, keep Auto (recommended) unless you are deliberately isolating a GPU or API problem.

Try another game and region. One title can have a membership or storefront restriction, while one region can have queue or server-capacity trouble.

Capture diagnostics before resetting data. Use Settings → About & support → Copy diagnostics → Export, and note the exact message, game, provider, region, app version, and steps that reproduce the problem.

Choose the symptom#

Sign-in and account#

Launch, queue, and session#

SymptomWhat it usually meansWhat to try
Upgrade or insufficient playability messageNVIDIA reports that the selected game or stream profile requires a higher membership tierChoose an entitled game/profile or change the GeForce NOW membership
Active session conflictNVIDIA believes another stream is still activeStop the other session, wait for cleanup, then launch again
Queue does not advanceThe selected region is at capacity, the queue request expired, or service state changedLeave and relaunch; choose another region, or turn on Settings → Network → Free-tier queue selector to compare queues before launch (PrintedWaste data)
Launch stalls on “Configuring your cloud gaming rig” or “Connected. Waiting for the first video frame.”Cloud rig setup or the native first-frame handoff is still in progressWait for the named step to finish; cancel once and relaunch if it never advances
Game opens from the public catalog but not the libraryThe required store account is not linked or syncedLink or resync the store under Settings → Account, then refresh
Favorites look incompleteGeForce NOW favorites coverage can be partial; home pins are separateRefresh the library; re-add the favorite if needed
Wrong storefront launches for a multi-store titleThe selected platform variant does not match the owned copyBefore launch, pick the store you own the game on (Steam, Xbox, Epic, and so on) in the game's details
Sign-in or catalog requests fail only with the API proxy onThe address in Settings → Network → Proxy address is unreachable or wrongTurn off Use proxy or fix the address. The proxy applies to API calls only; the stream always connects directly
One game fails while others launchThe failure is likely title, storefront, SKU, or membership specificRecord the exact game and storefront before reporting it
STREAM ENDED notice with an Error code: 0x… lineThe cloud server closed the session instead of you. dev shows the code it returned; a session that ends normally shows no noticeSelect Copy (X in console mode) and include the code and the game name in your report, then start the session again from the game

Do not repeatedly relaunch while an earlier CloudMatch session is still being released. Stop the session once, wait briefly, then make one clean attempt.

In the app · Console mode › Launch › In queue
OpenNOW console launch stage while queued for Cyberpunk 2077 on Steam in EU Central: You are in line, queue position 37 that updates when GeForce NOW reports it, the steps Session requested, Waiting for a rig, Setting up the rig and Connecting the stream, the time waited on this device and a Leave queue hint.
In the app · Console mode › Launch › Connecting
OpenNOW console launch stage after the rig is ready: Connecting to your game, waiting for the first video frame, with the rig card (RTX 4080, EU Central, 1440p at 120 FPS requested), the first three launch steps done, Connecting the stream in progress and a Cancel session hint.

Stream quality and video#

Start with H.264 · 1920×1080 · 60 FPS and a bitrate your connection can sustain. Prefer 8-bit, YUV 4:2:0 color quality. The Settings UI labels 4:4:4 profiles as Coming soon; they do not work yet. H.265, AV1, 10-bit 4:2:0, high frame rates, and ultrawide profiles still require compatible subscription profiles plus local GPU, driver, and display support. Codec Auto may select AV1 only when the probed platform/stream limits allow it.

SymptomIsolation stepNext action
Black screen with audioSwitch to H.264 and 8-bit 4:2:0, then restart the streamUpdate the GPU driver; leave the video backend on Auto unless diagnosing
Linux: no usable video backendNo hardware decoder is available. On Linux and macOS, Auto never falls back to software decodingOn Linux, choose Software (CPU) under Settings → Stream → Advanced → Video backend. It accepts 8-bit 4:2:0 SDR only and uses more CPU. Check the host VA-API driver for hardware decoding
Regular stutter or rising latencyLower bitrate first, then FPS; try enabling Save bandwidth for a steadier frame rate on constrained linksUse wired Ethernet or stronger Wi-Fi; stop competing traffic and try a closer region
Blocky image but stable inputIncrease bitrate graduallyKeep the highest value that remains stable rather than the maximum available value
Colors look wrongReturn color quality to 8-bit 4:2:0Avoid 4:4:4 profiles (Coming soon); re-enable 10-bit 4:2:0 separately if needed
One-time “stream color format changed” noticeThe negotiated/output format differed from the requested profilePlayback continues; keep 4:2:0 unless you intentionally selected another supported profile
Stutter after enabling 10-bit10-bit color can stutter on some systems; Settings warns when you select itSwitch back to 8-bit. If you dismissed the warning for good, set suppressTenBitWarning back to false in settings.json to see it again
H.265 unavailable on WindowsMicrosoft's HEVC Video Extensions may be missingOpen the HEVC help in Settings and install the free Store extension first (paid offer if needed). Restart OpenNOW. GPU hardware HEVC decode is still required
High GPU use with upscalingMetalFX (macOS) or FSR 1 (Windows/Linux) costs extra GPU timeTurn upscaling Off, or lower stream resolution/FPS if the local GPU is saturated
Flatpak cannot auto-updateFlatpak builds disable the in-app self-updaterUpdate with flatpak update io.github.opencloudgaming.OpenNOW from a Flatpak remote, or rebuild/reinstall a local .flatpak bundle
In-app update fails or does not installInstallation needs your confirmation and no active or recovering stream. Portable Windows installs on FAT or exFAT drives cannot be replaced in place. Builds older than v1.0.1 do not trust the update keyEnd the stream and retry Settings → Updates → Check for updates; note the failure message the updater shows. Move a portable install to an NTFS drive, or update it manually. Install v1.0.3 manually once if you come from v1.0.0
Entire app window is black vs only the video surfaceNote which one you see before changing settingsExport diagnostics and include both native-streamer.log and qt-native.log

On desktop, Check for updates is on Settings → Updates, not under About & support.

Change one variable at a time

Changing codec, resolution, FPS, bitrate, backend, and region together makes the result impossible to interpret. Begin with the conservative profile, then restore one option per stream.

In the app · Ctrl+G menu
OpenNOW Ctrl+G in-stream drawer during a session: FPS, output resolution, bitrate and the NVST · H265 · D3D11VA connection line, Back to game, quick toggles for microphone, Anti-AFK, stats overlay and fullscreen with their shortcuts, then Controllers, Invite a friend, Switch to console mode and End session, with the F3 stats bar (fps, latency, UDP receive rate, codec) in the corner.
In the app · Console mode › Guide (Ctrl+G)
OpenNOW console Guide (Ctrl+G, or the PS or Xbox button) over a live Forza Horizon 5 stream: the session line (2560×1440, 120 FPS, AV1, RTX 4080), Resume game focused, quick actions for screenshot, record, microphone, stats overlay, fullscreen and Anti-AFK, then Controllers & co-op, Shortcuts & help and End session, with a Screenshot saved toast.

Input, controller, and microphone#

  • Mouse does not control the game: click the stream to acquire pointer lock. Use the configured release shortcut (default F8) before interacting with OpenNOW again.
  • Keyboard mapping is wrong: set Settings → Controls → Keyboard layout to match your physical keyboard, then start a new session. The layout applies to the next session, not to an active stream. Linux gameplay keys follow physical positions (including German/Swedish OEM fixes); see Input.
  • Controller is not detected: connect it before launching, verify the operating system sees it, then restart OpenNOW. Close remapping software temporarily if it creates duplicate virtual controllers. An exclusive controller selection is preserved across disconnects when possible; the Settings label shows Selected controller disconnected until that pad returns.
  • Console mode is hard to leave or keeps starting: move the mouse or press a key; Settings → Console mode → Leave console mode on keyboard or mouse input (leaveConsoleOnPointer) is on by default. Turn off Start in console mode and Enter console mode when a gamepad is the only input if the app keeps opening in console mode. Console mode changes the browsing UI but does not change NVIDIA account state.
  • Clipboard paste does nothing: turn on Settings → Controls → Clipboard paste (default off), make sure keyboard input is active in the stream, then press Ctrl+V (Command+V on macOS). Each paste sends up to 64 KiB of text. There is no automatic clipboard sync.
  • Microphone is silent: grant microphone permission to OpenNOW at the operating-system level, set Settings → Audio → Microphone to Open microphone (default Disabled), and reconnect the stream so capture is negotiated again. If Settings says microphone capture is unavailable in this build, that build cannot capture audio.
In the app · Console mode › Guide › Controllers & co-op
OpenNOW console Guide › Controllers & co-op over the stream: P1 DualSense Wireless Controller and P2 Xbox Wireless Controller connected with battery levels, P3 and P4 waiting for a controller to connect or press a button, and a note that remapping and controller settings live in Settings › Input & controllers.

See Input and Controls for shortcuts, pointer behavior, and microphone modes.

Native stream path#

The Qt desktop app streams through the in-process native streamer over NVST. There is no browser streamer to fall back to.

To isolate a transport problem, set Settings → Network → WebRTC compatibility mode to NVST or WebRTC and start a new session. Automatic uses WebRTC for signed-in alliance-partner accounts and NVST for NVIDIA accounts. WebRTC needs direct UDP connectivity and has no microphone or clipboard text.

  1. Keep the video backend on Auto unless isolating a specific API.
  2. Restart the stream after changing codec, resolution, color quality, or backend.
  3. On black-screen reports, distinguish an entirely black application window from a stream-only black video surface.
  4. Use Settings → About & support → Copy diagnostics → Export. OpenNOW saves a redacted opennow-diagnostics-<timestamp>.txt file in its diagnostics directory and opens it. The report includes the current and previous run logs and bounded tails of native-streamer.log and qt-native.log. Secrets, URLs, tokens, e-mail addresses, and local user paths are redacted.
  5. Include GPU, driver version, platform package name (OpenNOW-Qt-…), and whether the same account/game works in the official GeForce NOW client.

Use Native Streamer for packaging, GPU presentation, and protocol details.

Reset local state#

Local settings and authentication are separate. Close OpenNOW before moving or deleting either.

DataLocation
Settings%APPDATA%\OpenNOW\settings.json (Windows), ~/Library/Application Support/OpenNOW/settings.json (macOS), $XDG_CONFIG_HOME/OpenNOW/settings.json or ~/.config/OpenNOW/settings.json (Linux), or $OPENNOW_DATA_DIR/settings.json. The previous valid copy is kept as settings.json.bak
Accounts and sign-in tokensaccounts.json in the data directory lists saved accounts without tokens. Tokens are kept in the OS credential store; on Windows they are encrypted files in secure-sessions/ with the key in Credential Manager. If the credential store is unavailable, tokens are saved unencrypted in fallback-sessions/. Legacy auth-state.json and sessions/*.json are migrated and removed
Profile PINsconsole-profiles-qt.json in the data directory (scrypt hashes, local only)
Diagnosticsdiagnostics/ in the data directory: current.log and previous.log (core), qt-native.log, native-streamer.log, and exported opennow-diagnostics-<timestamp>.txt reports
Caches and updatesartwork-cache/, store-cache-v2/, and updates/ (downloaded update packages) in the data directory
ScreenshotsOpenNOW/Screenshots/ in the system Pictures folder, or $OPENNOW_PICTURES_DIR/OpenNOW/Screenshots/
RecordingsOpenNOW/Recordings/ in the system Pictures folder, or $OPENNOW_PICTURES_DIR/OpenNOW/Recordings/
  • Move settings.json aside to reset preferences without deleting the saved sign-in.
  • Move auth/session files aside to reset the account session without resetting stream preferences.
  • Back up files before destructive troubleshooting if you need to inspect or restore them later.
  • Screenshots and recordings live in their own media directories; resetting settings or authentication does not require deleting captures.

Collect a useful report#

On desktop, prefer Settings → About & support → Copy diagnostics → Export. When showSessionReport is on (default), the Session report after a stream shows the transport, media backend, first-frame time, recoveries, and drop counts; Open diagnostics on that report shows the redacted recovery timeline.

If you file outside the app, include the following in a GitHub issue or the OpenNOW Discord:

  • OpenNOW version and whether it is a stable, nightly, or source build (OpenNOW-Qt-… package name when applicable)
  • Operating system, architecture, GPU, and GPU-driver version
  • Provider, GeForce NOW membership tier, selected region, and game/storefront when relevant
  • Codec, resolution, FPS, bitrate, color quality, and native video backend preference
  • Exact error text and a short, repeatable sequence of steps
  • Whether the same account and game work in the official GeForce NOW client
  • A diagnostics export, screenshot, or session summary with tokens, email addresses, device codes, and other personal data removed

Do not post credentials

Never attach session files, access tokens, refresh tokens, QR device codes, or unredacted account details to a public issue.

Switch-specific crashes, installation failures, and decoder problems belong in the OpenNOW-Switch issue tracker. Include whether Homebrew Menu was opened in applet mode or full-memory application mode.