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

There are two entirely different machines now answering to the name PS Remote Play, and Sony would rather you not think too hard about which one you are holding. One is the honest one: a low-latency stream piped out of your own PlayStation 5 sitting in rest mode down the hall, or across the country. The other is the fashionable one: a cloud stream fired out of a Sony data center with your console cold and dark, billed through PlayStation Plus Premium. They share an icon, a setup page, and almost nothing that matters to your thumbs.

The split became official on November 5, 2025, when Sony flipped the PlayStation Portal's cloud beta into a full launch and let it stream thousands of digitally owned PS5 games and the entire PS Plus catalog with the console powered off. Four months later, the March 17, 2026 Portal update added a 1080p High Quality mode and a batch of UX refinements. That is the version everyone is chasing, and it is what this tutorial gets you to — on the Portal, on a phone, on a laptop, or on the open-source client Sony pretends does not exist.

This is the long version: twelve numbered steps with the reasoning behind each, a full pass on the Chiaki-ng route, network engineering that actually moves the latency needle, and a troubleshooting table you can print. Budget thirty minutes. Read the two-modes section first, because half of every Remote Play support thread on the internet is a person using the wrong mode and blaming the wrong thing.

Remote Play vs Cloud: Two Machines, One App

Before you touch a setting, internalize which stream you want. The mode you pick changes the hardware you need, whether you pay a subscription, and how the game feels under your fingers. Getting this wrong is the single most common failure, and no amount of router tuning fixes a category error.

The console-tethered stream (Remote Play proper)

Traditional Remote Play streams from your PS5 or PS4. The console does the rendering, encodes the frame, and ships it to your client over the network while sitting in rest mode. Sony's own Remote Play site and the June 2026 setup guide are blunt on the one point people refuse to believe: this mode does not require PlayStation Plus. You own the console, you own the games, you stream them to yourself. That is the whole deal.

Because the pixels originate a few meters away rather than in Oregon, this is the low-latency path. It is also the only path that streams disc-based games, physical or digital, because it streams whatever your console happens to be running. If you have a PS5 and a home network, Remote Play is the mode you want ninety-nine times out of a hundred, and everything below is tuned to make it good.

The cloud-native stream (what launched Nov 5, 2025)

Cloud Streaming is the new trick. It was added as a beta in November 2024, gated behind a PlayStation Plus Premium subscription, and promoted to a full feature on November 5, 2025. Here the PS5 in your living room is irrelevant — it can be off, unplugged, or nonexistent. Sony's servers render the game and stream it to your Portal or phone. An April 9, 2025 update even bolted a Capture Gameplay feature onto the cloud beta, letting the Portal grab screenshots and clips that land in your PS Plus cloud account.

The catch is written in the fine print, not the trailer: physical copies cannot be cloud-streamed. Only digitally owned PS5 titles and PS Plus catalog games are eligible. Disc in the tray? The cloud will not touch it. Cloud Streaming is a convenience for the couch-free and the console-less, not a replacement for owning hardware — and it is the mode that carries a monthly bill.

The latency truth nobody prints on the box

You will see a figure floating around that local Remote Play runs at 1–5 ms. Do not internalize that as input lag. That number is the network round-trip time on a quiet LAN — the time a ping packet takes to leave and return — and it is real. What your thumbs feel is glass-to-glass latency: button press, controller poll, encode, transmit, decode, display. On a solid 5 GHz link that full pipeline is realistically 25–40 ms, not single digits. It is excellent for a streamed image. It is not zero.

Cloud Streaming stacks another ~30–40 ms of network on top of that pipeline, which is exactly why home Remote Play feels tighter than cloud even when both report a healthy connection. If you care about frame-perfect inputs, host from your own console and wire it to the router. If you care about not owning a console, take the cloud and accept the tax. Neither is 2 ms, and anyone who tells you otherwise is quoting a ping and calling it feel.

Prerequisites: Console, Client, Network

A tutorial that skips prerequisites is a support ticket in waiting. Here is the exact inventory — hardware, software versions, and the network floor — before you start clicking.

Console and account

