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

Remote Play is the most quietly competent thing Sony makes, which is precisely why nobody at Sony seems willing to advertise it honestly. It is not cloud gaming. It does not require a subscription. It does not stream from a data center in Oregon. It streams from the PlayStation sitting in your living room, encoded in dedicated silicon, across your own network, to whatever screen you happen to be holding. In 2026 that screen is increasingly the PlayStation Portal, the $200 slab Sony shipped in 2023 to a chorus of why does this exist, and then spent three years quietly making correct.

This is a tutorial, not a press release. By the end you will have a PS5 — or a PS5 Pro, or a decade-old PS4 — pushing a 1080p, 60 Hz, high-bitrate stream to a client at roughly 2 milliseconds of local-network latency, which is the single number that makes the whole enterprise worth doing. We will get there in twelve steps and about thirty minutes, assuming your network is not actively hostile. We will also tell you the things the setup wizard will not: that the host console must live on Ethernet and that this is not a suggestion, that the Portal still cannot pair a Bluetooth headset in 2026, and that the open-source client is, for a meaningful slice of people, the better client. The Machine does not editorialize about your taste in games. It does editorialize about your network topology.

Why Remote Play Beats Cloud in 2026

Before you touch a single menu, understand what you are actually building, because half of the bad advice on the internet comes from people who conflate two completely different products. Remote Play and PlayStation Plus Cloud Streaming are not the same thing, do not run on the same infrastructure, and do not fail in the same ways.

Remote Play is not cloud gaming, and never was

The single most important sentence in this article: Remote Play streams from your console, not Sony's server farm. According to Wikipedia's Remote Play entry, the feature is effectively mandatory — Sony's certification requirements oblige every PS4 and PS5 game to support Remote Play, with the lone exception of titles built around hardware the client cannot replicate, such as PlayStation Move or the old motion-wand nonsense. Support for PS5 games was folded into the app in November 2020, weeks before the console launched. That mandate is the lore worth knowing: it means your library is, almost in its entirety, streamable by design.

Contrast that with PlayStation Plus Cloud Streaming, which runs from Sony's data centers and, as of 2026, remains limited to PS5 titles only. Remote Play, by comparison, hands you the entire PS4 back catalog and the PS5 Pro-enhanced versions of current games — a distinction reviewers in 2026 explicitly flagged as the Portal's advantage over the cloud catalog. You own the hardware doing the work, so you own the whole library it can run.

The 2 millisecond argument

Latency is the entire game, and it is where Remote Play embarrasses the cloud. In 2026 latency tests on a local home network, the PlayStation Portal logged a consistent 2 milliseconds of latency during Remote Play — against 25 milliseconds previously recorded for cloud streaming. That is not a rounding error; it is the difference between a parry that lands and a parry that gets you killed. The reason is physics: a cloud session adds the round trip to a distant server on top of every encode and decode. A Remote Play session on your LAN adds only the trip from the console to the router to the client, which on a wired host is a couple of hops measured in single-digit milliseconds.

The pipeline matters here. The console captures a frame, hardware-encodes it to HEVC, fires it as UDP across your network, and the client hardware-decodes and paints it. Every link in that chain is tuned for throughput at a fixed cadence. Introduce jitter — variable delay between packets — and the decoder either stalls or drops frames, which you perceive as stutter regardless of how fat your bandwidth number looks. Low and stable beats high and erratic every time.

What the Portal 7.0 update actually changed

For two years the Portal was a competent 1080p Standard streamer and nothing more. That changed on March 17, 2026 (PDT) — March 18 in CET and JST — when Sony pushed a global system software update bringing the Portal to version 7.0 and, with it, a new 1080p High Quality mode that lets you select a higher bitrate than the default 1080p Standard. It was, per the rollout notes, designed to deliver higher visual fidelity, smoother interactions, and a more seamless overall experience, and it was the first major visual-fidelity upgrade for Remote Play since the Portal launched in 2023.

