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

Sony would like you to believe that PlayStation Remote Play is a single, simple thing you turn on with one toggle. It is not. In 2026 the phrase covers at least three different technologies wearing the same coat: your own console streaming its video to a phone, a hardware handheld called the Portal that also does cloud gaming, and an open-source client that outperforms the official app on every axis that matters. Getting a clean, low-latency session is genuinely a thirty-minute job. Getting it wrong is a multi-evening ordeal of dropped frames, unwakeable consoles, and error codes that Sony's support pages describe with the specificity of a horoscope.

This walkthrough is the version I wish existed the first time I set it up. Twelve numbered steps with the reasoning behind each, the exact firmware versions and port numbers, the config that actually works, and a troubleshooting table for when it does not. We will use the official app where it is the right tool and chiaki-ng where it is the better one. And we will correct a pile of 2026 misinformation along the way, including the price of the Portal, which is not what half the internet is telling you.

Remote Play vs. Cloud Streaming: Know What You Are Doing

Before you touch a single menu, understand the distinction that the marketing department has spent two years deliberately blurring. Remote Play and Cloud Streaming are not the same product, they do not have the same requirements, and confusing them is the root cause of most setup failures.

Your console is the server

In Remote Play, your own PS5 or PS4 renders the game, encodes the output into a video stream in real time, and sends that stream across your network to a client device. The client — a Portal, a phone, a laptop — is a dumb terminal. It decodes video and ships your button presses back. Nothing is being computed in the cloud. Everything depends on your console being powered (or in Rest Mode), your home network, and, if you are away from home, the public internet between you and your router.

This architecture is old. Remote Play shipped on the PS3 and PSP in 2006, came to PC and Mac around 2016 in the PS4 era, and landed on the PS5 when the console launched in November 2020. Anyone selling you PC or Mac support as a shiny 2025 feature is padding a press release. The only genuinely new thing is the polish.

Cloud Streaming is a different animal

Cloud Streaming, by contrast, runs the game on Sony's hardware in a data centre and requires a PS Plus Premium subscription. Your console can be off, unplugged, or nonexistent. In early 2026 the PlayStation Portal gained the ability to cloud-stream over 2,800 PS5 titles from your digital library and the PS Plus catalogue, which is the feature people mean when they excitedly claim the Portal 'no longer needs your PS5 on.' That claim is true — for Cloud Streaming, on a Premium plan. It is false for Remote Play, which will always need your console awake somewhere. TechRadar's 2026 review leaned on exactly this capability, and it is real, but it is not Remote Play.

What actually changed in 2026

Two Portal updates matter. System software 6.0.0 in early 2026 was the 'full launch': it switched on PS5 Cloud Streaming for Premium members, redesigned the home screen, added 3D audio over a headset, and remapped the PS button to a quick menu. Then 7.0.0, dated March 17, 2026 (PDT) and rolling out globally from March 18, added the headline 1080p High Quality mode plus trophy, search, and store-page refinements. The current build at time of writing is 7.0.2. Keep those two numbers straight, because a lot of coverage attributes 1080p High Quality to '6.0,' and that is simply the wrong version.

Prerequisites: Firmware, Devices, and Bandwidth

Remote Play punishes vague preparation. Nail the prerequisites and the rest is menu-tapping. Skip them and you will be reading the troubleshooting table by paragraph twenty.

The console side

You need a PS5 (any model, including PS5 Pro) or a PS4, on current system software. There is no minimum firmware trick here; just run the latest update, because Remote Play's protocol handshake occasionally changes and old firmware negotiates badly. The single most important hardware decision is boring: wire the console to your router with Ethernet. Wi-Fi on the console side introduces jitter that no amount of client-side tuning can undo, and every serious guide, Sony's included, assumes the console is hardwired. If you can only wire one device, wire the console, not the client.

Rest Mode matters too. Remote Play can wake a sleeping console, but only if you have explicitly permitted it. We configure that in Step 2. If your PS5 keeps refusing to wake from your phone, this is almost always why.

The client side

Here is where the version numbers get specific. The official PS Remote Play app (Google Play ID com.playstation.remoteplay, published by PlayStation Mobile Inc.) supports a range of platforms, each with its own floor. The Portal is a special case: it streams PS5 only — no PS4, no PS3 — even though the phone and PC apps happily handle a PS4.

On Android specifically, controller support is gated by OS version, and this trips people up constantly. The 2026 app listing spells it out:

