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

Remote Play is not new. Sony has been throwing games off its consoles and onto second screens since the PSP could pull a PS3 signal across the living room, and every generation since has shipped some version of the same promise: your console is over there, your screen is over here, and the network in between is somebody else's problem. What changed in 2026 is not the idea. What changed is that Sony finally built hardware — the PlayStation Portal — that treats Remote Play as the entire reason the device exists rather than a checkbox buried three menus deep, and then spent a year patching it until the picture stopped looking like a JPEG left out in the rain.

This is the tutorial. Twelve steps, roughly half an hour if your router cooperates and considerably longer if it does not. By the end you will have a 1080p 60 fps stream running at the highest quality Sony currently ships, you will understand why the headline latency figure is technically true and functionally a lie, and you will have a fallback — the open-source chiaki-ng client — for the day Sony's servers decide your account looks suspicious. We are going to do this precisely, because Remote Play rewards precision and punishes hand-waving.

One warning before we start. Most of the numbers you will read elsewhere about this feature are either marketing rounded up to the nearest lie or forum guesswork rounded down to the nearest vibe. The figures here come from Sony's own release notes and the physics of video encoding, and where those two disagree, physics wins.

What Actually Changed in 2026

The March 17, 2026 Portal Update

On March 17, 2026 (PDT), Sony shipped a global system software update for the PlayStation Portal — system software 7.0.0 — whose headline feature was a 1080p High-Quality mode for Remote Play and Cloud Streaming sessions. The Portal already streamed at a nominal 1080p on its 8-inch, 60 Hz LCD, but 1080p describes a pixel count, not an amount of information. The old mode starved the encoder of bitrate, so the panel dutifully drew 1920 by 1080 pixels of mush: banding in dark scenes, foliage that dissolved into wet gravel, smoke and particle effects that looked like someone had wiped the lens with a thumb. High-Quality mode raises the bitrate ceiling so the HEVC encoder has enough bits to resolve detail in motion, which is exactly where the old path collapsed. Sony's release notes describe it as "higher bitrates and smoother visuals," which is marketing for "we stopped choking the pipe." The current Portal build as of writing is 7.0.2; if yours is on anything older, update it before you do anything else in this guide. The full changelog lives on the PlayStation Blog announcement, and the same update reached Japan a calendar day later per the Japanese-language blog post — timezones, not a staggered rollout.

Cloud Streaming Left Beta

The second change predates the calendar year but defines the 2026 experience. On November 5, 2025, Cloud Streaming on the Portal graduated from beta to a permanent feature. The practical difference is enormous: you can now stream thousands of digitally owned PS5 titles and the entire PS Plus catalogue with your PS5 console powered completely off — or without owning a PS5 at all, provided you carry a PS Plus Premium subscription. The old beta required a local console idling in rest mode for certain game types; that requirement is gone. Cloud Streaming is not Remote Play, though the two share a client. Remote Play beams your own console's output; Cloud Streaming rents Sony's hardware in a data centre. That distinction matters for latency, for which games are eligible, and for what happens to your save files, all of which we will get to.

What Remote Play Still Isn't

Remote Play is not latency-free, it is not a substitute for sitting in front of the console for anything genuinely twitchy, and — despite what a hundred breathless 2026 explainers imply — the Windows and macOS apps are not a new arrival. They have existed since the PS4 era, roughly 2016, and the 2026 updates simply keep them current. Nor does the Portal do everything the phone app does: the Portal is a Wi-Fi-only device streaming from a PS5 host only, while the mobile, Windows, and Mac apps happily stream from a PS4 as well. If your host is still a last-gen box, that is fine — the app path covers you — but the Portal will not talk to it. Keep that hierarchy in your head; half the "my Portal can't find my console" threads are people pointing an 8-inch PS5 accessory at a PS4.

Prerequisites: Hardware, Versions, Bandwidth

The Console (Host) Requirements

