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

Sony has been shipping Remote Play, in one form or another, since a PSP could borrow a PS3 across the living room. In 2026 it remains the most honest feature PlayStation makes: a video stream of your console, encoded on the box you already paid for, sent to whatever screen you happen to be sitting in front of. No rented cloud instance. No separate games catalog to lease. No monthly tithe for the privilege of playing what you own. The PS5 does the work; some other device shows the picture. That is the entire trick, and it has aged better than nearly everything Sony has bolted on around it.

Sony's official Remote Play page, last touched on 21 August 2026, still describes the feature in flat, unglamorous terms: stream and play PS4 and PS5 games, switch between games, look at the console home screen, and browse the menus, all from a compatible device somewhere else. That is refreshingly modest for a company that will happily sell you a dedicated handheld whose whole job is to do this one thing. And it runs on more clients than most people realize: Windows, Mac, iPhone, iPad, Android phones, Android TV, another PS5, another PS4, and the PS Portal.

This is the 30-minute version: twelve numbered steps from a cold console to a wired 1080p session, plus the exact ports, the pitfalls, an eleven-row troubleshooting table, and a complete working configuration you can copy verbatim. We will also cover Chiaki-ng, the open-source client for people who want tuning knobs Sony refuses to expose. Deadpan promise up front: most of your problems will be network problems wearing a software costume.

Why It Still Matters in 2026

The pitch, with the marketing scraped off

Remote Play is local-hardware streaming. Your console encodes a live H.264 or H.265 video feed of whatever it is rendering, ships it across your network to a client, and the client sends your controller input back. Compare that to cloud gaming, where the game runs on a stranger's server farm and you rent access by the hour. Remote Play has no per-title licensing, no queue, no data-center round trip beyond your own router when you are at home. When you are away, the only extra hop is your ISP and theirs. It is the difference between borrowing your own car and hailing a cab that happens to look like it.

The other reason it endures is platform reach. A single feature turns a locked-down console into something you can play on a work laptop at lunch, a phone on a delayed train, or a TV in the spare room without buying a second PS5. If you have ever weighed the merits of a gaming PC against a console, and we have written at length about how that math actually shakes out in 2026, Remote Play quietly hands the console one of the PC's best tricks: play anywhere, on whatever hardware is nearby.

What actually changed in 2026

Two things worth caring about. First, the desktop app kept moving: the Windows client went from version 8.0.0.14120 on 28 March 2025 to 8.5.0.08070 on 19 September 2025 and then to 9.0.0.02120 on 29 May 2026. The Google Play listing was updated on 20 May 2026, and the iOS build carries a 2 October 2025 date requiring iOS 15.0 or later. This is not abandonware; it is a maintained product with a support lineage that traces straight back to Sony's own SCEI engineering domain.

Second, and more interesting, a software update pushed on 17 March 2026, first surfacing on the PS Portal, added a 1080p High Quality mode along with interface refinements. For years Remote Play topped out at 720p in practice for most people; the 1080p tier is the single biggest image-quality change the feature has seen in a long while. It also reiterated the bandwidth guidance that has not moved: 5 Mbps minimum, 15 Mbps recommended.

Who this is genuinely for

People with a decent home network and a reason to not be tethered to the TV. Commuters. Renters juggling one console across two rooms. Anyone who wants to keep grinding a save file on a laptop while the household claims the living room set. It is a poor fit for twitch-timing fighting-game frames over hotel Wi-Fi, and we will be honest about that in the latency section. But for the enormous middle ground of single-player and slower-paced games, it is close to magic that requires no magic to set up, just patience and a wired connection.

What Remote Play Actually Is

It is a video stream, not sorcery

Strip away the branding and Remote Play is three streams sharing one session: a compressed video feed flowing from console to client, a compressed audio feed alongside it, and a low-bandwidth input feed flowing back the other way. The console is the encoder and the server. The client is the decoder and the display. Every visual glitch you will ever see, blockiness, smearing, the picture dissolving into confetti, is the encoder being told to produce more data than the pipe between you and the console can carry, and dropping quality to compensate.

