01
Free a blocked development port
Search for a familiar port such as 3000, 5173, 5432, 6379, or 8080 and immediately see the owning process, PID, state, and full command line.
Desktop utility for blocked local ports
Find the process using your local port before it blocks the next run.
WhoUseMyPort is a focused Windows and macOS app for developers and system administrators who need a fast answer to one question: what is bound to this local port right now? The app scans the current socket table, resolves the owning PID and command, and lets you terminate the process when your operating system allows it. The repository also documents a structured OpenClaw workflow for source builds that need an agent-assisted second pass.
- Local-first desktop behavior
- Windows and macOS public binaries
- PID, command, protocol, and state in one view
- Repository workflow for OpenClaw-assisted diagnosis
Mac scan path
Uses lsof -i -P -n to read the local socket list without resolving host names.
Windows scan path
Uses netstat -ano and resolves process details against the local PID list.
Process control
Windows uses taskkill; Unix-like builds attempt TERM before KILL.
Public downloads
Windows .exe and macOS universal .dmg are linked from this site.
Built for the jobs that terminal output slows down.
This site exists to explain how the app works, where the downloadable builds come from, and when the GUI is the faster option than jumping between lsof, netstat, and process management commands.
02
Confirm whether a service is actually listening
Filter by protocol and state to separate long-lived listeners from short-lived client connections or sockets that are already closing.
03
Inspect before you kill
WhoUseMyPort surfaces the process name and command so you can tell the difference between a safe local dev server and something you should leave alone.
How the app works on each platform.
The product does not perform remote scans or network probing against other hosts. It reads the current machine's local socket data and resolves it back to the corresponding process information on the same system.
macOS flow
The current macOS build reads live socket information through lsof -i -P -n. That keeps host lookup out of the path and prioritizes a readable local result set.
- Shows local ports, protocol, state, PID, process name, and command.
- Works best when you need a quick read on a machine you are using directly.
Windows flow
The Windows build reads netstat -ano, parses the local address table, and then resolves additional process details for each PID.
- Built to avoid the console flashes that often appear when command-line helpers are launched from GUI tools.
- Pairs the port list with process lookups so the result is easier to interpret than raw netstat output.
Safety model
Terminating a process is an explicit user action. Whether the action succeeds depends on the permission model of the operating system and the target process.
- The app does not promise that every protected process can be terminated.
- Support content on this site explains when a restart is safer than forcing a kill.
Common local workflows.
These are the cases this site documents because they come up repeatedly in real development and operations work.
A
React or Vite server failed to restart
Search the expected port, inspect the command column, then decide whether to stop the stale process or restart the owning app normally.
B
Database port is occupied after shutdown
Check whether the socket is still in LISTEN, already closing, or tied to a second service instance before changing configuration.
C
Need to watch transient connections
Use the built-in auto-refresh intervals and state filters when you want to keep an eye on short-lived local connections without re-running commands manually.
The public website focuses on documentation, troubleshooting, release notes, and support. If advertising is introduced later, content will remain primary and ads will never be disguised as navigation or download controls.
Download the current public builds.
The site currently publishes Windows and macOS binaries. Linux build targets exist in the repository workflow, but there is no public Linux binary on this website yet.
Windows 1.0.0
Direct desktop binary for Windows 10 or later.
Download for WindowsFile hash and verification details are listed on the release notes page.
macOS 1.0.0
Universal macOS disk image for Intel and Apple Silicon on macOS 10.15 or later.
Download for macOSRead the support page before bypassing any operating-system security warnings.
Repository workflow for OpenClaw-assisted diagnosis.
Alongside the public downloads, the repository now ships a dedicated OpenClaw skill and a structured export flow in the current source build. The public binaries listed below remain version 1.0.0 until the next published build refresh.
01
Use the bundled repo skill
OpenClaw can load whousemyport-port-diagnostics directly from the repository workspace, or you can download the raw SKILL.md file from this website.
02
Export the visible table as a report
The current desktop source build can copy the active view as structured text, including filters, PID, state, protocol, and command fields.
03
Give OpenClaw something better than a screenshot
Structured rows make it easier to tell whether port 3000 is a listener, a transient client connection, or the wrong process entirely.
Read the supporting documentation before you decide whether the app fits.
The website is intentionally structured as more than a single download screen. Every page exists to answer a real product, support, or policy question.
Usage guide
Step-by-step help for reading the table, filtering results, understanding socket states, and deciding whether it is safe to terminate a process.
OpenClaw workflow
Learn how the bundled skill, direct SKILL.md download, shared installer, and structured export path fit together when you want agent help for a blocked localhost port.
Support center
Installation notes, macOS and Windows permission issues, known limitations, and what to include when you email for help.
Release notes
Current public file versions, file sizes, SHA-256 hashes, and a changelog for the website and desktop builds linked here.
Privacy and ads
Explains what stays local in the desktop app, what the website may log, and how Google ad technologies would be disclosed if enabled.
About the project
Describes the scope of WhoUseMyPort, the editorial standard for this site, and how support and monetization are handled.
Direct contact
Email the maintainer with your operating system version, port number, and an OpenClaw report or screenshot if you need help reproducing a problem.
Short answers to the questions reviewers and users usually ask first.
Does WhoUseMyPort scan remote hosts or cloud servers?
No. The current product is for the local machine you are using directly. It reads the local socket table and maps that data back to local processes.
Do I need administrator rights to use it?
Basic inspection may work without elevated rights, but terminating protected processes or reading some details can require administrator or system approval depending on the operating system.
What filtering and sorting options are available?
The desktop UI supports protocol and state filters, search by port or process details, sortable columns, and auto-refresh intervals for repeated checks.
How does the OpenClaw workflow fit into the project?
The repository now includes a dedicated OpenClaw skill plus a structured report export in the current source build. The setup steps and release status are documented on the OpenClaw page.
What data leaves my computer when I use the desktop app?
The app is designed to process port and process data locally. Website privacy, email support, and any future ad-related disclosures are covered in the privacy page.
Is this site only for ad placement?
No. The site is structured around product explanation, support, privacy, release notes, and contact information. Advertising, if added later, is secondary to those functions.