PS Remote Play 2026: 1080p in 12 Steps, 30 Min

Two things get sold under the phrase PS Remote Play, and they are not the same thing. One is a streaming client that pulls a live picture off your own PlayStation, sitting in your own living room, over your own network. The other is Sony renting you a slice of a data-center PS5 you will never touch. Marketing blurs the line on purpose. We are going to un-blur it, because every real configuration decision — bandwidth, latency, which console has to be awake, whether your disc games even work — depends on which one you actually mean.

This is a working tutorial, not a press release. You get a prerequisites list with real version numbers, a twelve-step setup you can finish in about half an hour, six copy-pasteable configuration blocks, a pile of pitfalls, and a troubleshooting table for when the picture freezes on a black screen and the error code means nothing. We will also cover the March 17, 2026 firmware that finally added a 1080p High Quality mode, and the open-source client that turns a Steam Deck into a better Remote Play handheld than the one Sony sells. Let us begin by refusing to conflate the two products.

Remote Play Is Not Cloud Streaming

If you take one idea from this article, take this one. Remote Play is a local relationship between two devices you own. Cloud streaming is a subscription relationship with Sony's servers. They share a codec and an app icon and almost nothing else. Getting them confused is how people end up buying a PlayStation Plus Premium tier they did not need, or waiting for a cloud queue when their own PS5 was sitting three feet away, powered off, doing nothing.

What Remote Play actually does

Traditional PS Remote Play runs the game on your PS5 (or PS4 — it works there too). The console does the rendering. A hardware encoder on the console compresses the frame to H.264 or H.265, ships it across your LAN or the open internet to a client — a Windows PC, a Mac, an iPhone, an Android phone, another PlayStation, or a PS Portal — and the client decodes it and paints it on screen. Your controller inputs travel back the other way. Because the machine doing the work is one you own, Remote Play will run anything that console can run, including disc-based games, because the disc is spinning in the drive you paid for. The console must be either powered on or in rest mode with networking left alive so the client can wake it. That is the whole trick.

What cloud streaming actually does

Cloud streaming, by contrast, needs no console of yours at all. Sony runs the game on a server, and — per the November 5, 2025 launch documented on the official PlayStation Blog — it is gated behind PlayStation Plus Premium. It streams thousands of eligible digital PS5 titles plus the Premium Game Catalog and Classics Catalog. It cannot stream a disc, and as of this writing the only consumer device that speaks it is the PS Portal. Your own PS5 can be unplugged in a closet; the cloud does not care. That independence is the entire selling point, and also the entire catch: you are limited to what Sony has licensed for streaming, not to what you own.

The latency reality (ignore the fake millisecond numbers)

You will see confident claims online that local Remote Play adds "1–5 ms" of latency while cloud adds "30–40 ms." Treat those numbers as fiction. One to five milliseconds is a LAN ping — the time a bare packet takes to cross your router — not end-to-end input latency, which also includes controller polling, the console's video encode, the network hop, the client's decode, and your display's own lag. Measured glass-to-glass, even a clean wired Remote Play session adds tens of milliseconds; it feels responsive but it is not zero. Cloud streaming stacks the round trip to Sony's data center on top of all that, which is why a cloud session over a mediocre connection feels floatier than the same game over local Remote Play. The honest rule: local is meaningfully snappier than cloud, and neither is as tight as a controller plugged straight into the console. Do not let anyone sell you a single-digit-millisecond fantasy. If you care about competitive input lag, you want a wired handheld or the couch, not a stream.

Prerequisites: Hardware, Software, Bandwidth

Skip this section and you will spend twenty minutes debugging a problem that a five-minute checklist would have prevented. Remote Play is unforgiving about three things: account mismatches, stale app versions, and bad Wi-Fi. Get all three right before you touch anything.

Console and account requirements

You need a PS5 or PS5 Digital Edition (or a PS4 / PS4 Pro) running current system software, and a PlayStation Network account — the same account signed in on the console you intend to stream from. This is the single most common failure: people sign into the app with a second account and wonder why the console never appears. One account, both ends. The console's primary/host activation must be set to the console you are streaming from. You do not need PS Plus of any tier for traditional Remote Play — that is a cloud-streaming requirement, not a Remote Play one.

