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

What Remote Play Is in 2026

Remote Play is Sony renting you back your own console. The PlayStation 5 or PlayStation 4 sitting under your television does the actual work — the CPU cycles, the GPU shading, the decryption, the game logic — and then it encodes that finished frame to H.264 or HEVC and squirts the video and audio across your network to a second screen. Your button presses travel back the other way. Nothing about the game runs on the phone, laptop, or handheld in your hands; that device is a glorified monitor with a gamepad stapled to it. Internalise that one sentence and ninety per cent of Remote Play's quirks stop being mysterious, because almost every problem you will ever have is a network problem wearing a video costume.

The feature, as Sony describes it

Sony's official Remote Play hub still frames it plainly: stream PS4 and PS5 games, switch between games, view the console's home screen, and browse menus on a compatible device over broadband or mobile data. That is the entire pitch, and it has barely moved since the PS5 gained the feature in November 2020. The lineage runs back further still — the PS3 and PSP were doing a cruder version of this in 2006, long before the marketing department settled on a name. Nearly every PS4 and PS5 title supports it; the handful of exceptions are games that insist on peripherals the protocol cannot carry, chiefly PlayStation Move motion controllers, because the stream transmits a gamepad and not a camera-tracked wand.

Because the source is a console you already own, the experience is effectively identical whether you are pushing pixels from a PS4 or a PS5 — the older machine simply hands off a lower internal resolution before the encoder gets to it. The client does not know or care which box is upstream. It negotiates a video size, receives frames, and returns inputs.

Three different things people call Remote Play

The confusion in 2026 is that Remote Play now names at least three separate products, and a fourth thing keeps sneaking into the conversation pretending to be it. First, the PlayStation Portal: an 8-inch, 1080p, 60Hz dedicated handheld that does nothing but Remote Play and, since late 2025, cloud streaming. Second, the PS Remote Play app: a free download for Windows, macOS, Android, iOS and iPadOS, and Android TV, which has existed in some form since the PS4 era and is not, whatever a breathless blog tells you, new in 2025. Third, the third-party clients — Chiaki-ng and Asobi — that reverse-engineered Sony's protocol and speak it on hardware Sony never blessed, from a Steam Deck to a Nintendo Switch. And the imposter: cloud streaming, where the game runs on Sony's servers rather than your console. That is a PlayStation Plus Premium feature, not Remote Play, even though the Portal now serves both from adjacent tiles in the same menu and Sony is delighted to let you blur the two.

What actually changed in 2025 and 2026

Four dates carry the year. On 5 November 2025, Sony switched on cloud streaming for the Portal for Plus Premium members, letting the device run digital PS5 games from your library with no console powered on at home at all. On 17 March 2026 (the 18th across CET and JST, where the rollout began the next day), the Portal's system software gained a 1080p High Quality mode for both Remote Play and cloud streaming, wrapped in the usual mumbled promises of higher visual fidelity, smoother interactions, and a more seamless overall experience. On 2 April 2026, Sony raised the Portal's price to $249.99 in the United States, £219.99 in the United Kingdom, €249.99 across Europe, and ¥39,980 in Japan, with Southeast Asia pricing following on 1 May. And across the whole year the free app crept up to version 9.x while the tinkerers' clients matured into genuinely usable software. Where a claim in this guide needs a second opinion, the clean cross-check trio is the PlayStation Blog, Engadget, and Ars Technica — and the Blog is the primary source for the March update, because it is Sony's own changelog and everything downstream is quoting it.

Prerequisites: Versions and Network

Remote Play fails for boring, predictable reasons, and almost all of them are decided before you press connect. Get the prerequisites right and the setup is fifteen minutes of menus. Get them wrong and you will spend an evening staring at a spinner. This section is the checklist; skip it at your own risk.

Console-side requirements

You need a PS5 (any model, disc or digital, base or Pro) or a PS4, running the latest system software. That is non-negotiable, and not for security-theatre reasons: Remote Play's handshake is versioned, and a console two firmware revisions behind will refuse or drop sessions from a current client. You need the console signed in to your PlayStation Network account, and you need that console set for Console Sharing and Offline Play so the account is treated as primary. The single most important physical requirement is a wired Ethernet connection to the console. Remote Play is asymmetric: the console is the sender, and Wi-Fi jitter on the sending side smears every frame you receive, whereas jitter on the client side merely delays your inputs. Cable the console. If you cannot, that is the first thing to fix.

