What Is Port 8080 Used For?

Port 8080 shows up everywhere in development, but it isn’t tied to any single program. It’s a convention more than an assignment. Here’s what it’s actually for and why so many tools land on it.

The short answer

Port 8080 is the unofficial “alternate HTTP” port. When port 80 (the standard web port) is unavailable or inconvenient, software falls back to 8080. IANA registers it as http-alt, and the 80 in 8080 is a deliberate visual echo of port 80, it’s meant to be read as “HTTP, but somewhere else.”

Why 8080 instead of 80?

Two practical reasons:

Port 80 needs privileges. On macOS and other Unix systems, binding to any port below 1024, including 80, requires root. Port 8080 sits in the registered range above 1024, so any program can bind to it without sudo. That alone makes it the natural default for development.
Port 80 is often already taken. On a server, the real web server (nginx, Apache) usually owns port 80. A second service, a proxy, an admin panel, a backend, needs somewhere else to live, and 8080 is the obvious, memorable choice.

What commonly runs on 8080

Apache Tomcat: 8080 is its default HTTP connector port out of the box.
Development and test web servers: many frameworks and tools default here.
HTTP proxies: forward and reverse proxies frequently listen on 8080.
Admin and management UIs: Jenkins, for example, defaults to 8080.
A second web app on a machine where 80 and 443 are already in use.

Because so many tools default to it, 8080 is also one of the most common sources of “port already in use” collisions, two programs both assume they can have it.

Is port 8080 secure?

Port 8080 carries plain, unencrypted HTTP by default, exactly like port 80. The number itself adds no security. For anything sensitive you’d want HTTPS, which conventionally uses 8443 (the alternate form of 443) rather than 8080. Running a service on 8080 is fine for local development; exposing one to the public internet without TLS is not.

How to see what’s using port 8080 on your Mac

Check whether anything is listening on it:

sudo lsof -i :8080 -n -P

If something owns it, you’ll see the process and PID:

COMMAND   PID   USER   ...  NODE NAME
java     2841  aaron   ...  TCP *:8080 (LISTEN)

Here Tomcat (running as java) holds the port. If the command returns nothing, port 8080 is free.

“Port 8080 already in use”, how to fix it

If a program won’t start because 8080 is taken, you have two choices:

Free the port by stopping whatever holds it:

kill -9 $(lsof -ti :8080)

Or move your app to a different port (8081, 8000, 9000). Changing your port is usually safer than killing a process you can’t immediately identify.

This is the same pattern as any port collision, see port already in use on Mac for the full approach, including how to decide which process is safe to stop.

80 → standard HTTP
443 → standard HTTPS
8000 → another common alternate HTTP / dev port
8443 → alternate HTTPS
3000 → Node / React dev default

Browse the full port reference for any number you run into.

Keep an eye on 8080 automatically

Portie shows you the moment anything claims port 8080, or any other port, on your Mac. It lists every open port with the owning app, protocol, and state in a live table refreshed every 3 seconds, so you can spot a collision before your server even complains.

Local monitoring is free. The $8.99 one-time unlock adds one-click process termination and remote port scanning. Download Portie to keep your dev ports under control.