On the console itself, two setting trees matter. Enable the feature, then make the console reachable while it sleeps. Do both now:

# On the PS5, enable Remote Play and rest-mode networking

Settings > System > Remote Play
    Enable Remote Play .......................... ON
    Link Device ................................. (shows an 8-digit code)

Settings > System > Power Saving
    Features Available in Rest Mode
        Stay Connected to the Internet .......... ON
        Enable Turning On PS5 from Network ...... ON

Why it matters: "Stay Connected to the Internet" keeps the network stack alive in rest mode, and "Enable Turning On PS5 from Network" lets the client wake the console from standby. Without both, the console drops off the network the moment it sleeps and your client reports it as unavailable — the classic "it worked when the TV was on" symptom.

Client device requirements (real version numbers)

Install the latest PS Remote Play app; the client refuses to connect on an outdated build and nags you to update on launch, so let it. Per Sony's official Windows setup page, the Windows requirements are concrete: Windows 10 (64-bit) or Windows 11, a 7th-generation Intel Core processor or later, 2 GB of RAM or more, 100 MB of free storage, a display of at least 1024×768, a sound card, and a USB port for the controller. Modest by design — the client only has to decode video, not render a game.

For the other platforms, per the App Store and Google Play listings: macOS runs on recent releases and is native on Apple Silicon (M-series) with hardware-accelerated H.264/H.265 decode; iOS/iPadOS wants a current version; Android needs 8.0 (Oreo) at minimum, with 12 or later recommended. One Android gotcha worth memorizing: to pair a DualSense you need Android 12, and a DualSense Edge needs Android 14. Older controllers (DualShock 4) pair more forgivingly. On PC and Mac, connect the controller over USB for the most reliable first pairing; Bluetooth works but is fussier during registration.

The bandwidth floor, and what those numbers really mean

Sony's stated minimum is 5 Mbps up and down, with 15 Mbps recommended — the same figures the March 2026 Portal firmware repeats. Read that carefully: it is a floor, not a target. Five megabits will connect and then punish you with a soft, blocky, stuttering picture the moment anything moves fast. The cloud-streaming beta documentation was blunter about the real thresholds: a 1080p stream wanted at least 13 Mbps and 720p wanted at least 7 Mbps. Those are the numbers to plan around. And the requirement is symmetric where it hurts most — your upload at the console's location matters as much as your download at the client, because the console is the one sending video. A gigabit-down / 20-up cable plan will happily stream to your phone across town and choke trying to stream out to it. If your router is the bottleneck, that is a fixable problem; our 2026 gaming-router breakdown covers which boxes actually hold a low-jitter uplink under load.

Steps 1–12: The Remote Play Walkthrough

Everything above was setup for this. Twelve steps, start to first frame, roughly thirty minutes if your network cooperates. Each step includes the reason it exists, because a step you understand is a step you can debug. Do them in order; the sequence is not arbitrary.

The twelve-step sequence