Client software versions

The clients live on independent version tracks, which is the second great source of confusion. The Portal is a hardware device with its own system software, currently 7.0.2. The downloadable app is on the 9.x line. The two numbers have nothing to do with each other. Here is where everything stood in mid-2026:

The cadence tells you Sony is still actively maintaining this. The Windows build reached 9.0.0.02120 on 29 May 2026, after 8.5.0.08070 on 19 September 2025 and 8.0.0.14120 on 28 March 2025 — a roughly two-a-year rhythm. Android moved faster and further: 9.1.0 on 27 May 2026, 9.0.0 on 18 March 2026, 8.5.1 on 6 November 2025, 8.5.0 on 17 September 2025, and 8.0.0 on 25 March 2025. Whatever platform you land on, install the newest build before you troubleshoot anything, because half the forum threads about disconnects are people running a client from last spring.

The network floor

Sony's stated minimum is 5 Mbps down and up; the recommended figure is 15 Mbps for both directions, and that recommendation is not decoration. The 1080p High Quality mode added in March will happily consume the full 15 and quietly degrade below it. Before you touch a client, test the console's own connection and read the numbers off the screen:

Settings > Network > Connection Status > Test Internet Connection

Expected on a healthy wired console:
  Internet Connection .......... Successful
  PlayStation Network Sign-In .. Successful
  Connection Type .............. Wired (LAN Cable)
  Download Speed ............... 320.4 Mbps
  Upload Speed ................. 41.2 Mbps
  NAT Type ..................... Type 2

Two lines matter more than the speeds. Connection Type should say Wired. And NAT Type should say Type 2; Type 3 is the single strongest predictor that Remote Play will work at home and die everywhere else. If you see Wi-Fi and Type 3 here, fix those before you go one step further. One more thing to kill in advance: the fantasy of 2-millisecond latency. A LAN ICMP ping of 2ms is not felt latency. Real glass-to-glass Remote Play latency — controller press to pixel change — is roughly 25 to 40 milliseconds on a good local network, and materially worse over the internet. Anyone quoting single-digit milliseconds is quoting the wrong number.

The 12-Step Setup Walkthrough

What follows is the whole procedure, console to client to first remote session, in twelve steps. Do them in order. The order is not arbitrary — each step removes a variable so that when something breaks at the end, you already know it is not the thing you fixed at the start.

The three phases at a glance

Steps 1 through 4 are the console: update it, arm Remote Play, fix the account, and configure rest mode. Steps 5 through 8 are the client: install it, sign in, pair it, and prove it works on your own LAN. Steps 9 through 12 are the payoff: wake, tune the picture, pair the controller properly, and only then go remote. Ninety per cent of setups that fail, fail because someone jumped straight to step 12.

