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

For roughly a decade, PS Remote Play was the feature you mentioned in the same breath as an apology. It worked, technically, in the way that a vending machine in a train station works: you got something edible, the latency was a coin flip, and the colour banding made every cutscene look like it had been screen-grabbed off a 2009 forum. People used it to keep playing while a partner watched television. Nobody used it because it was good.

That changed in 2026, and it changed for reasons that are unusually concrete. In March, Sony pushed a system software update that gave the PlayStation Portal a 1080p High Quality mode for both Remote Play and Cloud Streaming. The same year, a Portal firmware line that the community calls the 7.0 update tightened latency to the point where a reviewer measured around 2 ms on a home network and declared Remote Play crisper than cloud streaming for the first time. And in a quieter but more consequential shift, the Portal stopped strictly requiring a powered-on PS5 at all for certain titles, which means the phrase "Remote Play" now describes two completely different plumbing systems wearing the same coat.

This is a tutorial, so I will not waste your evening relitigating whether streaming a console you own back to a screen you also own is a sensible state of affairs. It is. The goal here is narrow and achievable: get a PS5 or PS4 paired, get a client configured, and get the picture to 1080p with the lowest latency your network will permit, in about twelve steps and roughly thirty minutes. We will use both Sony's first-party app and the open-source ecosystem, because the official client is fine until the exact moment you need it to do something Sony did not anticipate, at which point it is a brick.

Why Remote Play Won in 2026

Before you touch a setting, understand what the technology is actually doing, because every troubleshooting decision later in this article descends directly from the architecture. Remote Play is real-time video encoding. Your console renders a frame, hardware-encodes it to H.264 or HEVC, packetizes it, and fires it at your client over UDP. Your client decodes it, displays it, and shovels controller input back the other way. Everything that ever goes wrong with Remote Play is a symptom of one of those four stages choking.

The latency story is finally real

The headline number from 2026 is the one to internalize. A widely-circulated Portal review reported roughly 2 ms of latency on home Remote Play against about 25 ms for cloud streaming, and argued that since the Portal's 7.0 update, local Remote Play had pulled ahead of cloud on both crispness and responsiveness in home-network testing. Treat the 2 ms figure as a best-case input-to-display delta on a tuned local network, not a guarantee, but the direction is the point: a feature that used to add a perceptible half-beat of lag is now, on a good LAN, competitive with a directly-connected display. That is the difference between "playable" and "I forgot I was streaming."

The same review made a claim worth repeating because it reframes the whole exercise: the combination of a PS5 Pro plus Remote Play delivers the best visual fidelity available on the Portal. The Pro renders at higher internal resolution and reconstructs detail the encoder then preserves; cloud streaming, by contrast, hands you a generic data-center instance with no such advantage. If you own a Pro, Remote Play is not the compromise. It is the premium path.

The official architecture, stated plainly

Sony's own framing, on the official PS Remote Play site, is that the feature lets you control a PS5 or PS4 from a device "at a different location." That phrase is doing real work. It tells you the console is the host and the authority; the client is a thin terminal. It also tells you that "a different location" includes both the next room over and a hotel three time zones away, which are wildly different network problems wearing the same UI. Ninety percent of this guide is about making the first case excellent and the second case merely acceptable.

Two systems, one name

The 2026 complication is that the Portal, and to a lesser extent the phone apps, now blur Remote Play with cloud streaming. TechRadar's 2026 Portal coverage described the device as evolving from a Remote-Play-only accessory into something that also streams from your library or the PlayStation Plus catalog without the PS5 being switched on, and framed that as turning the Portal into a "cloud streaming machine." Keep the distinction crisp in your head, because the fixes diverge: Remote Play problems live on your home network and your console; cloud problems live in your ISP uplink and Sony's data center. We will tackle Remote Play first and properly, then address the cloud side separately.

Prerequisites and Bandwidth Math

Do not skip this section. The single largest cause of bad Remote Play sessions is people who started at Step 1 with hardware that was never going to deliver, then spent an hour blaming the software. Sort the prerequisites first.

Hardware and software you must have