You need a host to stream from and a client to stream to. On the host side: a PS5 (any model — base, Slim, or Pro) running current system software, or a PS4/PS4 Pro if you are using the app rather than the Portal. The host should be on wired Ethernet. This is not a suggestion dressed as a rule; it is the single largest quality determinant in the entire chain, because a dropped upstream packet on the console side corrupts a frame for every client downstream of it. If you own a Pro, the encoder is the same silicon path as the base unit — Remote Play does not stream at Pro-enhanced resolutions, so the practical delta you read about in our PS5 Pro versus base PS5 breakdown largely evaporates once you are streaming 1080p to a handheld. The host also must be set as your primary console for the account, or remote wake and authentication get flaky. And if your host is a PS4, note that the box that outsold the Xbox One roughly two to one still does Remote Play perfectly well — just at H.264 rather than HEVC, which costs you some efficiency.

The Client Devices and App Versions

Clients, in rough order of how good the experience is: a PlayStation Portal on system software 7.0.x (7.0.2 at time of writing); the PS Remote Play app on Android 10 or newer (Google Play package com.playstation.remoteplay, published by PlayStation Mobile Inc.); the iOS/iPadOS app; the Windows app; and the macOS app. All of the store apps auto-prompt for updates — the desktop versions in particular will refuse to connect on a stale build, and the fix is simply to launch the app and follow the update prompt, per Sony's own PS Remote Play support page. There is an Android TV build too, and its 2026 revision added HDR video and high-frame-rate output when both the TV and the PS5 hang off an HDR-capable display; Sony documents the specifics on the Remote Play on Android TV support page. One hard limitation worth internalising now: you cannot run Share Play and Remote Play at the same time. They are mutually exclusive on the host, and the error you get when you forget is unhelpfully vague.

Bandwidth: 5 Mbps Floor, 15 Mbps Real

Sony's official minimum is a 5 Mbps broadband connection; its recommendation for a good experience, on both Wi-Fi and mobile data, is 15 Mbps. Treat 5 Mbps as the number below which the app refuses to try and 15 Mbps as the number below which 1080p High-Quality will either not engage or will engage and then thrash. These are symmetric concerns: the host needs upstream headroom, the client needs downstream headroom, and both need to measure it at the point of use, not at the speed-test server across town. Measure from the client's actual location on its actual Wi-Fi band before you blame the software:

$ speedtest-cli --simple
Ping:      8.42 ms
Download:  84.31 Mbit/s
Upload:    12.68 Mbit/s
# Remote Play floor: 5 Mbit/s down. 1080p HQ target: 15 Mbit/s.
# Measure at the CLIENT, on the band you will actually use.

That reading has ample headroom for 1080p HQ. If your download at the client sits under 15 Mbps, the High-Quality toggle is the wrong first move; fixing the Wi-Fi is.

The Latency Truth: 1 ms Is a Lie

Network Latency vs. Glass-to-Glass

Here is the number that launches a thousand arguments: Sony and its friendlier coverage will tell you that Remote Play over local home Wi-Fi maintains latency between 1 and 5 ms, while cloud streaming sits at 30 to 40 ms. Both figures are real. Neither is the number you feel. That 1-to-5-millisecond figure is network transit — the time a packet spends crossing your LAN — and it is a genuine, measurable ping. It is also a small slice of a much longer chain. What you actually feel is glass-to-glass latency: the wall-clock time from pressing a button to the corresponding pixel changing on your screen. That number includes controller polling, video encoding on the host, the network hop, video decoding on the client, and the client panel's own scanout time. Add them up and even a flawless LAN lands around 25 to 40 milliseconds.

# Glass-to-glass latency budget: PS5 -> Portal, 1080p60 over LAN
controller poll         ~4 ms
HW HEVC encode          ~8-12 ms
LAN transit             ~1-3 ms      # the hop the marketing quotes
HW decode (client)      ~8-12 ms
panel scanout           ~8-16 ms
------------------------------------
felt (button to pixel)  ~25-40 ms

