01
Turn “address already in use” into an identified process
Filter by port or process name, jump to common development ports, and see the matching protocol, PID, process name, and executable path together.
Port Process ViewerMac Workflows
Find the process holding a local port, then stop only the right one.
Port Process Viewer uses native macOS process information to turn a port conflict into an exact owner: process name, protocol, PID, executable path, and port. Filter directly or use common development ports, then choose graceful Quit or Force Quit only after a confirmation repeats the target.
Start the 14-day trial in the app. No payment method is required to try Foldout.
Local tool processingFiles and tool work stay on your Mac.
100+ focused toolsFiles, PDFs, media, capture, and developer workflows.
Settings ready to goFormats, dimensions, and other values carry into the tool.
Try everything first14 days in the app. No payment method required.
This tool is a local inspection and workflow utility for files, settings, and development tasks you control. It reviews selected local information only; Foldout does not connect to other machines, manage accounts, monitor networks, or provide a live service. Use Foldout only with files, content, hosts, tokens, systems, or accounts you own or are authorized to inspect or process.
What it does
Identify a local listener and put every shutdown action behind an identity-aware confirmation.
List local listening processes and filter by port number or process name.
Jump to common web, API, database, cache, and development ports.
Review protocol, PID, executable path, and system-process warnings together.
Reveal the executable location before deciding whether the process is expected.
Request graceful shutdown with Quit or immediate termination with Force Quit.
Re-check the process start time immediately before signalling to protect against PID reuse.
Identify before acting
Resolve a port conflict without guessing which process will stop.
A fictional 5173 conflict proves exact ownership, native process details, common-port filtering, and the final graceful-shutdown confirmation.
02
Confirm the exact process before sending a signal
The final dialog repeats the process name, PID, port, and executable path, then explains that a normal Quit requests graceful shutdown before anything happens.
Why it belongs
Why Port Process Viewer earns a place in the toolbox.
The practical details that make this job faster, clearer, or safer than doing it by hand.
A port conflict becomes an identity
Port, protocol, process name, PID, and executable path stay together so an address-in-use error can be traced to the actual owner.
Common development ports are ready
Shortcuts for ports such as 3000, 5173, 5432, 6379, and 8080 remove repetitive filtering during local development.
System processes receive an extra warning
Foldout distinguishes ordinary development services from protected or system-owned processes before enabling a stop decision.
Shutdown remains identity-aware
The confirmation repeats the target and signal, then Foldout verifies the process incarnation again so a recycled PID is never treated as the stale result.
How to use it
From opening the tool to saving the result.
- 01
Enter a port or process name, or choose a common port.
- 02
Review the matching process identity and executable path.
- 03
Choose Quit or Force Quit only when the owner is correct.
- 04
Confirm the exact process and signal.
Questions
Before you try Port Process Viewer
What is the difference between Quit and Force Quit?
Quit sends SIGTERM so the process can shut down cleanly. Force Quit sends SIGKILL and stops it immediately.
Can stopping a process lose work?
Yes. Review the name and executable path first, and prefer Quit when the service can shut down normally.
Can a stale result stop a different process?
Foldout rechecks the selected process start time immediately before signalling and refreshes instead of acting if the identity changed.
Related tools