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

PS Remote Play is the closest thing Sony has ever shipped to a formal admission that your television is optional. You point a PlayStation 5 at your network, you point a client at the PlayStation 5, and the console obediently encodes its own output into an H.264 or HEVC video stream that a phone, a laptop, a Mac, another console, or an overpriced 8-inch handheld can consume from the next room — or, if your upstream bandwidth and your patience allow, the next timezone. The idea is older than the PS5. It is older than the PS4. It dates back to the PSP era, when remote play meant streaming a PS3 to a handheld over a connection that could not remotely handle it.

In 2026 it finally works the way the marketing always promised. The reason is a single system software update that rolled out globally on March 18, 2026 (March 17 in PDT), which Sony — characteristically — declined to attach a headline version number to. That update added a 1080p High Quality mode to the PlayStation Portal and to Cloud Streaming, pushing the stream to a higher bitrate than the old 1080p Standard default. It also arrived, per Sony's own figures, at a moment when Cloud Streaming monthly users had grown 162% year over year as of January 2026, and when more than half of all Portal owners were paying for PlayStation Plus Premium. Remote Play stopped being a curiosity. It became the product.

This is a tutorial, not a press release, so here is the deal up front: twelve numbered steps, roughly thirty minutes, three clients. We will configure the PS5 host correctly — most guides get the power settings wrong and then blame the network. We will set up the official app on a phone or PC and the Portal. Then we will set up chiaki-ng, the open-source client that exposes the bitrate, codec, and decoder controls Sony refuses to show you. Along the way we will bury the single most repeated lie about this technology — that its latency is 2ms — because it is not, it never has been, and the number is wrong by more than an order of magnitude.

What Actually Changed in 2026

If you last set up Remote Play in 2021 and walked away disappointed, the news is that the disappointment has a patch now. But the patch is narrow, and it is worth understanding exactly what moved and what did not, because almost everything you will read about the 2026 state of Remote Play conflates three separate things: the March 2026 update, the unchanged core requirements, and a pile of latency folklore.

The March 2026 update, decoded

The March 18, 2026 system software update is the whole story, so let us be precise about it. The headline feature is 1080p High Quality mode, selectable during both Remote Play and Cloud Streaming. It does not raise the resolution — the Portal's panel was already 1080p — it raises the bitrate. The previous ceiling, retroactively renamed 1080p Standard, starved the encoder of bits, which is why fast pans in a shooter used to dissolve into a slurry of macroblocks. High Quality mode hands the encoder more headroom, and the difference shows up exactly where it was worst: motion, foliage, particle effects, and dark gradients. Sony's own documentation is blunt that it also uses more data, which is the trade you are signing up for.

Everything else in the update is user-experience polish, and it is worth knowing because it changes what appears on your screen. Trophy notifications now render the trophy name, its image, and the full platinum animation instead of a terse banner. Game-invite notifications surface on-screen during an active stream. The search screen finally throws up the on-screen keyboard the instant you enter it, and new PlayStation users can create an account by scanning a QR code. None of this is revolutionary. All of it is the sound of a product being finished three years after launch. You can read Sony's own write-up on the PlayStation Blog.

What did not change (and the myths that persist)

The core requirements are exactly what they were when the PS5 shipped in 2020. You still need a PS5 or PS4 as the host — Remote Play streams a real console, it does not conjure games out of the ether. You still need 5 Mbps minimum, 15 Mbps recommended, per Sony's unchanged specification. The official Remote Play app has run on Windows and macOS since the PS4 era around 2016; anyone selling you PC Remote Play as new for 2025 is selling you a decade-old feature with a fresh coat of paint.

And then there is the latency myth. Somewhere on the internet a number — 2ms — took hold, and it is nonsense. A single frame at 60fps is 16.7ms. The claim asks you to believe the console can capture a frame, H.264-encode it, packetize it, transmit it over Wi-Fi, receive it, decode it, and display it in less than an eighth of the time that one frame is even on screen. It cannot. It cannot come close. We will put a real, defensible number on it in the next section, and you should mentally discard any review, forum post, or product page that quotes single-digit milliseconds.