Why "1 to 5 ms" Gets Quoted

Because it is flattering and because it is not, strictly, false. Marketing quotes the cheapest link in the chain and lets you assume it is the whole chain. The encode and decode stages are where the real time goes, and they are irreducible: you are compressing a 1080p60 video stream in hardware, shipping it, and decompressing it, and that codec round-trip has a floor no router upgrade will lower. This is the same reason a wired display connected directly to the console feels instant and a streamed one never quite does — you have inserted a full video codec into the input loop. Anyone quoting you a single-digit-millisecond input latency for a streamed game is either confusing ping with lag or selling you something.

What Cloud Streaming Costs You (30-40 ms)

Now stack the cloud path on top. Sony's 30-to-40-millisecond figure for Cloud Streaming is, again, primarily network latency — the round trip to the data centre — and it sits on top of the same encode/decode/display budget you already pay locally. In practice that pushes felt latency toward the 60-to-90-millisecond range, which is the difference between "fine for a turn-based RPG or a cosy builder" and "actively hostile for a fighting game or anything with tight parry windows." This is not a defect; it is the deal. Cloud Streaming trades responsiveness for the ability to play with the console off. Know which games you are willing to make that trade for, and keep the twitch stuff on local Remote Play — or, better, on the couch.

Setup in 12 Steps

The Twelve-Step Sequence

What follows is the full path from cold console to a running 1080p High-Quality stream. Do them in order; several later steps silently depend on earlier ones.

1. Update the host console. Settings > System > System Software > System Software Update. Remote Play features are gated behind firmware, and a mismatched host/client version pair produces connection errors that look like network faults but are not.
2. Enable Remote Play on the host. Settings > System > Remote Play > Enable Remote Play. Off by default on some units; nothing downstream works until this is on.
3. Activate the host as your primary console. Settings > Users and Accounts > Other > Console Sharing and Offline Play > Activate. This binds your account's licences and authentication to this box, which is what lets remote wake and pairing succeed without a re-login every session.
4. Enable rest-mode networking. Settings > System > Power Saving > Features Available in Rest Mode, then tick Stay Connected to the Internet and Enable Turning On PS5 from Network. Without both, a console in rest mode cannot be woken by the client, and you will be walking to the living room to press the power button like an animal.
5. Update the client. Portal to 7.0.x, or the phone/desktop app to its latest build. Stale desktop apps refuse to connect outright; the Portal will connect but hide the High-Quality option.
6. Sign in with the same PSN account. The client and host must be on the identical account. A household with multiple accounts is the second most common cause of "console not found" after network isolation.
7. Link the device. On the host: Settings > System > Remote Play > Link Device generates an 8-digit PIN. Enter it on the client. This is a one-time trust handshake; the client remembers the console afterward.
8. Make the first connection on the same LAN. Before you test it from a coffee shop, connect once with the client on your home Wi-Fi. Local pairing is more forgiving and isolates "the pairing is wrong" from "the internet path is wrong."
9. Wire the console; put the client on 5 GHz. Ethernet to the PS5, 5 GHz (not 2.4 GHz) Wi-Fi to the client. This single change fixes more stutter complaints than every software setting combined.
10. Set the resolution to 1080p High-Quality. On the Portal, in-session: Quick Menu > Maximum Resolution > 1080p High-Quality. In the apps, the resolution lives under the settings gear before you connect.
11. Set the frame rate to High. Prefer 60 fps where the client offers it. At 1080p60 the bitrate demand is real, which is why step 9 and step 5's bandwidth check matter.
12. Verify with the connection indicator. Open the on-screen connection overlay and confirm you are on 5 GHz, the bitrate is climbing toward its ceiling, and the dropped-frame figure is green. If it is not, stop and fix the network before you play.

