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

Remote Play is not a new idea, and pretending otherwise is how you end up disappointed. Sony first shipped the concept in 2006, when a PlayStation Portable could reach across a home network to a PlayStation 3 and render a soft, latent version of whatever was on the television. It was a party trick. It stayed a party trick through the PS Vita, survived Sony's 2012 acquisition of Gaikai — the streaming outfit whose technology became PlayStation Now and, eventually, the PS Plus cloud tier — and only became genuinely useful somewhere around the PS4's mid-life, when home broadband finally caught up with the ambition. In 2026 it crossed one more line: it became good enough that a reasonable person might reach for it instead of walking to the console. This tutorial is about getting it there — a PS5 or PS4 streaming to a phone, a laptop, a Mac, or a PlayStation Portal at a genuine 1080p, with input latency low enough that you stop noticing the network between your thumbs and the silicon.

Twelve steps, roughly thirty minutes if your network cooperates, and considerably longer if it does not. Most of this guide is about making it cooperate. Two events in the first half of 2026 make it worth documenting now. On 18 March 2026, Sony pushed a global PlayStation Portal update adding a 1080p High Quality mode — a higher bitrate ceiling for both Remote Play and Cloud Streaming, buried under Quick Menu, then Max Resolution, then 1080p High Quality, and requiring a session restart to take effect. Then, mid-year, Portal firmware Version 6.0 turned the device from a dumb terminal that needed your console into a standalone streaming box that mostly does not. We cover both, because they change the correct setup depending on what hardware you own. If you only want the fast path, the twelve numbered steps are the tutorial; everything around them is why each step exists, and what to do when it refuses to work.

What Actually Changed in 2026

If you set up Remote Play in 2021 and gave up because it looked like a wet oil painting, the news is that most of your objections have expiry dates now. The protocol did not change; the ceilings did, and one piece of hardware quietly stopped being a paperweight.

Remote Play Is Old. The Portal Is What Changed.

The mechanics of Remote Play — encode the console's framebuffer, ship it over UDP, decode it on a client, ship the controller inputs back — have been stable since the PS4 era. What changed in 2026 is the PlayStation Portal, the 8-inch handheld Sony launched in November 2023 as a device with exactly one job: be a screen and two DualSense halves for a PS5 sitting elsewhere in your house. For two years the Portal was a thin client and nothing more. If your console was off, or your network hiccuped, the Portal was a $200 brick with excellent haptics. Version 6.0, released mid-2026, ended that dependency by adding native PS5 game streaming — the device can now pull games from Sony's data centres directly, no console in the loop. It is the same trajectory OnLive charted and died on in 2015 (Sony bought OnLive's patents that year, which is not a coincidence), except this time the back end is a decade of PlayStation Now infrastructure instead of a startup's credit line.

1080p High Quality, Finally

The single most requested Remote Play improvement for a decade was make it sharper. On 18 March 2026 Sony delivered a global Portal update introducing a 1080p High Quality mode that raises the bitrate ceiling during both Remote Play and Cloud Streaming. Engadget's coverage the same week framed it as Sony chasing 'smoother interactions and a more seamless experience,' which is marketing for 'we stopped starving the encoder.' The practical effect is real: at a sufficient upstream bitrate, text stops smearing and gradients stop banding. The catch, and there is always a catch, is that the mode is gated on bandwidth and on restarting the session. You do not get it by wishing; you get it by feeding the encoder at least the 15 Mbps Sony recommends and then restarting so the negotiation runs again.

What Remote Play Still Refuses to Do

Precision matters more than enthusiasm, so here is the fence line. Sony's own official Remote Play documentation states plainly that some games do not support Remote Play at all, and that PlayStation VR2, the original PSVR, and the PlayStation Camera are incompatible peripherals — the headset tracking and passthrough simply do not survive the round trip. You also cannot run Share Play and PS Plus Premium cloud streaming simultaneously with a Remote Play session; they are mutually exclusive by design, not by bug. And Remote Play is not a capture pipeline: if your goal is a clean recording for editing or a broadcast overlay, you want a proper PS5 capture card feeding OBS at 4K60, not a compressed stream you re-compress. Remote Play is for playing at a distance. Keep the job description narrow and it will not disappoint you.

Prerequisites: Hardware, Software, Bandwidth

Every failed Remote Play setup I have ever diagnosed failed in one of three categories: the console was not actually ready, the client was the wrong version, or the network could not carry the load. Handle all three before you touch a single menu and you will save yourself the thirty-minute troubleshooting spiral that ends with you reinstalling drivers at midnight.

The Console Side

You need a PS5 (any model — disc, digital, Slim, or Pro) or a PS4, running current system software. 'Current' is not pedantry: the 1080p High Quality negotiation and the Portal 6.0 features are gated on firmware, and a console several updates behind will either refuse to pair or silently cap itself at 720p. Update the console fully before anything else. You also need the console configured to stay reachable while it sleeps, which is a power setting most people never open — covered in its own section below, because it is the single most common reason wake-up fails. Finally, the account signed into the console must be the account you will use on the client. Remote Play authentication is account-bound; a guest profile or a second family account will not register.

The Client Side

Your options are the official PS Remote Play app on Windows, macOS, iOS, or Android; a PlayStation Portal; or a third-party client such as Chiaki-ng for people who like to see the wiring. The official Android build (package com.playstation.remoteplay, published by PlayStation Mobile Inc. out of 2207 Bridgepointe Pkwy, San Mateo) lives on the Google Play Store and requires a PS5 or PS4 to function — it is a client, not a console emulator. On desktop, install from Sony's official Remote Play page and note the version. This matters in 2026 specifically: the Windows build reported as v9.0.0.2120 developed a habit early in the year of crashing a few minutes into a session, a defect logged extensively in the r/remoteplay community. If you are on that build and it dies on you, the fix is not superstition — it is reinstalling, updating GPU and chipset drivers, and firewall exceptions, in that order. You will need a supported controller: a DualSense or DualShock 4, paired to the client by USB or Bluetooth.

Bandwidth: The 15 Mbps Number

Sony's published requirement, restated across its download page and the Portal documentation through late 2025 and into 2026, is a broadband connection of at least 5 Mbps for basic use and at least 15 Mbps for a high-fidelity experience. A 2026 Tech Insider setup refresh confirmed the same 15 Mbps floor holds on Australian NBN, and — importantly — that standard Remote Play needs no PS Plus subscription to run. Treat 5 Mbps as the number below which you should not bother, and 15 Mbps as the number below which the 1080p High Quality mode will quietly downshift. And understand which 15 Mbps matters: it is the upload at the console's location and the download at the client's, at the same time, sustained, with low loss. The next section is about why that distinction ruins more setups than any other single factor.

Network First: The Part Everyone Skips

Here is the deadpan truth the setup wizards will never tell you: Remote Play is a networking exercise wearing a video game's clothes. The app is a thin shell over a UDP transport, and UDP is unforgiving. Get the network right and the software is trivial. Get the network wrong and no amount of reinstalling will save you.

Upload Is the Number That Matters

When people quote their internet speed they quote download, because that is the number the ISP prints on the box and the number the browser speed test shows first. Remote Play does not care about your download at home. When you are sitting on the couch streaming the PS5 in the next room, the console is the sender — it needs upload headroom to the client. When you are away from home streaming back to the house, the console still needs upload at the house end to push video out to the internet. In both directions, the console-side upstream is the bottleneck, and residential upstream is routinely a tenth of downstream. A '400 Mbps' cable plan with 12 Mbps upload will fail the 15 Mbps Remote Play recommendation while the marketing number laughs at you. Test upload specifically, at the console's location, before you blame anything else.

Ports, UPnP, and NAT

On the same LAN, Remote Play discovers the console by broadcast and needs no manual configuration. The moment you leave the house, you are asking one NAT to accept an inbound session through to a specific device, and that is where it breaks. Remote Play has used the same ports since the PS4 era: TCP 9295 for registration and control, UDP 9296 and 9297 for the audio, video, and input streams, and UDP 9302 for discovery and wake probes. Most home routers will open these automatically if UPnP is enabled and the console asks — which it does. If UPnP is off, or you are behind carrier-grade NAT (CGNAT), inbound sessions will fail no matter how many times you re-pair. CGNAT is the quiet killer here: your ISP shares one public IPv4 address across many customers, there is no port to forward because the port is not yours, and the only real fixes are a static IP from the ISP, an IPv6 path, or a relay. If remote-but-not-home is your use case and it simply will not connect, CGNAT is the first hypothesis, not the last.

2.4 GHz, 5 GHz, and Ethernet

Wi-Fi band selection is not audiophile fussiness; it is the difference between 20 ms and 150 ms of input lag. The 2.4 GHz band is congested, low-bandwidth, and shared with every microwave and baby monitor in the building; it will technically carry Remote Play and will feel like playing through syrup. The 5 GHz band has the headroom and the low latency Remote Play needs. Ethernet, where you can run it, removes the variable entirely. The single highest-leverage change most people can make — wire the console to the router by cable and put the client on 5 GHz — costs the price of a patch cable and fixes more stutter than any setting in the app. If you have ever wired a console for a lower-latency competitive setup the way people do when weighing a PS5 against a Series X, the same instinct applies double here.

Enabling Remote Play on the Console

The console-side setup is three settings deep, and two of them are the ones people miss. Do these in order and the client will find the console on the first try.

Turning the Feature On

On the PS5, open Settings, then System, then Remote Play, and switch on Enable Remote Play. On the PS4 the path is Settings, then Remote Play Connection Settings, and the same toggle. This is off on some fresh setups and, more annoyingly, can revert to off after certain factory-level operations. It is the first thing to re-check if a previously working setup suddenly cannot be found. The toggle costs nothing and gates everything downstream.

Rest Mode: The Setting That Breaks Wake-Up

This is the one. For the console to answer a Remote Play request while it sleeps — which is the entire point, since Wikipedia's own summary of the feature notes you never have to turn on the TV once a session is live — it must keep its network interface alive in Rest Mode. On the PS5: 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. On the PS4 the equivalents live under Power Saving Settings, Set Features Available in Rest Mode. If you skip this, the console will connect perfectly while it is awake and vanish the instant it sleeps, and you will waste an hour convinced the app is broken when the console simply pulled the network cable on itself. Enable both. There is no downside except a rounding error of standby power.

Linking Your Device

With the feature on and Rest Mode configured, link the client while both devices are on the same local network. In the PS Remote Play app, sign in with the same PSN account, and the app will discover the console automatically. This first, local pairing is what registers the client as trusted — it is the handshake that lets later sessions authenticate from anywhere. Do it at home, on the same Wi-Fi, once. Trying to register for the first time from a coffee shop is a common self-inflicted wound; the registration exchange wants the LAN, and skipping the local step is why remote-first attempts stall on an error code with no explanation.

The 12 Steps: Zero to 1080p

Everything above is context. This is the procedure. Each step includes the reason it exists, because a step you understand is a step you can debug. Do them in order; several depend on the ones before.

Steps 1–4: Prepare the Console

1. Update the console's system software fully. Settings, System, System Software, System Software Update and Settings, then let it pull the latest. Rationale: the 1080p High Quality negotiation and every Portal 6.0 feature are gated on current firmware, and a mismatched, out-of-date console will either refuse to pair or silently cap the stream at 720p. Start current or debug a moving target.
2. Enable Remote Play on the console. PS5: Settings, System, Remote Play, Enable Remote Play. PS4: Settings, Remote Play Connection Settings. Rationale: the feature is the gate for everything downstream and is off on some setups. If the client can never find the console, this toggle is suspect number one.
3. Configure Rest Mode networking. Enable Stay Connected to the Internet and Enable Turning On from Network under Power Saving. Rationale: without these two, the console drops off the network the moment it sleeps, so wake-on-demand — the entire reason to use Remote Play — silently fails while everything looks fine.
4. Give the console a static LAN IP via DHCP reservation. Do this in the router, pinning the console's MAC address to a fixed address. Rationale: port-forwarding rules and discovery break the instant the console's IP moves after a lease renewal. A reservation makes the address permanent so your rules keep pointing at the right box.

Steps 5–8: Pair the Client

1. Install the correct client for your platform. The official app from Sony's page, the Portal, or Chiaki-ng. Rationale: version matters — the v9.0.0.2120 Windows build has a documented mid-session crash, so if you land on it and it dies, you already know the fix path (reinstall, drivers, firewall) rather than flailing.
2. Sign in with the same PSN account on client and console. Rationale: Remote Play authentication is account-bound. A second family profile or guest account will authenticate to Sony but never register against the console, producing a connection that fails for reasons the error message will not explain.
3. Pair the client to the console on the same local network. Launch the client at home, on the same Wi-Fi, and let it auto-discover. Rationale: this local handshake is what registers the device as trusted for all future remote sessions. Skip it and try to register first from outside, and the exchange stalls — the registration step wants the LAN.
4. Run a real bandwidth test at the console's location. Measure upload, not download, and confirm at least 15 Mbps sustained. Rationale: 15 Mbps is Sony's high-fidelity recommendation and the threshold below which 1080p High Quality downshifts. Testing download tells you nothing useful about the direction that actually limits you.

Steps 9–12: Tune to 1080p High Quality

1. Confirm UPnP or forward the ports for off-LAN use. Enable UPnP, or forward TCP 9295 and UDP 9296, 9297, 9302 to the console's reserved IP. Rationale: on the LAN this is unnecessary, but the first time you connect from outside the house, an un-traversed NAT will drop the inbound session cold. Set it up before you travel, not after it fails.
2. Start a session and validate video, audio, and controller. Wake the console from the client and confirm all three work before touching quality settings. Rationale: you want a known-good baseline. Changing resolution and codec on top of a broken session just adds variables to an already failing test.
3. Raise resolution to 1080p and, on the Portal, enable 1080p High Quality, then restart the session. Quick Menu, Max Resolution, 1080p High Quality. Rationale: this is the 18 March 2026 feature, and it explicitly requires a session restart to renegotiate — the change does not apply to the session you are already in, only to the next one you start.
4. Lock in the working configuration. Wire what you can, note the exact settings, and save them. Rationale: Remote Play setups drift as firmware and drivers update. A written record of the state that worked turns a future breakage from an archaeology dig into a five-minute diff.

Config, Router Rules, and Firewall

The menus get you a working same-room session. Off-LAN reliability and the ability to actually diagnose failures come from the plumbing underneath: forwarded ports, firewall exceptions, and a couple of commands that tell you whether the problem is the network or the app before you waste an evening on the wrong one.

Router: Reservation and Port Forwarding

First pin the console's address, then forward the four ports to it. Reserving the IP first is not optional — forwarding to an address that later moves is how rules silently rot. The exact router UI varies, but the target state is this:

# PS Remote Play — forward these to the console's reserved LAN IP.
# Same ports the protocol has used since the PS4 era.

Protocol   Port(s)     Direction   Purpose
--------   -------     ---------   ---------------------------------
TCP        9295        in/out      Session registration + control
UDP        9296        in/out      Video / audio / input stream
UDP        9297        in/out      Video / audio / input stream
UDP        9302        out         Discovery + console wake probe

# Step 1: DHCP reservation — bind console MAC to a fixed IP.
#   e.g. AC:8B:A9:xx:xx:xx  ->  192.168.1.42  (permanent lease)
# Step 2: Forward all four rows above to 192.168.1.42.
# Step 3: Leave UPnP enabled as a fallback for clients that
#         negotiate their own mappings (the Portal does this).

Windows: Firewall Exceptions

The classic Windows failure — connects, runs for about a minute, then freezes or drops — is a stateful firewall killing the inbound UDP return stream once it decides the flow is stale. Sony's official connection-troubleshooting page explicitly names antivirus and firewall software as blockers and recommends adding the app to the exceptions list. Run this in an elevated prompt; adjust the install path to match your machine:

:: Run as Administrator. Allows the client's control + stream
:: ports and whitelists the executable so a stateful firewall
:: stops dropping the UDP return path after ~60 seconds.

netsh advfirewall firewall add rule name="PSRP TCP In" dir=in action=allow protocol=TCP localport=9295
netsh advfirewall firewall add rule name="PSRP UDP In" dir=in action=allow protocol=UDP localport=9296-9297
netsh advfirewall firewall add rule name="PSRP App" dir=in action=allow program="C:\Program Files (x86)\Sony\PS Remote Play\RemotePlay.exe" enable=yes

:: If the app still dies a few minutes in on build v9.0.0.2120:
::   1) update GPU + chipset drivers
::   2) reinstall the app clean
::   3) re-add these rules (a reinstall can wipe them)

Validating the Path Before You Blame the App

Before you reinstall anything, prove where the problem is. Two commands settle it. First, ping the console's LAN IP from the client — you want near-zero latency and zero loss on the same network:

$ ping -c 5 192.168.1.42
PING 192.168.1.42 (192.168.1.42): 56 data bytes
64 bytes from 192.168.1.42: icmp_seq=0 ttl=64 time=1.02 ms
64 bytes from 192.168.1.42: icmp_seq=1 ttl=64 time=0.98 ms
64 bytes from 192.168.1.42: icmp_seq=2 ttl=64 time=1.11 ms
64 bytes from 192.168.1.42: icmp_seq=3 ttl=64 time=0.95 ms
64 bytes from 192.168.1.42: icmp_seq=4 ttl=64 time=1.04 ms

--- 192.168.1.42 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.95/1.02/1.11/0.06 ms

Sub-2 ms and zero loss on the LAN means the local path is clean and the fault, if any, is farther out. Then confirm you actually have the upstream Sony recommends — test upload, and watch loss as closely as throughput:

$ iperf3 -c speedtest.example.net -u -b 20M -R
[ ID] Interval          Transfer     Bitrate        Jitter   Lost/Total
[  5] 0.00-10.00  sec   22.4 MBytes  18.8 Mbit/s    0.42 ms  3/1620 (0.19%)