The verdict from the field was blunt. In 2026 testing by Thumbsticks' PlayStation Portal review, performance on the Portal's 1080p 60 Hz LCD was described as exceptional, with the High Quality mode meaningfully raising the streaming bitrate for smoother visuals. If you bought a Portal in 2023 and shelved it, the 7.0 update is the reason to dig it back out. If you are buying now, it is the reason the device finally makes sense.

Prerequisites: Hardware, Software, Bandwidth

Skipping prerequisites is how people end up posting it doesn't work threads at 1 a.m. Read this section in full. Every requirement here exists because its absence produces a specific, infuriating failure mode later.

The hardware you actually need

On the host side you need a PS5, a PS5 Pro, a PS4, or a PS4 Pro — any of the four works, and the PS4 line is the reason Remote Play remains relevant a decade on. The marquee 2026 capability belongs to the Pro: per YouTube review testing, the PS5 Pro-enhanced versions of games, including full ray tracing and PSSR2 (PlayStation Spectral Super Resolution 2) upscaling, can be streamed directly to the Portal — provided the console is hardwired. If you want the prettiest possible stream, a hardwired PS5 Pro feeding a 7.0 Portal is the current ceiling.

On the client side you have three real options: the PlayStation Portal on firmware 7.0 or newer; any Android, iOS, Windows, or macOS device running the official app; or a PC running the open-source Chiaki-ng. You also need a router you actually control — meaning you can reach its admin panel — and a single Ethernet cable for the host. That cable is not optional, and we will spend an entire section explaining why. If you are weighing this against a dedicated capture rig for local low latency or recording, our PS5 capture card walkthrough covers the wired alternative in the same level of detail.

Software versions and the 5/15 Mbps line

The host console must be on the latest system software; an out-of-date console is the most boring cause of failed handshakes. The mobile and desktop client is the PS Remote Play app — Google Play ID com.playstation.remoteplay, published by PlayStation Mobile Inc. — and you can pull it from Google Play or the desktop builds on Sony's official Remote Play page. The app's own stated requirement is a broadband connection of at least 5 Mbps, with 15 Mbps recommended for a better experience. Treat 5 as the floor below which you should not bother, and 15 as the realistic target for a clean 1080p session. The Portal specifically needs firmware 7.0 for the 1080p High Quality option; below that, the menu entry simply will not exist.

Account and console-state requirements

Host and client must be signed into the same PSN account. The console must be either powered on or in rest mode — not fully shut down — and, for the cleanest licensing and wake behavior, activated as your primary console. Get those three facts wrong and the symptoms range from cannot find console to a session that connects and immediately drops.

For the record, because someone always asks: the app is maintained by PlayStation Mobile Inc. at 2207 Bridgepointe Pkwy, San Mateo, CA 94404. The listed support routes are the address remoteplay-contact@hq.scei.sony.co.jp, the corporate contact PlayStationMobileInc@sony.com, and a phone line at +1 650-655-5204 — a number you will never need to call, because nobody who answers it can fix a double-NAT, and a double-NAT is what is actually wrong with your setup.

The Network Foundation: Ethernet First

Everything downstream — resolution, bitrate, that 2 ms figure — rests on the network. Build it wrong and no menu setting saves you. Build it right and most of the troubleshooting section becomes irrelevant.

The non-negotiable Ethernet rule

For optimal Remote Play with PS5 Pro games in 2026, there is a rule that reviewers called, verbatim, non-negotiable: the PS5 console must be hardwired directly to the router or modem via Ethernet to minimize latency. The Machine will restate it without the diplomacy — if your host console is on Wi-Fi, you have already lost, and every other tweak in this article is you rearranging furniture in a burning house. Run the cable. Cat5e is plenty; Cat6 if you have it lying around. Straight from console to router. No powerline adapters, no Wi-Fi extenders pretending to be a backhaul.

Why Wi-Fi on the host destroys you