The minimum viable kit, with the versions that matter as of mid-2026:

• Host console: a PS5, PS5 Pro, or PS4 running current system software. The PS5 firmware line at time of writing is the 25.0x branch; update before pairing, because pairing tokens occasionally break across major firmware jumps.
• Client device: per Sony's own support and the 2026 Stuff explainer, PS Remote Play runs on Android phones and tablets, iPhone and iPad, Windows PC, and macOS. Sony's PC and Mac support page confirms Windows and macOS as first-party targets.
• Official app version: install the current PS Remote Play app from Sony directly, not a cached installer. The Windows app self-updates on launch; let it.
• Open-source alternative: chiaki-ng (the maintained fork of the original Chiaki project) for Linux, Steam Deck, and any case where you want manual bitrate and resolution control the official app hides. We will use it in the advanced section.
• A DualSense or DualShock 4 for the client end if you want haptics and adaptive triggers to survive the trip. They do, partially, over the official app and a USB-connected pad.

The bandwidth numbers, and what they actually mean

Here is where most guides lie to you by omission. The 2026 Stuff guide reports Sony recommends at least 5 Mbps for PS Remote Play and 15 Mbps or higher for better performance. Both numbers are correct and both are nearly useless without context, because they describe the wrong link. The 5/15 Mbps figure is the bottleneck between the two endpoints. For local Remote Play that bottleneck is your Wi-Fi or LAN, where you have hundreds of megabits to spare. For remote-over-internet, the bottleneck is your home's upload speed, because the console has to push video out of your house. Residential connections are asymmetric; a plan sold as "300 Mbps" might upload at 20. That upload number is your real ceiling.

Run the math before you blame the app. A useful rule: budget your sustained available throughput at the narrowest hop, subtract 30 percent for protocol overhead and jitter headroom, and that is your usable bitrate. Test the narrow hop directly:

# From the client device, on the SAME network as the console first.
# Find the console IP in PS5 Settings > Network > Connection Status.

ping -c 20 192.168.1.42        # console LAN IP

# Expected healthy LAN result:
# 20 packets transmitted, 20 received, 0% packet loss
# rtt min/avg/max/mdev = 0.8/1.4/3.1/0.4 ms
#
# What you are checking:
#   0% packet loss            -> non-negotiable for video
#   avg under ~5 ms on LAN    -> good
#   mdev (jitter) under 2 ms  -> good; high jitter = stutter

If that ping shows any packet loss at all on a local network, stop. You have a Wi-Fi or wiring problem, and no Remote Play setting will paper over dropped packets. Fix the network, then continue. If you are gaming over the internet, run the same test against your public endpoint and expect 15-40 ms with occasional spikes; anything above 80 ms average will feel like wading.

Wired beats wireless, and it is not close

The console end should be on Ethernet if it is physically possible. Remote Play is sensitive to jitter, and Wi-Fi introduces jitter the way a toddler introduces jam: enthusiastically and everywhere. If the console must be wireless, put it on the 5 GHz band, not 2.4 GHz, and keep it in line of sight of the router. The client can be wireless more forgivingly, but a Steam Deck or laptop on 5 GHz with a clear channel will still beat the same device on a congested 2.4 GHz band by a wide margin. If you are about to set up capture or streaming alongside this, the wiring discipline in our PS5 capture card setup walkthrough applies here too; a clean network topology pays both features at once.

Pairing the Console (Steps 1-4)

Pairing is the handshake that lets a client prove it is allowed to wake and stream this specific console. Get it right once and it persists; get it wrong and you will chase ghost "can't connect" errors for an hour. Four steps.

Step 1: Enable Remote Play on the console

Per Sony's official support page, the paths differ by console. On PS5, go to Settings > System > Remote Play and toggle Enable Remote Play on. On PS4, the toggle lives under Settings > Remote Play Connection Settings. Rationale: this flips the console from "ignore all stream requests" to "accept authenticated ones." Until this is on, every client will fail with a generic connection error and give you no hint why.

Step 2: Configure wake-from-rest