You need a PS5 or PS4 on current firmware and signed into your PSN account. Traditional Remote Play works from either console; Cloud Streaming is a PS5-catalog service tied to PS Plus Premium. Update the console first — Remote Play negotiates a handshake between client and host, and a stale system version is a reliable way to produce cryptic registration errors.

Sony recommends a wired connection for the console, and this is not boilerplate. Ethernet on the host removes the single largest source of stutter: a congested 2.4 GHz radio fighting your microwave. The client can be wireless. The host should not be. If the PS5 lives too far from the router for a cable, that is what powerline adapters and MoCA exist to solve.

Client hardware and app versions

The official PS Remote Play app runs on Windows PC, macOS, iOS, and Android, and — contrary to the excitable framing you will see — this is not new; desktop and mobile clients have existed since the PS4 era. Keep the app on the latest version; the release train has been bumpy (the 9.0 build shipped in March 2025 to a chorus of complaints, and the community has been speculating about a 9.5 follow-up, though nothing is confirmed). Update anyway — old clients drop new codecs and break against updated host firmware.

The hero device is the PlayStation Portal: an 8-inch 1080p 60 Hz LCD with split DualSense halves, launched in November 2023 at a $199.99 MSRP (still around £200 at UK retail). It is Wi-Fi only and, until the cloud updates, was a dumb terminal for your PS5. To unlock the 1080p High Quality mode, the Portal must be on the March 17, 2026 software update or later. If you want a client with real knobs — HEVC, hardware decode, an actual bitrate field — that is the Chiaki-ng section below.

The network floor (bandwidth, Wi-Fi, wired)

Sony's stated floor for 1080p High Quality is 5 Mbps, with 15 Mbps recommended for a good experience; the June 2026 guide confirms the service works on Australian NBN from 15 Mbps. Those are download-side numbers for cloud and downstream-to-client for Remote Play. Bandwidth is the easy part. The hard part is consistency — jitter and packet loss wreck a stream that a bandwidth test says is fine.

Practical floor: a 5 GHz or 6 GHz Wi-Fi link to the client, a wired host, and a router that does not fall over under load. If your only option is 2.4 GHz, expect artifacting and rubber-banding no matter what the speed test claims. Bandwidth buys resolution; latency and stability buy playability, and they come from the radio and the queue, not the megabits.

The 12-Step Setup

This is the full walkthrough for the official client — Portal, phone, or desktop app. It is written for the PS5; the PS4 paths are near-identical with older menu labels. Do them in order. Each step includes the reason it exists, because a step without a rationale is a step you will skip and regret.

Steps 1–4 — Prepare the console

1. Update the console firmware. Settings > System > System Software > System Software Update and Settings. Rationale: Remote Play negotiates codecs and keys between client and host; mismatched versions throw registration and connection errors that look like network problems but are not.
2. Enable Remote Play. Settings > System > Remote Play > Enable Remote Play. Rationale: it is a discrete toggle, and on a fresh or reset console it is off. No toggle, no host.
3. Turn on rest-mode networking. Settings > System > Power Saving > Features Available in Rest Mode — set Stay Connected to the Internet and Enable Turning On PS5 from Network to ON. Rationale: without these, a console in rest mode is deaf; the client cannot wake it, and every away-from-home session fails at connect.
4. Confirm the account and set as primary. Sign the console into the PSN account you will stream with; on PS4, mark it your primary/activated console. Rationale: Remote Play authorizes against your account, and cross-internet sessions expect the host to be your activated console.

The console-side settings, in one glance:

# PlayStation 5 -> Settings -> System
Remote Play:
  Enable Remote Play:                  ON
  Link Device:                         (shows 8-digit code, valid a few minutes)

Power Saving -> Features Available in Rest Mode:
  Supply Power to USB Ports:           Always
  Stay Connected to the Internet:      ON
  Enable Turning On PS5 from Network:   ON

Steps 5–8 — Install, sign in, register, first LAN session