PS Remote Play (Android) — controller support by OS floor:
  Android 10+   ->  DualShock 4   (PS4 pad)
  Android 12+   ->  DualSense     (PS5 pad)
  Android 14+   ->  DualSense Edge (Edge pad)
iOS / iPadOS 16+ ->  DualShock 4 / DualSense / DualSense Edge

If your DualSense will not pair to an Android phone for Remote Play, check the OS version before you blame the pad. A phone on Android 11 will run the app and stream video but refuse to bind a DualSense.

The network and the accounts

Sony's 2026 documentation puts the bandwidth floor at 5 Mbps and the recommendation at 15 Mbps, figures refreshed with December 2025 to January 2026 data and repeated verbatim on the PS Blog. That is per direction and it is optimistic for anything above 720p. Treat 15 Mbps as the minimum for 1080p High Quality or a 30,000 Kbps chiaki-ng session, and understand that a fast download number means nothing if your Wi-Fi is congested or your upload (for out-of-home play) is thin.

You need a PlayStation Network account signed in on both console and client — the same account. You do not need PlayStation Plus for Remote Play to function; Sony's own 2026 accessory documentation confirms this. Multiplayer titles that require Plus will still demand it once you are in-game, but the streaming itself is free. Only Cloud Streaming needs Premium.

The 12-Step Setup Walkthrough

This is the spine of the tutorial. Follow it in order — the order is not arbitrary, and doing Step 7 before Step 2 is how you end up with an unwakeable console. On a prepared network this is a thirty-minute job.

Steps 1 through 12

1. Update the console. Settings > System > System Software > System Software Update and Settings. Rationale: the Remote Play handshake and codec negotiation live in firmware; a stale build causes registration failures that look like network problems.
2. Configure Rest Mode wake. Settings > System > Power Saving > Features Available in Rest Mode, and enable Keep PS5 Connected to the Internet and Enable Turning On PS5 from Network. Rationale: without these two toggles, a sleeping console is a dead console as far as your phone is concerned.
3. Turn on Remote Play. Settings > System > Remote Play > Enable Remote Play. Rationale: this is the actual feature switch; it is off by default on a fresh console.
4. Wire the console. Plug Ethernet from the PS5 to your router and confirm Settings > Network shows a wired connection. Rationale: console-side Wi-Fi jitter is the number-one cause of stutter, and no client setting fixes it.
5. Reserve a static lease. In your router, bind the console's MAC address to a fixed LAN IP (for example 192.168.1.42). Rationale: manual connections and port forwarding both break the moment DHCP hands the console a new address.
6. Pick your client. Decide between the official PS Remote Play app, a Portal, or chiaki-ng. Rationale: the registration flow differs slightly and you want to commit before you generate a pairing code, which expires.
7. Install the correct app. On phone or PC, install PS Remote Play by PlayStation Mobile Inc. (com.playstation.remoteplay). Rationale: the store is full of imposters — see the pitfalls section — and installing the wrong one wastes an evening.
8. Sign in with the same PSN account on the client that you use on the console. Rationale: Remote Play authorises the pairing against your account; a mismatched login simply will not find your console.
9. Generate a Link Device code. On the console, Settings > System > Remote Play > Link Device produces an 8-digit code. Rationale: this one-time PIN is how the client proves it is allowed to register; it expires in minutes, so have the client ready.
10. Enter the code on the client and complete registration. Rationale: this exchanges long-lived keys so future sessions connect without a fresh PIN.
11. Start a session and verify. Launch Remote Play; you should land on your console's home screen within seconds. Rationale: verifying on the LAN first isolates any later out-of-home problems to the network, not the pairing.
12. Tune resolution and bitrate. On the Portal, set 1080p High Quality; in chiaki-ng, set 1080p60 and 30,000 Kbps. Rationale: defaults are conservative, and the whole point of a wired console is to spend that headroom on image quality.

Expected output: a healthy first connection

The official app shows you a spinner, a brief black screen, and then your console's UI. That is the entire feedback loop — Sony hides the diagnostics. chiaki-ng, mercifully, logs what is happening, and a clean PS5 session on a wired LAN looks like this:

[I] Discovery: found PS5  'CUH-Livingroom'  192.168.1.42  (ready)
[I] Registering console... account-id ok, PIN accepted
[I] RP-Key stored to profile
[I] Senkusha MTU probe -> 1454
[I] Video 1920x1080@60  HEVC  30000 Kbps  HW-decode=on
[I] Audio 48 kHz opus
[I] Session established   rtt ~28 ms   0 dropped frames