1. Update the console. On the PS5, take any pending system update. Remote Play negotiates a protocol version between console and client; a mismatched, out-of-date console can register but then fail to hold a session. Why: half of "it connects then black-screens" is a version skew.
2. Enable Remote Play on the console. Settings > System > Remote Play > Enable Remote Play. Why: the feature is off by default on many setups; the app will discover nothing until this is on.
3. Turn on rest-mode networking. Set both Stay Connected to the Internet and Enable Turning On PS5 from Network as shown in the prerequisites block. Why: so the console is reachable and wakeable when it is asleep, which is how you will use it 90% of the time.
4. Wire the console if you can. Run an Ethernet cable from the PS5 to the router. Why: the console is the uplink; a wired console removes the single biggest source of jitter and packet loss from the entire chain. Everything downstream benefits.
5. Install the client app. Put the latest PS Remote Play app on your PC, Mac, or phone (or grab Chiaki-ng for Linux — see below). Why: stale builds are rejected by the handshake; the app self-updates for a reason.
6. Sign in with the matching account. Log the client into the same PSN account that owns the console. Why: registration is account-scoped; a mismatched login is the number-one cause of "my console never shows up."
7. Connect the controller. Plug a DualSense into the PC/Mac over USB, or Bluetooth-pair it to a phone (Android 12+ for DualSense). Why: pairing the pad before the session avoids the client grabbing keyboard/touch input as a fallback and confusing you.
8. Pair the devices on the same network. For first-time registration, keep client and console on the same LAN. The app will auto-discover the console, or you enter the 8-digit code from Settings > System > Remote Play > Link Device. Why: local registration is far more reliable than doing the initial handshake across the internet.
9. Launch the session. Select the console in the client and connect. The console wakes (if asleep) and a live picture appears. Why: this is your baseline; confirm it works locally before you complicate anything.
10. Verify the connection quality. Run the console's own Test Internet Connection and note your speeds and NAT type (expected output below). Why: you want the numbers before a session goes bad, so you can tell what changed.
11. Set resolution and frame rate in the client. In the app's settings, choose your resolution and frame rate to match your bandwidth (1080p/60 if you cleared ~15 Mbps, 720p if not). Why: the client defaults are conservative; you are trading bitrate for smoothness deliberately, not blindly.
12. Test off-network. Disconnect the client from your home Wi-Fi, put it on cellular or a friend's network, and reconnect. Why: this proves WAN traversal works; if it fails only off-network, you have a NAT/port problem, not a Remote Play problem — jump to the network section.

What a successful connection looks like

Before you trust a session, run Settings > Network > Connection Status > Test Internet Connection on the console. A healthy result looks roughly like this — the exact speeds vary, but the sign-in and NAT lines are the ones to read:

Internet Connection ................. Connected
IP Address Acquisition .............. Successful
Internet Connection ................. Successful
PlayStation Network Sign-In ......... Successful
Download Speed ...................... 184.2 Mbps
Upload Speed ........................  41.7 Mbps
NAT Type ............................ Type 2

NAT Type 2 is what you want — it means the console can open the connections Remote Play needs without you touching the router. Type 3 is the warning sign: a strict NAT that will connect locally and then fail the moment you try to reach the console from outside the house. If you see Type 3, the network-tuning section is not optional for you.

Where the sequence usually breaks

Nine times out of ten the break is at step 6 (wrong account), step 8 (client and console on different subnets — a guest Wi-Fi network, a mesh node in "isolation" mode, or a VPN silently rerouting one device), or step 12 (strict NAT killing WAN play). None of those are Remote Play bugs; they are network topology telling you the truth. If step 9 gives you a picture but the audio is out of sync or the frame rate collapses under motion, that is a bandwidth problem, and you drop the resolution at step 11 rather than fighting the codec. Keep the twelve steps as your bisection tool: the first one that fails tells you which section to read next.

Network Tuning, Ports, and Wi-Fi

Remote Play lives or dies on the network, and the network has three levers: the radio your client uses, the path between the two devices, and — for internet play — whether your router will let an outside connection find the console. Pull them in that order.

Wired console, 5 GHz client

The ideal topology is boring and effective: console on Ethernet, client on 5 GHz Wi-Fi. The console is transmitting a compressed video stream continuously, so it is the device that most rewards a wired link — no contention, no roaming, no interference. The client only needs a clean 5 GHz channel; the 2.4 GHz band is a swamp of microwaves and neighbors and will introduce the exact micro-stutters that make a stream feel worse than the numbers suggest. If your handheld or phone keeps drifting onto 2.4 GHz, lock it to the 5 GHz SSID. Mesh systems are fine as long as the client is not being handed between nodes mid-session and "client isolation" / "AP isolation" is turned off — that setting exists to stop devices talking to each other, which is precisely what Remote Play needs to do.

Ports and NAT for internet play