5. Install the current client. Portal: take the March 17, 2026 update. PC/Mac/iOS/Android: install the latest PS Remote Play app from remoteplay.dl.playstation.net or the platform store. Rationale: old clients lack the newest resolution and codec options and can fail against updated hosts.
6. Sign in with the same PSN account. Rationale: the client and host authorize against one account; a second account will not see your console.
7. Register the device. On the console, open Settings > System > Remote Play > Link Device to get an 8-digit code, and enter it in the client. Rationale: this performs a one-time cryptographic pairing so the client can wake and connect to the host later without re-authenticating. The code expires in minutes — generate it when the client is ready to receive it.
8. Connect once on the same LAN. Keep client and console on the same network for the first session. Rationale: it isolates variables. If the LAN session works and the remote one does not, the problem is NAT or your ISP, not your setup. Confirm the host is reachable and the round-trip is sane first:

# Find the PS5 on your LAN (it answers on UDP 9302)
$ arp -a | grep -iE "playstation|sony"
? (192.168.1.42) at 00:d9:d1:xx:xx:xx on en0 ifscope [ethernet]

# Confirm local round-trip time (this is RTT, NOT input latency)
$ ping -c 5 192.168.1.42
64 bytes from 192.168.1.42: icmp_seq=0 ttl=64 time=1.83 ms
64 bytes from 192.168.1.42: icmp_seq=1 ttl=64 time=2.02 ms
64 bytes from 192.168.1.42: icmp_seq=2 ttl=64 time=1.71 ms
64 bytes from 192.168.1.42: icmp_seq=3 ttl=64 time=2.44 ms
64 bytes from 192.168.1.42: icmp_seq=4 ttl=64 time=2.09 ms
--- 192.168.1.42 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss
round-trip min/avg/max/stddev = 1.71/2.02/2.44/0.26 ms

Expected result: a clean stream at 1080p60 with a couple-millisecond RTT and zero packet loss. That RTT is the network floor — remember, real input latency lands at 25–40 ms once the encode/decode/display pipeline is counted.

Steps 9–12 — Tune, go remote, verify

9. Set resolution and enable 1080p High Quality. On the Portal, open the Quick Menu > Max Resolution and choose 1080p High Quality; on the app, set resolution and frame rate in the stream settings. Rationale: HQ raises the bitrate over 1080p Standard for a visibly cleaner image on a good link — and defaults tend to be conservative.
10. Test remote, off-LAN. Take the client onto cellular or a different Wi-Fi network and connect. Rationale: this is the real test. Home LAN success proves nothing about NAT traversal; only an off-network session confirms the wake-and-connect path works over the internet.
11. Configure the router if remote is flaky. Enable Smart Queue Management (SQM) to kill bufferbloat, and — only if strict/CG-NAT is blocking you — forward the transport ports. Rationale: most remote failures are NAT or bufferbloat, not bandwidth. See the network section for the exact config.
12. Verify and save your profile. Run a five-minute session in a game you know, watch for artifacting or input drift, and lock in the settings. Rationale: repeatability. A profile you validated once is a profile you trust at 11 p.m. on hotel Wi-Fi.

Twelve steps, roughly thirty minutes if the network cooperates. If you want the condensed maintenance angle for when the console itself gets cranky, our PS5 cache-clear walkthrough pairs neatly with this — a stuttering host is sometimes a full cache, not a bad link.

Going Open Source: Chiaki-ng

Sony's app is fine. Chiaki-ng is better for anyone who wants to drive. It is the maintained successor to the original Chiaki, an open-source Remote Play client that talks the same protocol as the official app but exposes the settings Sony buries — real bitrate, codec choice, hardware decoder selection, and controller mapping. The project lives at github.com/streetpea/chiaki-ng with docs at streetpea.github.io/chiaki-ng.

Why an open-source client at all

Three reasons. First, platforms: Chiaki-ng runs on Linux, Windows, macOS, and — critically — the Steam Deck and other handheld PCs, turning any of them into a Remote Play terminal that a Portal cannot match for flexibility. Second, control: it defaults to 1080p60, lets you push the bitrate to around 30,000 Kbps, pick HEVC over H.264, and choose the hardware decoder explicitly. Third, it is transparent — you can read exactly what it does with your credentials.

