Evidence checked: 8 October 2026
PS5 Remote Play with mouse and keyboard: what works?
Sony’s Windows PS Remote Play app streams your own PS5 and documents a connected PlayStation controller for gameplay. Your PC mouse can operate its control panel; this is not documentation of mouse aiming or WASD movement in a game. A translator is a separate input component whose output must work with the chosen client. ConsoleMouse is in development; this guide does not establish its compatibility. [MG-S02, LOCAL-FACTS]
Updated:
Choose the input connection first
If you want native mouse controls, connect compatible peripherals to the console and check the actual game’s actions. If you only want to play on a computer screen, Sony’s controller-based Remote Play may be enough. If you want physical mouse and keyboard controls through controller translation, you need an additional input layer, not just a video stream. Console recognition and Windows-client acceptance are different checks. [MG-S01, MG-S02]
Control your PS5 from a Windows PC
Scroll the table horizontally as needed. With a keyboard: focus the table and use the arrow keys.
| Path | Where input connects | What is established | What is not established |
|---|---|---|---|
| PS5 USB/Bluetooth peripherals Manufacturer documentation — not independently tested Sources: MG-S01 | Console | Sony documents connection and accessory settings. | A named game’s native aiming or movement. |
| Official Windows PS Remote Play Manufacturer documentation — not independently tested Sources: MG-S02 | Documented controller → Windows host by USB | Own-console streaming, controller workflow and mouse panel controls. | Generic mouse-to-stick translation. |
| Third-party client + translator | Depends on host, mapper and output | Specific inspected project roles. | A known-good combined Windows stack. |
| Planned ConsoleMouse Manufacturer documentation — not independently tested Sources: LOCAL-FACTS | Powered Windows PC or laptop → home network → own console | Planned HDMI TV/monitor and same-host PC-stream modes. | Released app, verified game support or measured latency. |
Set up Sony’s Windows client in this order
Use your own PS5 and a Windows PC or laptop. Sony documents Windows 10 64-bit or Windows 11, a seventh-generation Intel Core processor or later, 100 MB storage, 2 GB RAM, 1024 × 768 display, a sound card and USB port. These are Sony app requirements, not tested ConsoleMouse minima. Follow Sony’s current download and support pages rather than an unofficial installer. [MG-S02, MG-S03]
- 1. Download PS Remote Play from Sony’s official page and follow its installation prompts.
- 2. Update PS5 system software. On PS5, open Settings → System → Remote Play → Enable Remote Play.
- 3. For startup from rest mode, enable Stay Connected to the Internet and Enable Turning on PS5 from Network under the rest-mode features.
- 4. Turn on the PS5 or put it in the configured rest mode. Connect a documented DualSense, DualSense Edge or DUALSHOCK 4 controller to the Windows host by USB.
- 5. Start PS Remote Play, sign in with the same PlayStation account used on the console and select PS5.
- 6. If automatic connection fails, put the host and console on the same network. Use Settings → System → Remote Play → Pair Device and enter the displayed number only in your own Remote Play app. Do not send it to anyone.
- 7. Confirm picture, sound and ordinary controller gameplay before adding any translator. Before connecting from outside home, Sony advises checking the connection near the console.
The mouse controls the app panel—not a documented aim axis
Move the mouse over the Remote Play picture to reveal the panel. Sony describes Create, PS and Options buttons, app volume, microphone status, controller battery level and screen-size controls. Clicking PS opens the console control centre; changing app volume changes app audio. Those functions do not document relative mouse movement becoming the game’s right stick. [MG-S02]
A visible pointer or a working menu click is therefore useful evidence about the interface, not proof of in-game camera control. Likewise, typing in a text field does not establish WASD movement. Test the action you need instead of treating every keyboard or mouse event as equivalent.
Diagnose the first failing layer
Start with the documented controller baseline. Change one component at a time and record the client/build, input device and symptom. The sequence below is diagnostic reasoning, not a hardware test performed for this guide. [MG-S02, MG-S03]
Control your PS5 from a Windows PC
Remote Play setup and manual pairing
Scroll the table horizontally as needed. With a keyboard: focus the table and use the arrow keys.
| Symptom | First check | What not to infer |
|---|---|---|
| Console not found | Account, Remote Play setting, rest settings; then same-network manual pairing. | A mapper will fix console discovery. |
| Picture absent or unstable | Official controller connection and Sony’s connection support. | The mouse is necessarily the cause. |
| Controller does not work | Documented controller and USB connection first. | Translation can repair a failed baseline. |
| Keyboard only types | Identify the field and actual game action. | Typing proves movement. |
| Mouse only clicks the panel | Separate app controls from in-game camera input. | A click proves aiming. |
| Candidate virtual device missing Manufacturer documentation — not independently tested Sources: NC-OS05 | Verify recognition by the exact client/build, then delivery. | Being installed means the stack works. |
What a translator still has to solve
A translator captures keys and mouse motion, maps them to controller state and presents output that a particular client/build accepts. Mapping, virtual-device recognition and console transport are separate responsibilities. An installed mapper does not prove that its output reaches your game.
chiaki-ng is a PS4/PS5 Remote Play project, not an Xbox transport. The inspected stream code uses mouse events for touchpad gestures/clicks and keyboard events for controller buttons or stick directions. That is not evidence of native mouse aiming. Its SDL controller code makes device recognition an integration gate; the checked excerpts do not prove a virtual gamepad is accepted end to end. [NC-OS02, NC-OS04, NC-OS05]
input-remapper and Linux uinput can be considered parts of a Linux candidate: mapping plus virtual input still needs an accepted client and transport. They are not an established combined Windows solution. No such stack was assembled or tested here. [NC-OS08, NC-OS13]
Network guidance is not a responsiveness guarantee
Sony recommends at least 5 Mbps upload and download, and 15 Mbps in each direction for best performance. These are Sony Remote Play recommendations, not measured latency, a LAN guarantee or ConsoleMouse minimum bandwidth. Manual registration is same-network; Remote Play in general can connect from outside home. [MG-S02, MG-S03]
If the picture is unstable, investigate the streaming connection before changing the input method. A faster advertised internet package does not by itself identify the cause of a delayed action. This guide supplies no benchmark or latency winner.
Choose the picture path without losing the input host
In planned ConsoleMouse TV Play, mouse and keyboard connect to a powered Windows PC or laptop, then through the home network to your own console. The console’s normal HDMI output stays connected to a TV or monitor. In planned PC Play, the same Windows PC or laptop handles input and receives the console stream; the TV is unused. Both modes still require the Windows host and owned console. No capture card is specified. How TV Play handles video and audio on the Windows device, and compatibility, have not been verified here. [LOCAL-FACTS]
Use direct input if the game genuinely supports your needed actions; keep the controller if changing the display is all you need. For translation, inspect exact output/client dependencies. Read the related method, no-adapter and picture-path guides before buying a component. We develop ConsoleMouse and publish GTAMouse. ConsoleMouse remains in development, with no available app established by this guide.
Frequently asked questions
Can I aim using the Windows app’s mouse?
The checked Sony guide documents mouse-operated panel controls, not mouse aiming. A different input layer needs its own output/client verification.
Do I still need my own PS5?
Yes. This is own-console Remote Play, not a PC edition or a cloud-game entitlement.
Why can I click the panel but not move in the game?
The panel is an app interface. Movement needs the game’s native action or controller-state input accepted by the client.
Does 15 Mbps guarantee responsiveness?
No. It is Sony’s bandwidth recommendation, not a latency result or guarantee.
Is a Linux assembly a Windows solution?
No. The cited input-remapper/uinput candidate is Linux-specific and its complete delivery path remains untested.
Sources and evidence
- MG-S01 — PS5 keyboard and mouse setup
Manufacturer documentation — not independently tested · Retrieved:
- MG-S02 — Control your PS5 from a Windows PC
Manufacturer documentation — not independently tested · Retrieved:
- MG-S03 — Remote Play setup and manual pairing
Manufacturer documentation — not independently tested · Retrieved:
- NC-OS02 — chiaki-ng project
Manufacturer documentation — not independently tested · Retrieved:
- NC-OS04 — chiaki-ng stream input source
Manufacturer documentation — not independently tested · Retrieved:
- NC-OS05 — chiaki-ng SDL controller source
Manufacturer documentation — not independently tested · Retrieved:
- NC-OS08 — input-remapper project
Manufacturer documentation — not independently tested · Retrieved:
- NC-OS13 — Linux uinput documentation
Manufacturer documentation — not independently tested · Retrieved:
- LOCAL-FACTS — Product development contract
Manufacturer documentation — not independently tested · Retrieved: