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

Remote Play is the oldest good idea Sony has ever shipped and then ignored. It has been sitting in the firmware since the PSP, quietly promising that the console under your television could be played from anywhere, and for roughly fifteen years it delivered on that promise the way a vending machine delivers on the promise of a hot meal: technically, joylessly, and only if you didn't look too closely. That changed in 2025 and 2026. The native feature Sony has carried since the PlayStation Portable in 2006 finally has the bitrate, the dedicated hardware, and the honest network assumptions to be a primary way to play rather than a party trick you demo once and forget.

This is the long version of the setup — the one that explains why each toggle exists instead of just barking at you to flip it. We will build a connection that holds 1080p at 60 frames per second, understand the ports before we open them, and identify which of Sony's defaults are quietly sabotaging you. If you already know the theory and just want the sequence, we keep a stripped-down field-manual checklist for the same twelve steps. Everyone else: sit down. There is more going on inside this feature than Sony's marketing has ever admitted, and understanding it is the difference between a stream that feels like the game and a stream that feels like a hostage video.

Remote Play, Demystified

Before you touch a single setting, you need to know what this feature actually is, because Sony sells three different things under adjacent names and the confusion costs people entire evenings. Remote Play is not cloud gaming. It is not screen mirroring. It is your own console, in your own house, acting as a private game server for a screen somewhere else. Everything downstream of that sentence — the ports, the bandwidth math, the Ethernet zealotry — follows from it.

A Twenty-Year-Old Idea That Finally Loads

The lore is longer than most people realize. Remote Play debuted on the PSP in 2006 as a way to fling PS3 media and a thin sliver of games to the handheld over Wi-Fi. It was the headline pitch of the PS Vita in 2011 and, briefly, the entire reason to own one. The PS4 generation made it genuinely usable for the first time, and in 2016 Sony broke it out of the handheld ghetto entirely by releasing the PS Remote Play app for Windows PCs and macOS. In 2019 it landed on all Android and iOS devices worldwide, and in early November 2020 — just before the console's launch on November 12 — the app learned to stream the PS5.

Here is the part that matters as a matter of policy, and The Machine reads the fine print so you don't have to: Sony mandates Remote Play support. Every PS4 and PS5 game is required to function over Remote Play, with a single carve-out for titles that depend on peripherals the stream can't carry — chiefly PlayStation Move. That mandate is why your library, unlike a cloud catalog, is not a curated subset. If it runs on the console, it streams. Full stop.

What Remote Play Is Not

Cloud streaming — the PS Plus Premium tier, and the Portal's newer standalone mode — runs the game on Sony's servers in a data center and pipes the result to you. Your console can be unplugged. Remote Play is the opposite: your PS5 does the rendering, and the pixels travel from your living room to your hands. The distinction is not academic. Cloud streaming's latency and image quality are governed by Sony's infrastructure; Remote Play's are governed entirely by your network, which means you can actually fix them. It also means one hard limitation we will return to repeatedly: while you are Remote Playing, the console is yours and only yours. Nobody else can use it, and neither can you, for anything else.

Why 2025 and 2026 Were the Turning Point

For years the honest verdict on Remote Play was "impressive that it works at all." Then Sony shipped a system software update for the PlayStation Portal — the dedicated streaming handheld it launched in 2023 — that added a proper 1080p High Quality mode with a meaningfully higher bitrate. Reviewers who had spent two years politely calling the Portal "fine" suddenly measured input delay dropping and image clarity that, for the first time, looked crisper than the cloud streaming sitting right next to it. As of 2026 the pipe is wide enough that even a PS5 Pro's ray-traced, PSSR-reconstructed versions of games arrive on the Portal intact. That is a genuinely different product than the one that shipped, and it is why this tutorial exists in 2026 rather than being a historical footnote about a feature nobody used while they waited for the next console generation to slip further into the future.

Prerequisites & Bandwidth

Remote Play fails at the prerequisites stage more often than at any other. People skip straight to "install app, hit connect," the connection stutters, and they blame Sony. Nine times in ten the problem was decided before the app opened, by hardware and bandwidth choices made months earlier. Read this section like a pre-flight checklist, because that is what it is.

The Console Side

You need a PS5 (any variant — the launch model, the Slim, the Digital Edition, or the Pro) or a PS4 / PS4 Pro, running the latest system software. Update it before anything else; codec support and Remote Play stability both ride on firmware, and an out-of-date console will negotiate a worse stream. If you own a PS5 Pro, its enhanced rendering — ray tracing and PSSR image reconstruction — is what gets streamed, so the Pro is the one console where the source quality genuinely exceeds 1080p and benefits most from the High Quality pipe.

You also need a PlayStation Network account signed in on the console, and you want that console set as your primary system with Console Sharing enabled. This is the difference between the client waking a sleeping console cleanly and the client staring at a "can't find your console" error because the account handshake never completed. One DualSense (or DualShock 4 for PS4 streams) is assumed; the stream carries controller input, haptics, and adaptive-trigger data where the client supports it.

The Client Side

Pick your receiver. The official PS Remote Play app runs on Windows 10 and 11 (64-bit), macOS 11 Big Sur or later, and current releases of Android and iOS / iPadOS. Grab it only from Sony's own domain — the download link above — and not from a mirror, because a man-in-the-middle on a remote-control app is exactly the kind of thing you do not want. The PlayStation Portal is the appliance option: no OS to maintain, DualSense controls molded around a screen, purpose-built for exactly this. And for the tinkerers, there is chiaki-ng, the open-source client that runs on Linux, the Steam Deck, macOS, Windows, Android, and even the Nintendo Switch. We cover it in depth later; for now, just know it exists and it is legitimate.

The Network Floor

Sony's published minimum is 5 Mbps of broadband, with at least 15 Mbps recommended for a good experience. For the Portal specifically, Sony recommends roughly 13 Mbps for a stable 1080p connection. Treat 5 Mbps as the number below which you should not bother, 13–15 Mbps as the target, and remember that these figures apply at both ends and in both directions. The bottleneck at home is almost always upstream bandwidth at the console's location, because consumer connections are asymmetric and the PS5 has to send the whole stream. And then the rule that every 2025 and 2026 review repeats until it stops sounding like advice and starts sounding like scripture: hardwire the PS5 to the router or modem with Ethernet. It is non-negotiable. We will explain why in the network section, but do not argue with it now.

How It Works Under the Hood

You can set up Remote Play without understanding any of this, the same way you can drive without knowing what a differential does. But when it breaks — and over the internet it will, at least once — the people who understand the handshake fix it in minutes and the people who don't file a support ticket. Here is the whole machine in three moving parts.

Discovery, Registration, and the Stream

A Remote Play session has three phases, and each uses different ports. Discovery: the client shouts on the local network over UDP 9302 and the console answers with its name, type, and power state. Registration: the first time a client pairs, it exchanges cryptographic keys with the console over TCP 9295 using an eight-digit code you read off the console screen — this produces a stored credential so you never re-enter the code. Streaming: the live session runs over UDP 9296 and 9297, with UDP 8572 also involved in establishing the connection to the console or mobile device. If those primary ports are contested, Remote Play can roam within the 9295–9304 range on both TCP and UDP. Memorize the shape of this even if you forget the numbers: discover, register once, then stream.

Codecs and the Bitrate Ladder

The stream is hardware-encoded H.264 or, on the PS5's HDR and high-quality paths, H.265 / HEVC — the more efficient codec that fits more image into the same bandwidth. Resolution and frame rate set a target bitrate, and the "High Quality" modes are, functionally, just permission to spend more bits: the Portal's 1080p High Quality raises the ceiling well above 1080p Standard, and open-source clients routinely push 30,000 Kbps (30 Mbps) for a PS5 HDR stream. Every bit you add improves the picture and adds a hair of latency to the encode-transmit-decode chain. The entire art of tuning Remote Play is finding the highest bitrate your worst network moment can carry without the buffer running dry.