The host is the encoder, and the encoder must deliver frames on a metronome. Wi-Fi is a half-duplex, shared, contended medium: it retransmits lost frames, it backs off when your neighbor's microwave fires, and it introduces jitter that the decoder cannot smooth over. You can have 300 Mbps of Wi-Fi throughput and still stutter, because throughput is not the metric — consistency is. Ethernet gives the encoder a private, full-duplex lane with deterministic timing, which is exactly what a real-time video stream demands. This is also why the cloud-versus-local debate keeps landing in Sony's favor on hardware where the company controls the whole pipeline; if you enjoy that kind of platform accounting, our breakdown of why Sony out-shipped Microsoft this generation is the long version.

Client-side radio: 5 GHz or bust

The host is wired; the client, by definition, usually is not — a Portal or a phone is a handheld. So the client's radio becomes the weak link, and the rule there is equally simple: connect on 5 GHz or 6 GHz, never 2.4 GHz. The 2.4 GHz band is a junkyard of Bluetooth, old smart-home gear, and every other router on your street, and its congestion produces the exact jitter you spent money on Ethernet to avoid. Stand in the same room as the access point during setup, confirm the session is clean, and only then test how far the signal carries. On the Portal specifically there is an extra wrinkle: its controller-to-screen link uses radio too, so a congested 2.4 GHz environment can degrade input and audio independently of the video stream.

The 12 Steps to 1080p High Quality

Here is the procedure, start to finish. Do them in order. Each step states the rationale, because a step you understand is a step you will not skip, and the skipped step is always the one that breaks everything.

1. Update everything first. Put the host on the latest system software (PS5: Settings > System > System Software > System Software Update and Settings), update the PS Remote Play app from the store, and push the Portal to firmware 7.0 or newer. Why: The 1080p High Quality mode does not exist below Portal firmware 7.0, which rolled out globally on March 17, 2026 (PDT). A mismatched stack is the most common reason the option is simply missing from the menu.
2. Hardwire the console to the router. Run a Cat5e-or-better cable from the PS5/PS4 directly to the router or modem. Why: This is the non-negotiable rule. The host is the encoder, and only a wired link gives it the deterministic timing that produces the 2 ms result instead of intermittent stutter.
3. Reserve a fixed LAN IP for the console. In the router's DHCP settings, bind the console's MAC address to a static address — we use 192.168.1.40 throughout this guide. Why: Both port forwarding and Chiaki target an IP. If DHCP reshuffles the address next week, your carefully made forwards will point at a smart bulb.
4. Enable Remote Play on the console. PS5: Settings > System > Remote Play > Enable Remote Play. PS4: Settings > Remote Play Connection Settings > Enable Remote Play. Why: It is a toggle, and it is not always on out of the box. No toggle, no discovery, no session.
5. Configure rest-mode networking. PS5: Settings > System > Power Saving > Features Available in Rest Mode — enable both Stay Connected to the Internet and Enable Turning On PS5 from Network. Why: Without these two, a console in rest mode is unreachable; the client cannot wake it, and you are stuck walking to the living room to press the power button, which defeats the point.
6. Activate this console as primary. PS5: Settings > Users and Accounts > Other > Console Sharing and Offline Play. PS4: Activate as Primary PS4. Why: Primary activation cleans up license checks and wake behavior, eliminating a class of intermittent connect-then-drop failures that are miserable to diagnose after the fact.
7. Link the client device and capture the PIN. On the console: Settings > System > Remote Play > Link Device. Why: The official app pairs through your PSN login, but Chiaki and manual setups need the single-use, 8-digit PIN shown on this screen. Grab it now even if you think you will only use the app.
8. Install the right client. Portal owners proceed to configuration. Everyone else installs PS Remote Play (com.playstation.remoteplay) on a phone or PC, or Chiaki-ng on a desktop or handheld PC. Why: Choosing the client now, before you start fighting settings, keeps you from blaming the network for what is actually a client limitation.
9. Run the pre-flight bandwidth and latency test. From the client's network, measure your uplink and ping the console's reserved IP. Why: 5 Mbps is the floor and 15 Mbps the recommended minimum; confirming you clear that bar before you start saves you from chasing a bandwidth problem through five unrelated menus.
10. Validate on the same LAN before touching the internet. Put client and console on the same local network and start a session. Why: Isolate variables. If it fails on the LAN, the fault is the console or the app — not your ISP, not your port forwarding — and you have just halved your search space.
11. Forward the ports — only if you need internet play. Forward UDP 9295, 9296, 9297, and 9302, plus TCP 9295, to the console's reserved IP. Why: Same-LAN Remote Play needs zero forwarding. Over the internet, the stream's UDP flows need an explicit path through NAT, or the session dies at the handshake.
12. Set the quality ceiling and lock it in. In the app: 1080p, High frame rate. On the Portal: Quick Menu > Max Resolution > 1080p High Quality, then restart the session. Disable Wi-Fi power saving on the client. Why: Selecting High Quality engages the new high-bitrate path, and the Portal must restart the session to renegotiate it. Skip the restart and you stay on the old bitrate while wondering why nothing looks better.