The honest limitation: Chiaki-ng does Remote Play only. It connects to your console. It cannot touch Sony's Cloud Streaming, because that is a proprietary service with no public protocol. If your whole reason for streaming is a console-less cloud session, Chiaki is not your tool. If you own the console and want the best home-streaming client on a desktop or Deck, it is the one to beat — and it makes a Deck a more capable streaming client than the Portal, which is worth weighing against the handhelds in our Switch 2 vs Steam Deck breakdown.

Install by platform

On Linux, grab the AppImage from the Releases page or install the Flatpak; on Windows and macOS, download the installer or DMG from the same page. Steam Deck users install the Flatpak in Desktop Mode and add it to Steam as a non-Steam game.

# Linux: run the AppImage from the Releases page
$ chmod +x chiaki-ng-*-Linux.AppImage
$ ./chiaki-ng-*-Linux.AppImage

# Or install the Flatpak (confirm the current app id on the releases page)
$ flatpak install flathub io.github.streetpea.Chiaki4deck
$ flatpak run io.github.streetpea.Chiaki4deck

The Flatpak application ID carried over from the project's earlier name, so verify the current ID on the releases page rather than trusting a copied command. The AppImage path sidesteps that entirely — one file, chmod, run.

Register with your Account ID and the 8-digit PIN

Registration in Chiaki-ng needs two things: your PSN Account ID (a Base64 value) and an 8-digit PIN from the console's Link Device screen. Modern Chiaki-ng ships a one-click Login with PSN button that fetches the Account ID for you through a browser OAuth flow; the manual method — extracting the ID from a PSN login redirect and Base64-encoding it — still exists as a fallback if the button misbehaves.

The flow: open Chiaki-ng, click Login with PSN and authenticate to grab your Account ID; on the console, open Settings > System > Remote Play > Link Device for the 8-digit code; in Chiaki-ng's Register Console dialog, enter the console IP, your Account ID, and the PIN. The PIN is time-limited — have Chiaki open and ready before you generate it. Once registered, the console appears in the client's console list and Chiaki can wake it from rest, exactly like the official app.

# chiaki-ng -> Console (gear) -> Stream Settings
Resolution:            1080p
FPS:                   60
Bitrate:               30000   # Kbps; leave blank for auto
Codec:                 HEVC (H.265)   # fall back to H.264 on old GPUs
Hardware Decoder:      auto            # vaapi / videotoolbox / d3d11va
Audio Buffer Size:     9600            # raise if you hear crackle
Audio Output Buffer:   on

Tuning Quality: 1080p HQ, Bitrate, Codec

Defaults are conservative because Sony would rather ship you a soft, stable image than a sharp one that hitches on bad Wi-Fi. If your link is good, you leave quality on the table by accepting them. Here is where the real image quality lives.

1080p High Quality vs Standard

The March 17, 2026 Portal update introduced 1080p High Quality alongside the existing 1080p Standard, both selectable from Quick Menu > Max Resolution. The difference is bitrate: HQ allocates more bits to the same 1080p frame, which mostly shows up as cleaner gradients, less blocking in dark scenes, and sharper text — the places where compression artifacts are ugliest. It applies to both Remote Play and Cloud Streaming.

The cost is bandwidth headroom and sensitivity to jitter. HQ wants the 15 Mbps Sony recommends, not the 5 Mbps floor, and it punishes an unstable link harder than Standard does. Rule of thumb: on a wired host and a 5 GHz client, run HQ. On hotel Wi-Fi or a congested apartment block, drop to Standard and accept the softness — a stable soft image beats a sharp one that stutters every ten seconds.

Bitrate and codec (H.264 vs HEVC)

The official app hides the bitrate behind the resolution preset. Chiaki-ng does not, which is the entire argument for using it. At 1080p60 you can push toward 30,000 Kbps, but higher is not automatically better — past the point your link and decoder can sustain cleanly, extra bitrate just buys you buffering and dropped frames. Set it to roughly what your link can hold with headroom, not its theoretical ceiling.

