Getting Started with Process Remote
Use Process Remote to see what's running on a Windows PC or Mac, check CPU and memory usage, and close an eligible app from a paired device on your local network.
1. Install and Connect
- Install Process Remote on the Mac or Windows PC you want to inspect and on your Android phone or tablet, iPhone, iPad, Mac, or Windows controller.
- Connect both devices to the same local network. Your phone can use
Wi-Fi while the computer uses a wired connection to the same router. - Open Process Remote on both devices and allow local network access if prompted.
To inspect the Mac or Windows PC you're already using, open Processes and select This Device. This works without pairing. Android and iOS act as controllers for a Mac or Windows PC.
2. Pair and Set Permissions
- On the controller, open Processes, select the computer under Nearby devices, and send a pairing request.
- On the computer, confirm the request came from your controller. Use Advanced to review permissions before selecting Approve.
- Back on the controller, select the paired computer in Processes to open its list.
View allows a paired device to see the computer's process list, usage metrics, and available details, including executable paths and command lines. Manage also allows it to request process actions. Both are enabled by default for new pairings. Turning off View also turns off Manage. To change these permissions later, open Devices on the computer being inspected and select the paired controller.
If the computer doesn't appear, open Devices, choose Add, and select Look up IP address. Enter the computer's local IP address. Include its port after the address if it uses a custom port. The default is 41292.
3. Find and Inspect a Process
- Use search to narrow the list by process or executable name. Sort by Process, CPU, or Memory in either direction.
- Use Show system usage charts to see the computer's overall CPU and physical memory use. The charts hold recent readings for the current visit. CPU percentages use the computer's total CPU capacity.
- Select a row to open its details. You can see the PID, resource usage, executable path, and command line when available. Fields vary by operating system and by what it lets the app read.
Readings refresh about every three seconds while the selected computer's list or details are active. CPU may need a second sample before it appears. A list can show up to 2,048 processes and may be shorter if the computer limits the response. Narrow the search if the list is truncated.
4. Close or Force Stop a Process
- Open the process details and check that you selected the intended app or process. For a remote computer, your controller needs both View and Manage.
- Use Quit on Mac or Close on Windows to ask the app to exit. The app may prompt someone at the computer to save changes.
- To request a forced stop, use Force Quit on Mac or Terminate on Windows, then select OK to confirm. A forced stop can discard unsaved changes or corrupt data.
Actions depend on the process and the computer's operating-system permissions. Process Remote blocks actions against itself, protected or system processes, and processes belonging to another user. A request can be accepted while the app is still running. Check the result before assuming the process has exited.
5. Review History and Manage Devices
Open History to review process lists and details viewed, actions requested, and outcomes. The tab includes activity on This Device as well as requests sent or received. Use Clear to clear history, or open Settings and use Save to History and Number of saved items to control what is kept.
Use Devices to rename or remove a paired device and to change the permissions you grant on a Mac or Windows PC. Each computer controls access to its own processes.
Quick Troubleshooting
- The computer doesn't appear. Check that the app is running on the computer, both devices are on the same network, and local network access is allowed. Check for a firewall, VPN, or guest network that isolates devices. Try Look up IP address if automatic discovery fails.
- You can't open the computer's process list. Check that pairing was approved and that the computer has View enabled for your controller. If the pairing was removed, pair again.
- An action is missing or unavailable. Check Manage on the computer. Some processes are protected, and some Windows processes have no window that can accept Close.
- A process changed or ended. Return to the current list and check whether the process is still present. Opening the current row gives you a fresh view.
- A reading or detail is unavailable. Give CPU time to collect a second sample. If an individual detail stays unavailable, the operating system may restrict access or the field may be unsupported on that computer.
Home • Remote Tools • Process Remote • Getting Started