On the same LAN, you never touch ports — discovery and connection just work. Port forwarding only matters for WAN play, when the client is on a different network and needs to reach your console across the internet. Remote Play uses a small, well-documented set of ports; forward them to the console's static LAN address (set a DHCP reservation first, or the forward will point at the wrong device after the next lease renewal):

# PS Remote Play — router port-forward (WAN play only)
# NOT required on the same LAN. Forward to the PS5's reserved IP, e.g. 192.168.1.42

Protocol   Port(s)        Purpose
--------   ------------   ------------------------------------
TCP        9295           Control / registration handshake
UDP        9296           Session
UDP        9297           Audio / video stream
UDP/TCP    9295-9304      Fallback range if the defaults are busy
UDP        8572           Console discovery (LAN)

If your console reported NAT Type 3 in the connection test, forwarding these ports (or, less surgically, enabling UPnP so the console can request them itself) is what moves you toward Type 2 behavior for outside connections. Do not forward ports and leave UPnP on for the same service — pick one, or they fight. Carrier-grade NAT (common on some fiber and all mobile-home-internet plans) can make WAN Remote Play impossible no matter what you forward, because you do not own a public IP to forward to; that is an ISP conversation, not a router setting.

Bitrate, resolution, and the honest trade

Inside the client, resolution and frame rate are a direct bandwidth trade, not a free quality dial. At ~15 Mbps steady you can hold 1080p/60. Below that, 720p/60 will feel dramatically better than a starved 1080p, because a stream that runs out of bits does not politely lower detail — it smears, blocks, and drops frames under motion. The console's hardware encoder is fixed-function and fast, so the limiting resource is almost always the link, not the silicon. If you are streaming to a small handheld screen anyway, 720p is nearly indistinguishable and buys you a huge stability margin. Save 1080p for when you are casting to a laptop or a TV and you have the upstream to feed it.

The Open-Source Route: Chiaki-ng

Sony ships an official Remote Play app for Windows, Mac, iOS, and Android — and pointedly not for Linux, which means not for the Steam Deck, not for a desktop running a sane operating system, and not for the handheld you actually want to use. The community fixed that years ago. The answer is Chiaki-ng, the maintained next-generation fork of the original Chiaki, and it is the single best reason a retro-minded handheld owner should care about any of this.

Why Chiaki-ng exists

Chiaki is a free, open-source Remote Play client that reverse-engineered Sony's protocol and reimplemented it for platforms Sony ignores: Linux, FreeBSD, OpenBSD, Android, macOS, Windows, and even the Nintendo Switch. The original project (by thestr4ng3r) is in maintenance mode; Chiaki-ng — "ng" for next-generation, formerly known as chiaki4deck — is where active development lives, on the 1.10 series as of mid-2026, with ongoing work on streaming quality, congestion control, and HDR. Point it at a Steam Deck and you have, functionally, a PlayStation Portal that also runs your entire emulation library — which reframes the whole "do I buy a Portal" question. If you are weighing that hardware decision, our ROG Ally X vs Steam Deck OLED comparison and the broader Switch 2 vs Steam Deck piece are the context; a Deck that also does Remote Play is doing a lot for one price.

Install and register

On a Steam Deck or Linux desktop, the Flatpak is the path of least resistance. Install it, launch it, and register against your console (which must be awake or in rest mode on the same network for the first pairing):

# Steam Deck / Linux — install via Flathub
flatpak install flathub io.github.streetpea.Chiaki4deck
flatpak run io.github.streetpea.Chiaki4deck

# Confirm the client can see your console (Standby = rest mode, ready to wake)
$ chiaki discover -h 192.168.1.42
* Discovered host:
  State:                 Standby
  Host Addr:             192.168.1.42
  Host Type:             PS5
  Host Name:             PS5-042

Registration needs two things from you: your PSN Account ID (Chiaki-ng can look it up from your online ID) and a registration PIN the console generates under Settings > System > Remote Play > Link Device. Enter both once and the client stores the credentials; after that it wakes and connects on its own. The exact Flatpak application ID and the current registration flow are documented on the project's releases page — always cross-check it there rather than trusting a number in a blog post, this one included.