Still on the console, go to Settings > System > Power Saving > Features Available in Rest Mode (PS5) and enable both Stay Connected to the Internet and Enable Turning On PS5 from Network. Rationale: these two settings are what let a client wake a sleeping console. Skip them and Remote Play will only work when someone has manually turned the console on in person, which defeats the entire purpose. The most common "it worked yesterday" failure is a console that fully powered off instead of resting; these toggles keep the network radio alive in rest mode.

Step 3: Pair the device

This is the actual handshake. On PS5, go to Settings > System > Remote Play > Pair Device; the console displays an eight-digit code. On PS4, the equivalent is Settings > Remote Play Connection Settings > Add Device, again yielding a code. Rationale: the code is a one-time secret that binds your PSN account, the client, and the console into a trusted triple. The official app handles this invisibly when you sign in with the same account, but the manual code path exists for open-source clients and for when the automatic flow stalls. Write the code down; it expires in a few minutes.

Step 4: Verify the pairing handshake

If you are using an open-source client like chiaki-ng, you register the console explicitly. This is the step the official app hides, and seeing it makes every later failure legible:

# chiaki-ng registration, command-line form
# PSN account ID is the base64 value, NOT your online ID/handle.

chiaki register \
  --host 192.168.1.42 \
  --pin 12345678 \
  --psn-account-id 'aBcDeFgHiJk=' \
  --console-type ps5

# Expected output on success:
# [I] Registration successful.
# [I] Registered host: PS5-A1B2 (192.168.1.42)
# [I] RP-Key stored. You may now connect.
#
# If you instead see:
# [E] Registration failed: 0x80108527
#   -> wrong account ID format, or Remote Play not enabled (Step 1)

The RP-Key in that output is the persistent credential. Once stored, you never need the PIN again; the client wakes and connects using the key. If you ever factory-reset the console or change PSN accounts, the key is invalidated and you re-pair from Step 3. Getting your numeric PSN account ID is the only fiddly part of the open-source path; chiaki-ng ships a helper that logs into PSN and prints it, and the project's GitHub repository documents the exact incantation for your platform.

Installing the Client (Steps 5-8)

With the console paired, the client is the easy half. Four more steps, and here you make the one decision that defines your experience: official app or open-source.

Step 5: Choose your client

The official PS Remote Play app is the right default. It supports PS5 and PS4 on Windows and macOS, handles pairing automatically, and as of 2026 exposes the resolution and frame-rate options that matter. Install it from Sony's site, sign in with the PSN account you paired, and it will discover the console. Rationale for choosing it: it is the only client guaranteed to track Sony's protocol changes the day they ship. When a firmware update alters the handshake, the official app updates with it; open-source clients lag by days or weeks.

Choose chiaki-ng instead when you need one of three things the official app refuses to give you: a client on Linux or Steam Deck, manual bitrate control, or the ability to force a codec or resolution Sony's heuristics keep overriding. The trade is maintenance burden for control. If you have ever manually undervolted a CPU because the automatic curve was leaving performance on the table, you already understand the temperament that prefers chiaki-ng.

Step 6: Install and first-launch

Install, launch, and let the app self-update before you do anything else. Rationale: the version you downloaded is frequently not the version Sony is currently serving the protocol to; a stale client throws cryptic codec errors that vanish after the update it was trying to tell you to install. On Windows, also ensure your GPU drivers are current, because the client hardware-decodes the incoming video and an old driver will fall back to slow software decoding that adds latency and pins a CPU core.

# Windows: confirm hardware decode is available before you complain about lag.
# In PowerShell, check the GPU and driver date.

Get-CimInstance Win32_VideoController |
  Select-Object Name, DriverVersion, DriverDate

# Expected (healthy) output:
# Name                         DriverVersion   DriverDate
# ----                         -------------   ---------
# NVIDIA GeForce RTX 4070      32.0.15.7283    2026-04-11
#
# A DriverDate more than ~6 months stale is the first thing to fix
# if decode is falling back to CPU.

Step 7: Connect on the local network first