The host-side toggles from steps 2 through 4, written out as a menu tree so you can check them at a glance:

Settings > System > Remote Play
    [x] Enable Remote Play
Settings > System > Power Saving > Features Available in Rest Mode
    [x] Stay Connected to the Internet
    [x] Enable Turning On PS5 from Network
Settings > Users and Accounts > Other > Console Sharing and Offline Play
    [x] Activate        # marks this PS5 as your primary console

Why LAN-First Matters

Steps 8 and 9 exist to divide your problem space. Remote Play failures come in two flavours: authentication/pairing failures, and network-path failures. If you test cold from outside your home, a single error message has to represent both possibilities, and you will waste an hour toggling the wrong things. Prove the pairing works on the LAN — where NAT, port forwarding, and CGNAT are all irrelevant — and any subsequent failure from outside the house is, by elimination, a network-path problem. This is not fussiness; it is the fastest route to a working session, and it is the same divide-and-conquer logic that makes hardware debugging tractable.

Reading a Successful Pairing

A healthy 1080p High-Quality session, read off the Portal's connection indicator, looks roughly like this:

# Portal connection indicator, healthy 1080p HQ session:
Band:        5 GHz   (-46 dBm)
Bitrate:     ~28 Mbps (variable, HEVC)
Resolution:  1920 x 1080
Dropped:     0.1%   (green)
# Yellow or red on "Dropped" is the network, not the console.

The two figures that matter are band and dropped-frame percentage. If band reads 2.4 GHz, you are on the wrong radio and the ceiling on your bitrate is far lower than it should be. If dropped climbs above about 1 percent and turns yellow, you have a network problem no in-app setting will fix — go to the troubleshooting table.

Enabling 1080p High-Quality Mode

The Quick Menu Path

The single confirmed, Sony-documented way to switch a Portal session into the new mode is through the in-session Quick Menu. Hold the PS button, open Quick Menu, and set Maximum Resolution to 1080p High-Quality:

[ Portal ]  hold PS button  ->  Quick Menu
    Maximum Resolution  ->  1080p High-Quality
# Confirmed path (Sony, 17 Mar 2026). Set in-session; the Portal
# remembers the choice per registered console.

The choice is remembered per registered console, so you set it once for each host you stream from. If the option is missing entirely, your Portal has not taken the 7.0.0 update — go back to step 5. If it is present but greyed out, your measured client bandwidth is under the threshold the mode requires.

Bitrate and What HQ Actually Buys

High-Quality mode does not change the resolution — standard 1080p and 1080p High-Quality both output 1920 by 1080. What changes is the bitrate budget handed to the HEVC encoder. More bits per second means fewer compression artefacts in exactly the content that used to fall apart: gradients, fast motion, particle-dense scenes, and dark interiors where banding was most visible. It is the same principle as the difference between a low-bitrate and a high-bitrate stream of the same 1080p video file — identical pixel grid, wildly different amount of real detail surviving the compression. If you have ever wondered why a natively upscaled image looks cleaner than a streamed one, that is the encoder tax; techniques like Sony's own PSSR reconstruct detail on the console before it is ever encoded, and if you care about that pipeline our piece on PSSR 2 landing on the PS5 Pro covers where the reconstruction actually happens.

When to Leave It Off

High-Quality mode is not free. It demands the recommended 15 Mbps rather than the 5 Mbps floor, and on a marginal connection it will engage, exhaust your headroom, and produce more stutter than plain 1080p would have. On congested public Wi-Fi, on mobile data with variable signal, or any time the connection indicator shows band-hopping or a climbing dropped-frame count, drop back to standard 1080p. A stable, slightly softer image beats a sharp one that hitches every few seconds. The mode is a ceiling, not a floor; use it when the network can pay for it and not when it cannot.

Cloud Streaming Without a PS5

What You Can and Can't Stream

