The short version
- 01Test the console’s own connection and read the upload figure, not just download.
- 02Confirm Remote Play is enabled and the console stays online in rest mode.
- 03Check both console and device use the same PlayStation Network account.
- 04Pause other downloads and prefer 5 GHz Wi-Fi, or wire the device where you can.
- 05Check the NAT type in Remote Play settings before blaming your console.
- 06Try a second game, since some are never supported over Remote Play.
Start here
Check the upload speed, not just the download
Remote Play sends video from your console, so the console's side of the connection needs upload headroom that a normal speed test rarely makes you think about. Sony's minimum is 5 Mbps for both upload and download, with at least 15 Mbps recommended for both. Before anything else, confirm the console is signed in to the same PlayStation Network account as the device, that Remote Play is enabled on the console, and that the console is left connected to the internet while turned on or in rest mode.
Applies to: PS5 and PS4 consoles used with the PS Remote Play app on a phone, tablet, PC or Mac. PS4 owners have an extra requirement covered in section 1. PS Portal has its own troubleshooting path that Sony documents separately.
Where does it fail?
Remote Play has an unusually long chain — console, home network, internet, your device's network, the app — and it can break anywhere along it. The useful thing is that the failures are distinguishable: signing in fails differently from connecting, which fails differently from a session that starts and then stutters. Working out which of those you have narrows the list from twenty possibilities to about four.
It cannot find or connect to the console
Is Remote Play enabled and the account the same?
Check the basicsIt connects then stutters or drops
Is there enough upload speed?
Test both directionsIt fails only away from home
Is the network blocking it?
Check NAT and portsThe controller does not work properly
Is the controller supported on that device?
Check the controller1. The four things that must be true first
Sony's setup requirements are short and worth confirming rather than assuming. The console must be running the latest system software. Remote Play must be enabled on the console. You must be signed in to the same PlayStation Network account on both the console and the Remote Play device. And the console must be left connected to the internet while turned on or in rest mode.
That last one accounts for a large share of failures away from home. A console that is fully powered down cannot be reached, and rest mode only helps if the console's rest mode settings keep it connected to the internet. If Remote Play works while you are in the house and fails from elsewhere, this is the first thing to check.
PS4 owners have an additional requirement: the console must be activated as your primary console. That is not needed on PS5, so advice written for one does not transfer cleanly to the other.
The matching-account rule catches households with several profiles. Signing in to the app with a different account from the one on the console produces a failure that looks like a network problem and is not.
If it works at home and not away, look at rest mode and the console's internet connection before blaming your mobile connection.
2. Speed, and why upload is the number that matters
Sony's figures are specific: the minimum required connection speed for Remote Play is 5 Mbps for both upload and download, and for best performance a high-speed connection with upload and download speeds of at least 15 Mbps is recommended.
Both directions matters, and upload is the one people never check. Your console is sending video, so its connection uploads continuously — and home broadband is routinely asymmetric, with generous download and modest upload. A connection advertised at 200 Mbps may offer 10 Mbps up, which is above Sony's minimum and below its recommendation.
Test the console rather than a laptop. On PS5 the path is Settings, then Network, then Connection Status, then Test Internet Connection; on PS4 it is Settings, then Network, then Test Internet Connection. That measures the connection the console actually has, which is not necessarily the one your phone gets in the same house.
Sony also notes that other devices on your network might be using a large amount of bandwidth, and suggests waiting until they are idle. A household download or a 4K stream in another room will take the headroom Remote Play needs, and the symptom is stuttering rather than a failure to connect.
Minimum
5 Mbps up and down. Enough to connect; not enough to be pleasant.
Recommended
15 Mbps or more, in both directions, for the experience Sony designed.
3. Networks that block it, and the NAT problem
Away from home, the network you are on is as important as your console's. Sony notes that Remote Play uses UDP port 8572 and suggests considering opening that port — which is straightforward on your own router and impossible on someone else's.
NAT type is the related constraint. Sony's guidance is to check the NAT type in Remote Play settings and notes that NAT Type 3 networks may prevent Remote Play from working at all. That is common on hotel, workplace and public networks, and it is not something you can fix from the client side.
For a wired connection, Sony's steps are to restart the device, disconnect and reconnect the LAN cable, run a network speed test and reduce bandwidth use from other devices. For wireless, restart the device, confirm Wi-Fi works with other devices, run a speed test, pause downloads, disconnect other Wi-Fi devices, connect using 5 GHz Wi-Fi, and use a wired connection on PC or Mac where possible.
The 5 GHz recommendation is worth acting on. Remote Play is sustained video, which is exactly the workload that suffers on a congested 2.4 GHz band.
4. The app, and what to do in what order
Sony separates sign-in failures from connection failures, which is a useful distinction. For sign-in trouble the steps are to check the PlayStation status page for service alerts, verify the device's internet connection, restart the Remote Play app, restart the device, and reinstall the app if necessary. Checking the status page first is sensible — a platform-wide outage is not something you can troubleshoot.
For failures once signed in, the sequence is to confirm the accounts match, verify the console's Remote Play setup, test connectivity on both console and device, disable antivirus software that may be blocking it, sign out and back in, restart or reinstall the app, deactivate and reactivate the console, and — on PC and Mac only — pair the console manually.
Antivirus and firewall interference is a real cause on PC and Mac rather than a formality. Sony's advice is to check whether security software is blocking the app and, if so, to disable the relevant firewall settings or add Remote Play to the exceptions.
Sony documents two platform-specific fixes worth knowing. If the app crashes on PC: restart the PC, delete the AppData folder and reinstall Visual C++. If you get a blank screen on PC: restart, reinstall the app, and install the latest graphics drivers.
5. Controllers, and what Remote Play cannot do
If the session works but the controller does not, Sony's steps are to verify the device is compatible with the controller type, reset the device, reset the controller, and update the DualSense controller firmware where applicable. Compatibility is the first of those for a reason — support for particular controllers varies by platform and OS version.
Sony also states plainly that when you use a wireless controller with Remote Play, some of the controller's features may be restricted. That is a documented limitation rather than a fault, and it explains missing haptics or adaptive trigger behaviour that no amount of troubleshooting will restore.
There is a broader set of limitations worth knowing before you spend an evening on this. Sony lists things Remote Play cannot run alongside: Share Play, PlayStation Plus Premium streaming, game broadcasting on PS4, Blu-ray and DVD playback, PS VR2 or PS VR mode, music playback and video services.
And some games simply do not support it. Sony names games requiring PlayStation VR2, PlayStation VR or the PlayStation Camera as incompatible, and notes that certain images may not display during Remote Play. If one game fails while others work, that is the likely explanation.
A single game failing while everything else works is usually a compatibility limit, not a connection problem. Test a second game before troubleshooting the network.
6. Narrowing it down before contacting PlayStation
Three comparisons place almost every version of this. Does it work on your home network but not elsewhere? That points at the remote network's NAT type or blocked ports rather than your console. Does it fail for one game only? That is a compatibility limit. Does it connect and then degrade? That is bandwidth, not configuration.
Test on a second network before concluding anything — a phone's mobile hotspot is the quickest way to rule the original network in or out, and it takes two minutes.
When you contact support, give the console's own speed test results in both directions rather than a phone's, say whether the console is set to stay connected in rest mode, name the NAT type from Remote Play settings, say whether it fails at sign-in or after connecting, and note whether it is every game or one. Those five answers separate an upload problem from a rest mode setting from a blocked network from a game that was never supported.
Frequently asked questions
What internet speed does PS Remote Play need?
Sony's minimum is 5 Mbps for both upload and download, with at least 15 Mbps in both directions recommended. Upload is the number people never check — your console is sending video, and home broadband is routinely generous on download and modest on upload.
Why does Remote Play work at home but not away?
Usually the console isn't reachable or the remote network blocks it. Sony requires the console to stay connected to the internet while on or in rest mode. Away from home, NAT Type 3 networks may prevent Remote Play entirely, and it uses UDP port 8572 — neither of which you can change on someone else's network.
Do I need the same account on both devices?
Yes. Sony requires you to sign in to the same PlayStation Network account on the console and the Remote Play device. In a household with several profiles this is easy to get wrong, and the failure looks like a network problem rather than an account one.
Why does one game refuse to work over Remote Play?
Some games aren't supported — Sony names those requiring PlayStation VR2, PlayStation VR or the PlayStation Camera. Remote Play also can't run alongside Share Play, PS Plus Premium streaming, Blu-ray or DVD playback, or music and video services. Test a second game before troubleshooting anything.
Could my antivirus be blocking Remote Play?
On PC and Mac, yes, and Sony lists it as a step: check whether security software is blocking the app, then disable the relevant firewall settings or add Remote Play to the exceptions. Sony also documents deleting the AppData folder and reinstalling Visual C++ for PC crashes.
Why is my controller behaving oddly over Remote Play?
Partly by design. Sony states that when using a wireless controller with Remote Play, some of the controller's features may be restricted — so missing haptics or adaptive triggers can be a documented limitation. Otherwise, check device compatibility, reset both, and update DualSense firmware.
Sources and review notes
Checked on . Compiled by Glitchary from PlayStation's Remote Play connection troubleshooting documentation, which covers PS4 and PS5. Speed figures, port and NAT guidance and platform-specific fixes are Sony's and can change. The explanation of why upload speed matters more than download, and the hotspot test, are editorial. PS Portal has separate troubleshooting that Sony documents on its own page. Glitchary is independent of Sony Interactive Entertainment.