This framing matters because it tells you where to look when things break. If the game runs fine on the TV but looks like a fax over Remote Play, the console and the game are innocent. The network is the defendant, every time. The console does not know or care whether the client is in the next room or in another country; it just fills a buffer and hopes the far end drains it fast enough.

Remote Play versus cloud streaming

Sony sells both, and they are constantly confused. Cloud streaming runs the game on Sony's servers and is gated behind a PlayStation Plus Premium tier and a title catalog. Remote Play runs the game on your console and is free, with the only requirement being that you own a PS5 or PS4 and can reach it over the internet. If your console is off and unplugged, cloud streaming may still work; Remote Play absolutely will not, because there is nothing to stream from. Keep the distinction straight, because the fixes for one do nothing for the other.

The latency truth, stated plainly

You will see breathless claims of near-instant response, and once in a while a spec sheet will imply single-digit-millisecond latency. Ignore it. Real glass-to-glass latency, the delay from your thumb moving to the pixel changing on your screen, is more honestly in the region of 25 to 40 milliseconds on a good wired local network, and worse over the internet. A LAN ping of under one millisecond is not the number you feel; the felt number includes capture, encode, transmit, decode, and display, and every one of those stages costs time. Remote Play is superb for a sprawling RPG and merely tolerable for a rhythm game. Plan accordingly and you will never be disappointed; expect zero lag and you will rage.

Prerequisites: Hardware, Apps, Network

The console: PS5 or PS4, and one caveat

You need a PlayStation 5 or a PlayStation 4. The console is not optional and there is no PC-only mode; the whole point is that the console does the rendering. Both generations are supported as hosts in 2026, but the newest quality tiers, notably the 1080p High Quality mode, are a PS5 story. A PS4 will happily serve Remote Play, but do not expect it to match a PS5's image or its ability to push the higher-resolution path. The console must be signed into your PSN account, and that account must be the one you use on the client.

One frequently missed setting: the console you stream from should have Console Sharing and Offline Play enabled for your account (Users and Accounts, then Other), which designates it as your primary console for that profile. Skipping this is a leading cause of authentication errors that look like network faults but are not.

The client and its app versions

Pick your poison. The official app exists for Windows, Mac, iOS, iPadOS, Android, and Android TV, and Remote Play also runs console-to-console and on the PS Portal. Concrete 2026 version markers: the Windows client is at 9.0.0.02120 as of 29 May 2026; the Android listing was refreshed on 20 May 2026; the iOS build is dated 2 October 2025 and requires iOS 15.0 or later. For Android there is no single hard floor advertised, the Play listing reports that requirements vary by device, but Android 10 or newer is the safe practical baseline in 2026. The existence of a dedicated Android TV app means your living-room television can be a Remote Play client without a console attached to it at all.

Note for the historically minded: the PC and Mac clients are not a 2025 novelty. Sony brought Remote Play to desktop back in the PS4 system-software 3.50 era around 2016. What changed since is polish, resolution ceilings, and the sheer number of screens that can now act as a client.

The network floor: 5 Mbps and 15 Mbps

Sony's stated requirement is a high-speed connection: 5 Mbps minimum, 15 Mbps recommended, a figure repeated verbatim in the March 2026 Portal update notes. Two subtleties. First, this applies at both ends when you are away from home, because the console must upload the stream while the client downloads it. Second, the console's upload is usually the bottleneck on residential connections, where upstream bandwidth is a fraction of downstream. Test the upload where the console lives, not just the download where you are sitting.

# Remote Play floor: 5 Mbps min, 15 Mbps recommended (Sony).
# The CONSOLE uploads video; the CLIENT downloads it.
# Test upload at the console end and download at the client end.
$ speedtest-cli --simple
Ping:      11.284 ms
Download:  92.55 Mbit/s
Upload:    21.07 Mbit/s