PS5 Pro, PSSR, and what the stream actually carries

If your host is a PS5 Pro, Remote Play streams the Pro-enhanced render — the higher-resolution modes, the better ray tracing, and games reconstructed by PSSR (PlayStation Spectral Super Resolution, Sony's machine-learning upscaler). Note the acronym: it is PSSR, not PSSR2. There is no PSSR2, no matter how many times a spec sheet claims otherwise. The Pro does its expensive reconstruction locally, on the console, then the finished result is fed into the same Remote Play encode pipeline as any other PS5. You are not streaming the ray-traced framebuffer pixel-for-pixel — you are streaming a compressed video of it. Which is the entire reason bitrate, the thing the 2026 update finally addresses, matters more than the resolution label printed on the menu. A 4K-native Pro render squeezed through a starved encoder looks worse than a native 1080p render given room to breathe.

How Remote Play Actually Works

You cannot troubleshoot a black box. So before we touch a single setting, here is the machine under the hood — the pipeline, the honest latency figure, and the codec decision that separates a crisp stream from a smear.

The encode-transmit-decode pipeline

Every Remote Play session is the same five-stage assembly line, running sixty times a second. The PS5 renders a frame into its framebuffer. A dedicated hardware encoder compresses that frame into H.264, or HEVC depending on the client. The compressed data is packetized and pushed onto the network. Your client receives the packets, reassembles them, and hands them to a decoder — hardware if you configured it correctly, software if you did not. The decoded frame is drawn to your display, and your controller inputs make the same trip in reverse. Every one of those stages costs time, and the sum of those times is the latency the 2ms crowd wants you to ignore.

Two stages dominate. Encoding is fast because it runs on silicon purpose-built for it, but network transit is where a good setup and a bad setup diverge by an order of magnitude. On a wired host and a 5GHz client sharing one access point, transit is a handful of milliseconds. Over the open internet, through a double-NAT and a congested uplink, it is whatever the worst hop decides it is. This is why the single highest-leverage move — the thing every serious guide repeats — is to hardwire the PS5 to the router. Ethernet on the host is not optional if you care about the result. Wi-Fi on the host is the most common reason a setup that should be smooth is not.

The real latency number

Here is the honest figure. On a well-configured local network — PS5 on Ethernet, client on 5GHz Wi-Fi, both on the same router — added input latency lands in the range of 25 to 40 milliseconds glass-to-glass, on top of whatever your display's own latency already is. That is genuinely good. It is good enough for character action games, RPGs, most single-player shooters, and anything turn-based. It is not good enough for frame-perfect fighting-game inputs or ranked twitch shooters, and no software update will change that, because the physics of encode-transmit-decode set a floor that a 2ms claim pretends does not exist. Over the internet, add the network round trip to wherever your console physically lives — a 30ms round trip is 30ms of latency you cannot encode your way out of, and it is the reason a low-latency mouse matters far less here than it does on a native rig.

chiaki-ng users sometimes measure lower motion-to-photon numbers than the official app on identical hardware, mostly because they can force a hardware decoder and a codec the app would not have picked. But lower-than-the-app is still tens of milliseconds, not single digits. Anyone quoting you 2ms is quoting you a fantasy, and you should calibrate your expectations to the 25-to-40 band and be pleasantly surprised on a clean LAN.

Codecs: H.264 versus HEVC

Remote Play can carry H.264 or HEVC (H.265). HEVC compresses roughly the same visual quality into fewer bits, which matters enormously on a constrained uplink — the same 10 Mbps buys a cleaner picture under HEVC than under H.264. The official app negotiates this for you and does not ask your opinion. chiaki-ng lets you choose, and for a PS5 host on a decent connection, HEVC is the correct answer. The catch is the decoder: HEVC decoding must be hardware-accelerated on your client, or the CPU will cook itself trying to keep pace and you will get exactly the choppiness you were trying to eliminate. That single toggle is covered in Step 11, and it is the most consequential setting in this entire tutorial.

Prerequisites: Hardware, Software, Network

Gather these before you start. Nothing here is expensive or exotic, but a missing Ethernet cable or a client on the wrong Wi-Fi band will waste your thirty minutes and leave you convinced the technology is broken. It is not. Your network is.

Hardware you need

• A host console: PS5, PS5 Pro, PS4, or PS4 Pro. A real console is mandatory — Remote Play streams it, it does not replace it. The PlayStation Portal streams from a PS5 only; it will not talk to a PS4.
• A client device: a phone (iOS or Android), a Windows PC, a Mac, a PlayStation Portal (8-inch, 1080p, 60Hz, launched 2023), a Steam Deck or any Linux box via chiaki-ng, or even a Nintendo Switch via chiaki-ng's homebrew port.
• A controller: a DualSense for a PS5 host, or a DualShock 4 for a PS4 host. The Portal has DualSense controls, including haptics and adaptive triggers, built into its two halves.
• An Ethernet cable for the host. Non-negotiable if you want the 25-to-40ms result rather than the 80ms-and-stuttering one.

Software and versions

• PS5/PS4 system software: latest. Remote Play settings live in current firmware and the wake-from-network behavior depends on it.
• PS Remote Play app: latest, on Android, iOS, Windows 10 or newer, or macOS 11 or newer. Free, from Sony.
• PlayStation Portal: updated to the March 2026 system software or later — that is the update that unlocks 1080p High Quality mode.
• chiaki-ng: the latest release, from the GitHub releases page or from Flathub for Linux and Steam Deck. Track new builds on the releases changelog.
• A PSN account signed in on the host console.

The network you need

• 5 Mbps minimum (Sony's floor), 15 Mbps recommended. For 1080p High Quality and chiaki-ng's 30,000 Kbps target, plan for roughly 30 Mbps of headroom on the stream path.
• Host wired to the router. Client on 5GHz Wi-Fi (Wi-Fi 5 or better) or wired.
• No double-NAT, no VPN on the stream path, and keep the client off congested 2.4GHz.

Here is the whole checklist in one block you can keep open while you work:

# PS REMOTE PLAY 2026 — PREREQUISITE CHECKLIST

HOST        : PS5 / PS5 Pro / PS4 / PS4 Pro   (a real console is mandatory)
HOST FW     : latest system software
HOST LINK   : Ethernet to router             (non-negotiable for low latency)

CLIENT      : one of
              - PS Remote Play app  (Android / iOS / Windows 10+ / macOS 11+)
              - PlayStation Portal  (8in, 1080p, 60Hz; PS5 host only; Mar-2026 FW)
              - chiaki-ng           (Linux / Steam Deck / Windows / macOS / Switch)

CONTROLLER  : DualSense (PS5) or DualShock 4 (PS4)
ACCOUNT     : PSN account signed in on the host

NETWORK     : 5 Mbps   minimum        (Sony floor)
              15 Mbps  recommended
              ~30 Mbps for 1080p High Quality / chiaki 30,000 Kbps
CLIENT BAND : 5 GHz Wi-Fi, or wired
AVOID       : double-NAT, VPN on the stream path, 2.4 GHz congestion

Part 1: Configure the PS5 Host (Steps 1-4)

The host is where success or failure is decided. Four steps. Get the power settings right and the rest of this tutorial is a formality; get them wrong and you will spend an hour wondering why the app cannot find a console that is sitting three feet away.

Step 1 - Enable Remote Play on the console

On the PS5, go to Settings > System > Remote Play and turn on Enable Remote Play. On a PS4 the path is Settings > Remote Play Connection Settings > Enable Remote Play. Why: this flips the console into a mode where it will advertise itself for discovery and accept an encoded-stream session. Without it, every client on earth will search forever and find nothing. It is the master switch, and it is off by default.

Step 2 - Set the rest-mode power features

This is the step everyone skips and then regrets. Go to Settings > System > Power Saving > Features Available in Rest Mode and enable both Stay Connected to the Internet and Enable Turning On PS5 from Network. Why: Remote Play's headline trick is waking a sleeping console from your phone. If the console fully powers down, or drops its network link in rest mode, it cannot be woken, and you will get the classic could-not-connect error while standing in a coffee shop. These two toggles keep the network stack alive in rest mode so a wake packet can land.

# PS5 HOST — REQUIRED SETTINGS TREE

Settings
└─ System
   ├─ Remote Play
   │  ├─ Enable Remote Play ................. ON
   │  └─ Link Device ...................... (generates an 8-digit PIN)
   │
   └─ Power Saving
      └─ Features Available in Rest Mode
         ├─ Stay Connected to the Internet ......... ON
         └─ Enable Turning On PS5 from Network ..... ON

Step 3 - Hardwire the host and verify the connection

Plug the PS5 into your router with an Ethernet cable, then run Settings > Network > Connection Status > Test Internet Connection. Why: we established in the pipeline section that network transit is the stage that separates 30ms from 90ms. Wired removes the host's Wi-Fi from the equation entirely — no interference, no band-steering, no shared airtime with your neighbor's microwave. Confirm the test reports a wired connection and a download figure comfortably above your target bitrate. You are looking for stability, not a headline speed-test number.

# EXPECTED OUTPUT — Test Internet Connection

Internet Connection ......... Successful
Connection Type ............. LAN Cable (Wired)
IP Address .................. Obtained (192.168.1.42)
Internet Communication ...... Connected
NAT Type .................... Type 2
Download Speed .............. 300 Mbps
Upload Speed ................ 40 Mbps      <-- must exceed your stream bitrate

Step 4 - Link the device and get the 8-digit PIN

Back in Settings > System > Remote Play, select Link Device. The console displays an 8-digit PIN that is valid for a short window. Why: auto-discovery works beautifully on the same LAN and fails the moment you are on a different network. The PIN is the manual pairing path that works regardless — you will feed it into the official app (Step 6) or into chiaki-ng (Step 10). Generate it when you are ready to enter it; it expires, so do not screenshot it and walk away.

# EXPECTED OUTPUT — Link Device

Enter this number on the device you want to use.

    PIN:  8 2 4 1 9 0 3 7

(The code expires shortly. Generate a fresh one if it times out.)

Part 2: The Official App and the Portal (Steps 5-8)

The official path is the simple one. It auto-negotiates the codec, hides the bitrate slider, and just works — which is exactly why power users graduate to chiaki-ng in Part 3. But for most people, on a phone or a Portal, this is the whole tutorial. Four steps.

Step 5 - Install the app or prep the Portal

On a phone, PC, or Mac, install PS Remote Play from the app store or from Sony's official Remote Play page. On a Portal, make sure it has taken the March 2026 update — Settings > System > System Software > System Software Update. Why: the 1080p High Quality mode in Step 7 does not exist on pre-March-2026 Portal firmware. If Max Resolution shows only Standard options, you have not updated, full stop.

Step 6 - Sign in and connect

Launch the app, sign in with the same PSN account that is signed in on the host, and let it search. On the same network it will find the console automatically. If it cannot — different network, or a stubborn router — use the manual PIN path and enter the 8-digit code from Step 4. Why: the account is the authorization boundary. Remote Play checks that the client account matches the host's registered user; this is also the source of the Portal's well-documented nuisance around multiple PSN accounts, which switch clumsily and are best avoided mid-session.

# EXPECTED OUTPUT — PS Remote Play app

Searching for devices...
Found: PS5-8F2A   (192.168.1.42)
Connecting to PS5-8F2A...
Authenticating account............. OK
Starting Remote Play
Resolution: 1080p (Standard)   <-- we raise this in Step 7
Stream established.

Step 7 - Switch on 1080p High Quality

Once the stream is live, open the Quick Menu, go to Max Resolution, and select 1080p High Quality. Then restart the session to apply it. Why: this is the entire reason 2026 is worth talking about. High Quality lifts the bitrate ceiling that made the old default look like a compression artifact convention. It also uses more data, so it is the correct choice on your home network and a judgment call on a metered mobile connection.

# ENABLE 1080p HIGH QUALITY (App / Portal / Cloud Streaming)

During an active Remote Play or Cloud Streaming session:

    Quick Menu  ->  Max Resolution  ->  1080p High Quality

Then RESTART the session to apply.
Note: High Quality uses more data than 1080p Standard.

Step 8 - Handle frame rate, controller, and audio

In the app's settings you can bias toward resolution or toward a smoother frame rate; on a strong connection, keep the standard 60fps target. Pair a DualSense to a phone or PC over Bluetooth for real controls — touch controls exist but are a compromise. Why audio matters here: the Portal famously has no standard Bluetooth headphone support. Wireless audio requires a PlayStation Link accessory; otherwise use the 3.5mm jack. And do not expect Netflix or YouTube — the Portal still ships with no media apps, an omission that remains odd in 2026.

Part 3: chiaki-ng for Power Users (Steps 9-12)

chiaki-ng is the open-source, next-generation continuation of the original Chiaki project — a free Remote Play client for Linux, FreeBSD, OpenBSD, Android, macOS, Windows, and Nintendo Switch. It exists because the official app hides everything interesting. chiaki-ng hands you the bitrate, the codec, and the decoder, and on a Steam Deck it is the single best reason the device is a competent Remote Play handheld. Four steps, and the payoff is a stream that is measurably cleaner than the app on identical hardware.

Step 9 - Install chiaki-ng

On Linux or Steam Deck, install from Flathub (the app ID is io.github.streetpea.Chiaki4deck). On Windows or macOS, grab the installer from the GitHub repository. Why the app ID looks odd: chiaki-ng grew out of the Chiaki4deck fork aimed at the Steam Deck, and the Flatpak kept the identifier. It is the right package. If you are pairing this with a Deck, our Switch 2 versus Steam Deck breakdown covers why the Deck's open OS is exactly what makes clients like this possible.

Step 10 - Register your console (Account ID plus PIN)

Registration is a two-key handshake. chiaki-ng needs your PSN Account-ID (a Base64 string it captures when you log in through its built-in PSN flow) and a one-time 8-digit PIN from the console. On the PS5, generate that PIN exactly as in Step 4: Settings > System > Remote Play > Link Device. Then, in chiaki-ng, register the discovered console and enter the PIN. Why two keys: the Account-ID proves who you are; the PIN proves you have physical access to the console right now. Together they let chiaki-ng store a persistent host key so future connections are one click.

1. Open chiaki-ng and complete the PSN login so it captures your Account-ID.
2. Let it discover the console on your LAN.
3. On the PS5, open Link Device to display the 8-digit PIN.
4. Enter the PIN in chiaki-ng and register.

# chiaki-ng — CONSOLE REGISTRATION (expected output)

[psn]  Login successful. Account-ID captured (Base64): xY3k9Q...==
[disc] Scanning local network...
[disc] Discovered consoles:
          PS5   192.168.1.42   state: standby   registered: no
[reg]  Enter 8-digit Link Device PIN: 82419037
[reg]  Registering console 192.168.1.42 ...
[reg]  Registration successful. Host key stored.
[ok]   Console ready. Double-click to connect.

Step 11 - Set the decoder and codec

This is the most important setting in chiaki-ng. In the stream settings, enable the Hardware Decoder appropriate to your platform — VAAPI on Linux, VideoToolbox on macOS, D3D11 on Windows, NVDEC on NVIDIA — and select the HEVC codec for a PS5 host. Why: HEVC gives you more picture per bit, but only a hardware decoder can keep up with it at 60fps without pegging your CPU. Software decoding is the single most common reason a chiaki-ng stream stutters on a machine with bandwidth to spare. The official configuration docs are explicit that using the hardware decoder for your system improves performance significantly.

Step 12 - Set resolution, frame rate, and bitrate

Set 1080p, 60fps, and a bitrate of 30,000 Kbps for a PS5 host on a good local network — that is chiaki-ng's documented HDR target. Why these numbers: the docs note that 1080p carries more color data than 720p even when the effective detail is similar, thanks to chroma subsampling headroom, so 1080p is the right pick when your bandwidth supports it. If you hit choppy audio, video flashes, or lag, step down to 720p before you touch anything else, and treat 30fps as a last resort for a genuinely bad connection.

# chiaki-ng — RECOMMENDED SETTINGS (PS5 host, good LAN)

Video
  Resolution ............ 1080p         # drop to 720p if choppy
  FPS ................... 60            # 30 only as a last resort
  Bitrate ............... 30000 Kbps    # PS5 HDR target
  Codec ................. HEVC (H.265)  # H.264 only if HW decode is unavailable

Decoder
  Hardware Decoder ...... ON  (VAAPI / VideoToolbox / D3D11 / NVDEC)
  Zero-Copy ............. ON  where supported

Audio
  Buffer ................ smallest value that stays stable

Common Pitfalls (and Their Fixes)

Most Remote Play misery traces back to six or seven recurring mistakes. Here they are, grouped by where they live, with the fix stated plainly. If your stream is bad, it is almost certainly one of these, not a flaw in the technology.

Network pitfalls

Double-NAT is the quiet killer: an ISP gateway in router mode feeding your own router in router mode means two layers of address translation, and discovery and wake packets get lost between them. Put one device in bridge mode. 2.4GHz Wi-Fi on the client is the second: it is congested, low-bandwidth, and shared with every smart bulb in the building — force the client onto 5GHz. A VPN on the stream path is the third: even a fast VPN adds a hop and a re-encryption pass, and Remote Play is latency-sensitive enough to feel it. Turn it off for the session.

Host pitfalls

The rest-mode power settings from Step 2 are the number-one support ticket in disguise; if you cannot wake the console remotely, you skipped them. The single-account nuisance bites households: the Portal and app tie cleanly to one primary PSN user, and juggling accounts mid-session is clumsy by design. And if the host itself is misbehaving — sluggish, dropping sessions, refusing to wake cleanly — a cache clear and database rebuild often resolves it; our 15-minute PS5 cache-clear walkthrough does it without touching your saves.

Client pitfalls

A software decoder in chiaki-ng (Step 11) produces stutter on hardware that has bandwidth to spare — enable the hardware decoder. Leaving resolution on 1080p Standard after the March 2026 update wastes the whole point of the update; switch to High Quality in the Quick Menu. And a black screen with audio is not a bug: Remote Play deliberately refuses to stream HDCP-protected video, so Blu-ray playback and some streaming apps show black. Use Remote Play for games, which is what it is for.

Troubleshooting Table

When something breaks, work top-down: connection first, then wake behavior, then picture quality. The table below maps the symptom to the most likely cause and the fastest fix. Nine times out of ten the answer is in this table, and eight of those times it is a network problem wearing a costume.

The lookup table

When the console will not wake

If discovery works on the LAN but remote wake fails, the culprit is almost always the rest-mode power pair from Step 2, followed closely by double-NAT swallowing the wake packet. Confirm the two toggles are on, put your ISP gateway in bridge mode so only one device does NAT, and test the wake from inside the house first — if it will not wake from the next room, it will not wake from a hotel.

When the picture falls apart

Macroblocking, smearing on fast motion, and flashes of green or gray are bitrate-and-transit symptoms, not resolution symptoms. Raising the resolution label makes them worse, not better. Move the client to 5GHz, confirm the host is wired, switch the app to 1080p High Quality, and in chiaki-ng either raise the bitrate toward 30,000 Kbps or, if the connection genuinely cannot carry it, drop to 720p and accept a stable stream over an ambitious one.

Advanced Tips

Once the basics work, here is where the last few percent live — connecting from outside the house without cursing, the homebrew client ecosystem, and squeezing the pipeline for the milliseconds that are actually recoverable.

Wake-on-LAN and connecting from outside

Remote Play over the internet is the same protocol with a longer network leg. The console must be reachable and wakeable, which means the rest-mode toggles and a sane NAT are mandatory, not optional. Most home routers handle the hole-punching via UPnP; if yours does not, you are into manual port configuration, and the honest answer is that a wired host with UPnP enabled solves this for the overwhelming majority of setups. Test from a phone on cellular data, with the console in rest mode, before you rely on it away from home.

1. Confirm both rest-mode options are on (Step 2).
2. Put the ISP gateway in bridge mode to kill double-NAT.
3. Enable UPnP on the router, or forward the Remote Play ports manually.
4. Wake and connect from a phone on cellular before trusting it in the wild.

Steam Deck, Switch, and the homebrew clients

chiaki-ng's reach is the reason it matters. It turns a Steam Deck into a first-class Remote Play handheld with real bitrate control, and its Nintendo Switch port drags Remote Play onto hardware Sony would never sanction. This is the open-source dividend: the client keeps improving on the public changelog while the official app stays deliberately simple. It is a very different philosophy from the walled handheld approach — see how the ROG Xbox Ally handles streaming for the contrast.

Getting the last few milliseconds

The recoverable latency is in the client, not the console. Force a hardware decoder, prefer HEVC, keep the audio buffer as small as it will go without crackling, and — the big one — make sure nothing else is saturating your uplink while you play. A single large upload in the background will wreck a stream faster than any setting. If you have measured your added latency and it sits in the 25-to-40ms band, you are at the practical floor. Chasing lower is chasing a number that does not exist, and if you want proof of how far the hardware still has to travel before local-quality streaming is trivial, note that even the still-undated PS6 will not repeal the speed of light.

The Complete Working Configuration

Everything above, condensed into one reference you can copy and check line by line. If your setup matches this block and your stream is still bad, the problem is upstream of anything in this tutorial — your ISP, your router hardware, or a background process eating your uplink.

The PS5 host config

The host settings are the foundation. All four of these must be true, and the Ethernet line is the one people cheat on and regret.

The client config (app and Portal)

On the official path, the two settings that matter are the resolution mode and the restart that applies it. Everything else the app negotiates for you.

The chiaki-ng config

On the power-user path, the decoder and codec are the whole game, with bitrate and resolution as the levers you pull when the connection is imperfect.

# ============================================================
#  PS REMOTE PLAY 2026 — COMPLETE WORKING CONFIGURATION
#  Target: 1080p60, ~25-40 ms added latency on a clean LAN
# ============================================================

# ---- 1. PS5 HOST ----
Settings > System > Remote Play > Enable Remote Play ........... ON
Settings > System > Remote Play > Link Device ................. (PIN on demand)
Settings > System > Power Saving > Features in Rest Mode:
    Stay Connected to the Internet ........................... ON
    Enable Turning On PS5 from Network ....................... ON
Host uplink .................................................... Ethernet (wired)

# ---- 2. ROUTER / NETWORK ----
Host connection ............................................... wired, 1 Gbps
Client band ................................................... 5 GHz (Wi-Fi 5+)
NAT ........................................................... single (no double-NAT)
VPN on stream path ............................................ OFF
UPnP .......................................................... ON  (or manual ports)

# ---- 3. OFFICIAL APP / PORTAL ----
Quick Menu > Max Resolution ................................... 1080p High Quality
Frame Rate .................................................... Standard (60 fps)
Restart session after changing resolution ..................... yes
Portal firmware ............................................... March 2026 or later

# ---- 4. chiaki-ng (POWER USER) ----
Resolution .................................................... 1080p
FPS ........................................................... 60
Bitrate ....................................................... 30000 Kbps
Codec ......................................................... HEVC
Hardware Decoder .............................................. ON
Registered Account-ID ......................................... 

# ---- EXPECTED RESULT ----
#   Stream:   1080p @ 60 fps, HEVC, ~28-30 Mbps
#   Latency:  ~25-40 ms added on LAN   |   + network RTT over the internet
#   NOT:      "2 ms" — that number is fiction
# ============================================================

That is the machine, fully assembled. The 2026 update did the one thing that was actually missing — it gave the encoder enough bits to justify the 1080p on the box — and the rest was always a matter of wiring the host, respecting the physics, and refusing to believe the latency fairy tales. Thirty minutes, twelve steps, and a stream that finally looks like the hardware it is streaming from.