An rtt in the 25–40 ms range on a good LAN is normal and is what a competent glass-to-glass Remote Play session actually feels like. If a marketing sheet promises you '2 ms,' close the tab: that is a LAN ICMP ping, not felt input latency, and the two are not the same number.

Why the order matters

Steps 1 through 5 are all console-side and idempotent — you do them once and forget them. Steps 6 through 10 are the pairing ceremony, and they are time-sensitive because of the expiring PIN. Steps 11 and 12 are verification and tuning, and they belong last because you cannot sensibly tune a stream that has not connected. If you find yourself regenerating Link Device codes repeatedly, the problem is almost never the code; it is that Step 2 or Step 8 was skipped.

The PlayStation Portal and 1080p High Quality

The Portal is the most polished way to do Remote Play and the most locked-down. It is a fixed-function terminal: an 8-inch 1080p 60 Hz LCD with a split DualSense bolted to either side. There is no launcher, no browser, no sideloading. What you get is what Sony ships, which as of 2026 is genuinely good — and, after the March update, sharper.

Updating to 7.0.x

The Portal updates itself over Wi-Fi, but you can force it: from the home screen, open Settings and check for a system software update, then let it pull 7.0.0 or later. Confirm the build under the system information page. If your Portal is still showing the old home screen without the 1080p High Quality option, you are pre-7.0.0 and the update simply has not landed yet; there is no manual sideload path, so connect it to a solid network and wait it out. Sony's Portal system software information page lists every build and what it changed.

Turning on 1080p High Quality

This is the feature people bought the update for, and it is not in the settings menu where you would expect. You enable it mid-game, from the in-session Quick Menu. Hold the PS button, open the Quick Menu, and change the resolution setting:

# On the Portal, while streaming a game:
PS button -> Quick Menu -> Max Resolution -> 1080p High Quality
# then RESTART the game session for it to take effect

# What it does:
#   Resolution : unchanged (still 1920x1080)
#   Bitrate    : raised vs. 1080p Standard
#   Data use   : higher — not for a metered hotspot

The critical detail, which the official PlayStation.Blog announcement states plainly, is that High Quality does not raise the resolution — it is still 1080p — it raises the bitrate. You are spending more bandwidth to compress the same 1080p frame less aggressively, which cleans up the blocky mess that fast motion and dark scenes produce at lower bitrates. It also, as Sony notes, uses more data, so do not enable it on a metered cellular hotspot and then act surprised. Engadget's coverage is a good sanity check if you want the plain-English version.

The PS5 Pro and PSSR 2 reality check

Here is a claim you will see repeated: that in 2026 the Portal can stream PS5 Pro enhanced versions of games, ray tracing and all, including the machine-learning upscaler now marketed as PSSR 2. Technically, sort of. Practically, mind the pipe. PSSR 2 is real — it arrived in a March 2026 PS5 Pro update and has been rolling out to dozens of games as a free upgrade. But Remote Play does not teleport that enhanced frame to your Portal. Your PS5 Pro renders its gorgeous reconstructed 4K image, then Remote Play re-encodes it into a 1080p video stream and sends that. You are watching a compressed 1080p photo of a 4K painting.

So yes, a PS5 Pro that is hardwired via Ethernet will give you a cleaner Remote Play session than a Wi-Fi console, because the encode side has more headroom and less jitter. And yes, PSSR 2 improves the source frame before it is squashed, so there is a marginal quality benefit. But do not buy a $899.99 PS5 Pro expecting the Portal to show you native Pro fidelity. The Portal panel is 1080p and the stream is 1080p; the ceiling is the ceiling. The Ethernet recommendation is sound; the fidelity promise is oversold.

chiaki-ng: The Open-Source Client

If you own a PC, a Steam Deck, a ROG Ally, or a modded Switch, the official app is not your best option. chiaki-ng is, and it is where the tinkerers live. It speaks Sony's Remote Play protocol using your own account and a legitimate PIN — it cracks nothing — but it hands you every knob the official app hides.

Why bother with an unofficial client

chiaki-ng, maintained by streetpea as the successor to the original Chiaki by thestr4ng3r, reached v1.10.0 on April 3, 2026. That release, covered by GamingOnLinux, added better congestion control, an OpenGL renderer backend, adaptive queue depth, custom upscalers with VSync presets, configurable NAT port guessing with hole-punching fixes, and reworked audio, microphone, and haptics paths. It runs on Linux, FreeBSD, OpenBSD, Windows, macOS, Android and Switch, with iOS and tvOS compilation now in the tree. Crucially, it lets you set an explicit bitrate — 30,000 Kbps and beyond — where the official app just picks for you. The one honest caveat, which the project states loudly, is that it is not endorsed or certified by Sony. Nobody is coming to help you if it breaks.