Always validate the setup on the same LAN as the console before you try it from outside the house. Launch the client, select the discovered console, and connect. Rationale: the local case removes every internet variable, so if it fails here, the problem is the console, the pairing, or your Wi-Fi, all of which are fixable in the room you are standing in. If local works and remote does not, the problem is your router or ISP, which is a different chapter. Diagnosing the simple case first saves hours.

Step 8: Map the controller and test input latency

Connect your DualSense or DualShock 4 to the client device, ideally by USB for the lowest input latency, and confirm the console registers it. Rationale: input is the half of Remote Play people forget to test. A beautiful 1080p picture is worthless if button presses arrive a frame late. Run a quick subjective test in a menu-heavy game: navigate, and feel whether the cursor tracks your thumb or trails it. If it trails, the cause is almost always client-side decode latency or network jitter, not the controller. Bluetooth controllers add their own latency on top; prefer wired at the client.

1080p High Quality and Bitrate (Steps 9-12)

This is the section that did not exist before 2026, and it is the reason this guide is worth reading now rather than two years ago. The March 2026 update changed what "good" Remote Play looks like.

Step 9: Understand the March 2026 resolution tiers

On March 17-18, 2026, PlayStation pushed a global Portal system software update that added a 1080p High Quality mode for both Remote Play and Cloud Streaming. Sony said the rollout began "from March 18" and that the mode is selected in Quick Menu > Max Resolution on the Portal. Critically, Sony positioned 1080p High Quality as a higher-bitrate option than the existing 1080p Standard mode. Same pixel count, more bits per pixel, which means less compression blocking on detailed scenes, foliage, particle effects, and exactly the high-motion content where the old encoder fell apart. Rationale for caring: the resolution number stayed the same but the perceived quality jumped, because Remote Play was never resolution-limited so much as bitrate-limited. This is the setting that closes the gap with a directly-connected display.

Step 10: Select 1080p High Quality and restart the session

On the Portal, open Quick Menu > Max Resolution mid-session and choose 1080p High Quality. Sony's instruction, and this is the part everyone misses, is that you must restart the Remote Play or Cloud Streaming session after changing the setting for it to take effect. Rationale: the resolution and bitrate are negotiated at session start, in the handshake, not adjusted live. Change the setting, fully disconnect, reconnect, and only then are you actually getting the higher bitrate. People change the toggle, see no immediate difference because they did not reconnect, and conclude the feature is fake. It is not fake; it is just negotiated once.

# Conceptual: what the session negotiation looks like in chiaki-ng logs.
# This is why a restart is mandatory after changing the tier.

[I] Session request -> host 192.168.1.42
[I]   requested: resolution=1080p  fps=60  codec=HEVC
[I]   requested: bitrate=30000 kbps          # High Quality tier
[I] Host accepted: 1080p60 HEVC @ 30000 kbps
[I] Stream established. Decode: hardware (NVDEC)

# Compare the Standard tier negotiation:
[I]   requested: bitrate=15000 kbps          # Standard tier
[I] Host accepted: 1080p60 HEVC @ 15000 kbps
#
# Same resolution, roughly double the bits. The picture difference
# lives entirely in that bitrate line.

Step 11: Match the tier to your link, not your ego

Do not select the highest tier reflexively. 1080p High Quality demands more sustained bandwidth, and on a link that cannot hold it, the encoder will drop frames or fall back, giving you a worse experience than a clean lower tier. Rationale: a stable 1080p Standard stream beats a stuttering 1080p High Quality one every time, because the human eye forgives a softer image far more readily than it forgives a hitch. Use the tier your bandwidth math from the prerequisites section supports. On a wired LAN, take High Quality without hesitation. Over the internet on a modest upload, test High Quality, and if you see periodic frame drops, step down to Standard and accept the trade. On the official PC and mobile apps the equivalent control is the in-app video-quality setting; the same restart-to-apply logic holds.

Step 12: Lock in frame rate and codec

