What is using port 8000 on my Mac?

Port 8000 is a popular development default, used by Django's runserver, Python's http.server, and many other local servers. A listener almost always means a dev server you started. Run lsof -i :8000 to confirm.

Is it safe to kill a process on port 8000?

Yes. It's almost always a local development server, not a macOS service. Killing it frees the port and stops that server without affecting the system.

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

A previous dev server that crashed or was force-quit can keep 8000 bound. Run lsof -i :8000 to find the leftover process and kill it.

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

Port 8000 is one of the most common development server defaults. Django’s runserver, Python’s built-in http.server, and countless other local tools use it. A listener on 8000 is almost always a dev server you started.

What typically listens on port 8000

Django: python manage.py runserver defaults to 8000.
Python http.server: python -m http.server serves on 8000.
Other dev tools: Many frameworks and static file servers pick 8000 as a default.

It’s in the registered range (1024-49151), so any app can bind it without admin rights.

Is it safe to kill?

Yes. A process on 8000 is something running on your own machine, not a macOS system service. Killing it frees the port and stops that server. Just make sure it isn’t a server you still need.

Is it suspicious?

On a development machine, no. Seeing 8000 in use is routine. It’s worth a look only if you don’t recognize the owning process and don’t run local servers. The command below shows the name.

How to find and free port 8000 on macOS

lsof -i :8000

To free it:

kill -9 $(lsof -ti :8000)

If you keep hitting the conflict, see Port 3000 already in use on Mac, which covers the same fix for any dev port. Portie shows port 8000 with the app that owns it in its live list, and the $8.99 unlock lets you kill it from the row.