Same Room Versus Other Continent

On the same local network, none of the WAN complexity applies. Discovery works by broadcast, the ports never leave your router, and latency is sub-millisecond — this is the mode where Remote Play feels indistinguishable from playing on the couch, and it is where you should always test first. The moment you leave the house, everything changes: the client can no longer broadcast to find the console, so it relies on a stored registration and Sony's own connection-brokering to punch through both routers' NAT. Sony's app is good enough at this that most people never forward a port. Open-source clients and hostile network setups are less forgiving, which is the entire reason the ports above matter.

The 12-Step Walkthrough

This is the core of the tutorial. Twelve steps, each with the reason it exists, taking you from a cold console to a validated 1080p session in about half an hour. Do them in order. The ordering is not decorative — several steps only work because an earlier one set them up, and skipping around is the single most common way people brick their first attempt.

The Full Sequence

1. Update the PS5 system software. Settings, System Software, System Software Update and Settings, then install anything pending and reboot. Remote Play's codecs, bitrate ceilings, and connection logic all live in firmware; an outdated console negotiates a worse stream and may not expose the newest quality modes at all.
2. Enable the feature. From the home screen: Settings, System, Remote Play, and turn on Enable Remote Play. It is off by default and set per user, so the toggle has to be flipped under the account you will actually stream with. You only do this once per user, per console.
3. Set the console as primary and enable Console Sharing and Offline Play. Settings, Users and Accounts, Other, Console Sharing and Offline Play, Enable. This tells the console it may serve your account to a remote client without a fresh interactive login every time — the difference between waking cleanly and failing the account handshake.
4. Configure Rest Mode. Settings, System, Power Saving, Features Available in Rest Mode, then turn on both Stay Connected to the Internet and Enable Turning On PS5 from Network. Without these, a sleeping console is invisible and un-wakeable, and roughly half of all "can't find console" reports die right here. While you are in there, set the power supply for USB ports and network to stay active.
5. Hardwire the PS5 with Ethernet. Run a cable from the console to the router or modem. Wi-Fi introduces jitter — variance in packet timing — and Remote Play tolerates jitter far worse than it tolerates a lower average speed. This is the step people skip and the step that fixes the most problems. Non-negotiable, as every current review insists.
6. Install the client. On PC or Mac, install the PS Remote Play app from Sony's download domain; on mobile, get it from the App Store or Google Play; on the Portal, there is nothing to install. Using the official client keeps the crypto handshake and updates on Sony's rails.
7. Sign in with the same PSN account. Launch the client and sign in with the exact account you enabled Remote Play under in step 2. Pairing credentials are bound to the account; a mismatched login will find the console and then refuse to connect, which looks like a network fault but isn't.
8. Pair the client. On the same network, the client discovers the console automatically. If it can't — different subnet, guest Wi-Fi, or a stubborn router — pair manually: on the console go to Settings, System, Remote Play, Pair Device, and enter the eight-digit code the console shows into the client. This writes the persistent registration so future sessions are one tap.
9. Attach a controller to the client. On PC connect a DualSense over USB or Bluetooth; on mobile, pair the controller in the operating system's Bluetooth settings first, before opening the app, or the game won't see it. The Portal has its controls built in. A stream with no input is just very expensive television.
10. Run the first session on the same LAN. Start Remote Play while both devices sit on your home network. This validates that the console, the pairing, and the client all work with the network variable removed. If it fails here, the problem is configuration, not bandwidth — and you have just saved yourself an hour of blaming your ISP.
11. Set resolution and frame rate. In the app: Settings, Video Quality for Remote Play, then Resolution to 1080p and Frame Rate to High. On the Portal: start a session, open the Quick Menu, choose Max Resolution, and select 1080p High Quality. This is where you claim the bandwidth you built the whole setup to afford.
12. Test over the internet and tune. Now leave the LAN — mobile data, a friend's Wi-Fi, the office — and connect again. Watch for stutter or macroblocking, and if you see it, step the resolution or frame rate down until the stream is stable, then step back up. The internet session is the real test; the LAN session was the rehearsal.

