Shadow PC quietly rebuilt its lineup this summer. In late July 2026, Blade Group (the company behind Shadow) rolled out two new hour-capped tiers, Neo Lite and Power Lite, sitting under the existing uncapped Neo and Power plans. For Steam Deck owners and Linux users who have spent the past few years fighting driver support, Proton compatibility layers, and native port gaps, this changes the calculus: a full Windows desktop with an RTX-class GPU is now reachable from under $23 a month on an annual plan. But picking the wrong tier, or setting up the streaming client wrong on a non-Windows device, wastes hours of the very allowance you just paid for.
This tutorial walks through choosing between Shadow PC Lite and the standard Neo/Power tiers, migrating an existing subscription, and configuring the whole thing to run cleanly on a Steam Deck or a Linux desktop. If you’re coming in fresh without any Shadow account at all, our Shadow PC cloud gaming setup guide covers the baseline account creation flow; this piece assumes that part is done and focuses on the Lite-tier decision plus Deck and Linux specifics. By the end you will have a working cloud PC streaming at 1440p over Proton-friendly tooling, tuned bitrate and codec settings, and a monitoring habit that keeps you from burning through your monthly hour cap before the billing cycle resets.
What Shadow PC Lite actually changed in 2026
Shadow has offered a full remote Windows desktop since its earliest days, but pricing had crept upward over the years, pushing casual users toward rivals like Boosteroid or GeForce NOW. The Lite tiers, announced by Shadow’s official account in late July 2026 as “the same Shadow offers, at our lowest price yet, starting at €20/month,” were built to reverse that. They are not a stripped-down streaming app or a lower-resolution stream. They use the exact same underlying hardware pools as the standard Neo and Power tiers. The difference is entirely in the usage envelope: a 120-hour monthly cap and 4-hour maximum session length, versus roughly 210 hours and 6-hour sessions on the standard plans.
That distinction matters for anyone planning to use Shadow on a Steam Deck or Linux box as a secondary or travel machine rather than a full-time desktop replacement. If you are gaming two or three evenings a week, 120 hours a month is plenty of runway. If you are running Shadow as your only PC for work and play, the standard Neo or Power plan avoids the anxiety of watching a countdown timer.
Shadow’s own hardware documentation still lists the Neo-tier GPU as “GeForce RTX 4060 16GB-class (RTX 2000 Ada 16GB),” which is the same silicon Shadow has used across its mid-tier plans since the 2024 hardware refresh. Power and Power Lite step up to an RTX A4500-class card with 20GB of VRAM. Neither Lite tier is a cut-down GPU; you are trading time, not power, for the lower price.
Why Blade Group launched a capped tier now
Shadow’s pricing had been drifting upward for several years, and that drift opened room for lower-cost competitors that stream individual games rather than a full desktop. A capped-hour tier lets Blade Group sell the same GPU capacity to more subscribers without expanding data center hardware at the same rate, since most casual users never come close to a 210-hour ceiling anyway. For the company, Lite plans convert an underused resource, spare GPU cycles from full-time subscribers who stream less than they pay for, into a lower price point that competes directly with the free and near-free tiers of GeForce NOW and Boosteroid on sign-up cost, while still charging a premium for the full-desktop flexibility those services don’t offer.
Same silicon, different meter
It’s worth repeating because it trips up so many first-time buyers: Neo Lite and Neo run identical hardware. So do Power Lite and Power. There’s no separate “budget” data center or throttled GPU clock behind the Lite branding. What you’re actually purchasing is a smaller monthly time bank against the same infrastructure. That means a benchmark run on Neo will produce the same frame rates as one run on Neo Lite, at the same settings, on the same game. If you see a review or forum post claiming Lite tiers perform worse, treat it skeptically. Any performance gap you notice is more likely a network, codec, or resolution-profile issue covered later in this guide, not a hardware difference.
Prerequisites and what you need before starting
Gather these before you touch a subscription page. Skipping the prep step is the single biggest reason first-time cloud PC setups feel laggy or unreliable.
- A wired or 5GHz Wi-Fi 6 connection rated at 25 Mbps down / 5 Mbps up minimum for 1440p streaming; 50 Mbps down is recommended for headroom during peak ISP congestion hours.
- Steam Deck running SteamOS 3.9 or later (the version that shipped official support improvements for external streaming clients), or a Linux distribution with kernel 6.6+ and Mesa 24.x graphics drivers.
- A Shadow account with a valid payment method — Shadow accepts major cards and PayPal in US and EU markets.
- Shadow’s Linux client (the officially supported Debian/Ubuntu .deb package) or the Moonlight-compatible fallback for distros without native support.
- A Bluetooth or USB-C wired controller if you plan to play with a gamepad instead of Deck’s built-in inputs; the Deck’s own controls pass through natively once the client is running.
- At least 2GB of free local storage for client caching and log files.
- 15-20 minutes for the account setup and first stream test, plus another 30-45 minutes if you are migrating data from an existing Shadow subscription.
Step 1: Compare the four consumer tiers before you commit
Before creating an account, map your actual monthly play time against the plan caps. Shadow’s current lineup, current as of late August 2026, breaks down like this:
| Plan | Monthly price | Annual price (per mo.) | GPU | VRAM | RAM | Hour cap | Session limit |
|---|---|---|---|---|---|---|---|
| Neo Lite | $29.99 | $22.49 | RTX 2000 Ada | 16 GB | 16 GB DDR5 | 120 hrs | 4 hrs |
| Power Lite | $43.99 | $32.99 | RTX A4500-class | 20 GB | 28 GB | 120 hrs | 4 hrs |
| Neo | $37.99 | ~$30.39 (6-mo. prepay) | RTX 2000 Ada | 16 GB | 16 GB DDR5 | ~210 hrs | 6 hrs |
| Power | $54.99 | varies by term | RTX A4500-class | 20 GB | 28 GB | ~210 hrs | 6 hrs |
Both Lite tiers ship with a 256GB SSD and an 8-vCore AMD EPYC virtual CPU, the same as their non-Lite counterparts. The practical takeaway: if your play sessions rarely exceed 3-4 hours in one sitting and you are not streaming daily, Neo Lite covers most casual and weekend gaming without touching the standard Neo price. If you plan to run Shadow as a daily driver for remote work plus gaming in the evening, the hour cap on Lite plans will bite by the third week of the month, and the standard Neo tier is worth the extra $8-15.
Step 2: Create your Shadow account and select region
Head to Shadow’s official offers page and select your tier. Shadow assigns your virtual machine to a data center region based on your billing address and detected location, so sign up from the network you intend to actually use — signing up on a VPN and then streaming from your home connection can land you on a distant data center with 40-60ms of extra latency baked in before you even start troubleshooting.
During checkout, note that Shadow ran a new-customer discount window from August 26 through September 10, 2026 across European and North American markets, applied automatically at checkout for eligible tiers. If you’re reading this after that window closes, check the offers page directly since Shadow rotates these promotions roughly every 4-6 weeks.
Step 3: Install the Shadow client on Steam Deck via Desktop Mode
Shadow does not ship a native SteamOS package through the Discover Store, so you’ll install the Linux client manually from Desktop Mode. Hold the Power button and select Switch to Desktop, or tap the Deck’s Desktop Mode shortcut from the Steam menu.
# From Steam Deck Desktop Mode, open Konsole
sudo steamos-readonly disable
sudo pacman -Sy --needed base-devel git
wget https://shadow.tech/download/linux/shadow-latest.deb -O ~/Downloads/shadow.deb
cd ~/Downloads
# Convert the .deb for Arch-based SteamOS with debtap, or use the AppImage build if Shadow publishes one
sudo steamos-readonly enable
SteamOS is Arch-based, not Debian, which is why the straight .deb won’t install cleanly without conversion. Most Deck users instead grab Shadow’s AppImage build when available, or fall back to the Moonlight open-source client paired with Shadow’s Ganymede streaming protocol bridge. Once installed, add the Shadow client as a non-Steam game from Desktop Mode so it appears in Gaming Mode:
# In Desktop Mode, open Steam
# Games > Add a Non-Steam Game to My Library
# Browse to the Shadow AppImage or extracted binary
# Right-click the new entry > Properties > set launch resolution override to 1280x800 (Deck native)
Return to Gaming Mode and the Shadow client now launches like any other game, with Steam Input mapping your Deck controls to the Shadow session once you’re inside your cloud desktop. If you’re not already comfortable moving between Gaming Mode and Desktop Mode for installs like this, our Steam Deck Desktop Mode walkthrough covers the full toggle process and common Desktop Mode gotchas.
Step 4: Install the Shadow client on a Linux desktop
On Ubuntu, Debian, Fedora, or Arch-based desktop distros, installation is more straightforward since Shadow maintains an official Linux build.
# Ubuntu / Debian
wget https://shadow.tech/download/linux/shadow-latest.deb
sudo apt install ./shadow-latest.deb
sudo apt --fix-broken install # resolves any missing codec dependencies
# Fedora (via alien conversion)
sudo dnf install alien
sudo alien -r shadow-latest.deb
sudo dnf install ./shadow-latest*.rpm
# Arch / Manjaro (AUR)
yay -S shadow-pc-client
If your distro runs Wayland with Waydroid or another Android compatibility layer alongside Shadow, keep the two isolated rather than running them simultaneously against the same GPU context; see our Waydroid on Linux setup guide for the isolation approach we recommend there. Launch the client, sign in with your Shadow credentials, and let the app run its automatic network test. This test measures round-trip latency and available bandwidth to your assigned data center and recommends a starting bitrate, which you’ll tune further in Step 6. A healthy result on a wired connection to a nearby data center looks something like this:
Shadow Network Diagnostic
--------------------------------
Assigned region: Frankfurt (eu-central-1)
Round-trip latency: 9 ms
Jitter: 1 ms
Download bandwidth: 187 Mbps
Upload bandwidth: 23 Mbps
Packet loss: 0.0%
Recommended codec: HEVC
Recommended bitrate: 45 Mbps
Status: READY
If your latency reads above 40-50ms or packet loss is non-zero, the connection is still usable but you’ll notice more input delay than the numbers above. Anything past 80ms round-trip is a sign you signed up from the wrong region, or your ISP route to that data center is congested, and it’s worth contacting Shadow support to check whether a region reassignment is possible.
How Shadow PC Lite stacks up against GeForce NOW and Boosteroid
Before locking in a subscription, it’s worth understanding what Shadow trades away compared to game-streaming services that don’t hand you a full desktop, a distinction independent reviewers like PCMag have highlighted in their own coverage of the service. GeForce NOW and Boosteroid stream specific supported titles from your existing game library on Steam, Epic, or Battle.net, whereas Shadow gives you the underlying machine and lets you install anything.
| Service | Entry price | Model | Library | Session cap |
|---|---|---|---|---|
| Shadow Neo Lite | $22.49/mo (annual) | Full Windows cloud PC | Anything you install | 4 hrs, 120 hrs/mo |
| GeForce NOW (Ultimate tier) | Priced per NVIDIA’s current published rate | Game streaming | Supported titles you own | Session length varies by tier |
| Boosteroid | Lower entry price than Shadow per third-party comparisons | Game streaming | Supported titles you own | No full desktop access |
The practical difference shows up the moment you want to run something the streaming-only services don’t support: a modded game, a launcher-locked title, a benchmarking tool, or non-gaming software like a video editor. Shadow handles all of that because it’s a real Windows install with administrator access. GeForce NOW and Boosteroid are simpler to start with and typically cheaper at the entry tier, but they’re bounded by whatever titles their catalog supports and by how each publisher licenses cloud streaming rights (GeForce NOW’s own Linux app exited beta in 2026 with broader distro support, narrowing that particular gap somewhat). For Steam Deck owners specifically, the calculus often comes down to whether you’re chasing a specific unsupported game or workflow (pick Shadow) or you mainly want to stream mainstream titles you already own with the lowest possible monthly cost (pick a game-streaming service instead, and consider Shadow later if you outgrow it).
Step 5: Migrate an existing Shadow subscription to a new tier
If you’re already on a standard Neo or Power plan and want to downgrade to Lite to save money, or upgrade from Lite because you keep hitting the hour cap, the process runs through Shadow’s account dashboard rather than requiring a fresh signup.
- Log into your Shadow account dashboard from a browser (not the client itself).
- Navigate to Subscription > Manage Plan.
- Select the new tier. Shadow prorates the difference for upgrades; downgrades typically take effect at the next billing cycle rather than immediately, so you keep your current hardware allocation until then.
- If moving from a standard tier to Lite, back up any files stored outside of Shadow Drive first, since a plan change occasionally triggers a fresh VM provisioning cycle and local desktop customization (pinned taskbar apps, installed non-Steam software) does not always carry over cleanly.
- Confirm the change and wait for Shadow’s provisioning email, usually delivered within 10-15 minutes.
Games installed through Steam, Epic, or other launchers persist because they live on your cloud SSD, not on a specific physical machine tied to your old plan. What does not automatically persist is any manual driver tweak or third-party software you installed directly on the Windows desktop outside of a game launcher.
Step 6: Tune bitrate and codec settings for your connection
Default settings favor stability over quality, which is the right call for a first connection but leaves performance on the table once you know your network can handle more. Open the Shadow client’s settings panel and adjust these three values in order.
| Connection type | Recommended bitrate | Codec | Target resolution |
|---|---|---|---|
| Wired gigabit / strong Wi-Fi 6 | 40-50 Mbps | HEVC (H.265) | 1440p @ 60Hz |
| Standard home broadband (Wi-Fi 5) | 25-35 Mbps | H.264 | 1080p @ 60Hz |
| Mobile hotspot / hotel Wi-Fi | 10-15 Mbps | H.264 | 720p @ 30-60Hz |
HEVC gives noticeably cleaner detail at the same bitrate compared to H.264, but decoding it requires hardware acceleration. Steam Deck’s LCD and OLED models both handle HEVC decode natively, so leave it enabled there. On Linux desktops, verify your GPU driver exposes VA-API or NVDEC HEVC decode before switching; otherwise the client falls back to software decoding, which spikes CPU usage and can introduce stutter that looks like a network problem but isn’t.
Step 7: Configure display resolution to match your device
Shadow’s virtual desktop defaults to a resolution based on your first connected display, which causes problems if you regularly switch between a Deck’s 1280×800 screen and an external 1440p or 4K monitor. Set a per-device profile instead:
# Inside the Shadow client settings > Display
# Enable "Remember resolution per device"
# Deck profile: 1280x800, 60Hz, scale 100%
# Desktop monitor profile: 2560x1440, 144Hz (capped to your plan's refresh ceiling), scale 100%
Without this toggle, switching from your Deck back to a desktop monitor forces you to manually reset resolution inside the cloud Windows desktop every session, which wastes several minutes of your hour allowance on menu-diving instead of playing.
Step 8: Map Steam Deck controls for the cloud desktop
Because Shadow streams a full Windows environment rather than a single game, the Deck’s default control scheme needs a layer built for desktop navigation plus a second layer for in-game input once you launch a title inside the stream.
- From Gaming Mode, open the Steam Input overlay (Quick Access Menu > Controller icon) while the Shadow client is running.
- Create a new configuration and map the right trackpad to mouse movement, right trigger to left-click, and left trigger to right-click for desktop navigation.
- Bind a back-grip button to toggle a “gaming layer” that switches the right stick and face buttons to standard Xbox-style input, which most Windows games inside the Shadow session will recognize natively.
- Save the configuration and set it to auto-apply whenever you launch the Shadow client entry.
This two-layer approach avoids the common complaint that Shadow “doesn’t feel native” on Deck — the friction is almost always an input-mapping issue, not a streaming performance one.
Step 9: Set up Shadow Drive for persistent file storage
Shadow Drive gives you cloud storage that syncs between your Shadow desktop and local devices, which matters for anyone bouncing between a Deck, a Linux laptop, and an occasional Windows machine. Enable it from the account dashboard, then install the local sync client on any Linux machine where you want files to mirror automatically. On Steam Deck, Shadow Drive is best accessed through the browser-based file manager inside your cloud desktop rather than a local sync client, since running a background sync daemon on the Deck’s limited storage isn’t worth the tradeoff for most users.
Step 10: Install and configure Proton-adjacent tools inside your cloud Windows desktop
Here’s a detail that trips up new Shadow users coming from Steam Deck: your Shadow desktop runs full native Windows, so you do not need Proton at all inside the cloud session — Windows games run natively there. The confusion happens because you’re accessing it from a Linux-based Deck. Keep these two layers mentally separate:
- The Deck’s own SteamOS uses Proton to run Windows games locally; compatibility for any given title on native Deck hardware can be checked on ProtonDB before deciding whether you even need Shadow for it.
- Your Shadow session is a real Windows 10/11 desktop and needs no compatibility layer for Windows titles.
- Install Steam, Epic, GOG Galaxy, or Battle.net directly inside the Shadow Windows desktop exactly as you would on a physical Windows PC.
The practical benefit: games that run poorly or not at all under Proton on the Deck’s own hardware (kernel-level anti-cheat titles, some VR-adjacent tools, certain launcher-locked games) run natively once streamed from a genuine Windows install through Shadow.
Step 11: Monitor your monthly hour usage to avoid a mid-session cutoff
Both Lite tiers enforce a hard 120-hour monthly ceiling, and Shadow’s dashboard shows remaining hours but does not push an in-client warning until you’re close to the limit. Build a habit around this instead of relying on the UI alone. If you’ve been burned by a similar cap before, the discipline is the same one we outline in our Shadow PC hour caps guide, just applied to the newer Lite tiers instead of the original capped plans.
# Simple weekly budget math for a 120-hour Lite plan:
# 120 hours / 4 weeks = 30 hours/week average
# 30 hours / 7 days = ~4.3 hours/day sustainable pace
# Check remaining hours from the account dashboard, or via the client's
# account panel: Settings > Account > Usage This Cycle
The usage panel itself reports a running total plus a projected exhaustion date based on your recent pace, which is more useful than the raw hour count alone:
Usage This Cycle — Neo Lite
--------------------------------
Billing cycle: Sep 1 - Sep 30
Hours used: 68.5 / 120
Sessions this cycle: 19
Average session: 3.6 hrs
Projected exhaustion: Sep 24 (at current pace)
Days remaining in cycle: 22
A projected exhaustion date landing before the cycle actually ends is your cue to either pace down or upgrade to a standard tier before you get cut off mid-session. If you know a weekend binge session is coming, front-load lighter usage earlier in the billing cycle. Running out mid-session doesn’t lose your progress (most games auto-save or you can manually save before the cutoff), but Shadow does terminate the stream once the cap hits zero, and reactivating requires waiting for the next cycle or upgrading tiers mid-month at a prorated cost.
Step 12: Test end-to-end performance before committing to a long session
Run a short 15-20 minute test session before diving into a multi-hour gaming block. Check three things: input latency feel in a fast-paced game (a rhythm game or competitive shooter reveals lag fastest), visual clarity at your configured bitrate during fast camera movement, and audio sync, which is the first thing to drift if your network has jitter. If any of the three feels off, revisit Step 6’s bitrate and codec settings before assuming it’s a hardware limitation.
Securing your Shadow account across multiple devices
Running Shadow from both a Steam Deck and a Linux desktop means your credentials are entered on two separate devices, which is exactly the kind of setup that benefits from a bit of hardening before you start treating the cloud PC as a daily driver.
Enable two-factor authentication on the Shadow account itself
Shadow’s account dashboard supports two-factor authentication through an authenticator app. Turn this on before you add a second device, since an account takeover on a service that hands over a full remote Windows desktop is a bigger blast radius than a typical streaming subscription. Anyone with your login can access installed software, saved files on Shadow Drive, and any payment methods on file in the browser session.
Lock down the Windows desktop like any other PC
Because your Shadow instance is a genuine Windows install, it inherits genuine Windows risks. Keep Windows Update running inside the cloud desktop, avoid disabling Windows Defender to “save resources” (the virtual hardware has plenty of headroom for it), and be as careful about what you download inside the Shadow session as you would on a physical machine. A compromised Shadow desktop is still tied to your account and payment method, so the usual advice against installing cracked software or unverified executables applies with the same weight here.
Common pitfalls when setting up Shadow on Steam Deck or Linux
These are the mistakes that generate the most support tickets and forum complaints, based on the recurring patterns in Shadow’s community discussions and Linux gaming forums.
- Signing up while on a VPN. This assigns your VM to the wrong data center region, adding 30-80ms of avoidable latency that no amount of bitrate tuning fixes.
- Leaving HEVC enabled on unsupported hardware. Older Linux GPU drivers without proper hardware decode force software fallback, causing stutter that looks like a bandwidth issue.
- Forgetting the resolution-per-device setting. Constantly re-configuring display settings between Deck and monitor wastes real minutes off your hour cap.
- Installing Proton or Wine inside the Shadow Windows desktop. It’s unnecessary since the cloud desktop is native Windows; adding a compatibility layer there can actually break some game launchers.
- Choosing Power Lite when Neo Lite is sufficient. Unless you’re running GPU-intensive creative work or a specific title that needs the extra VRAM, the RTX 2000 Ada in Neo Lite handles the vast majority of 1440p gaming comfortably.
- Ignoring session length limits. The 4-hour cap on Lite tiers will forcibly disconnect an active stream. Save your progress well before the 4-hour mark, not at it.
- Running the sync client on Deck’s limited storage. Shadow Drive’s desktop sync client duplicates files locally; on a storage-constrained Deck, this fills space fast for little benefit versus browser-based access.
- Skipping the initial network test. The client’s auto-recommendation is a starting point, not gospel. Manually retest after any router firmware update or ISP plan change.
Troubleshooting: fixing the most common Shadow PC issues on Steam Deck and Linux
Work through these in order when something isn’t working. Most Shadow issues on non-Windows devices trace back to one of these eight causes.
- Stream won’t connect at all: Confirm your Shadow subscription is active and not mid-provisioning (check the dashboard for a “ready” status). New subscriptions can take up to 15 minutes to provision a VM.
- Black screen after connecting: Force-quit the client and restart. This usually resolves a stuck session handshake, particularly after a plan change or tier migration.
- Audio drops out mid-session: Check for background bandwidth consumers on your network (other devices streaming video, cloud backups running). Shadow’s audio channel is more sensitive to jitter than video.
- Controller inputs not registering in Gaming Mode: Re-verify your Steam Input configuration is set to auto-apply for the Shadow client entry specifically, not just your global default.
- Resolution resets every time you switch devices: Confirm “Remember resolution per device” is enabled in client settings; this toggle is off by default on fresh installs.
- Stuttering despite good bandwidth numbers: Switch from HEVC to H.264 temporarily to rule out a hardware decode issue on your specific Linux GPU driver version.
- Hour cap hit unexpectedly early: Check the dashboard usage log for idle sessions left running; Shadow counts connected time, not active gameplay time, so a forgotten open session burns hours.
- Games installed on the cloud desktop disappear after a tier change: This shouldn’t happen with normal upgrades/downgrades, but if it does, contact Shadow support with your provisioning confirmation email; games on Steam/Epic/GOG can be re-downloaded, but any manually copied files need Shadow Drive backup to recover.
Advanced tips: getting more out of Shadow on non-Windows devices
Once the basic setup is stable, a few refinements make the day-to-day experience noticeably smoother. First, create separate Steam Input profiles for desktop navigation versus specific game genres — a profile tuned for a shooter’s aim sensitivity is wrong for a strategy game’s menu navigation, and switching profiles takes seconds versus re-tuning settings each session. Second, if you’re running Shadow primarily for productivity work alongside gaming (video editing, code compilation, or Unreal/Unity development), the Pro tier’s higher default storage allocation and dedicated support channel are worth the price jump over Neo/Power, since the consumer tiers are optimized for gaming session patterns rather than sustained CPU-heavy compile jobs. Third, pair Shadow with a wired Ethernet-to-USB-C adapter on Deck for any competitive multiplayer session; Wi-Fi 6 is good enough for casual play, but wired connections shave a consistent 5-10ms of jitter that matters in fast-paced titles. Finally, set a calendar reminder a few days before your billing cycle renews to reassess whether your actual monthly hours matched your tier choice — Shadow’s usage dashboard keeps a rolling history, so after two billing cycles you’ll have real data instead of a guess.
Complete working project: a weekend Steam Deck cloud gaming setup
Putting it all together, here’s a complete configuration for someone using a Steam Deck as a travel companion with Shadow PC as the heavy-lifting backend:
# 1. Subscription: Neo Lite, annual billing ($22.49/mo effective)
# - Covers ~4.3 hrs/day average, fits weekend + 2 weeknight sessions
# 2. Steam Deck setup
sudo steamos-readonly disable
# install Shadow AppImage or Moonlight+Ganymede bridge to ~/Applications
sudo steamos-readonly enable
# Add to Steam as non-Steam game, launch resolution 1280x800
# 3. Client settings
# Codec: HEVC
# Bitrate: 35 Mbps (tuned down from 50 Mbps default for hotel/travel Wi-Fi)
# Resolution profile: Deck = 1280x800@60Hz, saved separately from desktop profile
# 4. Steam Input
# Layer 1: desktop nav (trackpad = mouse, triggers = clicks)
# Layer 2 (grip toggle): Xbox-style gamepad passthrough for in-stream games
# 5. Inside the Shadow Windows desktop
# Install Steam, Epic, GOG Galaxy natively (no Proton needed)
# Enable Shadow Drive browser access for save file backup
# 6. Weekly check
# Dashboard > Usage This Cycle — confirm pace stays under 30 hrs/week
This setup gives a Deck owner access to a full RTX 2000 Ada-class Windows gaming PC anywhere there’s a stable internet connection, at a lower monthly cost than most single AAA game purchases, while staying comfortably inside the Lite tier’s hour allowance for casual-to-moderate play. For more cloud and mobile gaming setups in the same vein, see our broader mobile gaming coverage.
Shadow PC Lite vs standard Neo/Power: which should you actually pick
The decision comes down to a single question: how many hours a month do you realistically stream? Below roughly 100-110 hours, Lite tiers save real money with zero hardware compromise. Above that, or if you use Shadow as a genuine daily-driver replacement for a physical desktop, the standard Neo or Power plan’s larger hour allowance and longer 6-hour session window removes the friction of watching a usage meter. Households sharing one Shadow subscription across multiple people, or anyone doing remote work sessions that regularly exceed 4 hours, should default to standard tiers rather than Lite. Everyone else, particularly Steam Deck owners looking for an occasional-use Windows gaming rig without touching their Deck’s own storage or battery life, will find Neo Lite the more cost-effective entry point in the current 2026 lineup.
Frequently asked questions
Does Shadow PC Lite use worse hardware than the standard Neo and Power plans?
No. Both Lite tiers run on the identical GPU, RAM, and storage configuration as their standard counterparts. The only difference is the monthly hour cap (120 vs roughly 210) and maximum session length (4 vs 6 hours).
Can I run Shadow PC natively on SteamOS without converting the Linux client?
Shadow does not publish a native Arch/SteamOS package through Discover. Most Deck users either convert the Debian package with a tool like debtap, use an available AppImage build, or connect through the open-source Moonlight client if Shadow’s streaming backend supports it in your region.
Do I need Proton or Wine inside my Shadow cloud desktop?
No. Your Shadow session is a genuine Windows 10/11 install, so Windows games and launchers run natively. Proton is only relevant to the Deck’s own local SteamOS environment, not to anything happening inside your streamed Shadow desktop.
What happens if I hit my hour cap in the middle of a game?
Shadow terminates the stream once your monthly allowance reaches zero. Most games auto-save, but it’s safer to track your usage via the dashboard and save manually before you’re likely to hit the limit. You can upgrade tiers mid-cycle for a prorated cost if you need immediate access.
Is 25 Mbps really enough bandwidth for smooth 1440p streaming?
It’s the practical minimum for a stable H.264 stream at 1080p-1440p. For consistently smooth 1440p at 60Hz with headroom for network fluctuation, 40-50 Mbps with HEVC enabled gives noticeably more consistent results, especially on shared home networks.
Can multiple people share one Shadow subscription?
Shadow accounts are designed for single-user access at a time; the cloud desktop and its hour allowance are tied to one account. Sharing login credentials across simultaneous sessions is against Shadow’s terms and won’t function as two separate concurrent streams.
Does switching from Neo to Neo Lite lose my installed games or files?
Games installed through Steam, Epic, or similar launchers persist since they live on your cloud SSD. Manually placed files not backed up to Shadow Drive carry some risk during a plan change, so back up anything important beforehand.
Is Shadow PC better than GeForce NOW or Boosteroid for Steam Deck users?
They solve different problems. GeForce NOW and Boosteroid stream individual supported games from a curated library. Shadow gives you a complete, persistent Windows desktop where you install anything you want, including titles or launchers those services don’t support, at the tradeoff of a higher monthly price and a personal hour allowance rather than unlimited access to a shared game catalog.