Config-file tuning

Where the official app gives you a dropdown, Chiaki-ng gives you a config file and real knobs — resolution, frame rate, a hard bitrate override, audio buffer size, and which hardware decoder to use (VAAPI on the Deck). A representative profile for a Deck on a strong 5 GHz link looks like this; treat the keys as illustrative and confirm the current names against the docs:

# Representative Chiaki-ng profile (verify keys in the official docs)
[settings]
video_resolution=1080p
video_fps=60
video_bitrate=15000      ; kbps — raise only if your link is rock-solid
audio_buffer_size=9600   ; larger = smoother audio, slightly more delay
hardware_decoder=vaapi   ; Steam Deck / most Linux GPUs

The Chiaki-ng documentation is the authority on the exact configuration keys, HDR setup, and per-platform decoder options; it is maintained, unlike most of what a search will surface. The video_bitrate override is the killer feature — the official app hides its bitrate ceiling, and Chiaki-ng lets you push past it when your network can take it, or clamp it down when it cannot.

PlayStation Portal and Cloud Streaming

The PS Portal started life as a Remote Play appliance — a screen bolted between two DualSense halves whose only job was to stream from your PS5. Over roughly eighteen months of firmware it grew into something else. This is the timeline that matters, because each update changed what the device fundamentally is.

The beta history: November 2024 to November 2025

Cloud streaming on the Portal arrived in beta on November 19, 2024, announced on the PlayStation Blog — the first time the device could run a game without your PS5 doing anything. The beta was rough and honest about it: streams topped out at 1080p/60, a 1080p stream wanted at least 13 Mbps and 720p at least 7 Mbps, and a long list of features were simply missing, including the Create button, 3D audio, party voice chat, game invites, and anything you had bought outright on the PS Store rather than gotten through the catalog.

On April 9, 2025 Sony filled in some of the gaps: Game Sorting (by recently added, name, or release date), a Queue System that shows an estimated wait when the streaming servers are full, an inactivity warning after ten minutes, and Capture Gameplay — the Create button finally went live during cloud sessions, auto-uploading screenshots and clips to the cloud, viewable in the PlayStation App under Library > Captures, and held for 14 days. (Note the detail the marketing glosses: those captures expire. Fourteen days, then gone.)

The November 5, 2025 cloud launch

Cloud streaming left beta on November 5, 2025 (6pm PT), and this is the update that turned the Portal into a standalone handheld. For PlayStation Plus Premium members it opened up not just the catalog but thousands of eligible digital PS5 games from your own library — streamed from the cloud with the console off. The launch lineup Sony highlighted was Astro Bot, Borderlands 4, Final Fantasy VII Rebirth, Fortnite, Ghost of Yōtei, Grand Theft Auto V, and Resident Evil 4, plus catalog titles like Cyberpunk 2077, God of War Ragnarök, Hogwarts Legacy, and The Last of Us Part II Remastered. (If you have seen this update credited with streaming "Spider-Man and WWE 2K25," that is a garbled retelling — the official list is above.) The same update refreshed the home screen into three tabs — Remote Play, Cloud Streaming, and Search — added 3D audio, and let you set a device passcode. The two modes now live side by side on one screen, which is exactly why people confuse them.

March 17, 2026: 1080p High Quality

The most recent piece is the March 17, 2026 firmware (March 18 in CET/JST), which added a 1080p High Quality mode. It is not a resolution bump — the Portal already did 1080p — it is a bitrate bump. In Sony's own words, it "enables players to enjoy games at a higher bitrate compared to the default 1080p Standard mode, providing a smooth and high-fidelity experience." You enable it mid-session:

# PlayStation Portal — enable the higher-bitrate mode
[Quick Menu] > [Max Resolution] > [1080p High Quality]
# then restart the Remote Play or Cloud Streaming session to apply

# Network: 5 Mbps minimum, 15 Mbps recommended

