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

PS Remote Play is the oldest idea Sony keeps reintroducing as though it were new. The pitch — the console does the work, a screen somewhere else shows the picture — first shipped in 2006, when a PSP could borrow a PS3's silicon over Wi-Fi and pretend to be a portable. It worked about as well as anything did in 2006. Two console generations later the idea finally has hardware built for it, the PlayStation Portal, and in 2026 it finally has the two firmware updates that make it worth configuring properly.

This is a setup guide, not a press release. In twelve steps and roughly half an hour you will get a stable Remote Play session running at 1080p, switch on the High Quality mode Sony added in system software 7.0.0, and learn which numbers matter and which are marketing. Then, because this is StaresBack, we will show you the open-source client that does the same job without asking Sony's permission.

Two updates define the current state of play. Version 6.0.0, the early-2026 "full launch," added PS5 Cloud Streaming for PlayStation Plus Premium members, a redesigned home screen, 3D audio over a headset, and a library of more than 2,800 streamable PS5 titles. Version 7.0.0, which rolled out globally on March 17 (PDT) and March 18 (CET/JST), 2026, added the 1080p High Quality mode this guide is built around; the current build as of writing is 7.0.2. If you own a Portal, update it before you touch anything else. If you want the short, screenshot-heavy version, our companion 1080p High Quality walkthrough covers the same ground with more pictures and less lore.

What PS Remote Play Actually Is

Before you change a single setting, understand what you are turning on. Remote Play is a low-latency video-streaming protocol, not a magic teleporter for your games. Your PS5 renders a frame, an on-board hardware encoder squeezes it into HEVC (or H.264 on weaker links), the bytes cross your network, and the client decodes and displays them. Every knob in this guide is really a knob on that pipeline: resolution, bitrate, codec, and the quality of the two network hops on either end.

The protocol under the marketing

The reason latency exists — and why nobody honest promises you zero — is that each stage costs time. Encoding a frame takes milliseconds. The wireless hop takes more. Decoding takes more still. On a clean local network the felt, glass-to-glass latency lands somewhere around 25 to 40 milliseconds: good enough for Horizon, borderline for Tekken, and a bad idea for ranked anything. Anyone quoting you single-digit milliseconds is either measuring an ICMP ping across the LAN — which is not what your thumbs feel — or selling something. Keep that number in your head; it is the honest baseline that every tuning step in this article is trying to protect.

Remote Play is not Cloud Streaming

This is the distinction Sony's own interface blurs and the one that causes half the confusion online. Remote Play streams your console's live output: whatever disc or download is installed on the PS5 sitting in your house, over your network, for free. Cloud Streaming — the headline feature of the 6.0.0 update — runs the game on Sony's servers instead, requires a PlayStation Plus Premium subscription, and is what the 2,800-games figure actually refers to. The two cannot run at once, and you cannot use Share Play while a Remote Play session is live either. When someone says the Portal now streams 2,800 titles, they mean Cloud Streaming. When you set up Remote Play, your catalog is simply everything installed on your own PS5.

What 6.0.0 and 7.0.0 changed

Per Sony's own PS Portal system software history, 6.0.0 introduced cloud streaming, the home-screen redesign, 3D audio when using a headset, passcode support, and a control tweak: the PS button now opens the quick menu on most screens. Then 7.0.0 added the 1080p High Quality resolution option and folded in cloud-streaming niceties — bundle game selection, invite notifications, trophy details. That control tweak is worth flagging up front, because muscle memory dies hard: on the Portal, the PS button's job during a session is to summon the quick menu, which is exactly where the resolution toggle you came here for lives. Nothing about the underlying Remote Play stack for phones or PCs changed — that support has existed since the PS4 era around 2016, no matter how many 2026 headlines imply otherwise.

Prerequisites: Hardware, Software, Network

Remote Play fails at the weakest link, and the weakest link is almost always something you did not check before you started. Do the boring inventory now and you will save yourself the troubleshooting table later.

Console requirements