Cloud Streaming, permanent since November 5, 2025 and requiring a PS Plus Premium subscription, lets the Portal stream from Sony's data centres rather than your console. The catalogue is thousands of digitally owned PS5 titles plus the full PS Plus library. The hard limit — and it is a licensing limit, not a technical one — is that physical game copies cannot be streamed. A disc grants you a licence tied to the console the disc is in; there is no disc in a data centre, so the cloud has no basis to stream it to you. Only digital ownership and the PS Plus catalogue qualify. If your library is disc-heavy, Cloud Streaming will look thinner than you expect, and that is the law of the thing working as intended rather than a bug.

Turning the PS5 Fully Off

The headline capability is that Cloud Streaming works with your own PS5 powered completely off — or with no PS5 in the house at all. The pre-November-2025 beta required a local console idling in rest mode for certain game types; that dependency is gone. This is the genuine convenience win: you are not waking your console, not consuming its power, and not depending on your home upstream bandwidth, because the stream originates in Sony's infrastructure. The cost is the latency we covered earlier — the 30-to-40-millisecond network figure stacked on the codec budget — and the catalogue restrictions above. It is a different tool for a different job than local Remote Play, and treating them as interchangeable is how people end up disappointed by both.

Recording Clips in Cloud Sessions

Cloud Streaming (Beta) reached the Portal on April 9, 2025, and one of its quirks survives into the permanent feature: because there is no local console to write to, clips you capture during a cloud session are handled differently. Press the Create button twice to start or finish recording a clip, and it is automatically uploaded to the cloud and retained for 14 days. That is a retention window, not permanent storage — if you capture something worth keeping, download it before the fortnight is up. If your goal is to build an archive rather than a temporary highlight, you want proper capture on the host side or a downstream recorder; our guide to saving a VOD walks through keeping footage you actually own rather than renting a 14-day clip locker.

Six Pitfalls That Kill the Stream

Network-Layer Pitfalls

Pitfall 1 — CGNAT. If your ISP puts you behind Carrier-Grade NAT, your "public" IP is shared with strangers and inbound connections to your console cannot be established from outside the home. The fix is to phone the ISP and request a genuine public IPv4 address (sometimes free, sometimes a surcharge, occasionally called a "static IP" upsell), or to lean on Cloud Streaming, which originates from Sony's side and sidesteps the problem entirely. Pitfall 2 — a router blocking the ports. Some routers or restrictive networks block the ports Remote Play needs. The fix, per Sony's own guidance, is to set up port forwarding to the console — the specific ports are in the chiaki-ng section below, and they are the same ports Sony's own client uses. A wired console connection is recommended alongside this, because port forwarding to a device that keeps changing its DHCP lease is a losing game; give the PS5 a static LAN IP first.

Wi-Fi and Radio Pitfalls

Pitfall 3 — the 2.4 GHz trap. If your client silently associates to the 2.4 GHz band — common when a single SSID covers both bands and the router "steers" you — your effective throughput and stability crater, and 1080p High-Quality either refuses to engage or stutters. The fix: force the client onto 5 GHz, either by choosing a 5 GHz-only SSID or by moving closer to the access point. Confirm it on the connection indicator, which reports the band. Pitfall 4 — band steering and roaming. Mesh systems that hand you between nodes mid-session cause periodic freezes as the handoff drops packets. The fix is to pin the client to a single node for the session, or disable aggressive band steering in the router if it supports doing so.

Console-State Pitfalls

Pitfall 5 — rest-mode networking off. If you skipped step 4, the client cannot wake the host, and you get a "console not found" that has nothing to do with the network and everything to do with a checkbox. The fix is the two toggles under Features Available in Rest Mode. Pitfall 6 — account and Share Play collisions. A client signed into a different PSN account than the host will never find it, and a host busy in a Share Play session will refuse a Remote Play connection because the two cannot run at once. The fixes are, respectively, to match the accounts exactly and to end any Share Play session on the host before connecting. Both produce vague errors; both are trivial once you know to look.