Codec matters more than raw bitrate. HEVC (H.265) delivers noticeably better quality per bit than H.264, so at a given bitrate an HEVC stream looks cleaner, or you can hold the same look at lower bandwidth. The trade is decode cost — HEVC needs a reasonably modern GPU with hardware decoding. If you see a black screen with working audio, your decoder cannot handle the codec; fall back to H.264 and update your GPU drivers. Always enable hardware decoding; software decode adds latency and heat for nothing.

Frame pacing and the 60Hz ceiling

Remote Play caps at 1080p60, and the Portal's panel is a 60 Hz LCD, so 120 fps ambitions stop at the hardware. That is fine — the bottleneck is never the refresh rate; it is frame pacing. A stream that delivers a steady 60 fps feels dramatically better than one averaging 60 but hitching, because the hitches are what your eye and thumbs register as lag.

Pacing comes from network stability, not settings. A wired host, a 5 GHz client locked to one band, and a router that manages its queue produce even frame delivery. A 2.4 GHz client roaming between access points produces the opposite no matter how you tune the codec. If the image looks like it is periodically freezing and catching up, stop adjusting bitrate and fix the radio — that is a network problem wearing a video-quality mask.

Network Engineering: Bands, Ports, QoS

This is where Remote Play is won or lost. Bandwidth is a solved problem for most people; stability is not. Three levers matter — the band your client uses, how your NAT handles the traversal, and whether your router drowns its own queue under load.

Band, channel, and the 5 GHz rule

Put the client on 5 GHz (or 6 GHz on Wi-Fi 6E hardware) and keep it there. The 2.4 GHz band is a shared junkyard — microwaves, Bluetooth, every neighbor's router — and its congestion produces exactly the jitter that ruins a stream. The one thing 2.4 GHz has going for it, range, is irrelevant when the fix is to sit closer to the router for a gaming session.

Disable band steering and fast roaming on the client's connection if your router lets you, or pin the client to a dedicated 5 GHz SSID. Band steering exists to move idle devices to the least congested band; mid-stream, that handoff is a visible hitch or a dropped session. A stream wants one radio, one band, one channel, held for the duration. Give it that and half your "random disconnect" problems evaporate.

Ports, NAT, and going remote

On a home LAN, none of this matters — discovery and connection just work. Off-network, you are at the mercy of two NATs and your ISP. Remote Play generally traverses NAT automatically via PSN's relay and hole-punching, so try it before touching your router. Only if remote sessions fail — and especially if your ISP uses carrier-grade NAT — do you reach for manual port forwarding.

# Router: prioritize the client + console, tame bufferbloat
Smart Queue Mgmt (SQM/fq_codel):     ENABLED
Upload limit  (~90% of true upload): 18000 kbit
Download limit (~90% of true down):  90000 kbit

# Remote Play transport (community-documented; usually NAT-traversed automatically)
TCP  9295             -> PS5 static IP
UDP  9296-9297        -> PS5 static IP
UDP  9302   (discovery)
# Only forward these if remote sessions fail behind strict/CG-NAT.

Give the console a static or DHCP-reserved IP before forwarding anything, or your rules will point at the wrong device after the next lease renewal. If you are behind CG-NAT and forwarding does nothing — because the ports terminate at the ISP, not your router — the clean fix is a VPN back to your home network, covered in the advanced section.

Bufferbloat and QoS

Bufferbloat is the silent killer. It is what happens when a device on your network saturates the uplink — a cloud backup, a game download — and your router's oversized buffers pile up packets, adding hundreds of milliseconds of latency to everything, including your stream. A speed test looks perfect; the stream falls apart the moment someone streams Netflix.

The fix is Smart Queue Management (SQM), typically fq_codel or cake, which keeps those buffers short and prioritizes latency-sensitive traffic. Set your SQM upload and download limits to roughly 90% of your measured real throughput — the deliberate haircut is what gives the algorithm room to manage the queue. On a router with SQM configured, a Remote Play session survives a background download that would have destroyed it on stock firmware. This single setting outperforms every codec tweak combined.

Common Pitfalls (and Fixes)

Most Remote Play failures fall into a handful of buckets, and none of them are exotic. Here are the ones that generate the support threads, grouped by where the mistake actually lives.