# 18.8 Mbit/s at 0.19% loss clears the 15 Mbps bar with margin.
# Under 15 Mbit/s, or above ~2% loss, the 1080p High Quality
# mode will renegotiate down to 720p to protect the stream.

PlayStation Portal 6.0: Streaming Without a Console

The Portal deserves its own section because Version 6.0 changed what the device fundamentally is. If you own one, the correct setup depends on whether you are doing Remote Play to your own console or using the new cloud path — and the two have different requirements, different costs, and one genuinely irritating control change.

2,800 Games, No Console Required

Version 6.0 launched full PS5 game streaming from the cloud, letting Portal owners stream over 2,800 digitally owned PS5 titles from their own library without a PS5 console in the loop at all, plus access to 3,000-plus titles from the PS Plus catalogue. Polygon's 2026 coverage put the significance bluntly: for many owners this eliminates the need for a PS5 or a Remote Play setup entirely, which is a strange thing for a Remote Play tutorial to admit, but precision demands it. If your games are digital and your internet is good, you can now bypass the entire console-side procedure above and stream from Sony's data centres. Remote Play to your own console still wins on latency and on playing disc-based or non-supported titles, but the cloud path is no longer a lesser sibling — it is a parallel product living in the same box. The Portal has quietly become the kind of standalone handheld people cross-shop against a Switch 2 or a Steam Deck, rather than a mere accessory.