Expected Output: A Healthy First Connection

On the LAN test in step 10, a healthy setup connects in two to four seconds, shows a brief "Connecting…" then the live console screen, and — critically — feels immediate. To sanity-check the network underneath it, ping the console's local address from the client; on a wired LAN you want sub-2ms times and, more importantly, times that barely vary. Average latency is not the enemy. Jitter is.

$ ping 192.168.1.42          # your PS5's reserved LAN address
64 bytes from 192.168.1.42: icmp_seq=0 ttl=64 time=0.9 ms
64 bytes from 192.168.1.42: icmp_seq=1 ttl=64 time=1.1 ms
64 bytes from 192.168.1.42: icmp_seq=2 ttl=64 time=0.8 ms
64 bytes from 192.168.1.42: icmp_seq=3 ttl=64 time=1.0 ms
--- 192.168.1.42 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss
round-trip min/avg/max/stddev = 0.8/0.95/1.1/0.1 ms
# stddev 0.1 ms = almost no jitter. This is what "good" looks like.

For reference, here is the exact console-side settings state your first ten steps should have produced. Screenshot it, because you will want to confirm it after any firmware update quietly resets a toggle:

PS5 -> Settings -> System -> Remote Play
    [x] Enable Remote Play

PS5 -> Settings -> System -> Power Saving -> Features Available in Rest Mode
    [x] Stay Connected to the Internet
    [x] Enable Turning On PS5 from Network

PS5 -> Settings -> Users and Accounts -> Other -> Console Sharing and Offline Play
    [x] Enable

Per-Platform Notes

On Windows, the first launch triggers a Windows Defender Firewall prompt — allow it on private networks or discovery silently fails. On macOS, grant the app any permission it asks for at first run so the controller is recognized. On mobile, the app can stream over cellular data, but you must toggle that on and accept that carrier upstream and NAT are wildcards; pair your controller in the OS before opening the app, every time. A PS4 used as a client to stream a PS5 is supported and genuinely useful for a second room, but the older hardware caps quality below what a modern phone manages. Sony documents each platform's quirks in its official Remote Play settings pages, which are worth a bookmark.

Portal & 1080p High Quality

The PlayStation Portal is the reason this article is a tutorial and not an obituary. When it launched in 2023 it was a competent but unremarkable 8-inch screen bolted between two halves of a DualSense, streaming at a resolution Sony was cagey about and a latency reviewers described with words like "acceptable." The 2026 software changed the verdict, and it did so with a single mode buried one menu deep.

What Update 7.0 Actually Changed

In March 2026 — the 17th in PDT, rolling into the 18th once you cross into CET and JST — Sony pushed system software version 7.0 to the Portal. The headline was a 1080p High Quality mode that raises the streaming bitrate above the default 1080p Standard, joined by QR-code login and a handful of interface refinements. A follow-up, 7.0.2, arrived on April 8, 2026 with minor fixes. The practical result, per hands-on testing across 2026, is that input delay dropped and the image became visibly crisper — for the first time sharper than the Portal's own cloud streaming sitting right beside it. That is the sentence that reversed two years of tepid reviews.

Turning On 1080p High Quality

It is not on by default, which is Sony's polite way of not overselling your bandwidth. During any Remote Play or Cloud Streaming session, open the Quick Menu and change Max Resolution.

PS Portal -> start a Remote Play session -> press [PS] for the Quick Menu
Quick Menu -> Max Resolution -> [1080p High Quality]

# Requires ~13 Mbps sustained; Sony recommends 15 Mbps for headroom.
# [1080p Standard] uses a lower bitrate -- that is the soft, "cloudy" look
# people mistake for a hardware limit. It is a menu setting, nothing more.

If the stream can't hold it — if you see the bitrate collapse into blocky mush during busy scenes — drop back to Standard. High Quality is a claim on bandwidth you have to actually possess. On a hardwired PS5 feeding a Portal on solid 5GHz Wi-Fi, most connections above 15 Mbps hold it comfortably.