Install and register

Install from the chiaki-ng GitHub releases (or Flathub on Linux), then register your console. Registration needs two things the official app hides from you: your PSN Account ID in Base64 — this is not your visible online ID — and the same 8-digit PIN from Settings > System > Remote Play > Link Device. Modern chiaki-ng can fetch the Base64 Account ID for you via a PSN login button; older workflows made you extract it by hand.

# chiaki-ng: Console Registration dialog
Console Type:            PS5
PSN Account ID (Base64): kR3n...==      # NOT your online ID
Registration PIN:        12345678       # from Link Device
Console IP (manual):     192.168.1.42   # optional if discovery works

Get the Account ID wrong — for instance, pasting your online ID instead of the Base64 value — and registration fails with a message that does not tell you why. That single mistake accounts for most 'chiaki-ng will not register' complaints. The chiaki-ng documentation walks through the login flow in the setup and configuration sections.

Recommended settings for PS5

Once registered, tune the stream. For a wired PS5 and a 5 GHz client, this is the configuration that holds up:

# chiaki-ng > Settings > Stream
Resolution:        1080p        # PS5 (PS4 caps at 720p)
FPS:               60
Bitrate:           30000 Kbps   # 0 = auto; 30 Mbps for a clean LAN
Codec:             HEVC (H.265) # fall back to H.264 on old GPUs
Hardware decoder:  auto/on      # never software-decode HEVC
Audio buffer:      9600         # raise if audio crackles

HEVC at 30,000 Kbps over a wired console is visibly cleaner than the official app's 1080p Standard and roughly on par with, or better than, the Portal's 1080p High Quality — because you chose the number instead of Sony choosing it for you. Keep the hardware decoder on; software-decoding HEVC on a laptop will spike your CPU and add the very latency you are trying to avoid.

Network, Ports, and the CGNAT Wall

Home LAN Remote Play mostly configures itself through discovery broadcasts. Out-of-home Remote Play — streaming your console from a hotel, an office, or a friend's couch — is where networking knowledge earns its keep. This is the section people skip and then file support tickets about.

The ports Remote Play uses

Remote Play talks over a small, specific set of ports. If you are forwarding through a router for out-of-home play, forward these to the console's reserved LAN IP:

# Forward to the console's static LAN IP (reserve a DHCP lease first)
Proto  Port(s)   -> Destination      Purpose
TCP    9295      -> 192.168.1.42      registration + control
UDP    9296      -> 192.168.1.42      A/V stream + Senkusha MTU probe
UDP    9297      -> 192.168.1.42      feedback / input
UDP    9302      -> 192.168.1.42      PS5 discovery
UDP    987       -> 192.168.1.42      PS4 discovery
# Fallback range some setups use: UDP/TCP 9295-9304
# PSN sign-in also needs OUTBOUND:
#   TCP 80, 443, 3478, 3479, 3480   UDP 3478, 3479

Port forwarding for out-of-home play

The routine is mechanical: reserve a static DHCP lease for the console (Step 5 already did this), forward the ports above to that IP, and connect the client using your home's public IP or a dynamic-DNS hostname. In the official app you use 'Manually register a device'; in chiaki-ng you add a manual console with the public address. The reason the static lease is non-negotiable is that a forwarded port pointing at yesterday's IP forwards to nothing.

CGNAT: when forwarding cannot save you

Here is the wall. If your ISP puts you behind Carrier-Grade NAT — common on fibre, most cellular home internet, and Starlink — you do not own a public IPv4 address, and no amount of router configuration will forward a port that your ISP is sharing among hundreds of customers. You can detect this in minutes: if your router's WAN IP is in the 100.64.0.0/10 range, or it does not match what a 'what is my IP' site reports, you are behind CGNAT. Your options are to ask the ISP for a real static IP (sometimes a paid add-on), tunnel through a VPN or a self-hosted relay like Tailscale, or give up on Remote Play out of home and use PS Plus Premium Cloud Streaming instead, which routes through Sony's servers and does not care about your NAT situation at all.

Five Pitfalls That Ruin the First Session

Every one of these has cost someone an evening. Read them now and save yourself the ticket.