1. Update the console to the latest system software. Settings then System then System Software then Update. Rationale: the Remote Play handshake is version-gated, and a stale console will reject or drop a current 9.x client with a generic error that tells you nothing.
2. Enable Remote Play on the console. Settings then System then Remote Play, and switch Enable Remote Play on. Rationale: it is a toggle, and if it is off, discovery finds the console and the connection dies at the last second, which reads exactly like a network fault and wastes an hour.
3. Set this console as your primary. Settings then Users and Accounts then Other then Console Sharing and Offline Play, and enable it. Rationale: Remote Play authenticates your account against this specific machine. Wrong primary, or a second account, produces the classic sign-in loop where the client connects, thinks, and boots you back to the list.
4. Configure rest mode to stay awake on the network. Settings then System then Power Saving then Features Available in Rest Mode, and enable both Stay Connected to the Internet and Enable Turning On PS5 from Network (the PS4 wording differs slightly). Rationale: this is the load-bearing step. Without it, the console drops off the network the moment it sleeps and no client on earth can wake it. This is the most common single point of failure in all of Remote Play.
5. Install your client. The official app comes from the Remote Play download page or your platform's store; the Portal ships with it; third-party clients come from their own repositories. Rationale: pick deliberately, because the client decides your ceiling — the Portal caps at 1080p, the app caps at 1080p, Chiaki-ng will push a fatter bitrate at the same resolution.
6. Sign in to the client with the same PSN account. Rationale: Remote Play maps account to console. A different account, even a family member's on the same console, simply will not see the machine, and the app offers no useful error — the console just is not there.
7. Register (pair) the device. On the same network, the app usually finds the console automatically. For manual pairing, on the console open Settings then System then Remote Play then Link Device, which shows an eight-digit PIN; enter it in the client. Rationale: registration exchanges the keys that let the client wake and authenticate the console later from anywhere. Skip a clean registration and remote wake will never work.
8. Do the first connection on the same LAN. Put the client on the same Wi-Fi or Ethernet as the console and connect. Rationale: this eliminates NAT, port forwarding, and your ISP from the equation. If it works here and only here, you have a network problem, not a Remote Play problem, and you have just proved it.
9. Wake and connect. Launch the client, pick the console, and let it wake the machine from rest and start the stream. Rationale: this is the moment the rest-mode settings from step 4 either pay off or expose themselves. If it will not wake, go back to step 4, do not pass go.
10. Set the video quality. In the app, Settings then Video Quality for Remote Play; on the Portal, the Quick Menu. Push resolution to Best or 1080p High Quality and frame rate to High. Rationale: defaults are deliberately conservative — often 540p or 720p — to protect people on bad connections, so a fresh install looks worse than the hardware can manage until you tell it otherwise.
11. Pair the controller properly. On phones and PCs, connect a DualSense by USB cable first, then switch it to Bluetooth; the Portal has its controller built in. Rationale: haptics and adaptive triggers only survive the round trip on a genuine DualSense, and a first-time USB pairing is far more reliable than fighting Bluetooth blind.
12. Now go remote. Move the client onto mobile data or a different Wi-Fi network entirely and repeat the wake-and-connect. Rationale: this is the real test. If step 8 worked and step 12 fails, the fault is squarely your network path — NAT, CGNAT, or a firewall — and the next section is where you fix it.

Expected output of a clean connection

The official app narrates none of this in text — it shows icons and a spinner — but conceptually a healthy first connection runs through this sequence, and knowing the sequence tells you where a failed attempt stalled:

[client] Searching for console on local network ...
[client] Found: PS5-7F3A at 192.168.1.20
[client] Console is in rest mode -> sending wake packet
[client] Wake acknowledged, console booting stream service
[client] Registered session key: OK
[client] Video negotiated: 1080p @ 60 fps, HEVC
[client] Connected. ~15 Mbps down, round-trip ~32 ms.

(The wording is invented; the order is not. If it never gets past
 'sending wake packet', your problem is rest mode, step 4. If it
 wakes but never negotiates video, your problem is bandwidth.)

Why rest-mode wake is the fragile part

Steps 4 and 9 fail together more than any other pair, and the reason is that waking a sleeping console over a network asks three things to cooperate that would rather not. The console has to keep a network stack alive in a low-power state. The router has to keep the console's DHCP lease and forwarding state warm while it sleeps, and cheap routers age both out aggressively. And, going remote, your ISP has to route an unsolicited wake packet to your house, which carrier-grade NAT flatly prevents. When wake works on your LAN but not from outside, none of the three has broken — it is the third, and the fix is a network fix, not a settings fix.

Network, Ports, and NAT

If Remote Play works at home and dies the moment you leave, you are in this section, and you will not be leaving until you understand three letters: NAT. Everything here is about getting a packet from the wider internet to a specific console behind your router, which is a problem home networks are actively designed to make hard.

The ports Remote Play uses

Remote Play and its compatible clients use a small, well-known set of ports. You rarely need to forward all of them — Sony's servers help clients hole-punch through typical home NAT — but when your firewall is strict or your NAT is symmetric, these are what you open:

The pattern worth remembering: TCP 9295 sets up the session, the UDP ports carry the actual game, and the 3478–3480 range is how your client and console find each other through Sony's rendezvous servers when neither has a clean public address.

Port forwarding when remote fails

If hole-punching is not enough, forward the ports manually. The prerequisite is a fixed address for the console, or your forwards will drift to the wrong device the next time DHCP reshuffles. Reserve the console's IP by MAC address in the router, then forward:

# 1. Give the console a fixed address (DHCP reservation by MAC).
PS5 LAN IP: 192.168.1.20

# 2. Forward these to 192.168.1.20 in the router:
  TCP  9295            # registration + control
  UDP  9295-9304       # stream, feedback, discovery fallback
  UDP  9302            # PS5 discovery

# 3. From a device on a DIFFERENT network, probe reachability:
nc -vz  your.public.ip 9295          # TCP control port
nmap -sU -p 9302 your.public.ip      # UDP discovery (open|filtered is normal)

The nc line is the one that gives a clean yes or no: if TCP 9295 answers from outside, your control path is open and the problem is elsewhere. UDP probes are murkier — open|filtered is the normal, unhelpful answer for a closed-but-not-rejecting port — which is exactly why you test the TCP port first.

CGNAT is the wall

Here is the failure that no amount of port forwarding will fix. If your internet provider puts you behind carrier-grade NAT — increasingly common on fibre, near-universal on mobile and on 5G home internet — you do not have a public IP address at all. You share one with hundreds of neighbours. There is no port on the internet that reaches your router, so there is nothing to forward. The symptoms are textbook: flawless on your home LAN, dead from every other network, NAT Type 3 on the console test. Your options are three. Ask the ISP for a real public IP, which some grant for free and some charge for. Sidestep it with a VPN back to your home network, covered in the advanced section, which makes a remote client look local. Or stop fighting and use the Portal's cloud streaming, launched 5 November 2025 for Plus Premium members, which runs from Sony's servers and does not care about your NAT at all — the one scenario where paying Sony genuinely solves the problem.

Turning On 1080p High Quality

For years the honest knock on Remote Play was that it looked soft — a smeary 720p that reminded you it was a stream. The March 2026 update is Sony's answer, and it is worth understanding precisely what it does and does not do before you go looking for it in menus.

What the March 2026 update actually did

On 17 March 2026 the Portal's system software (version 7.0.0, rolling out globally from the 18th) added a 1080p High Quality option for both Remote Play and cloud streaming. Read that carefully: the Portal's screen was always 1080p. The change is not more pixels, it is more bitrate behind the same pixels — a fatter, cleaner encode that stops the picture falling apart in busy scenes. The Portal is currently on 7.0.2, a follow-up performance-and-stability revision. The official app on PC could already select a 1080p Best setting before any of this; the Portal was the client that had been artificially capped lower, and this is what uncapped it. Do not confuse any of it with PSSR, the machine-learning upscaler that lives inside the PS5 Pro and its PSSR update. PSSR runs on the console before the frame is ever encoded; Remote Play's quality mode is about how cleanly that finished frame survives the trip. They are unrelated, and no, there is no PSSR2 riding along in a Remote Play stream.

Turning it on from the Portal

On the Portal, hold the PS button to open the Quick Menu and set the resolution there. Then restart the session — the change does not always apply mid-stream:

# PlayStation Portal -- hold the PS button for the Quick Menu
Max Resolution : 1080p (High Quality)
Frame Rate     : Smooth (up to 60 fps)

# Needs roughly 15 Mbps down. On congestion the Portal quietly
# steps back to 1080p Standard, then 720p, before it drops frames.

Turning it on in the app

In the app the controls live under Settings then Video Quality for Remote Play, and the resolution tiers map to bitrate like this:

# PS Remote Play (PC / Mac / mobile)
# Settings > Video Quality for Remote Play
Resolution : Best (1080p)
Frame Rate : High (60 fps)

# There is no 4K option. 1080p60 is the official ceiling on
# every first-party client, the Portal included.

If you set Best and the picture still looks soft, the app is silently downshifting because your connection cannot hold 15 Mbps. That is not a bug to file; it is the congestion control doing its job, and the fix is bandwidth, not settings.

Chiaki-ng and Asobi

Sony's clients are competent and safe and boring, and they will never run on the device you actually want. That is what the third-party clients are for. Two matter in 2026, and they occupy different corners: Chiaki-ng for the Linux-and-Deck-and-tinker crowd, Asobi for the Apple ecosystem and, interestingly, for cloud streaming without a Portal. Neither is endorsed by Sony, and both can break the day Sony rotates its protocol. Go in with that understood.