Ports, Routers, and the Config Files

This section is for the people doing internet play or running the desktop and open-source clients. If you only ever stream inside your own house, you can skim it — same-LAN Remote Play needs none of this. If you want to play from the office, read every word.

Pre-flight: measure bandwidth and latency

You cannot tune what you have not measured. Run this from the client's network before you blame anything. The ping result is the figure that should make you smile — sub-2 ms to a wired host is exactly the LAN behavior you are paying for.

# Pre-flight: measure uplink, downlink, and idle latency
# Run from the CLIENT's network (you can't shell into the PS5)
$ speedtest-cli --simple
Ping: 8.214 ms
Download: 187.42 Mbit/s
Upload: 23.07 Mbit/s

# Latency to the console on the LAN (use your PS5's reserved IP)
$ ping -c 5 192.168.1.40
64 bytes from 192.168.1.40: icmp_seq=1 ttl=64 time=1.94 ms
64 bytes from 192.168.1.40: icmp_seq=2 ttl=64 time=2.01 ms
64 bytes from 192.168.1.40: icmp_seq=3 ttl=64 time=1.88 ms
64 bytes from 192.168.1.40: icmp_seq=4 ttl=64 time=1.96 ms
64 bytes from 192.168.1.40: icmp_seq=5 ttl=64 time=1.90 ms
--- 192.168.1.40 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss
rtt min/avg/max/mdev = 1.880/1.938/2.010/0.052 ms

That 23 Mbit/s upload clears the 15 Mbps recommendation with headroom, the packet loss is zero, and the latency holds steady around 2 ms with a tiny mdev — low jitter. That is a green light. If your upload sits near 5 Mbps or your mdev is in the tens of milliseconds, fix the network before touching resolution.

Forwarding UDP 9295–9297 for internet play

For Remote Play over the internet, forward the control, video, and audio flows to the console's fixed address. Discovery rides UDP 9302, the streaming flows use 9296 and 9297, control uses 9295, and registration uses TCP 9295. Build the rules against the reserved IP, never a dynamic one.

# Static port-forward rules (forward to the PS5's reserved LAN IP)
# Required ONLY for Remote Play over the internet. Same-LAN needs nothing.
#
# Name             Proto   WAN port   ->  LAN host        LAN port
remoteplay-disc    UDP     9302       ->  192.168.1.40    9302
remoteplay-ctrl    UDP     9295       ->  192.168.1.40    9295
remoteplay-video   UDP     9296       ->  192.168.1.40    9296
remoteplay-audio   UDP     9297       ->  192.168.1.40    9297
remoteplay-regist  TCP     9295       ->  192.168.1.40    9295

To keep that reservation stable, pin the console by MAC at the DHCP layer. On any router running dnsmasq — which is most of the open-firmware world — the rule is one line:

# dnsmasq: pin the PS5 to a fixed LAN address by MAC, 24h lease
dhcp-host=70:9e:29:aa:bb:cc,192.168.1.40,ps5-host,24h

Firewalls and the desktop app

If you run the desktop app or Chiaki-ng on a Linux box, the host firewall has to let those same UDP flows in. On anything using ufw, four rules and a reload do it. The expected output is unglamorous, which is the point — firewalls that announce a lot are usually misconfigured.

# Open the Remote Play ports on a Linux client running the app or chiaki-ng
$ sudo ufw allow 9295/udp comment 'remote play control'
Rule added
$ sudo ufw allow 9296/udp comment 'remote play video'
Rule added
$ sudo ufw allow 9297/udp comment 'remote play audio'
Rule added
$ sudo ufw allow 9302/udp comment 'remote play discovery'
Rule added
$ sudo ufw reload
Firewall reloaded

Six Pitfalls That Wreck a Session

These are the failure modes The Machine sees over and over. None of them are exotic. All of them are avoidable. Each comes with the fix, stated plainly.

Pitfalls 1 and 2: the host on Wi-Fi, and the cloud mirage

Pitfall 1 — streaming with the host on Wi-Fi. This is the number-one mistake and the root cause of most stutter complaints. The fix is the non-negotiable rule: hardwire the console to the router. There is no software setting that compensates for a wireless host. Pitfall 2 — assuming Remote Play is the same as the cloud. People disable their console to save power, then wonder why Remote Play fails — because Remote Play streams from their console, which is now off. PS Plus Cloud Streaming runs without your console but is limited to PS5 titles only; Remote Play needs your own hardware awake and on the network. The fix is to leave the console in rest mode, never fully powered down, whenever you want to connect remotely.

Pitfalls 3 and 4: dead rest mode, and the Bluetooth purchase

Pitfall 3 — rest-mode networking left disabled. A console asleep with Stay Connected to the Internet off cannot be woken or reached. Symptoms look like a discovery failure but are really a power-setting failure. The fix is Step 5: enable both rest-mode network features. Pitfall 4 — buying Bluetooth headphones for the Portal. As of 2026 the Portal still cannot support Bluetooth audio devices, a hardware limitation reviewers called frustrating for anyone wanting third-party wireless headphones. The fix is to use the 3.5 mm jack or a PlayStation Link accessory, and to not spend money on a Bluetooth headset expecting it to pair. It will not.

Pitfalls 5 and 6: double NAT, and maxing a weak uplink

Pitfall 5 — double NAT or CGNAT on internet play. If your ISP modem is also routing and your own router sits behind it, your port forwards never reach the console and over-internet sessions fail at the handshake. The fix is to put the ISP box in bridge mode, run a single router, and — if you are stuck on carrier-grade NAT — consider Chiaki, which handles some traversal scenarios the app does not. Pitfall 6 — maxing resolution on a thin uplink. Selecting 1080p High Quality on a 5 Mbps connection produces constant downgrades and stutter, not beauty. The fix is honesty: match the resolution ceiling to your measured uplink, and only reach for High Quality once you have confirmed 15 Mbps or better with low jitter.

Troubleshooting Table: Symptom to Fix

When a session misbehaves, work the symptom, not your superstitions. The table below maps the ten failures you will actually encounter to their most likely cause and the fix that resolves them. Start at the top; the entries are roughly ordered from most to least common.

Reading the table without panicking

Notice how many rows resolve to the same two fixes: hardwire the host and update the firmware. That is not a coincidence. The overwhelming majority of Remote Play problems are network problems wearing a costume, and the second-largest category is version mismatch. If you took the prerequisites and network sections seriously, most of this table never applies to you.

When the error code is genuinely the console

The CE- and NW- family of errors point at the console itself rather than the link — usually stale system software or a corrupted Remote Play registration. Update first, then delete the linked device on the console and re-run Step 7 to generate a fresh PIN. Re-pairing from a clean slate clears a startling number of otherwise inexplicable failures, and it costs you thirty seconds.

