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

PlayStation Remote Play is old technology wearing a new coat. The feature that let a PSP borrow a PS3's games in 2006 is the same feature, conceptually, that now streams a PlayStation 5 to an 8-inch handheld on the other side of your house. What changed in 2026 is not the idea. What changed is the bitrate.

On March 17, 2026, Sony pushed system software version 7.0 to the PlayStation Portal and, with it, a 1080p High-Quality Mode that most people have wanted since the device arrived in late 2023. The panel was always 1080p. The stream feeding it was not. Version 7.0 closed that gap, and the internet promptly declared Remote Play "finally usable," which is both an exaggeration and, on a wired host with a 5GHz client, roughly true.

This is the long version of how to set it up correctly — twelve steps, the four UDP/TCP ports Sony's marketing copy never mentions, the difference between Remote Play and Cloud Streaming that half the forum posts get wrong, and the open-source escape hatch (Chiaki-ng) for when the official app disappoints. Expect roughly thirty minutes start to finish, most of it spent waiting for firmware to install.

What Remote Play Is in 2026

Before the twelve steps, a definition, because the single most common Remote Play problem is that people are trying to do a thing the software does not do.

The host-and-client model

Remote Play is a thin-client streaming system. Your PS5 or PS4 does all the work — it runs the game, renders every frame, mixes the audio — and then encodes that output as a video stream and shoves it across your network to a second device. That second device, the client, is dumb on purpose. It decodes the video, paints it on a screen, samples your controller inputs, and ships those inputs back upstream. Nothing about the game runs on the client. The official Remote Play app is, in engineering terms, a video decoder with a gamepad attached. That is why a five-year-old phone can "run" a PS5 game it has no business running: it isn't running anything.

The consequence is that Remote Play's quality is entirely a function of two things you control — the host's connection and the client's connection — and one thing you don't: the internet in between, if there is any. Get the network right and the experience is genuinely good. Get it wrong and no setting will save you, because the bottleneck is not the software.

Remote Play versus Cloud Streaming

This is the distinction that generates the most confused forum threads. Remote Play uses your console as the host. Cloud Streaming uses Sony's datacenter as the host. They feel similar on the Portal because they share a decoder and a UI, but they are architecturally different products with different requirements. Remote Play needs your own PS5 powered on or in rest mode at home. Cloud Streaming, which launched for PlayStation Plus Premium members on November 5, 2025, needs no console at all — Sony runs the game in a rack somewhere and streams it to you. If you turn your PS5 off at the wall and Remote Play stops working, that is not a bug. If Cloud Streaming keeps working under the same conditions, that is the whole point.

What version 7.0 changed on March 17, 2026

The headline feature of the 7.0 update is 1080p High-Quality Mode, and the nuance worth understanding is that it is a bitrate change, not a resolution change. The Portal's LCD has always been a 1080p, 60Hz panel; earlier firmware simply under-fed it, encoding the stream at a conservative bitrate that left the picture soft and prone to blocking in dark scenes. According to Sony's own rollout notes, the performance data behind the mode was collected from December 2025 to January 2026 before the March release, and the Japanese PlayStation Blog confirmed the mode is selectable during both Remote Play and Cloud Streaming, distinguishing it from the older standard 1080p output. Coverage from Polygon and Engadget framed it, correctly, as the fidelity bump the handheld should have shipped with. For the record, Remote Play itself is far older than the Portal: it predates this hardware by well over a decade, and the PC and Mac clients have existed since the PS4 era around 2016. The 2026 novelty is the picture quality, not the concept.

Prerequisites: Hardware, Software, Bandwidth

Remote Play has a short list of hard requirements and a longer list of things that are technically optional but practically mandatory. Skipping the second list is how people end up in the troubleshooting table.

The host: a PS5 or a PS4