You need a PS5 (any model — disc, Digital, Slim, or Pro) or a PS4, running the latest system software. The Portal only talks to a PS5; the phone and desktop apps will also drive a PS4. Whatever the console, it must be either powered on or in Rest Mode with networking left awake — a fully shut-down console answers nothing. If you own a PS5 Pro, note that Remote Play mirrors and re-encodes whatever the console renders, so the machine's PSSR upscaling reaches you as a compressed copy of an already-upscaled frame, not as native handheld reconstruction. You are watching a recording of the good picture, not the good picture itself.

Client requirements and versions

Pick your screen and check its floor:

• PlayStation Portal — an 8-inch 1080p LCD at 60 Hz, launched November 2023, split around a DualSense with real haptics and adaptive triggers. Update it to 7.0.2 or the 1080p High Quality toggle simply will not appear.
• Android — the PS Remote Play app requires Android 10 or later.
• iPhone / iPad — a current iOS or iPadOS release; the app is a free download.
• Windows / macOS — Windows 10 or 11, or a recent macOS. This is old, stable, and free, and it is the cheapest way to test before you buy a Portal.

Every one of these authenticates against your PlayStation Network account, and every one of them requires a physical console to exist somewhere. There is no console-free Remote Play. That is the whole design.

The network floor: 5 and 15 Mbps

Sony's numbers are unambiguous and the March 2026 PlayStation Blog post repeats them verbatim: a broadband Wi-Fi connection of at least 5 Mbps to function, and at least 15 Mbps recommended for a better experience. Read those correctly. The 5 Mbps figure is the minimum that will connect at all; it will hand you a soft, low-bitrate picture. The 15 Mbps figure is the one that matters for the High Quality mode you are here to enable, and it is a recommendation for the uplink from the console, not your download speed. Over cellular, the app will happily eat your data allowance — Sony says so plainly on the official PS Remote Play page — so treat mobile data as an emergency option, not a plan.

Console-Side Setup

Everything the client does depends on the console being configured to answer. Three settings do ninety percent of the work, and people skip all three.

Enable Remote Play and set the primary console

On the PS5, go to Settings → System → Remote Play and turn Enable Remote Play on. This flips the listener that answers discovery requests; without it, the console is invisible to every client on your network no matter how perfect your Wi-Fi is. Then go to Settings → Users and Accounts → Other → Console Sharing and Offline Play and set this PS5 as your primary. Primary-console status lets your account license content and authenticate sessions without re-checking every launch, and it is quietly required for wake-from-rest to behave the way you expect.

PS5  →  Settings

[ System → Remote Play ]
  Enable Remote Play ................. ON
  Link Device ....................... shows an 8-digit PIN (write it down)

[ System → Power Saving → Features Available in Rest Mode ]
  Stay Connected to the Internet .......... ON
  Enable Turning On PS5 from Network ...... ON

[ Users and Accounts → Other → Console Sharing and Offline Play ]
  Set this PS5 as your primary console .... ON

Rest Mode: the two switches that matter

The two Rest Mode toggles in that tree are the difference between a console you can wake from the couch and a brick that ignores you. Stay Connected to the Internet keeps the network interface alive while the console sleeps. Enable Turning On PS5 from Network lets an incoming Remote Play request actually power the machine up. Enable both. The trade is a few watts of standby draw against never having to walk to the console to turn it on — a trade every sane person makes. If you would rather not sleep the console at all, leave it fully powered; Remote Play does not care, it only cares that the console is reachable.

Wire the console, not the client

If you take one piece of advice from this section, take this: put the Ethernet cable on the console. The PS5 is the end that encodes and transmits, so its uplink quality sets the ceiling for the entire session. A wired console removes its Wi-Fi radio as a variable entirely and leaves you with exactly one wireless hop — the client's — to worry about. This is backwards from most people's instinct, which is to fuss over the handheld's signal while the console sits on congested 2.4 GHz. Wire the console; let the Portal or phone be the only thing on Wi-Fi.

The 12-Step Walkthrough (~30 Min)

Here is the whole procedure end to end. Each step has a reason attached, because a step you do not understand is a step you will undo the moment it inconveniences you. Budget about thirty minutes, most of which is firmware updates and one honest range test at the end.

Steps 1–6: console and network