Advanced Tips: Bitrate, Audio, Chiaki

You have a working 1080p session. This is how you make it better, route around the Portal's one genuine hardware flaw, and graduate to the client the enthusiasts actually run.

Bitrate, 1080p HQ, and headroom

The 1080p High Quality mode is, functionally, a bitrate increase — the same resolution and frame rate as Standard, but more bits spent per second, which is where the smoother, cleaner image comes from. Bits cost bandwidth, so High Quality wants the 15 Mbps recommendation honored with margin to spare. The practical move is to leave a buffer: if your measured uplink is exactly 15 Mbps, expect occasional dips under load; if it is 25 or more, High Quality holds rock-steady. This is also the regime where a hardwired PS5 Pro pays off, because its ray-traced, PSSR2-enhanced output is exactly the kind of detail-dense image that benefits from the extra bitrate rather than wasting it.

The Bluetooth wall and audio workarounds

The Portal's inability to pair Bluetooth audio in 2026 is its most-criticized constraint, and there is no firmware fix coming for a missing radio profile. Your options are the wired 3.5 mm headphone jack — which adds zero latency and is the choice The Machine recommends — or a PlayStation Link accessory, Sony's proprietary low-latency wireless standard built specifically because Bluetooth audio latency would wreck a game stream. If you already own decent wired headphones, you have already solved this. If you were about to buy AirPods for your Portal, redirect that money. They will not connect.

Chiaki-ng: the open-source escape hatch

For PC users, the official app is not the only client, and frequently not the best one. Chiaki-ng is a clean-room, open-source Remote Play client — legal interoperability software, no piracy, no gray area — that runs on Linux, Windows, and macOS, exposes finer control over bitrate and decoders, and turns a handheld gaming PC into a superb Remote Play terminal. Registration needs the 8-digit PIN from Step 7 and your PSN account ID. The command-line flow is the clearest way to show it working:

# Register a PS5 with chiaki-ng. You need:
#   1. PSN Account ID (base64)   2. an 8-digit PIN from the console
#   Console: Settings > System > Remote Play > Link Device  (shows the PIN)
$ chiaki discover -h 192.168.1.40
host '192.168.1.40':
  state:            standby
  host-type:        PS5
  host-name:        CUH-PS5
  system-version:   0x0a000000

$ chiaki register -h 192.168.1.40 \
    --pin 02468013 \
    --psn-account-id kVx4n2base64idHere== \
    --target ps5
[I] Sending registration request
[I] Registration successful
[I] RP-Key / RP-Regist-Key stored in ~/.local/share/Chiaki/Chiaki.conf

Once registered, Chiaki wakes the console from standby and streams with the same UDP flows the official app uses, which is why the firewall rules from earlier apply unchanged. The reason enthusiasts reach for it is control: decoder selection, custom bitrate ceilings, and rock-solid behavior on Linux handhelds where the official app does not run at all.

Portal vs Phone vs PC: Client Showdown

There is no single best client — there is the best client for your hardware and your tolerance for fiddling. Here is the honest comparison.

PlayStation Portal: the appliance

The Portal is the no-thought option, and in 2026 that is a compliment. It is a single-purpose 1080p 60 Hz appliance with real DualSense controls baked in, and with firmware 7.0 its image quality went from acceptable to, per Thumbsticks, exceptional. It streams the full PS4 library and PS5 Pro-enhanced games, a catalog the cloud service cannot match. Its flaws are exactly two: no Bluetooth audio, and total dependence on a console you keep awake. If you want to pick it up and play without configuring anything, this is your device. The Machine notes, dryly, that the appliance Sony was mocked for in 2023 is the one that aged best.

The PS Remote Play app on phone and PC