Power and Wi-Fi pitfalls

Pitfall 1: the console cannot wake. You start Remote Play, it hunts, it fails. The console is in Rest Mode with Enable Turning On PS5 from Network switched off. Fix: Step 2. Enable both Rest Mode network toggles and, ideally, leave the console fully on for your first successful session so you can isolate the wake problem from the pairing problem.

Pitfall 2: 2.4 GHz Wi-Fi anywhere in the chain. A wired console and a client on a congested 2.4 GHz band will stutter no matter what bitrate you set. Fix: put the client on 5 GHz (or 6 GHz), stand near the access point, and remember that a full-bars signal that is shared with a microwave and forty neighbours is not the same as a clean channel.

App and account pitfalls

Pitfall 3: installing the wrong app. Search 'PS Remote Play' and you will find impostors — notably a third-party 'PS Remote Play Controller' by USA Works Solutions out of Houston, which is not Sony's app. Fix: install only the app published by PlayStation Mobile Inc. with the ID com.playstation.remoteplay. If it is asking for odd permissions or costs money up front, it is not the real one.

Pitfall 4: expecting a PS4 or PS3 on the Portal. The Portal streams PS5 only. Your PS4 library is invisible to it. Fix: use the phone or PC app for a PS4 — those clients handle both consoles. This is also a fine reason to keep an old PS4 around; Sony shipped 117 million of them and every one still does Remote Play to a phone.

Feature-conflict pitfalls

Pitfall 5: fighting Share Play or Cloud Streaming. You cannot run a Share Play session or a Cloud Streaming session simultaneously with a Remote Play session on the same console — they are mutually exclusive uses of the box. Fix: end one before starting the other. If Remote Play refuses to connect and you were just cloud-streaming, that leftover session is likely the culprit; give it a minute to tear down.

Troubleshooting: Symptoms, Causes, Fixes

When it breaks, work the symptom, not the panic. The table below covers the failures you will actually hit, in rough order of frequency.

The failure table

Reading error codes

Sony's NW- and CE- error families are deliberately generic. An NW- code points at the network layer — check the PlayStation Network status page first, because a Sony-side outage will masquerade as a local fault and no amount of router-poking will fix it. A CE- code points at the console. Before you escalate, confirm the obvious: same account on both ends, console awake, client on a real network rather than a captive-portal hotel Wi-Fi that has not authenticated yet.

When to reboot what

Reboot in order of blast radius, smallest first: restart the Remote Play session, then the client app, then the client device, then the router, then the console. If a console-side fault persists after all that — corrupt cache, database weirdness, a game that will not launch under Remote Play — a Safe Mode pass is the next tool. Our PS5 cache-clear walkthrough covers the two-minute version, which resolves a surprising share of 'it just stopped working' cases without touching your saves.

Advanced Tips: Bitrate, Handhelds, and Wake Tricks

Once the basics hold, here is where you extract the last of the quality and convenience.

Bitrate and codec tuning

The official app auto-selects; chiaki-ng lets you push. On a wired PS5 and a 5 GHz client, 30,000 Kbps HEVC is the sweet spot — clean in motion, low enough to survive Wi-Fi hiccups. If you have a genuinely clean, wired-to-wired path, you can nudge higher, but returns diminish fast above 30 Mbps because the console's encoder and the 1080p ceiling both cap what the extra bits buy you. Prefer HEVC (H.265) for its efficiency; only fall back to H.264 on hardware too old to hardware-decode HEVC, because software-decoding it will cost you more latency than the codec saves. If audio crackles when you raise the bitrate, raise the audio buffer — it is a symptom of the stream outrunning the buffer, not a codec fault.

chiaki-ng on Steam Deck, ROG Ally, and Switch

This is the killer use case the Portal cannot touch. chiaki-ng turns any capable handheld into a Remote Play client with a real bitrate slider. A Steam Deck OLED or ROG Ally X running chiaki-ng gives you the Portal experience plus an actual operating system, a browser, emulation, and PC games — on hardware you may already own. On the Deck, add it as a non-Steam game and map the controls in Steam Input; on the Ally, it runs as a normal Windows app. The image quality, at matched bitrate, is indistinguishable from the official client, and you are no longer limited to streaming PS5 — a PS4 works too.

Wake-on-LAN and automation