1. Update both ends. Bring the PS5 to the latest system software and the Portal to 7.0.2 via Settings → System → System Software. Why: the 1080p High Quality toggle only exists on 7.0.0 and later, and mismatched firmware can fail the handshake or simply hide the option you came for.
2. Set the PS5 as your primary console. Settings → Users and Accounts → Other → Console Sharing and Offline Play. Why: primary status authenticates your account cleanly and is a prerequisite for reliable wake-from-rest.
3. Enable Remote Play on the console. Settings → System → Remote Play → Enable Remote Play. Why: this is the listener. Without it the console never answers the discovery packet on UDP 9302 and no client will ever find it.
4. Configure Rest Mode. Turn on both Stay Connected to the Internet and Enable Turning On PS5 from Network. Why: together they let a sleeping console wake on demand; skip them and you are walking to the console every session.
5. Reserve the console's LAN IP. Add a DHCP reservation in your router so the PS5 always gets the same address. Why: discovery and any future port-forwarding are far more reliable against a fixed address, and you will not have to re-point rules every time the lease renews.
6. Wire the console to the router. Ethernet if the cable will reach. Why: the console's uplink is the whole ballgame — it encodes and sends — so removing its Wi-Fi from the equation eliminates the single most common source of mid-session stutter.

Steps 7–12: client, session, and range test

7. Update and sign into the client. On the Portal or app, sign into the same PSN account as the console. Why: Remote Play authorizes by account identity; a different account will see the console but refuse to pair with it.
8. Pair the client. The Portal auto-discovers a console on the same network; the phone and desktop apps let you enter the 8-digit PIN from the Link Device screen. Why: the PIN is a one-time key exchange. Do it once and every future session connects silently, no PIN required.
9. Start a session and confirm the codec. Launch Remote Play and check that it negotiated HEVC at 1080p and 60 fps. Why: if it falls back to H.264 or 720p, Sony's on-board bandwidth probe decided your link could not hold the bitrate — fix the network before you tune anything else, because no setting overrides physics.
10. Turn on 1080p High Quality. In-session, open the quick menu, go to Max Resolution, choose 1080p High Quality, and restart the session when prompted. Why: the toggle only appears mid-session on 7.0.0+, and the encoder re-negotiates its bitrate on restart — it will not switch live.
11. Set audio and 3D audio. Connect a wired headset or a PSLink wireless device and enable 3D audio. Why: 3D audio (added in 6.0.0) only runs to a headset, never the Portal's speakers, and standard Bluetooth headphones are not supported for low-latency audio at all.
12. Lock it in and test range. Play ten minutes at the worst Wi-Fi spot you actually use — the kitchen, the far bedroom — and watch for frame drops. Why: a session that is flawless beside the router and unplayable down the hall is a Wi-Fi coverage problem, not a Remote Play problem, and you want to discover that now, not mid-boss.

When step 9 succeeds, a healthy session reads something like the output below. Note the codec, the resolution, and the drop rate — those three lines tell you whether the rest of the tuning is worth doing.

[ Remote Play ]  scanning local network ...
  found  : "PS5-LivingRoom"   192.168.1.42
  radio  : 5 GHz   -48 dBm   (good)
  probe  : Senkusha bandwidth test = 63 Mbps up
  codec  : HEVC / 1920x1080 / 60 fps
  state  : CONNECTED   lan-rtt 3 ms   dropped 0.2%

Turning On 1080p High Quality

This is the feature that justified an entire firmware release, and it is genuinely good — provided you understand what it does and does not do. It is not a resolution bump. It is a bitrate bump wearing a resolution's name.

Where the setting lives

You cannot set it from the home screen. It only appears during an active session, which trips up everyone who goes hunting through the settings menus and finds nothing. Start Remote Play, open the quick menu (the PS button, post-6.0.0), go to Max Resolution, and pick 1080p High Quality. The session restarts to apply it, because the encoder has to re-negotiate the stream with the console — it will not hot-swap the bitrate underneath a running game. The same toggle governs Cloud Streaming, so if you are a Premium subscriber the High Quality mode follows you into the cloud catalog too.

Same pixels, more bits

Here is the part the marketing soft-pedals. 1080p Standard and 1080p High Quality render the identical 1920×1080 frame. What changes is how many bits per second the encoder spends describing it. Standard compresses harder, which is why fast motion — a camera whip, a particle storm, tall grass in the wind — dissolves into blocking and smear on the old mode. High Quality spends more of your bandwidth on the same frame, so those scenes hold together. If you have ever watched a streaming movie fall apart during a dark, fast scene and snap back during a static one, you already understand the mechanism. Sony confirmed the rollout landed globally from March 18, 2026, and the consensus from launch coverage was consistent: same sharpness on paper, materially cleaner in motion.