Configuration mistakes

• Wrong mode entirely. Trying to cloud-stream a disc game, or expecting Remote Play to work with PS Plus but no console. Fix: re-read the two-modes section. Disc games and console-less use are mutually exclusive — Remote Play needs your console, Cloud Streaming needs a subscription and a digital library.
• Rest-mode networking left off. The classic. LAN sessions work, remote wake fails, and the user blames their ISP. Fix: enable Stay Connected to the Internet and Enable Turning On PS5 from Network. A console that cannot stay awake on the network cannot be woken from it.
• Stale client or console firmware. Registration throws an error, or a new resolution option is missing. Fix: update both ends. Remote Play is a handshake, and one stale side breaks it.
• Expired Link Device PIN. The 8-digit code lives for minutes. Generate it, then take your time entering it, and it dies. Fix: have the client's registration dialog open and ready, generate the PIN, enter it immediately.

Network mistakes

• Client on 2.4 GHz or roaming. Artifacting, rubber-banding, mid-session drops. Fix: pin the client to a single 5 GHz SSID, disable band steering and fast roaming.
• Wireless host. The console on Wi-Fi introduces jitter at the source that no client-side setting can undo. Fix: wire the console. Sony recommends it for a reason.
• Bufferbloat under load. Perfect until someone downloads something, then unplayable. Fix: enable SQM/QoS on the router, capped at ~90% of real throughput.
• CG-NAT. Remote works nowhere off-network and port forwarding does nothing. Fix: a VPN back home (WireGuard) or a request to your ISP for a non-CG-NAT IP.

Expectation mistakes

• Chasing 2 ms. Believing the LAN-RTT figure is input latency and then "fixing" a 25–40 ms feel that was never broken. Fix: recalibrate. Local Remote Play is excellent; it is not a directly attached display.
• Running HQ on a weak link. Forcing 1080p High Quality on unstable Wi-Fi and blaming the mode for stutter. Fix: drop to 1080p Standard or 720p on bad networks. Quality settings are a ceiling, not a promise.

Troubleshooting Table

When a session misbehaves, work the symptom, not your hunch. The table maps what you see to the most likely cause and the fix that actually addresses it. Work top to bottom — the common causes are near the top.

How to read the table

Each row is symptom, likely cause, fix. Start with the cheapest fix that matches your symptom and only escalate if it fails. Ninety percent of issues are the first three rows: discovery, radio, and bitrate. Resist the urge to reinstall everything before you have ruled those out.

The table

When to escalate

If the symptom survives every matching fix, the problem may be the host itself, not the stream. A PS5 with a bloated cache or a corrupt database can produce stutter and connection weirdness that no network tuning touches — that is when you run a cache clear and rebuild on the console. Only after the host is verified clean and the network is verified stable is a client reinstall or factory-level step justified. Reinstalling the app to fix a bufferbloat problem is how people lose an afternoon.

Advanced Tips

Once the basics work, these are the moves that separate a functional setup from a genuinely good one. None of them are in the official menu, which is precisely why they are worth knowing.

Chiaki-ng on Steam Deck and desktops

The best Remote Play client is arguably a Steam Deck running Chiaki-ng. Install the Flatpak in Desktop Mode, add Chiaki as a non-Steam game, and switch back to Game Mode for a controller-native launcher. Use Steam Input to map the Deck's controls, cap the TDP to keep the fans quiet during a stream (decoding a 1080p HEVC feed is light work), and you have a handheld that streams your PS5 with full HEVC and a real bitrate field — capabilities the Portal's locked firmware will not give you. It is a compelling answer to the handheld-streaming question the ROG Xbox Ally raised from the other platform's side.

On desktop, the same client turns a laptop into a better Remote Play terminal than the phone app, with explicit hardware-decoder selection (vaapi on Linux, videotoolbox on macOS, d3d11va on Windows). Pick the decoder your GPU supports rather than leaving it on auto if auto guesses wrong — a mis-selected decoder is a common cause of the black-screen-with-audio failure.

VPN home for LAN-grade remote