That upload figure of 21 Mbit/s clears the recommended 15 Mbps with room to spare, which is what you want if you intend to run the 1080p tier. If your upstream reads 6 Mbit/s, you are in minimum-viable territory and should plan on 720p and a lower bitrate.

The 12-Step Setup

Console-side (Steps 1 to 5)

Step 1 — Update the console's system software. Rationale: Remote Play features ship inside system software, and the client negotiates a protocol version at connect time. A console running a stale build and a client on 9.0.0.02120 can fail the handshake in ways that masquerade as network faults. Update first, always. On the PS5: Settings, System, System Software, System Software Update and Settings.

Step 2 — Enable Remote Play on the console. Go to Settings, System, Remote Play, and switch on Enable Remote Play. Rationale: nothing pairs or connects while this is off. It is the master switch, and it is the first thing to check when a device that worked yesterday suddenly cannot find the console.

Step 3 — Configure Rest Mode network features. Settings, System, Power Saving, Features Available in Rest Mode, then enable both Stay Connected to the Internet and Enable Turning On PS5 from Network. Rationale: without these, a console in Rest Mode is deaf to wake requests, and you will be forced to leave it fully powered on to reach it, which is wasteful and, in summer, audibly warm.

Step 4 — Confirm account and primary-console status. Sign the console into your PSN account and set Console Sharing and Offline Play as described in the prerequisites. Rationale: the client authenticates as your PSN account and expects that account to be registered on the target console. Mismatches here throw CE-series errors that people waste hours blaming on their router.

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

Step 5 — Give the console a reserved IP and, ideally, an Ethernet cable. In your router, create a DHCP reservation pinning the console to a fixed LAN address such as 192.168.1.42. Rationale: port forwarding and Chiaki-ng registration both depend on the console keeping a stable address; a DHCP lease that rotates will silently break your forwards. Wiring the console kills Wi-Fi jitter at the source, and the source is where jitter hurts most.

Client-side pairing (Steps 6 to 9)

Step 6 — Install the correct client. Get the desktop app from Sony's official download page and the mobile apps from the platform stores. Rationale: sideloaded or repackaged builds are a security liability and a version-mismatch risk. Match the 2026 versions listed above so you are not debugging a nine-month-old client against current system software.

Step 7 — Sign into the client with your PSN account. Use the same account the console is signed into. Rationale: Remote Play is account-scoped; the client discovers consoles that your account is registered on. Sign in with the wrong account and the client will honestly report that it cannot find any console, because from its point of view there is none.

Step 8 — Do the first pairing on the same local network. With the client and console on the same LAN, let the app auto-discover the console, or follow Sony's PC and Mac pairing flow that walks you through the console's system menus. Rationale: first-time registration over the open internet is fragile; local discovery is fast and reliable, and once a device is registered it can reconnect from anywhere. Register at home, roam later.

Step 9 — Set your video quality before you need it. In the client settings, choose resolution and frame rate. Rationale: defaults are deliberately conservative to survive bad connections. If you have the bandwidth from Step 5, set the 1080p tier now so your first real session is not a muddy 540p disappointment that convinces you the feature is broken.

PS Remote Play (Windows 9.0.0.02120)
  Settings (gear icon)
    Video Quality for Remote Play
      Resolution:  1080p (High Quality)
      Frame Rate:  Standard | High
    -> choose 'High' only on a wired 15+ Mbps link

First session and sanity check (Steps 10 to 12)

Step 10 — Test on the LAN first. Before you go anywhere, connect while sitting next to the console on the same network. Rationale: this isolates variables. If Remote Play is flawless on the LAN and terrible over the internet, the problem is unambiguously the wide-area path, not the console, the app, or your controller. Diagnose in the easy environment first.