The One-Console Tax

Here is the limitation nobody puts on the box, and The Machine will not let you discover it the hard way: a Remote Play session on the Portal cannot share the PS5. While you are streaming, the console is dedicated entirely to you. Nobody in the house can play it locally, it won't sit on the home screen for a roommate, and you cannot use it for anything else in parallel. If your household needs one person on the TV and another on the handheld, Remote Play is the wrong tool — that is a two-console problem, or a job for a capture card feeding a second display. Remote Play moves the single console around the house; it does not clone it.

Network Tuning: Ports & QoS

If the walkthrough got you a working LAN session and a shaky internet one, this is where you fix the internet one. Everything here is optional for same-network play and increasingly mandatory the further and harsher the network path becomes.

Hardwire the Console, Not Just the Client

We keep saying it because it keeps being the answer. The PS5 is the sender; it has to push a continuous, timing-sensitive UDP stream, and Wi-Fi's variable latency turns that stream into a slideshow during interference. Wire the console. If the client is stationary too — a desktop PC, a Portal in a fixed spot — wire or 5GHz that as well, and if you have Wi-Fi 6E, the 6GHz band is nearly interference-free and ideal for the client end. The asymmetry is the point: a wired console with a wireless client beats a wireless console with a wired client every single time, because the encode-and-send side is where jitter does the most damage.

Ports to Open (Only If You Leave the LAN)

On the same network you never touch this. For connections from outside your home, give the PS5 a static address (a DHCP reservation on its MAC is cleaner than a manual IP) and forward these to it. Most people find Sony's relay punches through without any of it — try first, forward only if the internet session refuses to connect.

# Router port-forward table -> destination = PS5's reserved LAN IP
# Needed ONLY for Remote Play from outside your home network.
TCP  9295          # registration / control channel
UDP  9296          # streaming
UDP  9297          # streaming
UDP  9302          # console discovery
UDP  8572          # session connect (console + mobile)
# If 9295-9297 are contested, Remote Play may roam 9295-9304 (TCP + UDP).

On the client PC, make sure the local firewall isn't dropping the return traffic. On Windows, an elevated Command Prompt and two rules cover it:

:: Run in an elevated Command Prompt on the client PC
netsh advfirewall firewall add rule name="PS Remote Play UDP" dir=in action=allow protocol=UDP localport=9296-9297
netsh advfirewall firewall add rule name="PS Remote Play TCP" dir=in action=allow protocol=TCP localport=9295

QoS, Upstream, and the Double-NAT Trap

Two things quietly murder internet Remote Play. The first is upstream bandwidth at the console's house — asymmetric plans give you generous download and stingy upload, and Remote Play needs the upload. You want roughly 15 Mbps up where the PS5 lives; check it, because it is usually far lower than the download figure people quote. If your router supports Quality of Service, prioritize the PS5's MAC address so a housemate's backup doesn't starve your stream. The second killer is double NAT or carrier-grade NAT (CGNAT): if your ISP hands you a shared, non-routable address, or you run a router behind the ISP's router, inbound connection-brokering can fail outright. Check the console's NAT type in Settings, Network, Connection Status; a Type 3 is a warning sign. The fix is bridge mode on one of the two routers, or asking the ISP to take you off CGNAT. Enabling UPnP on the router lets the console request its own port mappings and sidesteps a lot of this automatically.

Five Pitfalls (and Fixes)

These are the traps that account for the overwhelming majority of Remote Play misery. None of them are exotic. All of them are things Sony's setup flow will happily let you walk into without a word of warning.

Network Pitfalls

Pitfall 1 — Wi-Fi on both ends. The most common failure and the easiest fix. Two wireless hops means jitter stacked on jitter, and the stream buffers itself to death. Fix: Ethernet the console, always; wire or 5GHz/6E the client. If both ends are wireless and you refuse to change that, you have chosen a worse experience on purpose.