The cleanest fix for hostile NAT and inconsistent remote performance is to make "remote" look like "home." Run a WireGuard server on your router or a home device, connect the client to it, and Remote Play behaves as if you are on the LAN — discovery works, NAT traversal is a non-issue, and CG-NAT stops mattering because the tunnel handles it. The trade is a little added latency from the tunnel and dependence on your home upload speed, but for anyone stuck behind carrier-grade NAT it is the difference between working and not.

A travel router loaded with a WireGuard client is the road-warrior version: connect it to hotel Wi-Fi, let your Portal or laptop join the travel router, and every session is tunneled home automatically. It also sidesteps captive portals that block Remote Play's ports, which is a recurring hotel-Wi-Fi headache.

Capture, codecs, and squeezing the link

On the Portal, the April 2025 Capture Gameplay feature works in cloud mode — screenshots land straight in your PS Plus cloud account, useful if you play console-less and want clips without a capture card. For image quality per megabit, HEVC plus hardware decode is the winning combination every time your hardware supports it; reserve H.264 for old GPUs. And if you are on a marginal link, drop resolution before you drop bitrate — a clean 720p60 stream reads as far sharper in motion than a 1080p feed starved of bits, because motion is where compression artifacts scream loudest. This whole ecosystem only gets more central to Sony's plans as hardware ages; where it is heading is a live question we track in our PS6 timeline analysis, and it is a big part of why streaming has quietly become load-bearing across the PlayStation line since the PS4 era.

The Complete Working Config

Everything above, consolidated into a reference you can copy. This is the known-good baseline for a wired PS5 host and a 5 GHz client, running 1080p60 with HEVC. Adjust down for weaker links; the structure holds.

Console + network summary

Console: PS5 on current firmware, wired to the router, static/reserved IP, Remote Play enabled, and both rest-mode network features on. Router: 5 GHz (or 6 GHz) SSID for the client with band steering off, SQM enabled and capped at ~90% of real throughput, and the transport ports forwarded only if remote sessions fail behind strict NAT. Client: latest official app or Chiaki-ng, on 5 GHz, close enough to the router to hold a stable signal.

# --- Console (PS5) ---
System Software:                      latest
Remote Play:                          Enabled
Rest Mode -> Stay Connected:          ON
Rest Mode -> Turn On from Network:     ON
Network:                              Wired, reserved IP 192.168.1.42

# --- Router ---
Client band:                          5 GHz SSID, band steering OFF
SQM (fq_codel/cake):                  ON, limits ~90% of measured throughput
Forwarding (only if remote fails):    TCP 9295, UDP 9296-9297 -> 192.168.1.42

# --- Bandwidth targets ---
1080p HQ:   >= 15 Mbps recommended (5 Mbps floor)
1080p Std:  ~10-15 Mbps
720p60:     ~5-8 Mbps on a weak or shared link

The Chiaki.conf reference

Chiaki-ng writes its own config; you rarely edit it by hand. This simplified, illustrative version shows the settings that matter and where they live on Linux (~/.config/Chiaki/Chiaki.conf). Change values through the GUI and let the app manage the file — the point here is to see what "good" looks like, not to hand-author it.

# ~/.config/Chiaki/Chiaki.conf  (illustrative / simplified)
[settings]
resolution_local_ps5=1080p
fps=60
bitrate=30000
codec=hevc
hardware_decoder=auto
audio_buffer_size=9600
start_mic_unmuted=false

[registered_host]
server_nickname=Living Room PS5
ps5_mac=00d9d1xxxxxx
ap_ssid=YourHome-5G
rp_key_type=0

Bandwidth and settings targets

Match the preset to the link, not to your ambitions. The table below is the quick decision matrix: pick the row your network actually sustains under load — including a background download — not the one your speed test flatters you with.

That is the whole machine. Remote Play from your own console remains the sharpest, lowest-latency way to play a PS5 you are not sitting in front of; Cloud Streaming is the console-less convenience with a subscription and a latency tax. Pick the right mode, wire the host, pin the client to 5 GHz, and enable SQM — do those four things and the rest is polish. Everything else in this guide is just how to get the last twenty percent.