Linux players spent years streaming GeForce NOW through a browser tab and hoping the mouse cursor behaved. That changed on August 13, 2026, when NVIDIA announced that its native Linux app had graduated from beta, with support for Ubuntu 24.04 and later and a new Flatpak repository for installs and updates. If you want GeForce NOW on Linux without paying a cent, you can now do it with a proper desktop app.
The timing is good. NVIDIA put Call of Duty: Modern Warfare 4 on the service at launch on October 22, 2026, and it pitches the Ultimate tier as RTX 5080-class streaming with ray tracing for the campaign. You do not need Ultimate to follow this guide. The free membership is enough to install the app, link your stores, wire up a controller and tune your network, and every step here works the same way if you upgrade later.
This tutorial walks through 13 steps on Ubuntu, from checking your release to a one-file setup script you can rerun on any new machine. It covers the driver and Flatpak plumbing the app depends on, the Wayland versus Xorg question, and a browser fallback for the day the app misbehaves. If you only care about the Windows-side basics of the free plan, our GeForce NOW free tier and Steam walkthrough covers that ground. Here, the focus is Linux.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What the Native GeForce NOW Linux App Changes in 2026
Before August 2026, the Linux story was a patchwork. NVIDIA shipped a Steam Deck specific app in May 2025, which is not the same thing as a general Linux app. The native desktop client reportedly entered beta on January 29, 2026, according to GamingOnLinux’s coverage of the launch, and then spent roughly six and a half months collecting community feedback. The August 13 announcement says the final release focuses on performance, stability and polish.
Three details from NVIDIA’s announcement matter for this tutorial. First, the supported target is Ubuntu 24.04 and later. Second, installs and future updates flow through a new Flatpak repository that NVIDIA runs itself. Third, the cloud does the rendering, so your local hardware only has to decode video and send input. A ten-year-old laptop with a modest GPU can look like a gaming rig as long as it can decode H.264 or H.265 and sits on a decent connection.
Two other changes landed around the same time. On August 13, NVIDIA also said it had optimized DLSS Frame Generation in the cloud to cut latency, with the biggest gains at 60 or 120 frames per second in 1440p and 4K, plus server-side tweaks for CPU-heavy games for Performance members. A week later, on August 20, NVIDIA announced Firefox browser support, which gives Linux users a second route when the native app is not an option.
One more recent update deserves a caution. NVIDIA’s October 15 announcement of DLSS 4.5 controls names the apps for Windows, macOS, ChromeOS and SteamOS. It does not name the Linux app. Do not assume the new quality panel appears in your Flatpak build. Step 11 shows how to check what your install actually offers.
Prerequisites and Versions Before You Start
The list is short, and most of it is already on your machine. You need a 64-bit Ubuntu install, a GPU that can decode modern video, a wired or strong Wi-Fi connection, and a free NVIDIA account. Budget about 35 minutes if your driver is already current. Add 15 more if you need to install or reboot into a new driver.
| Requirement | What to use | How to check |
|---|---|---|
| Operating system | Ubuntu 24.04 LTS or later (26.04 LTS “Resolute Raccoon” or 26.10 “Stonking Stingray”) | lsb_release -ds |
| Packaging | Flatpak, from NVIDIA’s own repository | flatpak --version |
| GPU decode | Any GPU with H.264 and H.265 hardware decode | vainfo or nvidia-smi |
| Display server | Xorg on NVIDIA GPUs, Wayland on AMD and Intel GPUs | echo $XDG_SESSION_TYPE |
| Account | Free NVIDIA account | Sign-in screen in the app |
| Game libraries | Steam, Epic Games Store, Ubisoft Connect, Xbox PC Game Pass, GOG or EA | Accounts you already own |
| Network | Ethernet preferred, 5 GHz Wi-Fi acceptable | iw dev and ping |
The display server row comes straight from NVIDIA’s system requirements. Ubuntu itself costs nothing, and Ubuntu 26.10 is the newest release, with GNOME 51 and Linux kernel 7.3. NVIDIA’s wording is “24.04 and later,” so 26.04 LTS and 26.10 fall inside that promise. The 26.10 release is supported until July 2027, which makes the LTS releases the calmer choice for a machine you do not want to babysit.
Reports of NVIDIA’s system requirements page, published October 8 and updated October 13, list a dual-core 2.0 GHz or faster CPU, 4 GB of RAM, NVIDIA driver 580.126.07 or newer on NVIDIA GPUs, and Mesa 24.2.8 recommended on Intel and AMD GPUs. Treat those as the floor and check the live page before you buy hardware. If you are picking a plan rather than just testing, the general GeForce NOW setup guide explains the membership tiers and billing choices.
Free vs Paid on Linux: What You Actually Get
NVIDIA lists three membership names today: Free, Performance and Ultimate. It also sells day passes, and it says the day-pass cost can be applied toward a first monthly membership. That makes a day pass a cheap way to test the premium tiers on your own Linux box before committing. The free plan does not expire, and it does not require a card.
Here is the catch. NVIDIA’s official pages did not give me current numbers I could confirm for the free tier’s queue behavior or session length when I checked on October 22, 2026. Third-party trackers describe waiting lines at busy hours and capped sessions, but those figures change and I will not print one as fact. Your own stopwatch is a better source, and Step 6 shows how to measure it. The official FAQ is the place to confirm the rules before you plan a long session.
| Capability | Free | Performance | Ultimate |
|---|---|---|---|
| Costs money | No | Yes | Yes |
| Stream PC games you own on supported stores | Yes | Yes | Yes |
| Install-to-Play library (2,000+ extra games) | No | Yes | Yes |
| RTX 5080-class cloud rig | No | No | Yes |
| Day pass credit toward first month | Upgrade path | Applies | Applies |
The Install-to-Play row comes from NVIDIA’s own membership page, which says the feature is available exclusively for Performance and Ultimate members. For the Linux app specifically, NVIDIA reportedly states that a Premium membership is required for 5K, 4K and ultrawide streaming, NVIDIA RTX effects, and 120, 240 and 360 FPS streaming. In a browser, the same page reportedly lists Ultimate as the requirement for QHD and 120 FPS. In short, free members should expect standard resolutions and standard frame rates.
One purchasing change from October 22 does not touch Linux but shows where the service is heading. Existing supported Fire TV Stick users can now buy one-month Performance or Ultimate memberships through Amazon billing, as UrGameTips reported. If you are weighing GeForce NOW against Microsoft’s service before you commit, our GeForce NOW vs Xbox Cloud Gaming comparison lays out the trade-offs.
How Cloud Streaming Reaches Your Linux Desktop
A little theory saves hours of guessing later. When you press a key, the app sends that input to a GeForce NOW server. The server runs the game, encodes the frame as video, and streams it back. Your PC decodes the video and shows it. Every troubleshooting problem in this guide lives in one of three places: the decode on your machine, the network between you and the data center, or the server side that you cannot touch.
That split explains why the requirements look so odd. The game needs no local GPU power, yet NVIDIA still asks for a modern H.264 and H.265 capable GPU and a current driver. Decode is the one heavy job your hardware keeps. It also explains why upgrading the cloud tier changes picture quality and frame rate while leaving your input lag mostly alone. Input lag depends on the round trip, and distance to the server matters more than your plan.
Linux adds two wrinkles on top. First, the Flatpak sandbox sits between the app and your devices, so controllers, audio and GPU libraries all pass through a permission layer. Second, the display server decides how the decoded frames reach the screen. Wayland and Xorg handle that differently, which is why NVIDIA splits its guidance by GPU vendor. Keep those two layers in mind and most strange behavior stops being strange.
Step 1: Check Your Ubuntu Release and Session Type
Start by confirming what you are running. Three facts decide most of the problems you will hit later: the Ubuntu release, the kernel, and whether your desktop session runs on Wayland or Xorg. Open a terminal and run the commands below.
lsb_release -ds
uname -r
echo "Session: $XDG_SESSION_TYPE"
echo "Desktop: $XDG_CURRENT_DESKTOP"Example output on a fresh install looks like the block below. Your release string and kernel will differ.
Ubuntu 26.04 LTS
7.x.x-generic
Session: wayland
Desktop: ubuntu:GNOMEIf you see anything older than Ubuntu 24.04, stop and upgrade first. The official app targets 24.04 and later, and Flatpak runtimes on older releases lag behind. Derivatives such as Linux Mint or Pop!_OS may work because the app ships as a Flatpak, but NVIDIA only promises Ubuntu, so expect to debug alone on anything else. If you run SteamOS on a handheld, skip this guide and use our GeForce NOW on Steam Deck setup instead, since that route has its own app.
Write down the session type. NVIDIA specifies Xorg for NVIDIA GPUs and Wayland for AMD and Intel GPUs. If you own an NVIDIA card and the output says wayland, you have found your first likely problem, and Step 11 fixes it.
Step 2: Install or Update Your GPU Driver
The cloud renders the game, but your local GPU still decodes the video stream. A stale driver is the most common reason a Linux stream shows a black window or stutters. The steps differ by vendor.
NVIDIA GPUs. Let Ubuntu pick the recommended proprietary driver, install it, and reboot.
ubuntu-drivers devices
sudo ubuntu-drivers install
sudo rebootAfter the reboot, confirm the driver version. Reports of NVIDIA’s requirements put the minimum at 580.126.07, so compare your number against that.
nvidia-smi --query-gpu=name,driver_version --format=csv,noheaderIntel and AMD GPUs. These use Mesa, which Ubuntu updates through normal package upgrades. Install the diagnostic tools and read your versions.
sudo apt update && sudo apt upgrade -y
sudo apt install -y mesa-utils vainfo
glxinfo -B | grep -E "OpenGL (renderer|version)"
vainfo 2>&1 | grep -E "H264|HEVC"You want to see at least one H.264 line and one HEVC line in the vainfo output, each tagged with a decode entrypoint such as VAEntrypointVLD. If neither shows up, the app can fall back to software decoding on some setups, and your CPU fan will tell you about it within five minutes. Reports put the Mesa recommendation at 24.2.8, which any current Ubuntu LTS exceeds out of the box.
Step 3: Install Flatpak
Ubuntu does not ship Flatpak by default. The native app depends on it, so install it before anything else. The package is in the standard repositories.
sudo apt update
sudo apt install -y flatpak
flatpak --versionYou should see a line such as Flatpak 1.x.x. If you installed Flatpak just now, log out and back in once. Flatpak adds its export directories to your environment through a login script, and apps will not appear in the launcher until the session reloads. A full reboot also works, and you may already be due for one after the driver install.
Resist the urge to add Flathub for this app. NVIDIA distributes its build directly and, according to the January beta reports, had no plan to publish on Flathub. Any Flathub or AUR package with GeForce NOW in the name is a community wrapper, not the official client.
Step 4: Add NVIDIA’s Flatpak Remote
The remote is the address Flatpak pulls the app and its updates from. NVIDIA’s download page publishes the exact command, and the Arch Linux wiki documents the same repository file. Compare what you type against the download page, because repository addresses can move between releases.
sudo flatpak remote-add --if-not-exists GeForceNOW \
https://international.download.nvidia.com/GFNLinux/flatpak/geforcenow.flatpakrepo
flatpak remotesThe second command should list GeForceNOW next to any other remotes. Then ask the remote what it actually offers. This is the safest way to confirm the application ID before you install, and it protects you if NVIDIA renames the package.
flatpak remote-ls GeForceNOW --appExample output:
Name Application ID Version Branch
GeForce NOW com.nvidia.geforcenow x.x.x stableIf the list is empty or the command errors out, jump to the troubleshooting section. Corporate proxies and DNS filters cause most remote failures.
Step 5: Install and Launch the GeForce NOW App
With the remote in place, installation is one command. Flatpak will also pull in the runtime and, on NVIDIA systems, a GL extension matching your driver, so expect a download of several hundred megabytes on a clean machine.
sudo flatpak install GeForceNOW com.nvidia.geforcenow
flatpak run com.nvidia.geforcenowAnswer y when Flatpak asks to confirm the runtime installs. The first launch takes longer than later ones because the app builds its caches. After that, GeForce NOW should appear in your application grid like any native program.
Because the app runs inside a Flatpak sandbox, its settings and cache live under ~/.var/app/com.nvidia.geforcenow instead of your usual config folders. That is useful to know in two situations. When you want to reset the app to a clean state, delete that folder. When you want to see logs, look inside it first.
ls ~/.var/app/com.nvidia.geforcenow
flatpak info com.nvidia.geforcenowStep 6: Sign In and Measure Your Free-Tier Limits
Launch the app and sign in with your NVIDIA account. If you do not have one, create it with an email address and verify it. No card is required for the free plan. Once you land on the home screen, the app should show your membership name. If it says anything other than Free, you are looking at a trial or day pass.
This is the moment to learn your plan’s real limits, because NVIDIA’s pages did not give me figures I could verify today. Start a game, note the clock time, and write down three things: how long you waited in any line, whether an advertisement played before the session, and when the session ended. Do this twice, once at a quiet hour and once on a weekday evening. Queue behavior varies a lot with demand.
- Record the queue wait and the session length in a text file, with the date and your region.
- Check NVIDIA’s official FAQ for the current rules, since they can change without a client update.
- If waits are long, test again at a different hour before you decide the free tier is not for you.
You will feed the session length into the timer script in Step 13, so the notes are not busywork. They also give you hard data if you later decide a day pass or a monthly plan is worth the money.
Step 7: Link Steam, Epic and Your Other Game Stores
GeForce NOW does not hand you a library. It streams games you already own, so this step is where the free plan starts to feel useful. NVIDIA lists Steam, Epic Games Store, Ubisoft Connect, Xbox PC Game Pass, GOG and EA as supported sources, with availability varying by title.
The flow is the same on every platform. Search for a game you own in the app. If GeForce NOW supports it, the title appears. Pick it, and the app asks you to sign in to the store that holds your license. An older Trusted Reviews review of the Ultimate tier, written about the Windows client, describes the same library-linking flow and found it straightforward. The Linux app follows that pattern.
Keep your phone nearby. Steam Guard, Epic’s email codes and Ubisoft’s two-factor prompts all fire when a store sees a login from a new cloud machine. Approve them, and the store should remember the link on later sessions. Cloud saves from the store sync automatically in most titles, which means your progress follows you if you play the same game locally on another machine.
Do the linking while you are still in your first session, not in the middle of a game. Each store login takes a minute or two, and on a time-limited plan that is time you want to spend playing. Link one store, test one game, then add the others.
Step 8: Pick Games That Work Well on a Free Plan
Not every game suits a short session. Open-world RPGs that need hours to get going waste a free window. Match your library to the time you have. Short-session games shine: roguelikes, racing, fighting, extraction shooters, and anything with quick matches. Games with long installs or heavy downloads are a poor fit when the clock runs.
NVIDIA’s library keeps growing. The company announced 25 games for October 2026, Gears of War: E-Day arrived on October 8, and Call of Duty: Modern Warfare 4 launched on October 22. Remember that you must own a game on a supported store to play it, and the free tier does not include the Install-to-Play catalog, which is reserved for Performance and Ultimate.
Free-to-play titles are the cheapest way to fill the plan. Browse the in-app library for free games on supported stores and add a few to your account, since a free-to-play game costs nothing to own. Microsoft’s cloud service also has a route for select free-to-play games, according to third-party trackers, and our Xbox Cloud Gaming free setup for Mac shows the browser flow that works on Linux too.
Step 9: Set Up Controllers and Input
Keyboard and mouse work out of the box. Gamepads depend on the Flatpak sandbox letting the app see your input devices. Pair your controller, then test it outside the app first so you know whether the problem is the pad or the sandbox.
sudo apt install -y evtest jstest-gtk bluez
bluetoothctl
# inside bluetoothctl:
# power on
# scan on
# pair AA:BB:CC:DD:EE:FF
# trust AA:BB:CC:DD:EE:FF
# connect AA:BB:CC:DD:EE:FF
sudo evtestChoose your controller from the evtest menu and press buttons. If events scroll by, the system sees the pad. Now launch the app and check whether it responds. If the pad works in evtest but not in GeForce NOW, widen the sandbox for this one app. This grants broader device access than the default, so use it only if you need it.
flatpak info --show-permissions com.nvidia.geforcenow
flatpak override --user --device=all com.nvidia.geforcenowRestart the app after the override. To undo it later, run flatpak override --user --reset com.nvidia.geforcenow. Wired USB pads are the least fussy option, and Bluetooth adds a little latency on top of the stream, which is worth avoiding in fast games.
Step 10: Tune Your Network for Low-Latency Streaming
Cloud gaming is a network problem first. A fast connection with jitter feels worse than a slower, steady one. Use Ethernet if you can. If you must use Wi-Fi, check the band and the signal first.
iw dev
iw dev wlp3s0 link
ping -c 20 -i 0.2 -q 1.1.1.1Replace wlp3s0 with the interface name from iw dev. The link output shows the connected frequency. A value starting with 5 or 6 means a 5 GHz or 6 GHz band, which is what you want. A 2.4 GHz value means congestion is likely. The ping summary at the bottom shows packet loss and the spread between minimum and maximum round-trip time. Aim for zero loss and a tight spread.
Wi-Fi power saving is a quiet villain on Linux laptops. It lets the radio nap between packets, which shows up as stutter every few seconds. Turn it off for the current session, then make it permanent with NetworkManager.
sudo iw dev wlp3s0 set power_save off
nmcli connection show
sudo nmcli connection modify "YOUR_WIFI_NAME" 802-11-wireless.powersave 2
sudo nmcli connection up "YOUR_WIFI_NAME"The value 2 disables power saving for that connection. Next, test under load. Start a large download in one terminal and run the ping test in another. If latency balloons while the download runs, your router has a buffer problem, and a smart queue setting on the router will help more than any change on the PC. Our multi-platform free cloud gaming setup covers router QoS in detail.
| Symptom | Likely cause | First fix |
|---|---|---|
| Stutter every few seconds | Wi-Fi power saving | Disable it with nmcli |
| Image smears during motion | Congested band or distant access point | Move to 5 GHz or use Ethernet |
| Lag spikes only when others stream | Router buffer bloat | Enable smart queue management |
| Slow sign-in or store login | DNS or captive filtering | Switch DNS servers or drop the VPN |
| Long waits for a session | Free-tier demand | Try a different hour or a day pass |
Step 11: Fix Wayland and Xorg Display Quirks
NVIDIA’s requirements pair its own GPUs with Xorg and AMD or Intel GPUs with Wayland. If you have an NVIDIA card and your session reports Wayland, switch to Xorg before you troubleshoot anything else. Log out, click your username on the login screen, find the gear icon near the password box, and pick the Xorg option. Then log in and confirm.
echo "$XDG_SESSION_TYPE"
# expected on NVIDIA GPUs: x11
# expected on AMD or Intel GPUs: waylandIf your login screen offers no Xorg session on a newer release, stay on the LTS version rather than fighting it. That is a good reason to prefer Ubuntu 24.04 or 26.04 LTS for a dedicated streaming machine. Fractional scaling is another trap. If text looks blurry or the picture sits in a corner, set your display scale to 100 percent while you test, then raise it once streaming is stable.
Now open the app’s settings and look at what it offers. Resolution and frame rate options depend on your plan and display. As noted earlier, the DLSS 4.5 controls announced on October 15 list other platforms, so do not be surprised if your build lacks them. Premium-only settings such as 120 FPS or 4K streaming should be locked or absent on the free plan, which is expected behavior and not a bug.
Step 12: Set Up the Browser Fallback With Firefox
Every serious Linux setup needs a plan B. A browser route lets you keep playing while a Flatpak update is broken or a driver mismatch is unresolved. NVIDIA directs browser users to play.geforcenow.com, and its August 20 announcement added Firefox support to the list. Chromium-based browsers worked before that, according to the Arch Linux wiki, so you have two options.
# Firefox, in its own window
firefox --new-window https://play.geforcenow.com
# Chromium or Chrome in app mode, no tabs or address bar
chromium --app=https://play.geforcenow.comUse a dedicated browser profile for this. Extensions, ad blockers and tracking protection can interfere with the stream. Older Arch wiki notes mention an invisible cursor in Firefox on some setups, which NVIDIA’s newer support may have resolved. If it still happens to you, try the Chromium route. Expect browser sessions to cap at lower quality than the app, and note that NVIDIA reportedly lists Ultimate as the requirement for QHD at 120 FPS in a browser.
This route also works on machines you cannot install Flatpaks on, such as locked-down work laptops. Our guide to free cloud gaming on a Chromebook, smart TV or old laptop covers other browser-first devices.
Step 13: Script the Whole Setup as a Complete Project
The final step bundles everything into one script you can rerun on a new install. It checks the Ubuntu release, reads the session type, validates the NVIDIA driver, installs Flatpak, adds the remote, installs or updates the app, and prints a quick network summary. Save it as gfn-linux-setup.sh.
#!/usr/bin/env bash
set -euo pipefail
REMOTE_NAME="GeForceNOW"
REMOTE_URL="https://international.download.nvidia.com/GFNLinux/flatpak/geforcenow.flatpakrepo"
APP_ID="com.nvidia.geforcenow"
MIN_NVIDIA_DRIVER="580.126.07"
log() { printf '[gfn] %s\n' "$*"; }
fail() { printf '[gfn] ERROR: %s\n' "$*" >&2; exit 1; }
check_os() {
. /etc/os-release
[[ "${ID}" == "ubuntu" ]] || fail "Ubuntu expected, found ${ID}"
local major="${VERSION_ID%%.*}"
(( major >= 24 )) || fail "Ubuntu 24.04 or later required, found ${VERSION_ID}"
log "Ubuntu ${VERSION_ID} OK"
}
check_session() {
log "Session type: ${XDG_SESSION_TYPE:-unknown}"
if command -v nvidia-smi >/dev/null 2>&1 && [[ "${XDG_SESSION_TYPE:-}" == "wayland" ]]; then
log "WARNING: NVIDIA GPU on Wayland. NVIDIA specifies Xorg for NVIDIA GPUs."
fi
}
check_gpu() {
if command -v nvidia-smi >/dev/null 2>&1; then
local v
v="$(nvidia-smi --query-gpu=driver_version --format=csv,noheader | head -n1)"
if [[ "$(printf '%s\n%s\n' "$MIN_NVIDIA_DRIVER" "$v" | sort -V | head -n1)" != "$MIN_NVIDIA_DRIVER" ]]; then
fail "NVIDIA driver ${v} is older than ${MIN_NVIDIA_DRIVER}"
fi
log "NVIDIA driver ${v} OK"
else
log "No nvidia-smi found. Assuming Intel or AMD. Check Mesa with: glxinfo -B"
fi
}
install_flatpak() {
if ! command -v flatpak >/dev/null 2>&1; then
log "Installing Flatpak"
sudo apt-get update
sudo apt-get install -y flatpak
fi
log "$(flatpak --version)"
}
install_app() {
sudo flatpak remote-add --if-not-exists "$REMOTE_NAME" "$REMOTE_URL"
if flatpak list --app --columns=application | grep -qx "$APP_ID"; then
log "Updating ${APP_ID}"
sudo flatpak update -y "$APP_ID"
else
log "Installing ${APP_ID}"
sudo flatpak install -y "$REMOTE_NAME" "$APP_ID"
fi
}
network_preflight() {
log "Pinging 1.1.1.1 (20 packets)"
ping -c 20 -i 0.2 -q 1.1.1.1 | tail -n 2 | while read -r line; do log "$line"; done
}
check_os
check_session
check_gpu
install_flatpak
install_app
network_preflight
log "Done. Launch with: flatpak run ${APP_ID}"Make it executable and run it. On a machine that is already set up, it should finish in under a minute and change nothing except to pull any pending app update.
chmod +x gfn-linux-setup.sh
./gfn-linux-setup.shExample output on a healthy system:
[gfn] Ubuntu 26.04 OK
[gfn] Session type: x11
[gfn] NVIDIA driver 580.xxx.xx OK
[gfn] Flatpak 1.x.x
[gfn] Updating com.nvidia.geforcenow
[gfn] Pinging 1.1.1.1 (20 packets)
[gfn] 20 packets transmitted, 20 received, 0% packet loss, time 3811ms
[gfn] rtt min/avg/max/mdev = ... ms
[gfn] Done. Launch with: flatpak run com.nvidia.geforcenowAdd a small session timer so a time-limited plan never catches you mid-boss-fight. Set GFN_SESSION_MINUTES to the session length you measured in Step 6, minus a safety margin. The script launches the app, waits, and sends a desktop notification. It uses notify-send, which ships with Ubuntu desktop.
#!/usr/bin/env bash
# gfn-play.sh: launch GeForce NOW and warn before your session ends
MINUTES="${GFN_SESSION_MINUTES:-30}"
( sleep $(( MINUTES * 60 )) && \
notify-send "GeForce NOW" "About ${MINUTES} minutes in. Save your game soon." ) &
flatpak run com.nvidia.geforcenow "$@"The default of 30 minutes is a placeholder, not a claim about your plan. Replace it with your own number, for example GFN_SESSION_MINUTES=45 ./gfn-play.sh. Move the script into ~/.local/bin if you want to call it from anywhere. That completes the build, and you now have a repeatable GeForce NOW on Linux setup.
Common Pitfalls When Setting Up GeForce NOW on Linux
Most failed installs trace back to a short list of avoidable mistakes. Read these before you spend an evening on a problem that is not really a problem.
- Installing an unofficial wrapper. Community projects such as Electron-based clients exist, and some are useful, but they are not NVIDIA’s app. If you hit a bug, you will not get official help, and you risk handing credentials to code you have not read. Start with the official Flatpak.
- Skipping the reboot after a driver install. The kernel module and the user-space libraries must match. If
nvidia-smisays it cannot communicate with the driver, reboot before you do anything clever. - Staying on Wayland with an NVIDIA GPU. NVIDIA specifies Xorg for its own cards. Wayland sessions can show black windows, frozen frames or missing input. Switch sessions first and test again.
- Leaving Wi-Fi power saving on. It looks like a streaming problem, but the cause is your laptop radio napping. Disable it for the connection you game on.
- Linking stores in the middle of a session. Store logins and two-factor prompts eat time you may not have on a limited plan. Link everything up front.
- Assuming free means unlimited. The free plan has limits on waiting and play time. Measure them, read NVIDIA’s FAQ, and plan around them instead of finding out mid-game.
- Forgetting the browser fallback. When an update breaks the app on a Friday night, a ready-made browser profile saves the evening.
Our wider gaming coverage tracks changes to these services as they ship, which helps when a pitfall turns out to be a policy change.
Troubleshooting GeForce NOW on Linux: 10 Fixes
When something breaks, work through these in order. Each item names a symptom, the usual cause and the fix.
- The app window opens but stays black. This usually means a display server or driver mismatch. Confirm you are on Xorg if you use an NVIDIA card, update the driver, reboot, then run
flatpak updateso the matching GL extension installs. - The app does not appear in the application grid. Flatpak’s export paths load at login. Log out and back in, or launch it directly with
flatpak run com.nvidia.geforcenow. flatpak remote-addfails with a network or TLS error. Check the clock withtimedatectl, then your proxy and DNS. Try again on a different network, such as a phone hotspot, to rule out a filter.remote-lsshows no GeForce NOW entry. The repository address may have changed. Copy the current command from NVIDIA’s download page instead of the one in this guide.- Sign-in loops or fails. A wrong system clock breaks secure logins. Run
timedatectl, enable network time, and retry. Disable a VPN while you sign in, because some regions and VPN exits trigger extra verification. - The stream stutters every few seconds. Disable Wi-Fi power saving as shown in Step 10, or move to Ethernet.
- The controller works in
evtestbut not in the app. The sandbox may block device access. Apply the--device=alloverride from Step 9 and restart the app. - No sound. Check that PipeWire is running with
pactl infoand that the right output device is selected. Flatpak apps reach audio through a socket, so a restarted audio service sometimes needs an app restart too. - High CPU use and choppy video. Software decoding has probably taken over. Run
vainfoand confirm H.264 and HEVC decode entries. On Intel or AMD, upgrade Mesa. On NVIDIA, confirm the driver loaded. - Everything broke after a driver update. The Flatpak GL extension no longer matches. Run
flatpak update, thenflatpak list --runtime | grep -i nvidiato confirm the matching extension exists, and reboot.
If none of these helps, run the app from a terminal with flatpak run --verbose com.nvidia.geforcenow and read the first error line. Searching for that exact line usually finds a forum thread faster than any general query. And if you are still undecided about which service is worth your time, the ranking of the best cloud gaming services compares five of them side by side.
Advanced Tips for Power Users
Once the basics work, a few habits make the setup nicer to live with. Keep the app fresh by adding a weekly update to a systemd timer or cron job with flatpak update -y, since NVIDIA delivers fixes through the repository. Pin your driver version if a particular release works well for you, using apt-mark hold on the driver package, and release the hold on your schedule rather than letting a surprise update land before a gaming weekend.
Use a day pass as a free-to-paid bridge. Because NVIDIA credits the day-pass cost toward a first monthly membership, you can sample Performance or Ultimate on your own network, check whether RTX effects or higher frame rates make sense for you, and only then commit. Test on a day when you have free time, because the point is to compare against the free tier under similar conditions.
Linux users with a gaming PC at home have a second free option. Streaming from your own machine through Sunshine and Moonlight skips queues and session limits entirely, and our self-hosted Sunshine and Moonlight guide shows how to set it up over Tailscale. The two approaches complement each other. GeForce NOW covers you when the home PC is off or you are traveling.
Finally, keep a short log of what works. Note the Ubuntu release, driver version, session type, app launch command and any override you applied. When a future update breaks something, that file turns a mystery into a ten-minute rollback. Pair it with the setup script from Step 13 and you can rebuild the whole environment on a new disk quickly.
Frequently Asked Questions
Is GeForce NOW on Linux really free?
The app is free to install and NVIDIA offers a Free membership alongside Performance and Ultimate. Free members still need to own the games they stream on a supported store, and the plan has limits on queue and session behavior that you should confirm in NVIDIA’s FAQ.
Which Linux distributions does the native app support?
NVIDIA’s August 13, 2026 announcement says Ubuntu 24.04 and later. Because the app is a Flatpak, other distributions may run it, but only Ubuntu comes with an official promise.
Do I need an NVIDIA graphics card?
No. The cloud does the rendering. Your machine needs a GPU that can decode H.264 and H.265 video, and NVIDIA’s requirements cover Intel and AMD cards through Mesa as well as NVIDIA cards through the proprietary driver.
Should I use Wayland or Xorg?
Follow NVIDIA’s guidance: Xorg for NVIDIA GPUs and Wayland for AMD and Intel GPUs. If you see a black screen or input problems on an NVIDIA card, switch to Xorg first.
Can I play in a browser instead of installing the app?
Yes. Open play.geforcenow.com in a supported browser. NVIDIA announced Firefox support on August 20, 2026, and Chromium-based browsers have worked for longer. The app generally gives you more options, and reports say some high-end modes need an Ultimate plan in a browser.
Which game stores work with GeForce NOW?
NVIDIA lists Steam, Epic Games Store, Ubisoft Connect, Xbox PC Game Pass, GOG and EA, though each individual game must be supported by the service.
Will the new DLSS 4.5 controls work on Linux?
NVIDIA’s October 15, 2026 announcement names Windows, macOS, ChromeOS and SteamOS apps and does not mention Linux. Check your app’s settings after updating, and watch NVIDIA’s weekly GFN Thursday posts for a Linux mention.