Step 11 — Verify remote reachability and forward ports if needed. When LAN works but WAN cannot find the console, forward the Remote Play port set to the console's reserved IP, covered in full in the next section. Rationale: many routers handle NAT traversal automatically, but plenty do not, and carrier-grade NAT breaks it outright. Explicit forwards turn a temperamental connection into a deterministic one.

Step 12 — Connect over WAN, confirm, and tune. Leave the house, or drop the client onto mobile data, and connect. Watch the first minute for artifacts or stutter, then lower the bitrate a notch if the picture keeps dissolving. Rationale: the internet is not your LAN; the honest test is a real remote session, and small bitrate reductions buy large stability gains when your upstream is marginal.

Network, NAT, and Exact Ports

The ports Remote Play uses

Remote Play and the Chiaki family use a small, well-known port set. Control and session setup, the handshake sometimes called senkusha, runs over TCP 9295. The actual audio and video stream runs over UDP 9296 and 9297. Console discovery, the how-do-I-find-you broadcast, uses UDP 9302. When the official app or Chiaki claims it cannot locate your console over the internet, it is almost always the UDP streaming pair or the discovery port not surviving the trip through NAT.

# Forward these to the console's reserved LAN IP (example 192.168.1.42)
# TCP 9295        control / session setup (senkusha)
# UDP 9296-9297   the audio/video stream itself
# UDP 9302        console discovery

# If a Linux box is your gateway, ufw makes the intent explicit:
$ sudo ufw route allow proto tcp from any to 192.168.1.42 port 9295
$ sudo ufw route allow proto udp from any to 192.168.1.42 port 9296:9297
$ sudo ufw route allow proto udp from any to 192.168.1.42 port 9302
$ sudo ufw reload

Port forwarding when auto-discovery fails

On a consumer router the workflow is the same idea in a friendlier interface: find the port-forwarding or virtual-server section, create rules that map the ports above to the console's reserved IP, and save. Rationale for doing this by hand rather than trusting UPnP: UPnP works until it silently stops, usually after a firmware update or a lease change, and then you are debugging a moving target. A static reservation plus explicit forwards is boring and permanent, which is exactly what infrastructure should be.

The nastier failure is carrier-grade NAT, where your ISP shares one public address across many customers and you have no public-facing address to forward to at all. No amount of router configuration fixes CGNAT from the inside. Your options are to ask the ISP for a real or static IP, sometimes a paid add-on, or to sidestep the whole problem with a VPN back into your own LAN, covered in the advanced section.

Reading your connection quality

Before you forward anything, confirm the console is actually reachable and responsive on the LAN. A four-packet ping tells you latency and, crucially, whether you are dropping packets, which is what turns a stream to mush.

$ ping -c 4 192.168.1.42
PING 192.168.1.42 (192.168.1.42) 56(84) bytes of data.
64 bytes from 192.168.1.42: icmp_seq=1 ttl=64 time=0.712 ms
64 bytes from 192.168.1.42: icmp_seq=2 ttl=64 time=0.688 ms
64 bytes from 192.168.1.42: icmp_seq=3 ttl=64 time=0.741 ms
64 bytes from 192.168.1.42: icmp_seq=4 ttl=64 time=0.699 ms

--- 192.168.1.42 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3061ms
rtt min/avg/max/mdev = 0.688/0.710/0.741/0.019 ms

Zero percent packet loss and a tight sub-millisecond spread is a healthy wired LAN. If that same test over Wi-Fi shows loss or a wildly varying time column, you have found your artifacting culprit before you have even opened the app.

Getting Real 1080p

The 1080p High Quality toggle

The 1080p path is genuinely new-ish. It arrived with the software update dated 17 March 2026, first appearing on the PS Portal, and it is the reason Remote Play in 2026 finally looks presentable on a large screen rather than merely playable on a phone. In the official app you select it under video quality as the 1080p High Quality resolution; on the Portal and in-session on other clients, it lives in the Quick Menu under the maximum-resolution option. It is a PS5-tier feature; do not expect a PS4 host to serve it.