PS Plus Premium and the Fine Print

Here the wallet enters. Standard Remote Play to your own console needs no subscription — that has not changed and it is worth repeating, because Sony's marketing blurs the line. But streaming from the PS Plus catalogue via the Portal's new feature requires PlayStation Plus Premium, billed as an ongoing recurring fee at the then-current PS Store price. Streaming your own owned games is one entitlement; streaming from the Premium catalogue is another, and the second one is a subscription with a meter running. Know which one you are using. The failure mode is subscribing to Premium, assuming it is now required for everything, and paying monthly for a Remote Play session that never needed a cent. Read the entitlement, not the upsell.

The PS Button Remap Nobody Asked For

Version 6.0 also rewired the PS Button, and if you built muscle memory on the old behaviour, this will annoy you for a week. Previously a press of the PS Button could wake the PS5. As of 6.0, a short press always opens the Portal's quick-menu sidebar and no longer wakes the console; the long-press now returns you to the home screen. It is a defensible consolidation — one button, two predictable actions — but it means the old wake-the-console reflex is dead, and if your console is asleep you now wake it by other means. This is by design, not a fault, which is exactly why it will not show up in any troubleshooting list except this one. Version 6.0 also added 3D Audio to both PS5 game streaming and Remote Play, provided the individual title supports 3D Audio, delivering positional audio through headphones during a session — a genuinely nice addition that, unlike the button change, nobody will complain about.

Common Pitfalls and Their Fixes

These are the failures I see repeated most, grouped by what actually causes them. Each is common precisely because the setup wizard never warns you about it. Read these once and you skip the corresponding hour of frustration.

Network Pitfalls