Critically, this mode works for both Remote Play and Cloud Streaming — it is a quality tier, not a mode toggle — and it requires restarting the session to take effect. The same update brought UX refinements: better game-bundle detail pages, on-screen game-invite notifications, richer trophy pop-ups with platinum animations, an instant on-screen keyboard in search, and QR-code account creation. The bandwidth guidance is unchanged from the app at large: 5 Mbps to function, 15 Mbps to actually enjoy it.

5 Common Pitfalls (and Fixes)

These are the failures that generate the most wasted hours. Each has a real cause and a real fix; none of them require reinstalling anything, which is usually the first bad advice you will be given.

Network and discovery pitfalls

Pitfall 1 — Console invisible after it sleeps. You connect fine with the TV on, then it vanishes. Cause: rest-mode networking is off. Fix: enable both Stay Connected to the Internet and Enable Turning On PS5 from Network. This is the single most common Remote Play complaint and it is a two-toggle fix.

Pitfall 2 — Works on Wi-Fi, dies on cellular. Local sessions are perfect; the moment you leave the house it fails. Cause: strict NAT (Type 3) or carrier-grade NAT blocking the inbound path. Fix: reserve a static LAN IP for the console and forward TCP 9295 / UDP 9296–9297, or enable UPnP. If your ISP uses CGNAT, no port forward will save you — that is a plan or router-mode change.

Account and pairing pitfalls

Pitfall 3 — "No console found" during registration. Cause: the client is signed into a different PSN account than the console, or the two devices are on different subnets (guest network, VPN, or AP isolation). Fix: match the account exactly and put both devices on the same primary SSID with client isolation off for the initial pairing.

Pitfall 4 — Cloud game you own will not stream. You bought the game, it is right there, and cloud refuses. Cause: cloud streaming is Premium-only and limited to eligible titles — a game you purchased on the PS Store is not automatically stream-eligible, and physical discs never are. Fix: confirm PS Plus Premium and check the title's cloud eligibility; if it is not eligible, use Remote Play from your own console instead, which has no such restriction.

Audio, controller, and capture pitfalls

Pitfall 5 — Controller not recognized, or audio desync. Cause on mobile: a DualSense on an Android version below 12 (or a DualSense Edge below 14) will not pair. Cause on desktop: Bluetooth flakiness during registration. Fix: use USB for the first pairing on PC/Mac, update Android, and if audio drifts, raise the audio buffer (in Chiaki-ng) or drop resolution to free bandwidth for the audio channel. And remember Portal cloud captures self-delete after 14 days — pull anything you want to keep into the PS App and save it locally before it evaporates. If you are recording seriously rather than grabbing the odd clip, a dedicated capture card off the console output is the better tool; see our PS5 capture-card guide for what actually records 4K60.

Troubleshooting: 10 Errors in a Table

When a session fails, the error code is usually less useful than the symptom. This table maps what you actually see to the cause and the fix. Work top to bottom — the earlier rows are the more common failures.

How to read the table

Most Remote Play errors are network or account problems wearing a hexadecimal costume. The codes (the 0x and 8xxx strings) are internal and Sony rarely documents them precisely, so match on the symptom column first. If a fix says "see network tuning," it means the problem is your router or ISP, not the app.

The table

When to stop troubleshooting the app

If you have matched accounts, wired the console, cleared 15 Mbps both ways, and it still fails only over WAN, the problem is upstream of anything you can fix in the app — it is your ISP's NAT or a blocked port on hardware you do not control. That is the moment to stop reinstalling and start reading the router. And if the console itself is behaving strangely — corrupt database, storage errors bleeding into network flakiness — a safe-mode database rebuild is a legitimate reset that does not touch your games; our PS5 cache-clear walkthrough covers the safe way to do it.

Advanced Tips: Bitrate, Codecs, HDR

Once the basics work, there is a second tier of quality most people never touch because the official app hides the controls. This is where Chiaki-ng and the 2026 firmware earn their keep.

Prefer H.265 where you can decode it