Chiaki-ng

Chiaki-ng is the maintained fork — formerly chiaki4deck — of the original open-source Chiaki, and its current release is 1.10.0, dated 3 April 2026. It runs on Windows, macOS, Linux, FreeBSD, Android, and even a homebrew-enabled Switch, and its documentation is explicit that it is not endorsed or certified by Sony. Its advantage over the official app is control: you can push a genuinely high bitrate, choose your hardware decoder, add custom upscalers, and force VSync. The one trick that trips up every newcomer is registration, because Chiaki-ng authenticates against your PSN Account ID — a Base64 string — and not the Online ID you see on your profile:

# chiaki-ng registers against your PSN *Account ID* (Base64),
# NOT your visible Online ID. Get the 8-digit PIN from:
#   Console: Settings > System > Remote Play > Link Device

# GUI: click '+', enter console IP, Account ID, and the PIN.
# Legacy CLI equivalent:
chiaki discover -h 192.168.1.20
chiaki register --host 192.168.1.20 --psn-account-id <BASE64_ACCOUNT_ID> --pin 12345678

Once registered, a sane PS5 profile in its config file looks like this — note the 30000 Kbps bitrate, roughly double what the official app will give you at the same 1080p60:

# ~/.config/Chiaki/Chiaki.conf  (chiaki-ng 1.10.0)
[settings]
resolution_ps5 = 1080p
fps            = 60
bitrate        = 30000        ; ~30 Mbps, well above the app's ~15
codec          = h265
hw_decoder     = auto         ; vaapi (Linux), videotoolbox (macOS), d3d11va (Win)
audio_buffer   = 9600

The project's GitHub repository and its documentation site are the only sources you should trust for builds; a good editorial write-up of the 1.10.0 improvements ran on GamingOnLinux. It is the obvious client to pair with a Steam Deck, which is the exact device the fork was born to serve.

Asobi: Remote Play

Asobi is the newer and more surprising of the two. It is a third-party client that went from version 1.0 on 29 November 2025 to 1.1 on 13 February 2026, 1.1.9 on 26 March 2026, and 1.3.6 by 20 June 2026, and it lives where Chiaki-ng does not: iOS, iPadOS, tvOS, visionOS, macOS, and, via its Steam listing, the Steam Deck. Its party trick, as Tom's Hardware documented, is that it streams not only your own PS4 and PS5 over Remote Play but also PlayStation Plus Premium cloud gaming — the thing Sony had walled behind the Portal — onto a Steam Deck or an Apple TV with no console involved. It also does genuinely novel things on Apple silicon, including a visionOS 2D-to-3D conversion mode for stereoscopic play. The full changelog lives on its own site, and it is worth reading before you commit, because a client this ambitious is also a client with more surface to break.

Which one to pick

Use the official app if you want safety, painless wake-from-anywhere, and no fishing around for a Base64 Account ID; it is the correct default for most people and it is free. Use Chiaki-ng if you live on Linux or a Deck or a Switch, or if you simply want more bitrate than Sony will hand out. Use Asobi if you are in the Apple world or you specifically want Plus Premium cloud streaming without buying a Portal. And accept the shared caveat: the third-party clients do not modify your console, but they can and do stop working when Sony changes the protocol, so keep the official app installed as your fallback.

Five Pitfalls That Break It

Every one of these has cost someone an evening. Read them now and you buy that evening back. They cluster into three kinds of mistake: waking and identity, the network path, and session conflicts.

Wake and account failures

Pitfall 1 — rest mode is not configured, so the console never wakes. The symptom is a client that finds the console and then stalls on connect. The fix is step 4: enable both rest-mode network options. If your router still drops the console while it sleeps, some people schedule the console to stay fully on, but the cleaner fix is a router that keeps DHCP leases warm. Pitfall 2 — the wrong account or a non-primary console produces a sign-in loop. You connect, the screen thinks, and it kicks you back to the device list. The cause is almost always that Console Sharing and Offline Play is off, or the client is signed in as a different user than the console's primary. Match the account, enable console sharing, done.

Network-path failures