The bandwidth bill

Nothing is free. High Quality is exactly why Sony's 15 Mbps recommendation exists — it is the mode that consumes the headroom. If your uplink is marginal, turning High Quality on will make the picture worse, not better, because the encoder will target a bitrate the link cannot sustain and you will trade clean stills for stutter and dropped frames. The honest rule: enable High Quality only after step 9 has confirmed a stable HEVC/1080p session on Standard. If Standard already stutters, fix the network first; High Quality is a reward for a healthy link, not a fix for a sick one. The independent write-ups, including Engadget's coverage of the update, framed it the same way: a real improvement, gated behind real bandwidth.

Network Tuning: Bands, Bitrate, Ports

If the console is the engine, the network is the road, and most bad Remote Play experiences are potholes, not a bad engine. This section is where the felt-latency budget from the opening is either protected or squandered.

Bands, channels, and QoS

Put every client on 5 GHz, never 2.4 GHz. The 2.4 GHz band is a shared apartment full of microwaves, baby monitors, and your neighbors' routers; its congestion is exactly the jitter that turns a smooth stream into a stuttering one. On the router, if it supports Quality of Service, prioritize the console's reserved IP so its stream wins arbitration when the household starts a big upload. And if your router offers band steering that silently shuffles a device between bands, disable it for the client — Remote Play hates being moved between radios mid-session, because the roam event registers as a one-to-two-second freeze.

Ports for off-LAN play

On your own LAN, discovery is automatic and you never think about ports. The moment you want to play from outside the house, you are at the mercy of NAT, and you will want to forward the following to the console's reserved address. These are the ports Remote Play actually uses:

# Forward these to the PS5's reserved LAN IP (here 192.168.1.42)
TCP  9295  ->  192.168.1.42:9295   # registration + control
UDP  9296  ->  192.168.1.42:9296   # A/V stream + bandwidth probe
UDP  9297  ->  192.168.1.42:9297   # stream feedback
UDP  9302  ->  192.168.1.42:9302   # PS5 discovery  (PS4 uses UDP 987)

# Lazy but reliable: forward the whole range 9295-9304, TCP and UDP.
# PSN sign-in also needs outbound TCP 80/443/3478/3479/3480 and UDP 3478/3479.

Before you touch the router, confirm the link is actually clean with a plain ping and, if you have it, an iperf run. The expected output on a healthy LAN looks like this — and note the caption, because it is the whole point:

$ ping -c 5 192.168.1.42
64 bytes from 192.168.1.42: icmp_seq=1 ttl=64 time=2.31 ms
64 bytes from 192.168.1.42: icmp_seq=2 ttl=64 time=2.09 ms
...
rtt min/avg/max/mdev = 1.98/2.41/3.10/0.42 ms

$ iperf3 -c 192.168.1.42 -u -b 30M
[ ID] Interval        Transfer     Bitrate         Jitter    Lost/Total
[  5] 0.00-10.00 sec  35.8 MBytes  30.0 Mbits/sec  0.118 ms  0/25600 (0%)

# 2 ms is the LAN ICMP round-trip, NOT what your thumbs feel.
# Glass-to-glass (encode + Wi-Fi + decode) lands ~25-40 ms on a good LAN.

CGNAT: the wall you cannot climb

Here is the failure mode no amount of port-forwarding fixes. If your ISP puts you behind Carrier-Grade NAT — increasingly common on cellular home internet and cheap fiber — you do not own a public IP, you share one, and inbound forwarding is impossible because the port you opened lives on a router you do not control. The symptom is textbook: flawless at home, stone dead everywhere else. Your options are three: use Cloud Streaming instead (which is server-to-client and dodges the problem, at the cost of a Premium subscription), stand up a personal VPN back into your home LAN so the client appears local, or call your ISP and ask for a real IPv4 address, which they may or may not grant. There is no fourth option, and any guide that promises otherwise has not met CGNAT.

Five Pitfalls That Kill a Session