The friction in Remote Play is waking the console. Beyond Sony's Rest Mode toggles, chiaki-ng can send the wake packet itself when you launch a registered console, so a single tap both wakes and connects. On a home server you can script this further — a wake-on-LAN magic packet to the console's MAC, a short delay, then the client — and bind it to a Stream Deck button or a home-automation routine. The chiaki-ng automation docs cover the CLI hooks. It is over-engineering for most people and delightful for the rest.

2026 Myths: $269 Portals, 2 ms Latency, and PSSR 2 Streaming

The 2026 Remote Play discourse is riddled with numbers that do not survive a fact-check. Since you will meet all of these, here is the correction, on the record.

The $269 Portal that does not exist

You will see the Portal priced at $269.99. It is not. Per Sony's own price-change announcement, the Portal moved to $249.99 in the US effective April 2, 2026, up from its $199.99 launch price in November 2023 — £219.99 in the UK, €249.99 in Europe, ¥39,980 in Japan. The same round of increases put the PS5 at $649.99 and the PS5 Pro at $899.99. A $50 rise on a Remote Play terminal is a real story; a fabricated $70 rise is not. Use the real number.

'2 ms latency' and other physics violations

No Remote Play session has 2 ms of felt latency. That figure is someone quoting a LAN round-trip ping and calling it input lag. Real glass-to-glass latency — button press to pixel change — on a good wired LAN is roughly 25 to 40 ms, which is why competitive fighting-game players still prefer the couch. The 7.0.0 update genuinely reduced input delay and the Portal genuinely feels crisp, but 'crisper than cloud streaming' is a comparison, not a millisecond count. Treat any specific sub-10 ms claim as marketing that wandered into the spec sheet.

Streaming PSSR 2 to a Portal

We covered this above, and it is worth restating because it is the most confidently repeated myth: Remote Play re-encodes whatever the console renders into a 1080p stream. A PS5 Pro rendering a PSSR 2, ray-traced, 4K frame is still, at the Portal end, a compressed 1080p video of that frame. The Ethernet-to-router recommendation is legitimate — it stabilises the encode — but nobody is receiving native Pro fidelity over Remote Play, because the panel and the stream are both 1080p. Enjoy the enhancement on your TV; accept the re-encode on your handheld.

The Complete Working Configuration

Here is the whole thing in one place. Set the console once, pick your client, and paste the stream numbers. This is the configuration this article has been building toward.

Console configuration (set once)

# PS5 — one-time setup for Remote Play
Settings > System > System Software > Update            [latest]
Settings > System > Remote Play > Enable Remote Play    [ON]
Settings > System > Power Saving >
    Features Available in Rest Mode
      - Keep PS5 Connected to the Internet              [ON]
      - Enable Turning On PS5 from Network              [ON]
Network: wired Ethernet to router
Router:  reserve static DHCP lease -> 192.168.1.42

# Pairing (per client, PIN expires in minutes)
Settings > System > Remote Play > Link Device -> 8-digit code

Official app / Portal configuration

# PS Remote Play app (com.playstation.remoteplay, PlayStation Mobile Inc.)
Sign in: same PSN account as the console
Register: enter the 8-digit Link Device code
Client network: 5 GHz Wi-Fi or wired

# PlayStation Portal (system software 7.0.0+)
In-game: PS button -> Quick Menu -> Max Resolution
         -> 1080p High Quality
Then restart the game session to apply.

chiaki-ng configuration

# chiaki-ng v1.10.0 — registration + stream
Console Type:      PS5
Account ID:           # NOT online id
Registration PIN:  <8-digit code from Link Device>
Console IP:        192.168.1.42                   # static lease

[stream]
resolution        = 1080p       # PS4 caps at 720p
fps               = 60
bitrate           = 30000       # Kbps; 0 = auto
codec             = HEVC        # H.264 only on very old GPUs
hardware_decoder  = auto
audio_buffer      = 9600        # raise if audio crackles

# Out-of-home: forward TCP 9295, UDP 9296-9297, UDP 9302 (PS5)
# Behind CGNAT: use a VPN/Tailscale relay or PS Plus Cloud Streaming

That is the entire job. Console wired and awake-capable, client on a clean 5 GHz link, the correct app or chiaki-ng registered with a legitimate PIN, and a bitrate you chose rather than one Sony guessed. Do it in this order and the thirty-minute estimate holds. For the deepest reference, keep three tabs open: Sony's official Remote Play page for the supported-device list and the pause-on-TV-resume-on-phone workflow, the chiaki-ng repository for releases and issues, and the chiaki-ng documentation for the settings that the official app will never let you touch. Everything else is just tapping through menus — and now you know which menus, and why.