Is it safe to kill a process using port 8080?

Usually yes. Port 8080 is almost always a local development server or proxy you started yourself. Killing it stops that server and frees the port without affecting macOS. Just make sure you're not ending a build or container you still need.

Why is port 8080 in use when I didn't start anything?

A previous dev server, a Docker container, or a Java app like Tomcat or Jenkins often holds 8080 after crashing or being force-quit. Run lsof -i :8080 to see the owning process.

Is port 8080 a security risk?

On your own machine for local development, no. The risk comes from exposing 8080 publicly in production without authentication or TLS, where it's a common scan target.

Port 8080: What's Using It and Is It Safe to Kill?

Port 8080 is the most common alternative HTTP port. If something on your Mac is using it, that something is almost always a web server or proxy you, or a tool you installed, started locally.

What typically listens on port 8080

Port 8080 is not reserved for any single program, which is exactly why so much software defaults to it. The usual suspects:

Development servers: Spring Boot and other Java frameworks, many Node.js setups, and countless “quick start” tutorials use 8080 by default.
Tomcat and Jenkins: Both ship with 8080 as the out-of-the-box port.
HTTP proxies: Local proxy servers and API gateways listen here.
Docker containers: A container publishing a web service often maps it to 8080 on the host.

Because it sits in the registered range (1024-49151), any app can bind it without admin rights.

Is it safe to kill?

In nearly all cases, yes. A process on 8080 is something running on your own machine, not a macOS system service. Killing it frees the port and stops that server, and nothing in macOS depends on 8080.

The only caution: make sure you’re not ending a server you still need, like an active build or a container running other work.

Is it suspicious?

On a development machine, no. Seeing 8080 in use is routine. It’s worth a look only if you don’t recognize the owning process and you never run web servers. Check the process name first (the command below shows it). Malware rarely picks 8080 specifically, but any unknown listener is worth identifying.

How to find and free port 8080 on macOS

List the process holding the port:

lsof -i :8080

The COMMAND and PID columns tell you what it is and give you the ID to kill:

kill -9 $(lsof -ti :8080)

That sends SIGKILL and releases the port immediately.

Portie does the same without Terminal: it shows port 8080 with the app that owns it in its live list, and the $8.99 unlock lets you quit or force-kill that process from the row. For a stuck dev server, that’s a two-second fix.