Troubleshooting Table

Reading the Errors

Remote Play's error messages are famously uninformative — a generic "can't connect" covers a dozen distinct causes. The table below maps the symptom you actually see to the cause that is usually behind it and the fix that usually clears it. Work top to bottom; the earlier rows are the more common faults.

The Reset Sequence That Fixes Most Things

When a session goes wrong in a way the table does not neatly name, the fastest reset that clears the widest range of faults, in order: close the client app fully; put the host into rest mode and then fully off for thirty seconds (a real power-down, not just rest); confirm the router has not handed the PS5 a new DHCP lease; reopen the client and reconnect on the LAN before trying from outside. This clears stale sessions, refreshes the pairing token, and re-establishes the port mappings, which between them account for the majority of "it worked yesterday" complaints.

The Open-Source Route: Chiaki-ng

Why Chiaki-ng Exists

Sony's client is fine until it is not: it runs only on Sony's blessed platforms, it hides advanced controls, and it will occasionally decide your session is unwelcome for reasons it declines to explain. Chiaki-ng is the maintained community answer — an open-source Remote Play client, the actively developed successor to the original reverse-engineered Chiaki project, living at github.com/streetpea/chiaki-ng and shipping version 1.10.0 as of April 3, 2026. It runs on Linux, Windows, macOS, and — the reason a lot of people install it — on handhelds like the Steam Deck, where Sony ships nothing. If you are weighing which handheld to point at your console, the trade-offs in our ROG Ally X versus Steam Deck OLED comparison apply directly, because chiaki-ng is what turns either of them into a de facto Portal. It is not Sony-endorsed, but it authenticates with your own account and streams from your own console — it is a different client for a service you already pay for, not a bypass of anything.

Registering with Your Account ID and PIN

Registration is the one step that trips everyone, because chiaki-ng needs your PSN Account ID in Base64 form — a machine identifier — not your human-readable online ID. Get the Base64 Account ID from any of the community tools that extract it, then generate an 8-digit registration PIN on the console the same way the official app does: Settings > System > Remote Play > Link Device. Feed both into the client:

# chiaki-ng > Add Console (+) > Register
Host:             192.168.1.42          # PS5 static LAN IP
PSN Account ID:   AbCdEf01gH2iJk==      # Base64, NOT your online ID
Registration PIN: 01234567              # 8 digits, from Link Device
Broadcast:        on (LAN)  /  off (WAN + port-forward)
# PIN path: PS5 > Settings > System > Remote Play > Link Device

Get the Account ID wrong — the single most common failure — and registration simply refuses; there is no partial success to mislead you. Once registered, the console persists in the client and you never re-enter the PIN.

Ports and Firewall Rules

For streaming across the internet rather than the LAN, chiaki-ng needs the same ports Sony's client uses, forwarded to your console's static LAN IP:

# Forward to the PS5 static LAN IP (WAN Remote Play and chiaki-ng)
TCP  9295      # session / control channel
UDP  9296      # A/V stream
UDP  9297      # controller input + feedback
UDP  9302      # discovery (senkusha handshake)
# Use UPnP OR manual forwarding. Never both.

That last comment is not decoration. If UPnP has already opened these ports dynamically and you also forward them statically, some routers double-map the ports and break the very connection you were trying to fix. Pick one method. For a fixed home setup, static forwarding to a static console IP is the more predictable choice; UPnP is fine if your router implements it competently, which is a genuine if.

Advanced Tips

Wire Everything You Can

The recurring theme of this entire guide is that the network, not the software, sets your ceiling. Wire the host to the router with Ethernet, without exception. If your client is a desktop or a TV, wire that too — the Android TV app in particular benefits, and its HDR and high-frame-rate modes want the stability. For handheld clients that cannot be wired, a USB-Ethernet adapter on a dock is not overkill for a stationary setup; a wired Steam Deck running chiaki-ng is a noticeably steadier experience than the same Deck on Wi-Fi. Every wired link you add is one fewer source of the packet loss that turns a frame into a smear.