Set the frame-rate target to match the game and the client's display. Most Remote Play runs at 60 fps; if a game is locked to 30 internally, forcing 60 on the stream wastes bandwidth on duplicate frames. Prefer the HEVC (H.265) codec over H.264 where the client supports hardware decode for it, because HEVC delivers the same quality at meaningfully lower bitrate, which is the whole game when bandwidth is your constraint. Rationale: codec choice is the highest-leverage setting nobody touches. HEVC at 20 Mbps can look like H.264 at 30. If your client's GPU is recent enough to decode HEVC in hardware (confirmed in Step 6), use it. If it falls back to software, the latency cost may outweigh the bitrate savings, in which case H.264 is correct. This is exactly the kind of codec-versus-hardware trade we walk through in the OBS encoding rebuild guide, and the reasoning transfers cleanly.

The Portal, Cloud, and No-Console Play

Everything above assumes the classic model: your console is the host, and it is on. In 2026 the Portal broke that assumption, and you need to understand the new model because it changes what "Remote Play" even means.

The console-off shift

The headline from 2026 Portal coverage is that the device can now stream games from your library or the PlayStation Plus catalog without the PS5 being switched on. TechRadar described this as turning the Portal into a "cloud streaming machine" and framed it as a major expansion beyond traditional console-tethered Remote Play. A separate 2026 update video from the SpawnPoiint channel reported that users can now play purchased games from the store without needing a PS5 at all, provided the titles display the streaming-supported icon, naming Spider-Man Remastered, Miles Morales, and Spider-Man 2 as examples. The mechanism is the distinction that matters: this is cloud streaming from Sony's data center, not Remote Play from your living room. Your console is irrelevant to it. The Portal is talking to a server farm.

What is actually streamable without a console

The 2026 coverage gives a concrete inventory. The streaming options now span both PlayStation Plus Premium catalog titles and eligible purchased games. Reported examples include Sword of the Sea, WWE 2K25, The Last of Us, and Spider-Man. The rule of thumb: if a game shows the streaming-supported icon in your library, the Portal can play it without waking your PS5; if it does not, you are back to classic Remote Play and the console must be on. This bifurcation is permanent and worth memorizing, because the troubleshooting paths diverge completely depending on which one you are using.

Which path you actually want

Given the choice, prefer Remote Play. The 2026 latency numbers settle it: roughly 2 ms on home Remote Play against about 25 ms on cloud streaming, with the reviewer concluding that since the 7.0 update, local Remote Play beat cloud on both crispness and latency. Cloud streaming is the right tool only when your console is unreachable, off, or you genuinely want to play a Plus Premium title you do not own. For everything you own and can reach, the console-hosted path is faster and, on a PS5 Pro, sharper. The cloud capability is a convenience floor, not a ceiling. If you are weighing the Portal against other handheld-streaming approaches, the broader hardware landscape we cover in the PS5 versus Xbox Series X breakdown contextualizes why Sony is leaning this hard into streaming as a platform strategy.

Common Pitfalls and Fixes

These are the failure modes I see most often, ranked by how much time they waste before people realize the cause. Each has a fix that takes minutes once you know where to look.

Pitfall 1: Blaming the app for an upload bottleneck

Symptom: excellent quality at home, a smeary mess over the internet. Cause: your home upload speed, not download, is the ceiling for remote sessions, and residential plans are asymmetric. A "500 Mbps" plan may upload at 20. Fix: test upload from the console's network with a real speed test, subtract 30 percent for overhead, and set your bitrate tier below that. The Stuff guide's 5 Mbps floor and 15 Mbps recommendation refer to this narrow link; if your upload is under 15, 1080p High Quality over the internet is not happening, and no setting changes that.

Pitfall 2: The console fully powered off

Symptom: "can't connect to console" from outside the house, worked yesterday. Cause: the console powered off completely instead of entering rest mode, so its network radio is dead and nothing can wake it. Fix: re-do Step 2, enabling Stay Connected to the Internet and Enable Turning On PS5 from Network in rest-mode features. Then, when you leave, put the console to rest deliberately rather than holding the power button to full-off.

Pitfall 3: Changing resolution and not restarting the session