The catch is that a toggle is a request, not a guarantee. Selecting 1080p tells the console to target that resolution; whether you receive it depends entirely on whether your connection can carry the bitrate 1080p demands. Set it on a wired 15-plus Mbps link and it is glorious. Set it on congested hotel Wi-Fi and the encoder will quietly downscale anyway, and you will have gained nothing but a longer settings menu.

Bitrate, frame rate, and the trade-offs

Resolution is only half the picture; bitrate is the other half and the one that actually decides how the image looks in motion. A 1080p stream starved of bitrate looks worse than a 720p stream given room to breathe, because the encoder spends its meager budget spreading detail thin instead of rendering less detail cleanly. The official app hides bitrate behind its Standard and High frame-rate presets, which is fine for most people. Chiaki-ng, discussed next, exposes bitrate directly, and a figure around 30000 Kbps is a sane 1080p60 target on a strong connection.

Frame rate is the other lever. High frame-rate mode doubles the temporal smoothness at the cost of needing more bandwidth and a beefier decoder. On a marginal link, dropping from High to Standard frame rate frees up headroom that the encoder can reinvest in a cleaner image. When in doubt, prioritize a stable 30 over a stuttering 60.

The PS Portal and its 1080p update

The PS Portal deserves a mention because it is the purest expression of Remote Play as a product: an 8-inch, 1080p, 60Hz handheld whose only function is to be a Remote Play client. Its 17 March 2026 software update is what introduced the 1080p High Quality mode alongside interface refinements, and it carried the same 5 Mbps minimum, 15 Mbps recommended guidance as everything else. If you have found yourself pricing one against, say, buying a whole second system to keep up with a heavyweight like the games arriving around GTA 6's November 2026 launch, the Portal is Sony's argument that you already own the console that matters and just need a screen for it.

The Chiaki-ng Alternative

Why an unofficial client exists at all

Sony's app is competent and locked down. It decides your bitrate, hides the decoder, and offers no serious tuning. Chiaki-ng is the answer for people who want the knobs. It is a maintained fork of Chiaki, the open-source, clean-room Remote Play client that reverse-engineered the protocol years ago; the current lineage, chiaki-ng, reached version 1.10.0 on 3 April 2026 and lives at its public GitHub repository. It runs where the official app is awkward or absent, notably Linux, Steam Deck, and single-board handhelds, and it exposes bitrate, decoder selection, and hardware-decode options directly.

To be clear about the lore and the law: Chiaki-ng is not endorsed or supported by Sony. It is a third-party interoperability project, the kind of clean-room reimplementation that has a long and mostly defensible legal history when it talks to hardware you own using your own credentials. It is legal to use with your own console and your own account. It is not a piracy tool, it grants no access you did not already have, and it will not help you if it breaks; you are the support department. Use it because you want control, not because you expect a safety net.

Registration: Account ID plus an 8-digit PIN

Chiaki-ng authenticates using your PSN Account ID, a Base64-encoded value ending in an equals sign, together with a one-time 8-digit registration PIN that the console generates. On the console you find the PIN under Settings, System, Remote Play, Link Device. As with the official app, do the registration once while on the same LAN as the console; after that the profile persists and reconnects from anywhere.

$ chiaki discover -h 203.0.113.7
discovered host:
  host addr:  203.0.113.7
  host name:  PS5-7F3A9C
  host type:  PS5
  state:      standby
  running:    (nothing)

That discovery output is what success looks like: the client can see the console, knows it is a PS5, and reports it sitting in standby, ready to be woken. A state of standby is good news; it means Rest Mode wake is configured correctly and the console is reachable. If discovery returns nothing, you are back in the ports-and-NAT section.