The app is the most flexible client because it runs on hardware you already own. In 2026 it also closed a convenience gap: you can launch a game directly from the PlayStation App on a phone, pressing a single button to start a session without ever turning on a TV. Paired with a clip-on controller, a modern phone is a credible Remote Play screen, and the desktop builds turn any laptop into one. The trade-off is touch controls unless you bring your own gamepad, and a slightly less tuned experience than the purpose-built Portal. It is the right pick when you want Remote Play without buying another device.

Chiaki-ng on a handheld PC

Run Chiaki-ng on a Windows or Linux handheld and you get the most configurable Remote Play experience available, plus a device that also plays its own native library. This is the play for people who already own a ROG Ally or a Steam Deck and would rather not buy a Portal — and if you are choosing between those two handhelds in the first place, our ROG Ally X versus Steam Deck OLED comparison lays out the 50-fps, $150 gap that decides it. For the broader handheld landscape, including how Valve's machine stacks up against Nintendo's, the Switch 2 versus Steam Deck breakdown is the companion read. The cost of all this flexibility is setup effort; Chiaki rewards people who enjoy the config files in this article and frustrates people who wanted an appliance.

The Complete Working Configuration

Here is the entire known-good profile in one place — console, network, and clients — the configuration The Machine would hand to a friend who said just tell me what to set. It is the consolidation of every step and rule above. Copy it, adapt the IP and MAC to your network, and you have a reproducible 1080p High Quality setup.

Console-side master config

Everything on the console exists to make it reachable, wakeable, and properly licensed. These are the settings that, once correct, you never touch again.

Network and router config

The network half is where the latency is won or lost. The wired host, the reserved IP, the absence of double NAT, and the client's choice of radio band are the four levers that matter; the rest is noise.

The full known-good profile

This is the complete configuration as a single reference block. If a future session misbehaves, diff your live setup against this and the discrepancy is almost always your answer.

######################################################################
# STARESBACK.GG -- Known-good PS Remote Play 1080p HQ configuration
# Target: PS5 Pro (hardwired) -> PlayStation Portal fw 7.0, June 2026
######################################################################

[ console : ps5 ]
  system_software     = latest      # System > System Software > Update
  remote_play         = enabled     # System > Remote Play
  rest_mode_internet  = on          # Stay Connected to the Internet
  wake_from_network   = on          # Enable Turning On PS5 from Network
  power_save_idle     = never       # do not enter rest mode mid-session
  primary_console     = activated   # Console Sharing and Offline Play
  link_device_pin     = single-use, 8-digit, from Link Device

[ network : host ]
  uplink              = Ethernet, cat5e+, straight to router/modem
  lan_ip              = 192.168.1.40   # DHCP-reserved by MAC
  double_nat          = none           # ISP box in bridge mode
  forward_udp         = 9295, 9296, 9297, 9302   # internet play only
  forward_tcp         = 9295                      # internet play only

[ network : client ]
  radio               = 5 GHz / 6 GHz only, never 2.4 GHz
  wifi_power_save     = disabled
  measured_uplink     = >= 15 Mbps   # 5 Mbps hard floor
  lan_latency_target  = ~2 ms

[ client : portal ]
  firmware            = 7.0 or newer
  max_resolution      = 1080p High Quality   # Quick Menu > Max Resolution
  apply               = restart the session after selecting
  audio               = wired 3.5mm or PlayStation Link  # NO Bluetooth

[ client : app ]
  app_id              = com.playstation.remoteplay   # PlayStation Mobile Inc.
  resolution          = 1080p
  frame_rate          = High
  min_bandwidth       = 5 Mbps (15 Mbps recommended)
######################################################################

That is the whole machine. A hardwired host on the latest software, a reserved IP, a client on a clean 5 GHz radio, the Portal on firmware 7.0 with High Quality selected and the session restarted — and you are streaming your own console at roughly 2 ms, with a library the cloud cannot touch. Remote Play was always the quietly correct answer; 2026 just gave it the bitrate to prove it. Where Sony takes the idea next is its own question — our look at the PlayStation 6 release window is the place to speculate about that. For now, run the cable, set the config, and stop streaming from Wi-Fi.