{"id":1454,"date":"2026-08-12T02:41:44","date_gmt":"2026-08-12T02:41:44","guid":{"rendered":"https:\/\/www.projectimmerse.com\/blog\/?p=1454"},"modified":"2026-08-13T00:29:17","modified_gmt":"2026-08-13T00:29:17","slug":"how-to-find-and-kill-a-process-by-pid-without-losing-your-mind","status":"publish","type":"post","link":"https:\/\/www.projectimmerse.com\/blog\/how-to-find-and-kill-a-process-by-pid-without-losing-your-mind\/","title":{"rendered":"How to Find and Kill a Process by PID (Without Losing Your Mind)"},"content":{"rendered":"\n
\"How<\/a>
Find the PID using a process or port lookup, then terminate the process from the command line.<\/figcaption><\/figure>\n\n\n\n

If you’ve ever stared at a terminal that says Port 3000 is already in use<\/code> and felt a small piece of your soul leave your body, this post is for you. Whether you’re running Next.js, a random Node script, or fifteen forgotten npm run dev<\/code> processes from three weeks ago, learning to manage processes by PID will save you a restart, a Stack Overflow rabbit hole, and possibly your sanity.<\/p>\n\n\n\n

Let’s break down what a PID actually is, how to find one, and how to (gracefully or violently) shut it down.<\/p>\n\n\n\n\n\n\n\n

What Is a PID, Anyway?<\/h2>\n\n\n\n

PID stands for Process ID<\/strong> \u2014 a unique number your operating system assigns to every running process. Think of it like a name tag at a networking event, except instead of “Hi, I’m Dave from Marketing,” it’s “Hi, I’m 62311, and I’m hogging port 3000.”<\/p>\n\n\n\n

Every app, script, and background service running on your machine has one. Some processes behave. Others linger long after you’ve closed the terminal window, quietly eating memory like it’s an all-you-can-eat buffet.<\/p>\n\n\n\n

How to List Running Processes (and Their PIDs)<\/h2>\n\n\n\n

Before you can kill a process, you need to find it. Here’s how, depending on your operating system.<\/p>\n\n\n\n

On Linux\/macOS<\/h3>\n\n\n\n

To see everything running on your machine:<\/p>\n\n\n

\nps aux\n\n<\/pre><\/div>\n\n\n
This dumps a full list, which is great for browsing but a little much if you’re looking for one specific troublemaker.<\/p>\n\n\n\n
For a cleaner list of just PIDs and command names:<\/p>\n\n\n
\nps -e -o pid,comm\n\n<\/pre><\/div>\n\n\n
For a live, constantly updating view (basically Task Manager for your terminal):<\/p>\n\n\n
\ntop\n\n<\/pre><\/div>\n\n\n
or, if you have it installed, the significantly prettier:<\/p>\n\n\n
\nhtop\n\n<\/pre><\/div>\n\n\n
Want to search for something specific, like all your rogue Node processes?<\/p>\n\n\n
\nps aux | grep node\n\n<\/pre><\/div>\n\n\n
On Windows<\/h3>\n\n\n\n
Command Prompt:<\/p>\n\n\n
\ntasklist\n\n<\/pre><\/div>\n\n\n
PowerShell (if you like your process lists a little more scriptable):<\/p>\n\n\n
\nGet-Process\n\n<\/pre><\/div>\n\n\n
Filter by name:<\/p>\n\n\n
\ntasklist | findstr node\n\n<\/pre><\/div>\n\n\n
Finding a PID by Port Number<\/h2>\n\n\n\n
Sometimes you don’t care about the process name \u2014 you just know something<\/em> is squatting on a port you need. This is incredibly common with local dev servers.<\/p>\n\n\n\n
On Linux\/macOS:<\/p>\n\n\n
\nlsof -i :3000\n\n<\/pre><\/div>\n\n\n
This instantly tells you what’s using port 3000 and gives you its PID, no guessing required.<\/p>\n\n\n\n
On Windows:<\/p>\n\n\n
\nnetstat -ano | findstr :3000\n\n<\/pre><\/div>\n\n\n
The PID shows up in the last column. Cross-reference it if you want a name:<\/p>\n\n\n
\ntasklist \/FI "PID eq 12345"\n\n<\/pre><\/div>\n\n\n
How to Kill a Process by PID<\/h2>\n\n\n\n
\"How
Find the process using a port, kill it by PID, then verify that the port is free.<\/figcaption><\/figure>\n\n\n\n
Once you’ve got your PID, ending it is refreshingly simple.<\/p>\n\n\n\n
The polite way<\/strong> (sends a termination signal and asks the process nicely to wrap things up):<\/p>\n\n\n
\nkill <PID>\n\n<\/pre><\/div>\n\n\n
The “I have asked twice already” way<\/strong> (forceful, immediate, no negotiations):<\/p>\n\n\n
\nkill -9 <PID>\n\n<\/pre><\/div>\n\n\n
On Windows, the equivalent is:<\/p>\n\n\n
\ntaskkill \/PID <PID> \/F\n\n<\/pre><\/div>\n\n\n
Most of the time, plain kill<\/code> works fine. Reach for -9<\/code> only when a process is being stubborn \u2014 kind of like how you ask your dog to get off the couch once, twice, and then just pick it up.<\/p>\n\n\n\n
Real-World Example: The Next.js Port Conflict<\/h2>\n\n\n\n
This scenario is basically a rite of passage for anyone building with Next.js. You run your dev server, and instead of the usual clean startup, you get something like this:<\/p>\n\n\n
\n\u26a0 Port 3000 is in use by process 62311, using available port 3001 instead.\n\u2a2f Another next dev server is already running.\n\n- Local:        http:\/\/localhost:3000\n- PID:          62311\n- Dir:          \/Users\/you\/projects\/your-app\n\nYou can access the existing server at http:\/\/localhost:3000,\nor run kill 62311 to stop it and start a new one.\n\n<\/pre><\/div>\n\n\n
Next.js is doing you a favor here \u2014 it’s not just erroring out, it’s handing you the exact PID and the exact command to fix it. All you have to do is listen:<\/p>\n\n\n
\nkill 62311\n\n<\/pre><\/div>\n\n\n
Then restart your dev server like nothing happened:<\/p>\n\n\n
\nnpm run dev\n\n<\/pre><\/div>\n\n\n
Want to double-check the port is actually free before you get your hopes up?<\/p>\n\n\n
\nlsof -i :3000\n\n<\/pre><\/div>\n\n\n
No output means the coast is clear.<\/p>\n\n\n\n
A Few Handy Extras<\/h2>\n\n\n\n