These are the mistakes that generate the most it-just-does-not-work posts, sorted by which layer they live in. Each has a fix that takes less time than complaining about it.

Network-layer mistakes

Pitfall 1 — Client on 2.4 GHz. The single most common cause of random stutter. 2.4 GHz jitter reads to the decoder as dropped frames. Fix: force the client onto a 5 GHz SSID and stay there.

Pitfall 2 — Double NAT. A modem-router feeding a second router means two NAT layers, and your forwarded ports land on the wrong one. Fix: bridge the modem, or forward the range on both devices, or move the console behind the outer router. Symptomatically this shows up as a session that pairs but then times out.

Console-layer mistakes

Pitfall 3 — Rest Mode networking off. The console sleeps, drops its network interface, and never wakes for the incoming request. Fix: the two Rest Mode toggles from the console-setup section — Stay Connected to the Internet and Enable Turning On PS5 from Network — both on.

Pitfall 4 — Console on Wi-Fi at the edge of range. People obsess over the handheld's signal and forget the console is the transmitter. A weak console uplink caps the whole session. Fix: wire the console, or at minimum move it to strong 5 GHz.

Client-layer mistakes

Pitfall 5 — Hunting for the resolution toggle in the menus. 1080p High Quality does not exist outside an active session, so searching the settings tree returns nothing and people conclude their firmware is broken. Fix: start a session first, then open the quick menu → Max Resolution. And if the option is genuinely absent mid-session, your Portal is below 7.0.0 — update it. A sixth, honorable-mention pitfall: expecting Bluetooth headphones to carry game audio. They will not; use wired or a PSLink device, or you get no 3D audio and often no audio at all.

Troubleshooting Table

When a session misbehaves, work from the symptom to the layer it lives in. The table below covers the ten failures you will actually hit, in rough order of frequency. If your problem is less a single symptom and more that the console is generally acting strange, it is worth a broader reset first — our PS5 cache-clear procedure resolves a surprising amount of streaming weirdness without touching your saves.

Reading the table by layer

Every row maps to one of three layers — network, console, or client — and the fix always lives in the same layer as the cause. Diagnose in that order: prove the network first, the console second, the client last, because a network fault can masquerade as all three.

The two stubborn cases

Two rows deserve extra words. The black screen after Connected is almost always a stale session or an HDCP/codec fallback; clearing the console cache and rebuilding the database clears it more often than any setting change. The perfect at home, dead everywhere else row is CGNAT nine times out of ten, and no client-side toggle will fix a NAT you do not control — that one is Cloud Streaming or a VPN, full stop.

When to stop tuning and reset

If three fixes in a row change nothing, stop tuning and reset the state instead of the settings: power-cycle the router, cold-boot the console, delete and re-register the client, then start again from a known-good baseline. More sessions die from half-applied fixes stacked on top of each other than from any single misconfiguration.

Advanced: The Chiaki-ng Escape Hatch

Sony's app is fine. It is also a walled garden: it runs where Sony ships it and nowhere else, and it makes its own decisions about your bitrate. If you want Remote Play on a Steam Deck, a Linux box, a Raspberry Pi, or a hacked Switch — or you simply want to set the bitrate yourself — the answer is Chiaki-ng.

Why an unofficial client exists

Chiaki-ng is an open-source re-implementation of Sony's Remote Play protocol, maintained by streetpea as a fork of the original Chiaki (by thestr4ng3r). The current release is v1.10.0, dated April 3, 2026, and it runs on Linux, FreeBSD, OpenBSD, Android, macOS, Windows, and the Nintendo Switch. It states plainly on its own front page that it is not endorsed or certified by Sony Interactive Entertainment — which is the honest disclaimer, not a warning. It decrypts no games and cracks no accounts; it speaks the same protocol your Portal speaks, using your own credentials. The chiaki-ng repository and its documentation site are the canonical sources; do not download it from anywhere else.

Account ID, PIN, and registration

Registration is a one-time affair with one gotcha: Chiaki-ng wants your PSN Account ID as a Base64 string, which is not your visible online ID. The docs walk through extracting it, and once you have it you pair exactly as the official app does — with the 8-digit PIN from the console's Link Device screen.