You need a console. The PS Remote Play app requires a PS5 or PS4 to act as the host; there is no version of this feature that streams from nothing. For the console-free experience you want Cloud Streaming, which is a PS5-title service on Premium, not Remote Play. If you're weighing which console to keep as your always-on host, note that the base PS5 is a perfectly good Remote Play host — you do not need the Pro for this, and our PS5 Pro versus PS5 breakdown covers where the extra money actually goes (rendering you'll never see over a stream). The host must be able to reach the internet in rest mode, and the account you stream with must be authorised on it. Both are settings, both are covered in the steps.

The clients: Portal, Windows, Mac, Android, iOS, SteamOS

The PlayStation Portal is the purpose-built client: an 8-inch 1080p 60Hz screen bolted between two halves of a DualSense, launched at an RRP of £200 and still listed at roughly that in 2026. It is the only client that gets 1080p High-Quality Mode, because it is the only client Sony ships firmware for. Everything else runs the PS Remote Play app: Windows and macOS (present since the PS4 era, not a 2025 novelty despite what breathless coverage implies), Android 10 or newer, and iOS. On Windows you'll want a machine that can hardware-decode without breaking a sweat — any recent laptop qualifies, and if you're shopping, our 2026 gaming laptop guide is overkill for a decoder but will never be the bottleneck. SteamOS — the Steam Deck — has no official app, but third-party clients cover it; more on that in the advanced section.

