Port Kill

Find and kill any port,
one click

See all listening TCP ports on your Mac. Categorized by type, searchable by name or number, killable in one click. No more terminal guesswork. Free forever.

The Problem

Killing a port should not take 3 commands

Every developer knows the drill: lsof -i :3000 | grep LISTEN, find the PID, then kill -9 12345. It works, but it is slow, error-prone, and you do it multiple times a day. Port conflicts are one of the most common interruptions during development.

Benefits

Port management without the terminal

See All Listening Ports

Real-time scan of every TCP port in use on your Mac. No terminal commands, no guessing what is running where.

Auto-Categorization

Ports are grouped by type: Dev Servers, Python, Java, Docker, Databases, Web Servers, and System. Color-coded badges make scanning instant.

One-Click Kill

Find the port, click kill. Confirmation dialog prevents accidental kills. No more piping lsof to grep to kill -9.

Search & Filter

Search by port number or process name. Filter by category. Find port 3000 in seconds, not minutes.

Auto-Refresh

Configurable auto-refresh keeps the port list current. Spot new processes as they start without manual rescanning.

Free Forever

Port Kill is completely free in FavTray. No trial, no upgrade required, no feature limitations. Free forever.

How It Works

Three steps, zero terminal

1

Open Port Kill

Click the FavTray icon, select Port Kill. All listening ports appear instantly.

2

Find the port

Search by number (3000) or name (node). Ports are categorized and color-coded.

3

Kill it

Click the kill button, confirm, done. The process is terminated and the port is freed.

Common Ports

Ports developers encounter daily

Port Commonly Used By
3000 React, Next.js, Express, Rails
3001 React (secondary), create-react-app
4321 Astro dev server
5173 Vite dev server
5432 PostgreSQL
6379 Redis
8080 Spring Boot, Tomcat, generic HTTP
8443 HTTPS alternative, Tomcat SSL
27017 MongoDB
9090 Prometheus, various dev tools
Who It's For

Built for developers who fight port conflicts

Frontend Developers

Port 3000 already in use? Find what is using it and kill it in one click instead of hunting through terminal commands.

Backend Developers

Multiple services on different ports. See them all at a glance, categorized by type. Kill a stale server without affecting others.

DevOps Engineers

Docker containers, databases, and dev servers all competing for ports. Auto-categorization makes it clear what is what.

Full-Stack Developers

Running React on 3000, API on 8080, Postgres on 5432, and Redis on 6379? See everything in one view.

FAQ

Frequently asked questions

Is Port Kill really free?

Yes. Port Kill is completely free forever in FavTray. All features — scanning, categorization, search, kill — are available with no trial, no upgrade, and no feature limitations.

How does Port Kill find processes?

Port Kill uses the macOS lsof command under the hood to scan all listening TCP ports. It then categorizes processes by type and displays them in a searchable, filterable interface.

Can I accidentally kill a system process?

Port Kill shows a confirmation dialog before killing any process. System ports are labeled and can be hidden via a toggle. You cannot accidentally kill a process without confirming.

Does it replace lsof and kill commands?

Yes. Instead of running 'lsof -i :3000 | grep LISTEN' followed by 'kill -9 PID' in the terminal, Port Kill lets you find the port, see the process, and kill it in one click.

Can I exclude certain processes from the list?

Yes. Port Kill has a configurable exclusion list. Add process names you never want to see, and they will be hidden from the scan results.

Stop fighting port conflicts

Port Kill is free forever in FavTray. Plus eye rest, AI tracking, window manager, and 3 more tools.

FavTray is coming soon

Join the waitlist and we'll notify you when we launch.

No spam. Unsubscribe anytime.