QoS and Router Prioritisation

If your household shares bandwidth — someone streaming 4K video in the next room while you play — give the console's traffic priority in the router's Quality of Service settings. Prioritise by the console's static IP or by the Remote Play ports. This does not create bandwidth from nothing, but it stops a competing download from stealing the headroom that 1080p High-Quality depends on, which is the difference between a clean session and one that hitches whenever someone opens Netflix. On a link that is genuinely marginal, dropping to standard 1080p and adding QoS beats forcing High-Quality and hoping.

Controller and Display Latency

Two often-missed sources of felt lag sit outside the network entirely. First, the display: if your client feeds a TV or monitor, enable that panel's game mode, because the display's own image processing can add tens of milliseconds that no streaming setting will recover. Second, the controller path: chiaki-ng exposes controller mapping and lets you tune button and back-paddle behaviour that the official client hides, which is worth doing if you are gaming on a Steam Deck's built-in controls rather than a DualSense. Neither fixes the codec tax from the latency section — nothing does — but both shave real milliseconds off the total, and on a streamed input loop every millisecond you can find is one worth keeping.

The Complete Working Configuration

The Console and Client Settings

Everything above, condensed into a reference you can check against a working setup. If a session misbehaves, compare it to this line by line before you start changing things at random:

# ---- Complete working Remote Play config (reference) ----
HOST:     PS5, wired Ethernet, activated as primary console,
          rest-mode networking ON, system software current
CLIENT:   Portal 7.0.2  (or app: Android 10+ / iOS / Win / macOS, latest)
NETWORK:  client 15+ Mbps, 5 GHz Wi-Fi, UPnP on (or ports forwarded)
PORTS:    TCP 9295, UDP 9296, UDP 9297, UDP 9302
SESSION:  Quick Menu > Maximum Resolution > 1080p High-Quality
FALLBACK: chiaki-ng 1.10.0, Account ID (Base64) + 8-digit PIN

The Chiaki-ng Config File

For the open-source path, a known-good chiaki-ng configuration for a 1080p60 HEVC session, which you can adapt to your platform's hardware decoder:

[settings]
resolution=1080p
fps=60
bitrate=30000            ; Kbps, HEVC; leave blank for auto
codec=HEVC               ; HEVC-HDR only if host and display support it
audio_buffer_size=9600   ; raise this first if audio desyncs
hw_decoder=vaapi         ; vaapi (Linux), videotoolbox (macOS), d3d11va (Windows)
audio_out_device=default

[registered_hosts]
name=PS5-Living-Room
address=192.168.1.42

The hw_decoder line is the one to get right per platform: hardware decode is what keeps the decode stage in the latency budget down around 8 to 12 milliseconds instead of ballooning under software decode. On Linux with Intel or AMD graphics use vaapi; on macOS use videotoolbox; on Windows use d3d11va. Leaving the bitrate blank lets the client negotiate; pinning it to 30000 Kbps matches the ceiling a healthy 1080p HQ session reaches and is a sensible fixed target on a link you have already measured.

The Router and Firewall Checklist

Finally, the network side, which is where the whole thing lives or dies. Give the PS5 a static LAN IP so its port mappings do not drift with DHCP. Forward TCP 9295 and UDP 9296, 9297, and 9302 to that IP, or enable UPnP — one or the other, never both. Prioritise the console's traffic in QoS if the household shares the pipe. Confirm you are not behind CGNAT before you troubleshoot anything WAN-side, because no amount of local configuration defeats a shared carrier IP. Wire the host. Put the client on 5 GHz. Measure the bandwidth at the client. Do those six things and the software, for once, simply works — which, given how much of this guide has been about the software lying to you, is the closest thing to a happy ending Remote Play offers.