Pitfall 2 — Double NAT and CGNAT. Internet sessions that connect on the LAN but time out from outside are almost always a NAT problem, not a bandwidth one. Fix: check NAT type, put one router in bridge mode, enable UPnP, and if your ISP uses CGNAT, call them — no amount of port forwarding beats an address that isn't routable.

Configuration Pitfalls

Pitfall 3 — The Rest Mode trap. If "Stay Connected to the Internet" and "Enable Turning On PS5 from Network" are off, a sleeping console cannot be found or woken, and you get a "can't find console" error that looks like a network fault. Fix: enable both, under Features Available in Rest Mode, and set the power supply to stay active. This is step 4 for a reason.

Pitfall 4 — Wrong account or non-primary console. Pairing is bound to a PSN account, and a console that isn't set as primary with Console Sharing can refuse the remote handshake. Fix: sign the client in with the exact account you enabled Remote Play under, and enable Console Sharing and Offline Play on the console.

Client Pitfalls

Pitfall 5 — Controller not recognized on mobile. Open the app first, pair the controller second, and the game never sees the pad. Fix: pair the DualSense in your phone's Bluetooth settings before launching the app, every session. And the bonus sixth pitfall, because it is everywhere: HDR or a resolution the pipe can't carry. A black screen with working audio, or constant macroblocking, is often an HDR or bitrate mismatch. Fix: drop to 1080p Standard or 720p, disable HDR on the client, and on a PC update the GPU drivers so the hardware decoder is actually available.

Troubleshooting Table

When it breaks in the field, you want a lookup table, not an essay. Here is the one to keep. Match the symptom, apply the fix, escalate only if it doesn't take.

The Table

Decoding the Error Codes

Sony's error strings are famously unhelpful, but the pattern is learnable. Anything in the 8801xxxxx family during connection is, in practice, almost always a network reachability problem — ports, NAT, or a firewall eating the return traffic — and not a fault with the account or the console itself. The infamous 8801330d, in particular, resolves for most people the moment the ports are forwarded or the NAT type improves. Before you assume the worst, confirm the LAN session still works: if it does, the console and pairing are fine and you are chasing a WAN path problem, which narrows the search enormously.

The Reset Sequence

When individual fixes don't take, run this in order and stop as soon as it works: quit the client fully; put the PS5 into Rest Mode and pull power for thirty seconds to force a cold network stack; if problems persist, clear the PS5's system cache from Safe Mode, which resolves a surprising range of Remote Play flakiness with zero data loss; then re-pair the client from scratch with a fresh eight-digit code. Reserve rebuilding the database or a factory reset for the genuinely broken — they are rarely the actual fix and cost you an hour.

Advanced: Chiaki-ng

Sony's app is fine. It is also a locked box: you get the sliders Sony decided you get, and no more. For people who want to run Remote Play on hardware Sony never blessed — a Steam Deck, a Linux handheld, a Raspberry Pi — or who want direct control over bitrate, codec, and decoder, the answer is chiaki-ng. This is the advanced-tips section, and it is where Remote Play stops being an appliance and becomes a tool.

Why Chiaki-ng Exists

Chiaki is a free, open-source Remote Play client built by reverse-engineering the protocol. The original project is now in maintenance mode; active development moved to streetpea's chiaki-ng, the next-generation fork that carries the improvements and the ongoing support. It runs where the official app can't and gives you knobs the official app won't: manual bitrate, forced codec, explicit hardware-decoder selection, and tight Steam Input integration so the trackpads map to the DualSense touchpad. On a Steam Deck it turns the handheld into a superb PS5 client, waking the console and dropping you into a game straight from Gaming Mode. It is legal — it authenticates with your own account against your own console — and it is genuinely better than the official app in the hands of someone who wants to tune it.

Registering the Client

On a Steam Deck, switch to Desktop Mode, open the Discover store, search for chiaki-ng, and install the Flatpak (searching "chiaki4deck" still surfaces it, but "ng" is the current line). Elsewhere, grab a build from the GitHub releases. Registration mirrors the official flow — discover the console, then pair with the eight-digit code — but chiaki-ng also needs your PSN AccountID, which its built-in login helper retrieves for you.