# Register once from the SAME LAN as the console.
# Console path: Settings > System > Remote Play > Link Device (shows an 8-digit PIN)
$ chiaki register --host 192.168.1.42 --pin 20260517 --psn-account-id BASE64ACCOUNTID==
[I] registration successful
[I] wrote profile to ~/.config/Chiaki/Chiaki.conf

A Chiaki-ng config that actually works

The reason to bother with any of this is the settings the official app will not give you: a hard 1080p60 target, an explicit 30000 Kbps bitrate, and hardware decoding so your CPU is not the bottleneck. Hardware decode maps to VideoToolbox on a Mac, VAAPI on Linux, or D3D11 on Windows, and turning it on is frequently the single change that converts a stuttering software-decoded mess into a smooth session. Set the audio buffer generously if you hear crackling; a little extra latency there is worth the stability.

Common Pitfalls (and Fixes)

Rest Mode, first pairing, and Wi-Fi

The three faults below account for the overwhelming majority of Remote Play failures, and all three are self-inflicted and trivially fixable once you know to look.

• The console is fully off, not in Rest Mode. A powered-down console cannot be woken over the network. Fix: leave it in Rest Mode with both network features from Step 3 enabled, or leave it fully on if you prefer the heat and the electricity bill.
• First pairing attempted over the internet. Remote registration is fragile and fails in confusing ways. Fix: register on the same LAN once, then roam. A registered device reconnects from anywhere; an unregistered one over WAN is a coin flip.
• The console is on Wi-Fi. Wireless jitter at the encoder end poisons the whole stream. Fix: wire the console with Ethernet. This is the highest-impact single change you can make and it is not close.

Bandwidth math and IP churn

• Bitrate set above your upstream. Requesting 1080p60 on a 6 Mbps upload guarantees drops and confetti. Fix: match your target to the console's actual measured upload, and remember the 5 Mbps floor exists for a reason.
• No DHCP reservation. When the console's IP rotates, your carefully crafted port forwards point at nothing. Fix: reserve the console's address in the router before forwarding anything.
• Carrier-grade NAT. No public address means no inbound forwarding is possible. Fix: request a real IP from your ISP, or VPN into your own LAN as described below.

Expectations that will hurt you

• Assuming bandwidth equals latency. A gigabit line does not make Remote Play feel instant; the felt floor is roughly 25 to 40 ms wired and worse over WAN. Fix: adjust your genre expectations, not your router.
• Expecting full DualSense haptics everywhere. Advanced controller feedback passes through cleanly on some clients, notably the Portal and console-to-console, and inconsistently on others. Fix: for haptics-critical play, use a first-party client; for everything else, do not sweat it. And note you cannot run a SharePlay session and Remote Play simultaneously; the console serves one such session at a time.

Troubleshooting Table

The table

Symptom on the left, the cause that is almost always true in the middle, the fix that almost always works on the right. Work top to bottom; the common faults are listed first.

Reading error codes

Sony's CE-series and NW-series codes are terse, but they cluster into two buckets. CE-prefixed codes on connect usually mean an account or registration problem: the client and console disagree about who you are. NW-prefixed codes mean the network path failed: discovery, ports, or reachability. Treat the prefix as a signpost. A CE code sends you back to Step 4 and account status; an NW code sends you to the ports section.

When to just restart everything

Before you spend an hour on a config safari, try the boring fix: reboot the client, reboot the router, and fully restart the console. If the console has been up for weeks and its Remote Play stack is wedged, a clean restart, or clearing its cache, resolves a surprising share of intermittent faults. We walk through the console-side cleanup in detail in our guide to clearing the PS5 cache the right way; it is the retro-repair equivalent of blowing on a cartridge, except it actually works.

Advanced Tips

Go wired, at both ends when you can