# chiaki-ng  register a console (one time)
# On PS5: Settings → System → Remote Play → Link Device  ==> 8-digit PIN

Console            : PS5
PSN Account ID     : aB3xY9k2Q1c=     # Base64, NOT your online ID
Registration PIN   : 12345678         # from the Link Device screen
Console passcode   : (optional, if you set one in 6.0.0)

Then set the stream profile by hand. This is the whole reason to be here — the official app will not let you pin a manual bitrate, and manual is exactly what you want on a wired LAN, where auto tends to lowball:

# chiaki-ng  stream profile (wired LAN, PS5)
resolution   = 1080p
fps          = 60
bitrate      = 30000     # Kbps, manual. 0 = auto, which underspends on LAN
codec        = HEVC
hw_decoder   = enabled   # essential; software decode adds latency and heat
audio_buffer = 9600      # raise if audio crackles; costs a little latency

Advanced tips: HDR, haptics, and a Steam Deck

A few things worth knowing once you are off the rails. Turn the hardware decoder on and confirm it is actually engaging — software decode is the difference between cool and hot silence, and it quietly inflates latency. On a controller with a gyro, Chiaki-ng can map motion controls the official app ignores. The client is a superb fit for a Steam Deck: install it, register once, and you have a 1080p Remote Play handheld with real desktop-class Wi-Fi and a battery you can hot-swap opinions about. For the audio-buffer figure, treat 9600 as a starting point — drop it for lower latency if your link is pristine, raise it if you hear crackle. And keep the golden rule from earlier: wire the console, 5 GHz the Deck. The client being fancy does not repeal physics.

The Complete Working Configuration

Everything above, consolidated into one reference you can copy to a note and re-apply after any factory reset. If you keep only one block from this article, keep this one.

Console settings, consolidated

These are the exact console-side values a healthy setup uses. Nothing here is optional; each line maps to a failure in the troubleshooting table if you skip it.

# ===== PS5 (the transmitter) =====
System → Remote Play → Enable Remote Play ............... ON
System → Power Saving → Rest Mode:
    Stay Connected to the Internet ..................... ON
    Enable Turning On PS5 from Network ................. ON
Users and Accounts → Console Sharing / Offline Play ...... ON (primary)
Network:
    Connection ......................................... WIRED (Ethernet)
    LAN IP ............................................. DHCP reservation, fixed
System Software ........................................ latest

The reference client profile

Whether you are on the Portal or Chiaki-ng, these are the targets. The Portal reaches them through the quick menu; Chiaki-ng reaches them through its config. Same destination, two doors.

# ===== Client (Portal or Chiaki-ng) =====
Firmware / app version ................. Portal 7.0.2  |  Chiaki-ng 1.10.0
Wi-Fi band ............................. 5 GHz only
Resolution ............................. 1080p
Quality mode ........................... 1080p High Quality  (set in-session)
Frame rate ............................. 60 fps
Codec .................................. HEVC
Bitrate (Chiaki-ng) .................... 30000 Kbps, manual
Hardware decoder (Chiaki-ng) ........... ON
Audio .................................. wired headset or PSLink (for 3D audio)

# ===== Off-LAN only =====
Router port-forward to console IP ...... TCP/UDP 9295-9304
CGNAT present? ......................... use Cloud Streaming or a home VPN

Pre-flight checklist

Run this list before you blame the software. In order: both ends updated; Remote Play enabled; primary console set; both Rest Mode toggles on; console wired; client on 5 GHz; same PSN account both ends; codec confirmed HEVC/1080p in-session; High Quality enabled only after Standard is proven stable; range-tested at your worst spot. Ten checks, maybe five minutes, and they pre-empt the overwhelming majority of the failures people spend an evening on instead.

That is the entire job. Remote Play in 2026 is finally a mature feature dressed up as a new one — 6.0.0 gave it a real launch, 7.0.0 gave it a picture worth streaming, and Chiaki-ng gives it somewhere to run that Sony never intended. None of it is hard once you accept the one rule the marketing keeps hiding: this is a network product, not a magic one. Fix the network and everything else falls into place. And if you are configuring all this while you wait for the next box from Sony, do not hold your breath — by our reading the PS6 lands in 2028 at the earliest, which means the PS5 you just wired to your router is the console you will be streaming from for years yet.