Symptom: selected 1080p High Quality, see no difference. Cause: resolution and bitrate are negotiated at session start; a live toggle does nothing until reconnect. Fix: Sony's own instruction from the March 2026 update: after changing the setting, fully restart the Remote Play or Cloud Streaming session. Disconnect completely, reconnect, then evaluate.

Pitfall 4: Wi-Fi jitter on the console end

Symptom: intermittent stutter and brief freezes on a fast connection. Cause: the console is on Wi-Fi, probably 2.4 GHz, and packet timing is inconsistent even though raw throughput looks fine. Fix: wire the console with Ethernet. If impossible, move it to 5 GHz, get it line-of-sight to the router, and change the Wi-Fi channel to an uncongested one. Remote Play tolerates lower bandwidth far better than it tolerates jitter.

Pitfall 5: Software video decode on the client

Symptom: high CPU usage on the client, added latency, fan noise, sometimes the wrong codec. Cause: stale GPU drivers forcing software decode of the incoming video. Fix: update GPU drivers (Step 6), confirm the client is using hardware decode, and prefer a codec the client's GPU decodes in hardware. A laptop pinning a CPU core to decode HEVC in software will feel laggy no matter how good the network is.

Pitfall 6: Double NAT and blocked ports for remote sessions

Symptom: local works flawlessly, remote refuses to connect at all. Cause: two layers of NAT (ISP modem plus your own router both routing) or a firewall blocking Remote Play's UDP ports. Fix: put the ISP device in bridge mode to eliminate double NAT, and ensure the Remote Play ports are open. The relevant ports are TCP 9295, UDP 9296, UDP 9297, and UDP 9302; forward them to the console's static IP if your router will not negotiate them automatically.

# Static lease + port reference for the console, router-side.
# Reserve the console's IP by MAC so it never changes, then
# ensure these ports reach it. Syntax varies by router; the
# values do not.

Host reservation:
  MAC  AA:BB:CC:DD:EE:FF  ->  192.168.1.42   (PS5)

PS Remote Play ports:
  TCP  9295   ->  192.168.1.42
  UDP  9296   ->  192.168.1.42
  UDP  9297   ->  192.168.1.42
  UDP  9302   ->  192.168.1.42

# A static lease matters because port-forward rules point at an IP.
# If DHCP reassigns the console, your rules silently aim at nothing.

Troubleshooting Table

When something breaks mid-session, match the symptom to the row and work the fix. This table is ordered roughly by frequency, most common at the top.

Reading the ping test correctly

The single most diagnostic command is the ping test from the prerequisites. Run it whenever a session degrades, and read all three numbers: packet loss tells you whether the link is dropping data (fatal for video), average tells you baseline delay, and mdev (mean deviation, i.e. jitter) tells you how consistent the timing is. A link with 30 ms average and 1 ms jitter streams beautifully; a link with 8 ms average and 15 ms jitter stutters. Latency you can compensate for; jitter you cannot.

When the official app gives you nothing

Sony's app reports errors as opaque codes with no detail, by design. When you hit one and the code search yields nothing useful, switch to chiaki-ng temporarily purely as a diagnostic; its verbose logs will tell you whether the failure is at registration, session negotiation, codec selection, or transport. You can read the log, fix the real problem, and go back to the official app. The open-source client is worth installing even if you never use it daily, just for the moment the first-party app stonewalls you.

Advanced Tips

Past the basics, a handful of moves separate a setup that works from one that consistently feels like local play.

Quality-of-Service tagging on the router

If your router supports QoS, prioritize the console's traffic. Remote Play is real-time and unforgiving of contention; a single large download on another device can inject the jitter that ruins a session. Tag the console's traffic as high priority, or at minimum reserve bandwidth for it. The effect is dramatic on a busy household network and invisible on an idle one, which is why people who test alone never see the problem their family causes nightly.

# Example QoS intent (translate to your router's UI/CLI).
# Goal: console video gets a dedicated slice and high priority.

class remoteplay {
    match host 192.168.1.42        # the PS5
    match proto udp ports 9296,9297,9302
    priority high
    min-bandwidth 25mbit           # reserve, do not borrow
    burst allow
}