# Steam Deck (Desktop Mode): install from Discover, then launch:
$ flatpak run io.github.streetpea.Chiaki4deck

# chiaki-ng discovers consoles on the LAN:
* Discovered console
    host:      192.168.1.42
    state:     STANDBY (rest mode)   -- or READY (powered on)
    host-type: PS5

# On the PS5:  Settings -> System -> Remote Play -> Pair Device
# Read the 8-digit code, enter it in chiaki-ng, click [Register].
# Use the built-in login helper to fetch your PSN AccountID first.

Tuning the Config File

Everything the GUI exposes lands in a plain-text config you can edit and version. On the Flatpak build it lives at the path below. Set 1080p and 60fps for a wired setup, fall back to 720p or 30fps on a shaky link, force H.265 for a PS5 HDR stream, and pick the hardware decoder your platform actually has — vaapi on Intel/AMD Linux, for example. The official chiaki-ng configuration docs enumerate every option and the recommended values per device.

# ~/.var/app/io.github.streetpea.Chiaki4deck/config/Chiaki/Chiaki.conf
[settings]
resolution=1080p          ; drop to 720p if Wi-Fi is unreliable
fps=60                    ; drop to 30 to survive a weak link
bitrate=30000             ; Kbps; leave blank for auto
codec=h265                ; HEVC; required for PS5 HDR
hw_decoder=vaapi          ; match your platform's decoder
audio_buffer_size=9600    ; raise if audio stutters

One extra step on the Steam Deck: apply a community controller layout (search "chiaki-ng" or "chiaki4deck" in the layout picker) so the back buttons and trackpads map sanely. Without it the touchpad is unusable and half your inputs go nowhere.

The Complete Configuration

Here is the whole thing in one place — the reference state a well-built Remote Play setup should be in. If you are debugging someone else's connection, or your own after a firmware update reshuffled a menu, diff reality against this and the discrepancy is usually your bug.

PS5-Side Checklist

System software:           latest (Settings -> System Software -> Update)
Remote Play:               ENABLED (per user)
Console Sharing:           ENABLED (Users and Accounts -> Other)
Rest Mode -> Stay Connected to the Internet:        ON
Rest Mode -> Enable Turning On PS5 from Network:     ON
Rest Mode power supply:    Always (USB + network active)
Network:                   WIRED Ethernet to router  <-- mandatory
NAT type:                  Type 1 or 2 (check Network -> Connection Status)

Router-Side Checklist

PS5 address:               DHCP reservation on the PS5 MAC (static)
QoS:                       prioritize the PS5's MAC address
UPnP:                      ENABLED (lets the console self-map ports)
Double NAT:                NONE (bridge mode if two routers)
# Port-forward to the PS5 ONLY for connections from outside the LAN:
TCP 9295 ; UDP 9296 ; UDP 9297 ; UDP 9302 ; UDP 8572
# Contended ports may roam within 9295-9304 (TCP + UDP).

Client-Side Reference Config

# Official PS Remote Play app
Resolution:    1080p        (Settings -> Video Quality for Remote Play)
Frame Rate:    High (60fps)
Controller:    DualSense, paired at the OS level before launch
Firewall:      allow the app on private networks

# PlayStation Portal (system software 7.0+)
Quick Menu -> Max Resolution -> 1080p High Quality   (needs ~13 Mbps)

# chiaki-ng (advanced)
resolution=1080p ; fps=60 ; codec=h265 ; hw_decoder=
Bitrate:       30000 Kbps for a wired PS5 HDR stream

Build that, wire the console, and Remote Play stops being the feature you forgot you paid for and becomes the one you use every day. The technology was always there — Sony has shipped it since 2006 and mandated it on every game since. What arrived in 2026 was the bitrate to make it honest and a handheld good enough to deserve it. The rest was never Sony's job to explain. It was ours.