Pitfall 3 — the console is on Wi-Fi. This one masquerades as a dozen other problems: artifacting, sudden quality drops, brief freezes. Because the console is the sender, its upstream jitter corrupts frames before they leave the house, and no client-side setting can undo that. Cable the console. Pitfall 4 — the client is on 2.4 GHz Wi-Fi. The 2.4 GHz band cannot reliably sustain 15 Mbps in a real home full of interference, so 1080p High Quality starves and downshifts. Force the client onto 5 GHz or Ethernet. Pitfall 5 — CGNAT or double-NAT. Works on the LAN, dead everywhere else, NAT Type 3. No port forward helps because you have no public address to forward from. Request a public IP, tunnel back with a VPN, or fall back to cloud streaming. This is the pitfall that sends people to buy a Portal thinking their app is broken, when the app is fine and the ISP is the problem.

Session conflicts

Two more that are less about networking and more about rules. Remote Play permits exactly one session at a time, and it cannot run at the same time as Share Play — start either while the other is live and someone gets kicked. And while Remote Play itself is not HDCP-blocked, feeding its output through a capture card downstream can throw a black screen, because the protected content path objects to being recorded. If you are trying to capture a Remote Play session and getting black, connect directly and stop routing it through capture hardware.

The Troubleshooting Table

When it breaks, resist the urge to change five things at once. Find the symptom, apply the single most likely fix, retest. The table is ordered roughly from most to least common.

How to read it

Match your symptom in the left column, read the likely cause, apply the fix, and only then move to the next row if it did not take. The causes are listed in order of probability, so try the first fix before the exotic one — it is almost always rest mode, an account mismatch, or bandwidth, in that order.

The table

When to go nuclear

If nothing in the table lands and the console misbehaves in other ways too — slow menus, apps that will not launch, corrupt downloads — the fault may be the console's own storage state rather than Remote Play. That is the point to clear the PS5 cache and rebuild its database from Safe Mode, which is harmless and occasionally fixes stubborn session drops. Only after that, and only if remote-but-not-local still fails, is it worth deleting the registration on both ends and re-pairing from step 7. Do not lead with the nuclear option; it is the last resort, not the first.

Advanced Tips and Tuning

Once the basics work, the difference between a stream that is fine and a stream you forget is not the real thing comes down to three levers: the network path, the client decoder, and how you get home from outside without opening ports.

LAN tuning

The console's upstream is the scarce resource, so prioritise it. Most routers with any QoS worth the name let you tag a device's traffic as highest priority; do that for the console and, if the router allows it, mark the feedback and control UDP ports so they never queue behind a family member's download:

# Router QoS -- give the console's upstream priority (concept).
Device        : PS5  (MAC AA:BB:CC:DD:EE:FF)
Priority      : Highest
DSCP tag      : EF (46) on UDP 9296-9297
Upstream floor: 20 Mbps reserved
# Feedback and control travel UPSTREAM from console to client;
# starving that path is what produces 'rubber-band' input lag.

If you cannot run an Ethernet cable to the console, powerline or MoCA adapters beat Wi-Fi for the sender in almost every house, because a slightly slower but rock-steady wired-ish link outperforms a fast but jittery wireless one for streaming. Also, ban background downloads on the console during sessions — a game updating in the background will happily eat the entire upstream and leave your stream gasping.

Client-side tuning

Turn the hardware decoder on; software decoding adds latency and cooks the client's battery. Choose your codec by priority: HEVC (h265) is more efficient and looks better per megabit, so it wins on constrained connections, while H.264 decodes with marginally less latency on older client hardware. On Chiaki-ng specifically, the custom upscaler and VSync options in 1.10.0 are worth experimenting with — a good upscaler on a small handheld screen hides a multitude of bitrate sins. And raise the audio buffer a notch if you hear drift; a slightly larger buffer trades a few milliseconds of audio latency for the end of desync, which is the right trade for everything except rhythm games.

Remote-from-anywhere without port forwarding

The cleanest answer to CGNAT and strict NAT alike is to stop exposing anything to the internet and instead put the client and the console's LAN on the same encrypted mesh. WireGuard or Tailscale do this in minutes, and Remote Play then sees a console that looks local no matter where you physically are:

# Beat CGNAT without port forwarding: put the console's LAN and the
# client on the same WireGuard mesh.
# On an always-on box at home (or a router that supports it):
tailscale up --advertise-routes=192.168.1.0/24
# On the client, anywhere in the world:
tailscale up
# Now the client reaches 192.168.1.20 directly. Remote Play sees a
# 'local' console and never touches Sony's relay or your NAT.

This is the single most reliable way to run Remote Play over the internet in 2026. It sidesteps CGNAT entirely, requires no forwarded ports, and encrypts the whole path as a bonus. The only cost is that you need an always-on device at home to advertise the route — a spare Pi, a NAS, or a router that runs the client natively.

The Complete Configuration

Everything above, condensed into one reference you can work down. If your setup matches this, Remote Play will work at home and, network permitting, from the other side of the planet.

Console, app, and Portal

######## CONSOLE  (PS5 or PS4, latest system software) ########
Remote Play ................ Enabled
Console Sharing / Offline .. Enabled (this console set as primary)
Rest Mode:
  Stay Connected to Internet ......... ON
  Enable Turning On from Network ..... ON
Network .................... Wired LAN, NAT Type 2

######## OFFICIAL APP  (PS Remote Play 9.x) ########
Account .................... same PSN account as the console
Resolution ................. Best (1080p)
Frame Rate ................. High (60 fps)
Controller ................. DualSense, paired by USB first then Bluetooth

######## PLAYSTATION PORTAL  (system software 7.0.2) ########
Quick Menu > Max Resolution . 1080p (High Quality)
Frame Rate ................. Smooth (up to 60 fps)
Cloud Streaming ............ optional, PS Plus Premium, no console needed

Network and third-party clients

######## NETWORK ########
Console reservation ........ 192.168.1.20 (by MAC)
Forward to console ......... TCP 9295 ; UDP 9295-9304 ; UDP 9302
Remote client .............. 5 GHz Wi-Fi or Ethernet, 15 Mbps or more down
Behind CGNAT? .............. use WireGuard / Tailscale, or Portal cloud streaming

######## CHIAKI-NG 1.10.0  (optional, third-party) ########
resolution_ps5=1080p ; fps=60 ; bitrate=30000 ; codec=h265 ; hw_decoder=auto
Register with PSN Account ID (Base64) + 8-digit PIN from Link Device

######## ASOBI 1.3.6  (optional, third-party) ########
Platforms .................. iOS / tvOS / visionOS / macOS / Steam Deck
Streams .................... PS4 + PS5 Remote Play, plus PS Plus Premium cloud

Keep the official app installed even if you daily-drive a third-party client, and keep every client updated, because the fastest way to break a working setup is to let one end drift a firmware behind the other. For the canonical firmware notes, Sony's Portal system software page is the reference that will not lie to you.

The Verdict

Remote Play in 2026 is, for the first time, quietly good. The picture is a real 1080p, the clients are mature, and there is finally a way — several ways — to run it on whatever screen you own. It is also, in the way of all Sony hardware, gently nickel-and-dimed: the good picture wants 15 Mbps you may not have, the dedicated handheld now costs $249.99 after an April price rise, and the CGNAT problem that breaks it for a growing share of users is one Sony solves only by selling you a cloud subscription. The technology grew up; the business model did not.

Who should just use the app

Most people. The free PS Remote Play app on a phone you already own, plus a DualSense you already own, delivers the entire experience for nothing. It wakes from anywhere, it needs no Base64 Account ID, and at version 9.x it is stable. If you have a decent home network and a phone clamp, you are done, and you should feel no urge to spend money.

Who should buy the Portal

Buy the Portal for two reasons and no others: you want a dedicated screen that is always charged and never rings, or you specifically want Plus Premium cloud streaming in your hands with no console running at home. If you are choosing which console to stream from in the first place, that is a separate question answered in our PS5 Pro versus PS5 comparison — Remote Play looks the same from either, so buy the console for the games, not the stream.

The Machine's bottom line

Do the twelve steps in order, cable the console, and prove it on your own LAN before you blame the internet. If it works at home and fails outside, it is NAT every single time, and the honest fix is a VPN mesh, not a heavier settings menu. Use the official app by default, reach for Chiaki-ng or Asobi when Sony's hardware list does not include the thing in your hands, and keep them all updated. Get those right and Remote Play stops being a party trick and starts being the reason you left the console under the television in the first place.