One security note that belongs here: download the app only from the official channels. The Android build is published by PlayStation Mobile Inc. (Sony's San Mateo, California entity) on the Google Play Store, and desktop installers come from remoteplay.dl.playstation.net, which serves language-specific builds for GB, EN, and the rest. If an "app" is asking for your PSN password from anywhere else, it is not the app.

Bandwidth: the numbers that actually matter

Sony lists two figures and they are both correct in their own way. The absolute minimum is 5Mbps up and down. The recommended figure is 15Mbps up and down, described in the official documentation as delivering "a better Remote Play experience." Treat 15Mbps as the floor, not the ceiling, and understand that the number that matters most is the upload speed at the host's location, because that is the pipe the video has to fit through. A 500Mbps download does you no good if the host site can only push 6Mbps up. For an in-home session over a good 5GHz link you'll comfortably exceed both numbers; for Remote Play across the internet, the host's upstream is the whole ballgame.

PS REMOTE PLAY 2026 — VERSION & REQUIREMENT CHECKLIST
----------------------------------------------------
Host console
  PS5 system software ........... latest (2026) update
  PS4 system software ........... latest (2026) update   # Remote Play only, no Cloud
Client
  PlayStation Portal firmware ... 7.0 or newer (7.0.2 current)   # 1080p HQ needs 7.0+
  PS Remote Play (Windows) ...... current build from remoteplay.dl.playstation.net
  PS Remote Play (macOS) ........ current build from remoteplay.dl.playstation.net
  PS Remote Play (Android) ...... Android 10+  (publisher: PlayStation Mobile Inc.)
  PS Remote Play (iOS) .......... current App Store build
Network
  Minimum ....................... 5 Mbps up / 5 Mbps down
  Recommended ................... 15 Mbps up / 15 Mbps down
  Host link ..................... wired Ethernet preferred, else 5 GHz Wi-Fi
Subscription
  Cloud Streaming ............... PlayStation Plus Premium (PS5 titles only)

Setup: 12 Steps to First Connection

What follows is the full sequence for a first-time pairing. Do them in order; several later steps silently depend on earlier ones. Budget thirty minutes, most of which is firmware.

Prep work: firmware and accounts

Two things gate everything else. First, the host and the client must both be on current software — 1080p High-Quality Mode simply does not appear on Portal firmware older than 7.0, and pairing can fail against stale console firmware. Second, the account you intend to stream with must be properly authorised on the host, or you'll pair successfully and then get kicked the moment the console needs to prove you're allowed. Handle both before you touch the network.

The twelve steps

1. Update the host console. On the PS5, install the latest system software and reboot. Rationale: Remote Play capabilities and the handshake protocol are gated on firmware; an out-of-date host is the most common cause of "it pairs but won't connect."
2. Update the client to 7.0 or newer. On the Portal, take the update to 7.0.2; on desktop and mobile, install the current build from the official source. Rationale: 1080p High-Quality Mode is a 7.0 feature, and older clients negotiate a lower ceiling regardless of your network.
3. Enable Remote Play on the host. Go to Settings > System > Remote Play > Enable Remote Play and switch it on. Rationale: the feature is off by default; without this the console will not answer discovery requests at all.
4. Turn on rest-mode networking. Under Settings > System > Power Saving > Features Available in Rest Mode, enable Stay Connected to the Internet and Enable Turning On PS5 from Network. Rationale: this is what lets a sleeping console wake and stream on demand; skip it and Remote Play only works while the PS5 is fully powered on.
5. Authorise the account. Set the console as your activated device via Settings > Users and Accounts > Other > Console Sharing and Offline Play. Rationale: this is the silent authentication that keeps sessions from dropping; an unauthorised account pairs and then disconnects.
6. Wire or 5GHz the host. Connect the PS5 to the router by Ethernet if you possibly can; if not, put it on the 5GHz band. Rationale: the host's upstream is the bottleneck for the entire session, and 2.4GHz Wi-Fi is where good intentions go to buffer.
7. Put the client on a strong 5GHz signal. Use the same network for your first setup — cross-internet can wait. Rationale: pairing is easiest on the same LAN, and it isolates any later problem to the network rather than the configuration.
8. Sign into the same PSN account on the client. Launch the app or Portal and log in with the account you authorised in step 5. Rationale: the client and host identify each other by account; a mismatched login is the second most common pairing failure.
9. Generate a registration number. On the host, open Settings > System > Remote Play > Pair Device to display a registration number. Rationale: this short-lived code is how the client proves it's yours; it exists precisely so a stranger on your network can't attach.
10. Enter the number on the client, fast. Type it into the app's pairing prompt before it expires. Rationale: the code is valid only for a short window (on the order of fifteen minutes); a slow phone-and-couch relay is enough to miss it.
11. Launch the first session and read the indicator. Connect, and watch the connection-quality readout the client shows on start. Rationale: the first session tells you whether your network is healthy before you've committed to a game.
12. Set your default resolution and frame rate. Once stable, choose your target output for future sessions (for the Portal, that's the resolution menu covered next). Rationale: locking a sensible default stops the client from renegotiating quality every time conditions wobble.

Expected output: what a good first connection looks like

A healthy same-LAN session connects in a few seconds and reports its status plainly. On the desktop app you'll see something close to this in the connection readout:

Connecting to PS5...
  Discovery ......... host found (192.168.1.50)
  Registration ...... OK
  Session ........... established
  Video ............. 1080p @ 60fps
  Connection ........ Excellent   (est. latency ~28 ms, LAN)
Press Options to open the stream settings.

The number to watch is latency. On a wired host and a 5GHz client, glass-to-glass latency in the mid-20s to low-40s of milliseconds is normal and very playable. Anyone quoting single-digit millisecond Remote Play latency is quoting a LAN ping, not what your thumbs actually feel — the encode, transmit, decode, and display pipeline has a real cost, and no firmware repeals it.

Enabling 1080p High-Quality Mode

This is the feature people updated for, so here is exactly how to turn it on and, more usefully, when you shouldn't.

The Quick Menu path

On the Portal, during or before a session, open the Quick Menu, select Max Resolution, and choose 1080p High-Quality. That's the whole toggle.

PlayStation Portal — enable 1080p High-Quality Mode
---------------------------------------------------
1. Press the PS button ............ opens the Quick Menu
2. Select Max Resolution
3. Choose 1080p High-Quality       # requires firmware 7.0+
   (options: 720p / 1080p / 1080p High-Quality)
Applies to: Remote Play AND Cloud Streaming

If 1080p High-Quality is greyed out or missing, you are not on 7.0 — go back to step 2 of the setup. It is that binary.

What "High-Quality" actually means

The mode does not add pixels; the Portal was already a 1080p display. It adds bitrate. Earlier firmware encoded the stream conservatively, which is why fast motion smeared and dark scenes fell apart into compression blocks. High-Quality Mode raises the bitrate ceiling so the same 1080p frames arrive with more information intact — cleaner gradients, less blocking, sharper motion. Sony validated the mode on data gathered from December 2025 through January 2026, and the Japanese PlayStation Blog was explicit that it applies to both Remote Play and Cloud Streaming, which is the useful part: your cloud sessions get the same fidelity bump as your local ones.

When to enable it — and when it hurts

Here's the part the changelog won't tell you: more bitrate needs more headroom. On a connection comfortably above the 15Mbps recommendation, High-Quality Mode is a clear upgrade and you should leave it on. On a marginal connection — a congested apartment 5GHz, a host uploading over a mediocre broadband line — forcing the higher bitrate buys you a prettier picture that stutters, because the stream now wants more than the pipe can deliver and the client compensates by dropping frames. If your sessions were already borderline, test High-Quality against standard 1080p back to back and keep whichever actually feels smoother. Fidelity you can't sustain is not fidelity; it's a slideshow with good taste.

Cloud Streaming for PS Plus Premium

Cloud Streaming is the half of the Portal's 2026 story that has nothing to do with your console, and it's worth understanding on its own terms.

What launched on November 5, 2025

On November 5, 2025, Sony switched on Cloud Streaming for PlayStation Plus Premium members on the Portal — the ability to stream select digital PS5 games directly from Sony's servers with no console in the loop. The launch shipped with hundreds of compatible titles drawn from the PlayStation Plus Game Catalog and the Classics Catalog, including marquee names like Cyberpunk 2077, God of War Ragnarök, and The Last of Us Part II Remastered. It's the feature that turns the Portal from a companion screen for your PS5 into a semi-independent handheld — as long as you keep paying for Premium.

The catalog and its limits

The catalog has grown since launch; by the middle of 2026 the streamable library had expanded past roughly 2,800 titles as Sony folded in more of the Game Catalog and Classics lineup. But note the word select. Cloud Streaming does not stream your library — it streams Sony's eligible catalog. A game you bought outright that isn't on the cloud list won't appear there; for that game you're back to Remote Play and your own console. This is the same distinction from the top of the article, now with a billing dimension: Remote Play is included with the hardware, Cloud Streaming is a Premium-tier feature you rent.

Which one to actually use

If you own the console, it's home, and it's on your network, use Remote Play. It has lower latency (no round-trip to a datacenter), it plays your entire library including physical discs, and it costs nothing beyond the hardware. Reach for Cloud Streaming when the console is genuinely unavailable — powered off by someone else, being used on the TV, or simply too far to reach over your home network. It's a fallback and a convenience, not a replacement for the box under your television. For the games actually worth firing up the box for — say, whatever's topping the charts by the time GTA 6 finally lands — Remote Play from your own PS5 will always look and feel better than the cloud equivalent.

Network Tuning: Ports & Forwarding

Most Remote Play problems that aren't firmware problems are network problems, and most network problems come down to three things: which ports are open, whether the host has a stable address, and whether you're on a decent radio.

The ports Remote Play actually uses

Sony's consumer documentation is coy about specifics, but Remote Play communicates over a small, fixed set of ports. For an in-home session on a normal flat network you never touch these — discovery just works. They matter the moment a firewall, a guest network, or an internet connection sits between client and host.

PS REMOTE PLAY — PORTS
----------------------
TCP  9295      session / control channel
UDP  9296      video + audio stream
UDP  9297      video + audio stream
UDP  9302      discovery / connection setup

If Remote Play works on your LAN but fails the instant you try it from outside, one or more of these is being blocked or not forwarded. That's the fix, below.

Static IPs and port forwarding

Sony's 2026 support material explicitly advises checking that your router permits the ports Remote Play uses, and suggests port forwarding where an ISP or firewall blocks the connection. To do it properly, first pin the host to a fixed local address — either a static IP on the console or, cleaner, a DHCP reservation on the router keyed to the PS5's MAC — so the forward doesn't break the next time leases shuffle. Then forward the ports to that address:

# Router port-forward map — forward to the host's reserved address
# Example host: PS5 at 192.168.1.50

TCP  9295   ->  192.168.1.50
UDP  9296   ->  192.168.1.50
UDP  9297   ->  192.168.1.50
UDP  9302   ->  192.168.1.50

# Verify the console's current address first:
#   Settings > Network > Connection Status > View Connection Status
# Then reserve it:  Router > LAN > DHCP Reservations > Add (MAC -> 192.168.1.50)

One warning that saves hours: if your ISP puts you behind carrier-grade NAT (a double-NAT, common on mobile broadband and some fibre plans), port forwarding on your own router accomplishes nothing, because the public-facing NAT isn't yours to configure. Symptoms are LAN Remote Play that works perfectly and internet Remote Play that never connects no matter what you forward. The fixes are a real public IP from the ISP, or a client that tunnels around the problem — which is one of the reasons the third-party clients in the advanced section exist.

Wi-Fi, Ethernet, and the 5GHz rule

Wire the host. This is the single highest-value change you can make, because the host's upstream carries the entire video stream and Ethernet removes an entire category of failure. If the host must be wireless, put it on 5GHz, not 2.4GHz — the 2.4GHz band is slower, more congested, and shared with every microwave and Bluetooth device in range. Before blaming the software, confirm you actually have the throughput you think you have. From the client, a quick iperf3 run to your router tells you the truth:

# From the client device, test throughput to the router (or the host):
$ iperf3 -c 192.168.1.1 -t 15

Connecting to host 192.168.1.1, port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-15.00  sec   118 MBytes  66.0 Mbits/sec   receiver

# 66 Mbit/s is comfortably above the 15 Mbps recommendation.
# Anything under ~20 Mbps here and 1080p High-Quality will struggle.

If that number is healthy and Remote Play still stutters, the problem is upstream of your test — the host's connection or the internet path — not the client's radio.

Common Pitfalls and Fixes

Seven ways people break Remote Play without realising it, grouped by where the mistake lives.

Network mistakes

Pitfall 1 — the host on 2.4GHz. The most common quality complaint traces back to a console sitting on the 2.4GHz band because that's what it connected to first. Fix: move the host to 5GHz or, better, Ethernet, and confirm with an iperf3 run.

Pitfall 2 — expecting WAN to feel like LAN. Remote Play across the internet adds the round-trip to wherever the host is, plus the host's upstream limit. Fix: set expectations, wire the host end, and accept that a session from a coffee shop will never match one from the next room. If it must be tight, forward the ports and prefer wired networks at both ends.

Pitfall 3 — carrier-grade NAT. Covered above, and worth repeating because it masquerades as a software bug. Fix: test whether LAN works and WAN doesn't; if so, stop changing settings and talk to your ISP or switch to a tunnelling client.

Configuration mistakes

Pitfall 4 — rest-mode networking left off. If you can stream while the PS5 is fully on but "can't find" it after it sleeps, you skipped step 4. Fix: enable Stay Connected to the Internet and Enable Turning On PS5 from Network under rest-mode features.

Pitfall 5 — the registration number timing out. The pairing code expires. Relaying it slowly across a room, or getting interrupted, means it's dead by the time you type it. Fix: have the client open and ready on the pairing screen before you generate the number, then enter it immediately.

Content and hardware mistakes

Pitfall 6 — HDCP and capture hardware in the chain. Certain apps and some capture-card setups sitting between the console and its display can interfere with the stream or produce a black screen. Fix: connect the host directly to a display it trusts, remove pass-through capture devices when troubleshooting, and restart the session.

Pitfall 7 — confusing Remote Play with Cloud Streaming, and Share Play with both. People expect Remote Play to work with the console off (it won't — that's Cloud Streaming), or try to run Share Play and Remote Play at once (you can't; they're mutually exclusive). Fix: match the tool to the job — console at home and on, Remote Play; console unavailable and you're on Premium, Cloud Streaming; don't expect to combine Share Play with either.

Troubleshooting Table

When a session misbehaves, work the table before you work yourself into a reinstall.

Reading the failure before the fix

Remote Play failures cluster into three families: discovery (the client can't find the host), session (it finds it but won't connect or keeps dropping), and quality (it connects but looks or feels wrong). Identifying the family first saves you from, say, forwarding ports to fix a problem that was really the host sitting on 2.4GHz. Discovery failures are usually rest-mode or network-isolation issues; session failures are usually firmware, account, or NAT; quality failures are almost always bandwidth.

The diagnostic table

When to reset the host instead

If discovery and session both fail intermittently and nothing in the table sticks, the host's own cache may be the culprit — a corrupt database or system cache produces exactly the kind of vague, inconsistent networking flakiness that resists targeted fixes. Before you factory-reset anything, clear the console's caches in Safe Mode; our two-minute PS5 cache-clear walkthrough is the low-risk first move, and it fixes more "mystery" Remote Play problems than it has any right to.

Advanced: Chiaki-ng & SteamOS

When the official app isn't enough — no client for your platform, or you want control Sony doesn't expose — the open-source ecosystem picks up the slack. Understand the trade-off first: these are third-party tools, not Sony products, and they are not endorsed. They work by speaking the same protocol, and they are entirely at your own risk.

Chiaki-ng: the open-source client

Chiaki-ng is the actively maintained fork of the original Chiaki project — a from-scratch Remote Play client that runs where the official app won't, including Linux and the Steam Deck's SteamOS. The current release, v1.10.0 (April 3, 2026), supports 1080p60 streaming, bitrates up to around 30,000 Kbps, and hardware decoding, which is why it's the default recommendation for Steam Deck owners. It lives on GitHub at streetpea/chiaki-ng, and the project's own documentation is the authoritative setup source — not any single forum thread.

Registration is the one fiddly part. Chiaki authenticates with your PSN Account ID (a Base64 string, not your visible username) and an eight-digit PIN generated on the console. The flow looks roughly like this:

# 1) On the PS5, open the pairing PIN:
#    Settings > System > Remote Play > Link Device   ->  8-digit PIN

# 2) Discover the host from the client:
$ chiaki discover -h 192.168.1.50
192.168.1.50  ready   host-type: PS5

# 3) Register with your Base64 Account ID and the PIN:
$ chiaki register \
    --host 192.168.1.50 \
    --psn-account-id AbC1dEf2gHi= \
    --pin 12345678

# Registration OK — the host is now saved for future sessions.
# (Syntax is illustrative; the GUI wizard automates all three steps.)

I've marked the CLI as illustrative deliberately — most people should use the GUI wizard, which walks the same three steps without the typos. The Account-ID-plus-PIN scheme is the same trust model as the official Pair Device flow, just exposed instead of hidden.

PX Play and SteamOS

If you'd rather not compile anything, PX Play is a third-party option that brought Remote Play to SteamOS in 2026 with conveniences the base experience lacks — automatic console mapping and connection handling, including reconnecting over a mobile hotspot. It's the more hands-off route for Steam Deck owners who want Remote Play to behave like an app rather than a project. As with Chiaki-ng, it is not a Sony product; weigh that as you see fit.

The registration internals, briefly

Why the two different codes? The official app's registration number and Chiaki's Account-ID-plus-PIN both solve the same problem — proving a client is authorised to attach to a specific console — but they expose different amounts of the machinery. The Link Device PIN path is what third-party clients hook into because it hands over a stable identifier (your Account ID) plus a one-time secret (the PIN), which together let the client re-establish sessions later without re-pairing every time. It's the same reason you pair once and connect for months: the trust is stored, not renegotiated. If you ever rotate or lose that stored registration, you simply generate a new PIN and register again.

The Complete Working Configuration

Everything above, condensed into one reference you can work down top to bottom.

Recommended settings, in plain language

Wire the host or put it on 5GHz. Update both ends to current software, and the Portal specifically to 7.0 or newer. Enable Remote Play, rest-mode networking, and account activation on the console. Keep a DHCP reservation for the host and, if you stream over the internet, forward TCP 9295 and UDP 9296/9297/9302 to it. Turn on 1080p High-Quality Mode only if your throughput clears 15Mbps with room to spare. Expect mid-20s-to-40s-millisecond latency on a good LAN and don't believe anyone who promises less.

The full configuration block

# =====================================================================
#  PS REMOTE PLAY 2026 — COMPLETE WORKING CONFIGURATION
# =====================================================================

# --- HOST (PS5) ------------------------------------------------------
System > Remote Play > Enable Remote Play ................. ON
System > Power Saving > Features Available in Rest Mode:
    Stay Connected to the Internet ....................... ON
    Enable Turning On PS5 from Network ................... ON
Users and Accounts > Other > Console Sharing and Offline Play
    This console is activated ............................ YES
System software ......................................... latest (2026)
Network link ............................................ Ethernet (preferred)

# --- CLIENT ----------------------------------------------------------
PlayStation Portal firmware ............................. 7.0.2 (>= 7.0)
Quick Menu > Max Resolution ............................. 1080p High-Quality*
    (* only if sustained throughput > 15 Mbps)
Desktop / mobile app .................................... current official build
Client radio ............................................ 5 GHz, single AP

# --- NETWORK ---------------------------------------------------------
Minimum bandwidth ....................................... 5 Mbps up / down
Recommended bandwidth ................................... 15 Mbps up / down
Host address ............................................ DHCP reservation (e.g. 192.168.1.50)

# Port forwards (only needed for Remote Play across the internet):
TCP  9295  ->  192.168.1.50      # session / control
UDP  9296  ->  192.168.1.50      # stream
UDP  9297  ->  192.168.1.50      # stream
UDP  9302  ->  192.168.1.50      # discovery

# --- CLOUD STREAMING (optional) --------------------------------------
Subscription ............................................ PS Plus Premium
Scope ................................................... Sony PS5 catalog (not your library)
1080p High-Quality ...................................... supported (same toggle)

# --- SANITY CHECK ----------------------------------------------------
iperf3 to router >= 20 Mbps ............................. required for 1080p HQ
Expected LAN latency .................................... ~25-40 ms glass-to-glass
LAN works / WAN fails ................................... suspect carrier-grade NAT
# =====================================================================

A closing note on expectations

Configured correctly, Remote Play in 2026 is the best it has ever been, and on a Portal running 7.0 it clears the bar the hardware set for itself in late 2023. But it remains a streaming system bounded by physics and your ISP. The settings above get you everything the software can give; the rest is your upstream, your radio, and the distance the photons have to travel. No toggle fixes a thin pipe.

The Verdict

Who this is for

Remote Play in 2026 finally earns the enthusiasm. If you own a PS5 and a Portal — or any capable client — the twelve-step setup above turns a console tethered to one television into something you can play from any room with a decent 5GHz signal, at a genuine 1080p once you flip on High-Quality Mode. For couch-to-bedroom, house-to-garden, or console-in-the-lounge-while-someone-watches-TV, it's excellent, and it costs nothing beyond hardware you already own.

Where it still disappoints

Across the open internet it's a different, humbler product — beholden to your host's upstream and, if your ISP hides you behind carrier-grade NAT, occasionally impossible without a workaround. Cloud Streaming papers over the "console is off" case but only for Sony's catalog and only on Premium, and the Portal is still a single-purpose £200 device that does one thing. That one thing, in 2026, it now does well. The Portal isn't the only handheld worth owning — our Switch OLED versus Switch 2 comparison covers the standalone alternative — but as a window back to your PS5, nothing else is this clean.

The bottom line

Update to 7.0. Wire the host. Put the client on 5GHz. Turn on High-Quality Mode only when your bandwidth earns it. Forward four ports if you're going long-distance, and keep Chiaki-ng in your back pocket for the platforms Sony ignores. Do those things and Remote Play stops being a compromise and starts being the feature it always claimed to be — a decade and several console generations late, but here at last.