Everything in this guide comes back to one instruction: use Ethernet. Wire the console without exception. Wire the client whenever it is physically possible, which on a laptop means a USB dongle and on a handheld means docking it. Wi-Fi is not merely slower; it is inconsistent, and Remote Play punishes inconsistency far more than it punishes a slightly lower average speed. A steady 25 Mbps wired link beats a bursty 100 Mbps wireless one every time. If you must go wireless, use the 5 GHz band, stand close to the access point, and lower your bitrate to leave headroom for the inevitable dips.

VPN back into your own LAN

The most robust way to play away from home, and the only real fix for carrier-grade NAT, is to run a VPN server on your home network and have the client dial into it. Once connected, the client behaves as though it is on your home LAN, and Remote Play's local discovery finds the console with no port forwarding at all. WireGuard is the modern, low-overhead choice; many routers run it natively now. The trade-off is a little extra latency from the VPN hop, which is a fair price for a connection that simply works instead of one that depends on your ISP's NAT mood. This also neatly dodges every double-NAT headache in one move.

Streaming, capturing, and encoder tuning

Because the client is just an app showing a video feed, you can capture or record it with ordinary screen-capture software, which is handy if you want to stream a Remote Play session rather than tether a capture card to the console. If you go that route, our walkthrough on grabbing and handling VODs covers the downstream side of that workflow. On the encoder end, the single most effective tuning move is enabling hardware decoding on the client so the GPU, not the CPU, does the heavy lifting; on Chiaki-ng that is a one-line change, and it is the difference between a smooth 1080p60 and a slideshow on modest hardware. If you find yourself wishing for more control than any of this offers, that instinct is the same one that leads people to tuning RetroArch cores by hand, and Chiaki-ng scratches the same itch for streaming.

Complete Working Configuration

Console settings checklist

This is the known-good state. If your console matches every line below, the console side is not your problem, and you can focus entirely on the network. Set it once and forget it.

PS5 host (system software up to date)
  Remote Play ............................. Enabled
  Rest Mode: Stay Connected to Internet ... On
  Rest Mode: Turn On PS5 from Network ..... On
  Console Sharing and Offline Play ........ Enabled (your account)
  Network connection ...................... Wired (Ethernet)
  LAN IP .................................. 192.168.1.42 (DHCP reserved)

The router and firewall config

Forward exactly these three rules to the console's reserved IP. Nothing more is required, and opening additional ports only widens your attack surface for no benefit.

# Router / firewall -> forward to 192.168.1.42
TCP  9295         # control / session setup (senkusha)
UDP  9296-9297    # audio + video stream
UDP  9302         # console discovery

# CGNAT users: skip forwarding entirely and use a WireGuard
# tunnel back into the LAN; local discovery then just works.

The Chiaki-ng profile

And finally, a complete Chiaki-ng profile tuned for a wired 1080p60 session on a strong connection. Drop the bitrate to 15000 on a flaky link and leave hardware decoding on regardless; it costs nothing and saves everything. This, plus the console checklist and the three forwards above, is the entire working configuration.

[settings]
resolution=1080p
fps=60
bitrate=30000            ; kbps; drop to 15000 on a flaky WAN link
audio_buffer_size=9600   ; raise if you hear crackling
decoder=hardware         ; VAAPI (Linux) / VideoToolbox (Mac) / D3D11 (Win)
hw_decoder=auto
audio_out_device=default

[registered_host]
name=PS5-7F3A9C
type=PS5
addr=203.0.113.7         ; your WAN IP or DDNS name; LAN IP when at home
rp_key_type=1

[network]
; forwarded on the router to 192.168.1.42
; TCP 9295, UDP 9296-9297, UDP 9302

That is the whole feature, honestly configured: a console that wakes on demand, three ports that carry the stream, a client tuned to your actual bandwidth, and expectations calibrated to a 25-to-40-millisecond floor rather than a marketing fantasy. Set it up once, wire what you can, and Remote Play becomes the quiet, dependable thing it has always been under the branding. For the authoritative details, keep Sony's own pages and the Chiaki-ng repository bookmarked; both are linked throughout, and both will outlast this article's version numbers.