# Why min-bandwidth and not just priority:
# priority wins contests, but a reservation guarantees the slice
# even when three other devices are saturating the uplink.

Static IP plus DDNS for reliable remote wake

For consistent remote-over-internet sessions, give the console a static DHCP lease (so port forwards never go stale) and, if your home IP changes, run dynamic DNS so the client always finds your network. The official app handles discovery through Sony's relay when both ends are signed in, but a direct path via your own DDNS hostname is lower-latency than relaying through Sony's infrastructure. This is the same network hygiene that makes self-hosted services reliable, and it pays off most precisely when you are furthest from home and least able to fix things in person.

Codec and bitrate tuning in chiaki-ng

The open-source client exposes the knobs Sony hides. You can pin HEVC, force a specific bitrate, and lock resolution so the heuristics stop second-guessing your link. The discipline mirrors hardware tuning generally; if you have read our analysis of where PlayStation hardware is heading, you will recognize that Sony's roadmap increasingly assumes streaming as a first-class delivery method, which is exactly why investing in a tuned client now is not wasted effort. Set the bitrate explicitly rather than trusting auto-negotiation when your link is stable and known; auto exists to protect bad connections, and on a good one it sometimes leaves quality on the table.

Complete Working Configuration

Here is a complete, working reference for a tuned PS5-to-PC Remote Play setup on a wired LAN, targeting 1080p High Quality at 60 fps with HEVC. Adapt the IPs to your network. This is the configuration I would hand someone who said "just give me the thing that works."

Console-side settings

# PS5 console settings (set once, in person)

Settings > System > Remote Play
  Enable Remote Play .................... ON
  Pair Device .......................... (completed, RP-Key stored)

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

Settings > Network > Connection Status
  Connection ........................... Wired (Ethernet)
  IP Address ........................... 192.168.1.42 (static lease)

# On Portal, mid-session:
Quick Menu > Max Resolution > 1080p High Quality
  -> then RESTART the session for it to apply

Router-side configuration

# Router configuration

# Static lease so port forwards never break
Host reservation:
  AA:BB:CC:DD:EE:FF -> 192.168.1.42 (PS5)

# Port forwarding to the console
TCP 9295 -> 192.168.1.42
UDP 9296 -> 192.168.1.42
UDP 9297 -> 192.168.1.42
UDP 9302 -> 192.168.1.42

# QoS prioritization
class remoteplay {
    match host 192.168.1.42
    priority high
    min-bandwidth 25mbit
}

# ISP modem: bridge mode ON (eliminate double NAT)

Client-side configuration and verification

# chiaki-ng client profile (PC, wired or 5GHz)

[host "PS5-A1B2"]
    address      = 192.168.1.42
    console-type = ps5
    rp-key       = 

[stream]
    resolution   = 1080p
    fps          = 60
    codec        = hevc          # H.264 fallback if no HW decode
    bitrate      = 30000         # kbps, High Quality tier
    audio-buffer = small

[input]
    controller   = dualsense
    connection   = usb           # lowest input latency

# Verification pass after launch — expected healthy output:
# [I] Host PS5-A1B2 reachable (0% loss, avg 1.4 ms)
# [I] Session established: 1080p60 HEVC @ 30000 kbps
# [I] Decode: hardware (NVDEC)
# [I] Input: DualSense (USB), haptics passthrough OK
#
# If all four lines appear, you are done. This is the target state:
# wired console, hardware decode, High Quality tier, USB controller.

If you reach that four-line output, you have the setup the 2026 reviewers were measuring at roughly 2 ms latency. Everything beyond it is diminishing returns. The honest summary of where Remote Play landed in 2026 is this: for anything you own and can reach on a clean wired network, console-hosted Remote Play at 1080p High Quality is now the best-looking, lowest-latency way to play your library on a screen that is not your television, full stop. Cloud streaming is the convenience option for when your console is unreachable, and the no-console Portal streaming is a genuinely useful floor for travel and for Plus Premium titles. But the premium path runs through your own console, your own network, and the twelve steps above. Wire the console, restart the session after the toggle, and stop trusting auto-negotiation on a link you have already measured. The rest is just patience.