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

PS Remote Play is one of those features Sony has been quietly shipping for two decades and somehow still undersells. The pitch is simple: your PlayStation renders the game in your living room, re-encodes each frame, and squirts it across your network to whatever screen you happen to be holding. No cloud, no data center in Virginia deciding how your inputs feel, no monthly fee. Done right, it is the closest thing to a Vita successor that Sony refuses to call a Vita successor.

Done wrong — console on Wi-Fi, bitrate cranked past what the link can carry, Rest Mode misconfigured so the thing won't even wake up — it is a stuttering, purple-tinted mess that makes people blame the technology instead of their router. This is the long version: prerequisites with real version numbers, a twelve-step setup you can actually follow, the March 2026 PlayStation Portal 1080p update, the open-source route for Steam Deck and Linux, and a troubleshooting table for when it inevitably misbehaves. We will also quietly correct a few numbers that have been circulating, because precision is the entire point of doing this properly.

What Remote Play Actually Is (and What It Isn't)

A twenty-year-old idea that finally works

Remote Play is older than most of the people currently arguing about it online. Per Wikipedia's Remote Play entry, Sony shipped the first version in 2006, pairing the PlayStation 3 with the PSP so the handheld could act as a second screen for content running on the console. It was clumsy, the Wi-Fi of the era was worse, and almost nobody used it. Sony kept going anyway: the PS Vita made Remote Play a headline feature, Xperia phones inherited it, and by 2019 the net had widened to Android, iOS, Windows, and macOS. When the PS5 arrived, Remote Play support for the new console was folded into the app in early November 2020, days ahead of the console's November 12, 2020 launch.

The reason it works now and didn't then is boring and entirely about plumbing: home upload speeds, 5 GHz Wi-Fi, and hardware video decoders that turn an H.264 or H.265 stream into frames without cooking the battery. The idea never changed. The infrastructure caught up to it.

Remote Play is not Cloud Streaming — do not confuse them

This is the single most important distinction in the article, so read it twice. Remote Play streams a game from a console you own, sitting in your house. Your PS5 does the rendering, encodes the frame, and sends it over your LAN or the open internet to your phone, PC, or Portal. Cloud Streaming — the thing bundled into PlayStation Plus Premium — renders the game on Sony's server hardware in a data center and streams that to you instead. They look superficially identical, and the PlayStation Portal now does both, which is precisely why people muddle them.

The practical difference is latency and control. With Remote Play, the only things between your thumb and the game are your home network and, if you are away, the public internet. With Cloud Streaming you also inherit the round trip to a data center and whatever that server happens to be doing. When a 2026 Portal review or a Polygon video says local Remote Play now outperforms cloud streaming on crispness and input delay, this is the mechanism: fewer hops, and a bitrate you set yourself.

The mandatory-feature rule (why almost everything just works)

Sony requires that every PS4 and PS5 game support Remote Play. The only sanctioned exception is titles built around peripherals that can't be virtualized onto a touchscreen or a standard pad — PlayStation Move wands, the old PlayStation Camera, that class of hardware. In practice this means you don't have to consult a compatibility list before you start. If it runs on the console, it streams. That is a genuinely rare thing in this hobby, where compatibility usually means a spreadsheet and three footnotes. Remote Play is the opposite: universal by mandate, and boring in the best possible way.

Prerequisites & Requirements

The hardware you actually need

You need two things: a source console and a client. The source is a PS5, PS5 Pro, PS4, or PS4 Pro. The client is whatever you're going to hold — an Android or iOS phone or tablet running the PS Remote Play app, a Windows PC, a Mac, a dedicated PlayStation Portal, or, if you're willing to leave the official path, a Steam Deck or Linux box running Chiaki-ng. For input you want a DualSense, a DualSense Edge, or a DualShock 4. The Portal has its controls built into the chassis, split around an 8-inch 1080p LCD running at 60 Hz; that panel is why 60 fps is the hard ceiling on a Portal no matter what your console is rendering.

One cable matters more than any of that: an Ethernet cable for the console. We will keep coming back to this, because it is the difference between Remote Play that feels like local play and Remote Play that feels like a bad dream about local play.

Software versions, pinned down

Everything should be current. The console wants the latest system software — not optional, since the 2026 image-quality work depends on it. The official app, published on Google Play as com.playstation.remoteplay by PlayStation Mobile Inc., updates itself; take the update. The desktop client runs on current Windows 10/11 and recent macOS, and you can grab it from Sony's PC and Mac support page. The PlayStation Portal specifically needs system software 7.0 or later — the update that rolled out globally in March 2026 — to expose 1080p High Quality mode. Chiaki-ng you pull fresh from its GitHub releases.

Component	Minimum	Recommended (2026)
Source console	PS4 / PS4 Pro	PS5 / PS5 Pro, latest firmware
Client	Phone or PC, current OS	PS Portal (SS 7.0+) or Steam Deck + Chiaki-ng
Controller	DualShock 4	DualSense / DualSense Edge
Bandwidth	5 Mbps	15–30 Mbps, low jitter
Console link	Wi-Fi (tolerated)	Wired Ethernet (non-negotiable)

Bandwidth: the floor versus what you actually want

Sony's official Remote Play page lists broadband of at least 5 Mbps as the requirement and 15 Mbps as the recommendation for Wi-Fi or mobile data. Believe the second number and ignore the first. 5 Mbps will connect and then punish you with a soft, smeary 720p that collapses the instant anything on screen moves. For 1080p at 60 fps you want 15 Mbps as a genuine floor and 25–30 Mbps of headroom if you're pushing the Portal's High Quality mode or Chiaki at 30 Mbps.

Note the direction of travel, because most guides skip it. When you play inside your house, LAN bandwidth is effectively free and the internet doesn't enter the picture at all. When you play from a hotel or a friend's couch, the number that matters is your home's upload speed — that is what your console has to push out to reach you. Plenty of connections are 300 down and 20 up; that 20 is your Remote Play ceiling away from home, not the 300.

Network Setup: The Foundation Nobody Wants to Hear About

Ethernet on the console is non-negotiable

Sony's own guidance for getting the best Remote Play performance is blunt: hardwire the console directly to the router or modem via Ethernet. This is not audiophile-grade superstition. Remote Play is exquisitely sensitive to jitter — the variance in packet arrival times — far more than to raw throughput. A Wi-Fi console shares airtime with every other device in the house and reacts to every microwave, wall, and neighbouring access point by introducing tiny delays. Each of those delays is a dropped or late frame. Wire the console and the single largest source of jitter disappears.

The correct topology is asymmetric on purpose: console on Ethernet, client on Wi-Fi. The console is stationary, so it has no excuse to be wireless. The handheld is mobile, so it gets the 5 GHz band. Before you touch any PlayStation menu, confirm the console's wired link is healthy by pinging your router from any machine on the LAN:

$ ping -c 5 192.168.1.1     # your router's LAN address
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.92 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.03 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.88 ms
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss
rtt min/avg/max/mdev = 0.88/0.95/1.03/0.06 ms

Sub-millisecond, zero loss, and — critically — a tiny mdev (mean deviation). That last figure is your jitter proxy. If mdev is jumping into the tens of milliseconds on a wired link, something is wrong with the cable or switch before Remote Play ever enters the conversation.

Do the bandwidth math before you blame Sony

Run an actual speed test rather than trusting the sticker on your ISP's plan. Command-line or app, doesn't matter, but read both directions:

$ speedtest-cli --simple
Ping:      11.4 ms
Download:  218.55 Mbit/s
Upload:    23.71 Mbit/s      # the number that matters when you leave the house

Inside the house, 218 down is irrelevant and the LAN carries the stream. Away from home, that 23.71 Mbps upload is your entire budget, and Remote Play at 1080p wants a real chunk of it. If your upload is 5–10 Mbps, plan on 720p when travelling and make peace with it. The technology cannot invent bandwidth that your ISP declined to sell you.

Ports, NAT, and the UPnP question

On a normal home network with UPnP enabled, you never think about ports — the console asks the router to open what it needs and the router obliges. The trouble starts with double NAT (an ISP gateway and your own router both handing out addresses) or carrier-grade NAT, where your "public" address is shared and inbound connections have nowhere to land. If away-from-home Remote Play refuses to connect while home works fine, NAT is the prime suspect. Where you must configure things by hand, these are the ports Remote Play commonly needs:

# PS Remote Play — ports to allow if UPnP is disabled
# (UPnP normally opens these for you; verify against Sony/Chiaki docs)
UDP  9296        # session / control
UDP  9297        # audio + video streaming
UDP  9303        # discovery
TCP  9295        # registration / handshake
# General PSN reachability
TCP  80, 443
UDP  3478, 3479, 3480

The clean fix for double NAT is to put the ISP box into bridge mode so your router owns the single public address. Failing that, a manual port forward or a DMZ pointed at the console's reserved IP does the job. Carrier-grade NAT is nastier — no port forward can help when you don't have a real public address — and the honest answer there is a VPN back into your home network, which we return to in the advanced section.

The 12-Step Setup Walkthrough

Before you begin: the target state

Every setting below exists to serve one of two goals — let the console be reached, and let it wake up when it's asleep. Here is the finished configuration you are aiming for; screenshot it and work backwards if you prefer:

Settings > System > Remote Play
  Enable Remote Play ............... On
Settings > Users and Accounts > Other > Console Sharing and Offline Play
  This PS5 ......................... Activated (primary)
Settings > System > Power Saving > Features Available in Rest Mode
  Stay Connected to the Internet ... On
  Enable Turning On PS5 from Network On

The twelve steps, each with a reason

1. Update the console system software. The 1080p image-quality work and a pile of connection fixes live in current firmware. An out-of-date console will connect and then look worse than it should for no reason you can see.
2. Enable Remote Play on the console. Go to Settings > System > Remote Play and switch Enable Remote Play to On. It is off by default; without this the console is invisible to every client, full stop.
3. Activate the console as primary. Under Settings > Users and Accounts > Other > Console Sharing and Offline Play, activate this console. This authorises it to authenticate your account and to be woken remotely; skip it and away-from-home sessions throw login errors.
4. Turn on the Rest Mode network features. In Settings > System > Power Saving > Features Available in Rest Mode, enable both Stay Connected to the Internet and Enable Turning On PS5 from Network. Without these two, a sleeping console cannot be woken by the app and Remote Play only works while someone is physically home to turn it on — which defeats the purpose.
5. Hardwire the console via Ethernet. Plug it straight into the router. As covered above, this kills jitter at the source and is the single highest-impact thing you will do all day.
6. Sign in on the console with the account you'll use everywhere. Remote Play authenticates by PSN account, and the client must sign in with the same account. A mismatch is the most common self-inflicted "why won't it connect" wound.
7. Install the client. The official PS Remote Play app on your phone, PC, or Mac; or Chiaki-ng on a Steam Deck or Linux box. Get it from the official source, not a random mirror — this app touches your PSN credentials.
8. Pair the client to the console. In the official app, sign in with your account; if prompted, get a pairing number from Settings > System > Remote Play > Pair Device on the console and enter it. This is the one-time handshake that ties the two devices together.
9. Do the first test on the same LAN. Before you go anywhere, connect while the client is on your home Wi-Fi. This isolates variables: if it fails locally, the problem is configuration, not the internet, and you've just saved yourself an hour of blaming your mobile carrier.
10. Set video quality to match your link. Pick a resolution and frame rate the connection can sustain — 720p or 1080p, 60 fps if you can hold it. On a Portal, set 1080p High Quality (next section). Starting conservative and climbing beats starting greedy and stuttering.
11. Test input and tune. Play something twitchy for two minutes. If you see block artifacts on motion or periodic freezes, drop the bitrate or resolution a notch. Remote Play would rather be a clean 720p than a broken 1080p, and so would you.
12. Go remote and verify wake-from-rest. Put the console into Rest Mode, leave your Wi-Fi for cellular or another network, and connect. If the console wakes and the session opens, you are done. If it wakes on LAN but not remotely, the fault is NAT or ports, not the console.

Expected result

A healthy first connection looks like this: the client lists your console by name within a second or two of opening, you tap it, a short black screen with a "connecting" spinner appears, and then the console's home screen fades in at your chosen resolution with audio in sync. Input should feel immediate on a wired-console LAN and merely good over the internet. If the picture is sharp on menus but softens the moment a game starts moving, that is the encoder trading detail for motion under a bitrate cap — expected behaviour, and your cue to check bandwidth rather than panic.

The PlayStation Portal & 1080p High Quality Mode (2026)

What the March 2026 update actually changed

Here is a correction worth making loudly, because the wrong date is all over the place: the Portal's big Remote Play upgrade shipped in March 2026, not 2025. Sony's own PlayStation Blog post is dated March 17, 2026 (rollout began that day PDT, March 18 in Europe and Japan), and it introduces system software 7.0. If a guide tells you this happened in 2025, it is copying a typo.

The headline is 1080p High Quality mode, which Sony describes as letting players "enjoy games at a higher bitrate compared to the default 1080p Standard mode," for what it calls "a smooth and high-fidelity experience." In plain terms: same resolution, fatter pipe, fewer compression artifacts on motion. The update also folded in QR-code account sign-in and a batch of Cloud Streaming niceties — on-screen game-invite notifications, richer trophy pop-ups with platinum animations, and a faster search interface. Those last items are Cloud Streaming polish; the 1080p bitrate bump is the part that matters for Remote Play.

How to turn on 1080p High Quality

It is not on by default and it is not buried, but it is easy to miss. During an active Remote Play or Cloud Streaming session on the Portal:

# On the PlayStation Portal, mid-session:
Hold the PS button > Quick Menu
  Max Resolution > 1080p High Quality
# Restart the Remote Play / Cloud Streaming session to apply the new bitrate.

The setting applies to both Remote Play and Cloud Streaming, and it genuinely wants that session restart — the higher bitrate negotiates at connection time. If your home network can't sustain it you'll see the stream drop resolution to protect the framerate, which is the correct trade and a sign to stay on Standard rather than force the issue.

About that "2 ms" figure and the PS5 Pro talk

Two claims circulating about the 2026 Portal deserve a technical reality check, because The Machine does not print marketing numbers uncorrected. First, the "2 millisecond latency" figure: nothing in Sony's update notes mentions it, and it is not physically plausible as glass-to-glass latency. Encoding a single 60 fps frame, moving it across even a perfect LAN, and decoding it cannot happen in 2 ms — one frame is already ~16.7 ms of unavoidable cadence. Two milliseconds is, at best, a LAN round-trip ping, not the delay you feel between thumb and pixel. Realistic Remote Play glass-to-glass latency on a wired console and 5 GHz client is in the tens of milliseconds. The honest, defensible claim is the one the reviews actually make: local Remote Play beats Cloud Streaming on responsiveness because it skips the trip to a data center. That's true. "2 ms" is not.

Second, PS5 Pro enhancements. If your source console is a PS5 Pro, then yes — the Pro's ray tracing and its PSSR upscaling (PlayStation Spectral Super Resolution; there is no product called "PSSR2") run on the console and their output is what gets streamed. But understand the mechanism: the Pro renders and upscales, then Remote Play re-encodes that finished frame and compresses it for the wire. You are watching a compressed video of the Pro's output on an 8-inch 1080p60 panel, not native PSSR reconstruction on the handheld. It looks good. It is not magic, and the panel still caps you at 1080p and 60 Hz. For thoughts on where this all goes next, our rundown of the PS6 release timeline has the roadmap.

The Open-Source Route: Chiaki-ng on Steam Deck & Linux

Why bother with a third-party client

Sony never shipped an official Remote Play app for Linux or the Steam Deck, which is exactly the gap the open-source world exists to fill. The original client, Chiaki by Florian Märkl, reverse-engineered the Remote Play protocol years ago; the actively maintained fork today is chiaki-ng (formerly chiaki4deck) by streetpea. On a Steam Deck it turns Remote Play into a first-class experience with proper controller mapping, and — the real draw — it hands you manual control over resolution, framerate, codec, and bitrate that the official app hides. If you already run a Deck, our Switch 2 versus Steam Deck breakdown covers why it's the more open handheld; Remote Play via chiaki-ng is a large part of that argument.

Installation on the Deck is a Desktop Mode job. Install from Flathub through the Discover store, or pull the latest AppImage straight from the releases page:

# Steam Deck (Desktop Mode): install from Flathub via Discover,
# or grab the latest AppImage from the releases page:
#   https://github.com/streetpea/chiaki-ng/releases

chmod +x chiaki-ng-Linux-*.AppImage
./chiaki-ng-Linux-*.AppImage

Registration: the AccountID and PIN dance

This is where people get stuck, so read carefully. Chiaki does not register with your public Online-ID (the name your friends see). It needs your PSN Account-ID — a non-public numeric identifier, usually handled as a Base64 string. Modern chiaki-ng has a PSN Login button that fetches it for you via OAuth; if that fails, community tools can convert an Online-ID to the Base64 Account-ID. Then you need a one-time PIN from the console:

# 1. In chiaki-ng, click "PSN Login" to fetch your Account-ID (Base64),
#    or look it up from your Online-ID with a PSN Account-ID tool.
# 2. On the console, get a one-time registration PIN:
#      PS5: Settings > System > Remote Play > Link Device
#      PS4: Settings > Remote Play Connection Settings > Add Device
# 3. In chiaki-ng: Add Console, then enter:
Console IP / Host : 192.168.1.42
PSN Account-ID    : 0000000000000000==   (Base64, NOT your Online-ID)
Registration PIN  : 12345678             (8 digits, expires quickly)

Note the console menu is Link Device (PS5) or Add Device (PS4), which is a different item from the Pair Device the official app uses. The PIN is short-lived, so generate it and enter it promptly. If registration fails, ninety percent of the time it is because someone typed their Online-ID into the Account-ID field. Don't be the ninety percent.

Recommended settings straight from the docs

The chiaki-ng configuration docs give sane defaults, and they map cleanly onto the same principles as the official app — just exposed as knobs:

# chiaki-ng — recommended settings for a PS5 source
Resolution ......... 1080p        # 720p for a PS4 / PS4 Pro source
FPS ................ 60
Bitrate ............ 30000 Kbps   # ~30 Mbps; drop to 15000 on weak links
Codec .............. H265 (HDR if your PS5 and display support it)
Hardware Decoder ... enabled      # e.g. vaapi on the Steam Deck's GPU
Audio Buffer ....... default
# Console on Ethernet, Steam Deck on 5 GHz Wi-Fi.

The hardware decoder line matters more than it looks: leaving it off makes the Deck's CPU chew through H.265 in software, which spikes power draw, heats the unit, and adds latency. Turn it on. And the 30 Mbps bitrate is a local-network figure — over the internet, back it down to whatever your home upload can sustain, per the speed test you already ran.

Five Pitfalls That Ruin Remote Play

Network pitfalls

Pitfall 1 — Console on Wi-Fi. The classic. Symptom: intermittent stutter and macroblocking every few seconds even though your speed test looks fine. Cause: Wi-Fi jitter on the console. Fix: run Ethernet to the console. This resolves more Remote Play complaints than every other fix combined, and it is the one people most resist because the console is already "connected." Connected is not the same as stable.

Pitfall 2 — Double NAT or CGNAT. Symptom: flawless at home, dead the moment you leave. Cause: two routers stacked, or a carrier-grade NAT that gives you no real public address. Fix: put the ISP gateway in bridge mode so your router holds the single public IP; for CGNAT, skip port forwarding entirely and tunnel home with a VPN (see advanced tips). No amount of in-console tweaking fixes a NAT problem.

Console-state pitfalls

Pitfall 3 — Rest Mode network features disabled. Symptom: works only while you're home to switch the console on manually. Cause: Stay Connected to the Internet and Enable Turning On PS5 from Network are off. Fix: enable both, in Power Saving > Features Available in Rest Mode. A console that can't be woken over the network is a console you can only Remote Play into when you don't need to.

Pitfall 4 — Console not set as primary, or wrong account. Symptom: login or authorisation errors on connect, especially away from home. Cause: the console isn't activated for Console Sharing, or the client is signed into a different PSN account. Fix: activate the console as primary and confirm the client uses the identical account. If your household juggles multiple PSN accounts, note the shared-household nuisance that Portal reviewers flag — switching users is deliberately awkward.

Client pitfalls

Pitfall 5 — Bitrate written a cheque the link can't cash. Symptom: freezes, audio dropouts, or a stream that keeps collapsing to a blurry low resolution. Cause: the target bitrate exceeds sustainable bandwidth, so the encoder thrashes. Fix: lower the bitrate or resolution until it holds steady, then climb back slowly. Pitfall 6 (a freebie) — HDR or codec mismatch. Symptom: washed-out colour or a black screen with working audio. Fix: match the client's HDR setting to the console's, and toggle hardware decoding. When the console itself is misbehaving — corrupt cache, sluggish menus bleeding into the stream — our guide to clearing the PS5 cache without losing data is the right first move before you blame Remote Play at all.

Troubleshooting Table

The lookup table

Symptoms map to a small number of causes. Find yours, apply the fix, and resist the urge to change five things at once — change one, retest, repeat.

Symptom	Likely cause	Fix
Console not found / not listed	Remote Play disabled, or client on a different network	Enable Remote Play; put both on the same LAN for setup; or add the console manually by IP
"Can't connect within the time limit"	Rest Mode wake features off, or NAT blocking inbound	Enable both Rest Mode network options; fix double NAT / UPnP
Stuck at soft, blurry 720p	Insufficient bandwidth or a capped bitrate	Run a speed test; raise bitrate; use Ethernet on console and 5 GHz on client
Stutter every few seconds	Wi-Fi jitter on the console	Hardwire the console via Ethernet
Noticeable input lag	Bitrate too high for the route, or long path	Lower resolution/bitrate; test on LAN to isolate the internet
Black screen with working audio	HDR or codec mismatch, decoder issue	Match HDR settings; toggle hardware decoding
Drops when the phone screen sleeps	Aggressive battery optimisation	Exempt the Remote Play app from battery optimisation
Works at home, fails away	Double NAT / CGNAT / closed ports	Bridge mode, UPnP, or VPN back to the home network
chiaki-ng "Register failed"	Online-ID used instead of Account-ID, or stale PIN	Use the Base64 Account-ID and a fresh 8-digit PIN
Portal has no 1080p HQ option	Firmware older than system software 7.0	Update the Portal to the March 2026 release or later

Expected output: what a healthy session looks like

When everything is right, the numbers are quiet. A wired console pings its router under 1 ms with negligible mdev. A speed test shows upload comfortably above your target bitrate. And a chiaki-ng session log opens without drama:

[I] Connecting to 192.168.1.42
[I] Registered console found, using stored credentials
[I] Session negotiated: 1920x1080 @ 60fps, H265
[I] Video decoder: hardware (vaapi)
[I] Stream established, RTT ~9 ms, 0.0% packet loss

RTT in single digits, zero loss, hardware decode confirmed. That is the whole game. If your log shows software decode or climbing packet loss, you now know exactly which line to chase.

When the console itself is the problem

Occasionally Remote Play is the messenger, not the message. If the console's own interface is sluggish, apps crash, or downloads stall, the stream inherits all of it. Rule the console out with a cache clear and database rebuild before you spend another hour on network settings — it's fifteen minutes and it costs you nothing.

Advanced Tips: Bitrate, DualSense, and Playing From Anywhere

Tuning bitrate and resolution like you mean it

The official app hides most of this; chiaki-ng exposes it, which is the entire reason to run it. The mental model: resolution sets detail, framerate sets smoothness, and bitrate is the budget that pays for both under compression. At 1080p60 the docs' 30 Mbps is a good local ceiling. Over the internet, take your measured upload, subtract 20% for overhead and headroom, and set the bitrate below that. A rock-steady 12 Mbps 1080p stream beats a 25 Mbps stream that spikes and stalls, because Remote Play punishes variance harder than it punishes a lower average. Chase low jitter first, high numbers second.

DualSense features over the wire

Remote Play carries more of the DualSense than people expect. Over a wired or Bluetooth DualSense on a PC or the Portal, haptic feedback and adaptive-trigger resistance largely pass through, along with the gyro for motion aiming. The caveats are physical: Bluetooth adds its own small latency, and the Portal's built-in controls give you the haptics and triggers natively without a pairing dance. If a game leans hard on trigger tension — a bow draw, a trigger pull — you'll feel it, which is more than any cloud service reliably delivers.

Playing from hotels, cellular, and behind CGNAT

Away-from-home Remote Play is where the law-and-lore knowledge earns its keep. Cellular works — 15 Mbps of clean LTE will run 720p and often 1080p — but mobile jitter is unpredictable, so keep a lower bitrate profile saved for the road. Hotel Wi-Fi is a minefield: captive portals, client isolation that blocks device-to-device traffic, and blocked UDP ports all break Remote Play in ways no console setting can fix. The universal solvent for hotel networks and CGNAT alike is a VPN or mesh tunnel (Tailscale, WireGuard, or similar) that puts your client back inside your home network — at which point Remote Play thinks you're on the couch and behaves accordingly. And when you specifically need zero-latency local play or clean recordings rather than remote streaming, the right tool isn't Remote Play at all; it's a capture card, and our PS5 capture-card walkthrough covers that path end to end.

The Complete Working Configuration

Console-side settings (copy this)

Every value below is one of the two goals from the walkthrough — reachable, and wakeable. This is the canonical PS5 layout; the PS4 menus are near-identical with slightly different wording.

########## CONSOLE (PS5) ##########
System > Remote Play ................. Enable Remote Play: On
Users and Accounts > Other >
  Console Sharing and Offline Play ... Activated (primary)
System > Power Saving >
  Features Available in Rest Mode:
    Stay Connected to the Internet ... On
    Enable Turning On PS5 from Network On
Network ............................... Wired (Ethernet) to router
Screen and Video > HDR ................ On (only if the client supports it)

Client-side settings (official app, Portal, and Chiaki-ng)

########## OFFICIAL APP (PC / Mac / Mobile) ##########
Sign-in account ....... same PSN account as the console
Resolution ............ 1080p, or 720p on weak links
Frame Rate ............ High (60 fps)
Video Quality ......... lower this FIRST if you see artifacts

########## PORTAL (system software 7.0+, March 2026) ##########
Quick Menu > Max Resolution > 1080p High Quality
(restart the session to apply)

########## CHIAKI-NG (Steam Deck / Linux) ##########
Resolution 1080p / FPS 60 / Bitrate 30000 Kbps (local)
Codec H265 (HDR optional) / Hardware Decoder enabled

Router and network checklist

########## ROUTER / NETWORK ##########
Console connection .... Ethernet, not Wi-Fi
UPnP .................. Enabled (or forward UDP 9296/9297/9303, TCP 9295)
Double NAT ............ Eliminated (ISP box in bridge mode)
CGNAT ................. Tunnel home via VPN / mesh if present
QoS ................... Prioritise the console's MAC/IP if available
Client band ........... 5 GHz Wi-Fi (or Ethernet on a PC client)

Set it up once, the right way, and Remote Play stops being a party trick and becomes infrastructure — the PS5 in the cupboard, the game on whatever screen is nearest. If you want the same result stripped to the bare motions, our condensed 12-step quickstart is the version to bookmark. Everything else here is the reason each of those steps exists — and the reason your neighbour's setup stutters while yours doesn't.