Remote Play can encode in H.264 or H.265 (HEVC). HEVC is roughly twice as efficient — the same visual quality at a lower bitrate, or better quality at the same bitrate — which is exactly what you want on a constrained uplink. The catch is decode support on the client: modern Apple Silicon Macs, recent iPhones, and current Android flagships decode HEVC in hardware, but older or cheaper clients fall back to H.264 and eat the bitrate penalty. On Chiaki-ng, the decoder is explicit in your config (VAAPI on the Steam Deck); pick the hardware path and let the GPU do the work, or you will burn battery and add latency decoding in software.

Push the bitrate the official app hides

The stock PS Remote Play app makes bitrate a black box tied to its resolution presets. Chiaki-ng exposes it directly via video_bitrate, and on the Portal the March 2026 1080p High Quality mode is Sony's version of the same idea — a higher-bitrate tier you opt into via [Quick Menu] > [Max Resolution]. The rule is the same in both places: raise the bitrate only as far as your steady, worst-case uplink supports, not your speed-test peak. A stream tuned to your peak will look glorious for ten minutes and then fall apart when your upload dips under load. Tune to the floor, not the ceiling.

HDR, off-network play, and expectations

Chiaki-ng has been adding HDR support, and it can look genuinely good on an OLED handheld — but HDR increases the data you are shipping, so it competes directly with your bitrate budget. On a marginal connection, SDR at a higher effective bitrate beats HDR that is starved for bits. For off-network play over cellular, accept that you are at the mercy of your upload at home and the mobile network's jitter; 720p with a conservative bitrate is the configuration that actually holds up on a train, not 1080p High Quality. Set expectations by the weakest link in the chain, which on the road is almost never the console.

The Complete Working Configuration

Here is the whole thing in one place — every setting that matters, on both ends, that this article has argued for. If you copy nothing else, copy this. It is the configuration that gets a stable 1080p session on a competent home network and degrades gracefully when the network is not.

Console-side recap

########## CONSOLE (PS5) ##########
Settings > System > Remote Play
    Enable Remote Play ............................ ON
    Link Device ................................... use 8-digit code / PIN

Settings > System > Power Saving > Features Available in Rest Mode
    Stay Connected to the Internet ................ ON
    Enable Turning On PS5 from Network ............ ON

Network
    Connection .................................... WIRED (Ethernet)
    NAT Type (target) ............................. Type 2
    Reserved LAN IP (for WAN play) ................ e.g. 192.168.1.42

Client-side and network recap

########## CLIENT ##########
App ....... PS Remote Play (latest) — or Chiaki-ng 1.10.x on Linux/Deck
Windows ... Win 10/11 64-bit, 7th-gen Intel Core+, 2 GB RAM, 100 MB, USB
Mobile .... Android 12+ for DualSense (14 for DualSense Edge); recent iOS
Account ... SAME PSN account as the console (non-negotiable)
Controller. DualSense via USB (desktop) or Bluetooth (mobile)
Wi-Fi ..... 5 GHz band; AP/client isolation OFF; same SSID for pairing

########## STREAM ##########
Resolution ... 1080p if steady ~15 Mbps up/down, else 720p/60
Portal HQ .... [Quick Menu] > [Max Resolution] > [1080p High Quality]
Codec ........ HEVC (H.265) if the client decodes it in hardware
Bandwidth .... 5 Mbps min / 15 Mbps recommended; 13 Mbps floor for 1080p

########## WAN (optional) ##########
Port-forward to console IP: TCP 9295, UDP 9296-9297 (fallback 9295-9304)
CGNAT present? WAN Remote Play will not work — ISP fix required

The verdict

Remote Play, configured this way, is one of the quietly best features PlayStation ships and one it markets almost not at all. It turns any screen you own into a window onto your console, for free, with no subscription and no catch beyond the network. Cloud streaming is the flashier, more constrained cousin — genuinely useful on a Portal when your PS5 is off and you have Premium, genuinely irrelevant if you own the console and can just wake it. Keep the two straight, wire the console, feed it 15 Mbps, and put Chiaki-ng on whatever handheld you already carry. That last move — a Steam Deck that also does Remote Play — is the one that makes the whole PS Portal proposition look optional, which, for a lot of people, it is.