Pitfall 1 — Trusting Wi-Fi for the console. The console on 2.4 GHz Wi-Fi is the single most common cause of macroblocking and stutter. Fix: wire the console to the router by Ethernet, or at minimum move it to 5 GHz. This one change resolves more image-quality complaints than every in-app setting combined. Pitfall 2 — Testing download instead of upload. You confirm your '400 Mbps' plan and cannot understand why 1080p keeps collapsing. Fix: test upload at the console's location; residential upstream is often a tenth of downstream and is the real ceiling. Pitfall 3 — Double NAT or CGNAT. Off-LAN sessions fail no matter how many times you re-pair. Fix: identify whether your ISP puts you behind carrier-grade NAT; if so, request a static IPv4, use an IPv6 path, or accept that off-LAN Remote Play needs a relay.

Power and Wake Pitfalls

Pitfall 4 — Forgetting Rest Mode networking. Everything works while the console is awake and dies the instant it sleeps. Fix: enable both Stay Connected to the Internet and Enable Turning On from Network under Power Saving. This is the most common wake-up failure and it is a two-toggle fix. Pitfall 5 — Antivirus or firewall silently blocking. The session connects, runs about a minute, then freezes — the classic stateful-firewall drop, and exactly the pattern behind many v9.0.0.2120 crash reports. Fix: per Sony's own guidance, add the app to firewall exceptions or disable the interfering rule, then update GPU and chipset drivers. If the console itself is misbehaving after a firmware update, a Safe Mode cache clear on the PS5 resolves a surprising share of otherwise inexplicable connection faults.

Expectation Pitfalls

Pitfall 6 — Expecting Remote Play to be a capture or broadcast tool. People pipe Remote Play into recording software and wonder why the output is soft and laggy. Fix: understand that Remote Play is a compressed stream meant for playing, not a clean source; for recording or streaming, use dedicated capture hardware. Pitfall 7 — Assuming the Portal's cloud streaming is free, or that Remote Play needs a subscription. Both errors cost money or block you. Fix: remember standard Remote Play needs no subscription, while the Portal's PS Plus catalogue streaming requires PS Plus Premium — two different entitlements, and you should know which you are invoking before you are surprised by a paywall or a bill.

Troubleshooting Table

When something breaks mid-session, you want a symptom-to-fix lookup, not an essay. Match the symptom, apply the fix, move on. The table below covers the failures that account for the overwhelming majority of Remote Play support threads in 2026.

Connection Failures

Connection problems are almost always network or power state, and the error codes rarely tell you which. Work top-down: is the console reachable, is it awake, is the path traversable. The first three rows of the table are, in practice, where 80% of 'cannot connect' complaints resolve.

Video and Audio Artifacts

Artifacts — blockiness, black screens, desync — split cleanly into bandwidth problems and decoder problems. Blockiness that worsens with motion is bandwidth; a black screen with working audio is almost always the client's video decoder or GPU driver. Knowing which family you are in halves the search space before you change a single setting.

The Table

Advanced Tips: Latency, Codecs, Chiaki

Once the basics hold, there is a second tier of tuning that separates a session you tolerate from one you forget is even remote. This is where you trade convenience for control, and where the open-source world quietly outbuilt Sony years ago.

Wire Everything You Can

The advanced-tips answer to almost every latency question is the same as the beginner answer, only more so: eliminate wireless links. Wire the console to the router. If your client is a PC, wire it too. If the client must be wireless, force it onto a clean 5 GHz channel with a wide band and nothing else contending — a dedicated SSID for the console and client, isolated from the household's phones and laptops, is not paranoia, it is engineering. Every wireless hop you remove takes a variable-latency, packet-loss-prone segment out of the loop. The Portal cannot be wired, which is the one place this advice runs out; for everything else, copper beats radio every time, and the difference at the thumb is measurable.

Chiaki-ng: The Client Sony Didn't Write

Around 2019, someone reverse-engineered the Remote Play protocol and released Chiaki, an open-source client that spoke Sony's language without Sony's blessing. It survives today as the maintained chiaki-ng fork on GitHub, with the original still archived at thestr4ng3r/chiaki. It matters for advanced users because it exposes the knobs Sony hides: exact bitrate, codec selection, hardware decoder backend, audio buffer sizing, and framerate, all in a plain config file you can version and diff. It runs on Linux, on handhelds, on machines the official app abandoned. The legality is the comfortable kind — it interoperates with hardware you own using a protocol you are authorised to use, which is a very different thing from circumventing a copy-protection measure, and no court has treated protocol interoperability of this sort as a DMCA §1201 violation. A representative Chiaki-ng config looks like this:

# ~/.config/Chiaki/Chiaki.conf  (Linux / macOS)
# Third-party client speaking the same protocol as the Portal.

[settings]
resolution=1080p
fps=60
bitrate=15000            ; kbps — matches Sony's 15 Mbps guidance
codec=h265               ; HEVC; falls back to h264 on old clients
audio_buffer_size=9600
hardware_decode=true
video_hw_decoder=vaapi    ; videotoolbox on macOS, d3d11va on Windows

[registration]
console_type=ps5

3D Audio and HDR

Two 2026-era touches are worth enabling deliberately. Version 6.0 added 3D Audio to Remote Play and cloud streaming for titles that support it, so if you play through headphones, confirm the game is 3D-Audio-compatible and enable it — positional audio survives the stream and is a real immersion upgrade at zero latency cost. HDR is the opposite lesson: it looks superb when the whole chain supports it and produces washed-out or black-screen output the moment one link does not. If you hit colour or black-screen trouble, disabling HDR on the console is a fast, reversible diagnostic that isolates whether the fault is the tone-mapping path or something else. Enable what your chain fully supports; treat HDR as a variable to eliminate the instant the image looks wrong.

The Complete Working Configuration

Here is the entire configuration in one place — the state that produces a stable 1080p High Quality session with low latency. Reproduce this and you reproduce the result. Print it, save it, diff against it when a future update breaks something and you cannot remember what changed.

Console Settings

The console is the sender and the wake target, so its settings decide whether the session exists at all. Get these four right and the console side is done.

# ---- PS5 / PS4 CONSOLE ----
System software:            latest (updated before setup)
Remote Play:               ENABLED
  PS5 path:  Settings > System > Remote Play
  PS4 path:  Settings > Remote Play Connection Settings
Rest Mode networking:
  Stay Connected to Internet:        ON
  Enable Turning On from Network:    ON
  path: Settings > System > Power Saving >
        Features Available in Rest Mode
Account:                   same PSN account as the client
HDR:                       off if diagnosing image faults

Network Settings

The network is where reliability lives or dies. A reserved IP, four forwarded ports, and a wired console are the load-bearing pieces; the rest is margin.

# ---- ROUTER / NETWORK ----
Console connection:        Ethernet (preferred) or clean 5 GHz
DHCP reservation:          console MAC -> 192.168.1.42 (fixed)
Port forwards -> 192.168.1.42:
  TCP 9295                 registration + control
  UDP 9296                 stream
  UDP 9297                 stream
  UDP 9302 (out)           discovery + wake probe
UPnP:                      enabled (fallback for Portal)
Upstream bandwidth:        >= 15 Mbps sustained, < ~2% loss
CGNAT:                     none (required for off-LAN sessions)

Client Settings

Finally the client, whose job is to decode fast and stay out of the way. The official app auto-negotiates most of this; the values below are what a correctly negotiated 2026 session looks like, and what you set by hand in Chiaki-ng.

# ---- CLIENT (app, Portal, or Chiaki-ng) ----
App version:               current (avoid stale v9.0.0.2120 on PC)
Controller:                DualSense or DualShock 4
Connection:                Ethernet or 5 GHz Wi-Fi
Resolution:                1080p
1080p High Quality:        ON  (Portal only)
  path: Quick Menu > Max Resolution > 1080p High Quality
  note: RESTART the session to apply
Framerate:                 60 fps
Codec:                     H265 (HEVC), H264 fallback
Hardware decode:           ON
3D Audio:                  ON for supported titles, via headphones
Firewall:                  app added to exceptions (Windows)

# Validated result: stable 1080p, sub-frame local latency,
# no macroblocking above the 15 Mbps upstream floor.

That is the whole machine. The irony worth sitting with is that in 2026 the hardest part of Remote Play is no longer Remote Play — it is the network underneath it and the entitlements around it. Sony spent twenty years turning a PSP party trick into something that genuinely disappears in use, and the remaining friction is the friction of home networking, which was never theirs to fix. Get the upstream, wire what you can, forward the four ports, and remember which subscription you are actually using. The stream will take care of itself. And when you inevitably start wondering whether the next console generation makes any of this obsolete, that is a question for the PS6 release-date timeline, not this guide — for now, the couch and the coffee shop are close enough.