Native macOS utility

PortClear

See which server you left running and what port it's holding — then how much space node_modules is eating.

Finds Node processes left running in the background and the ports they are holding, with a button to free them. It also scans a folder and shows every node_modules with its size and last-used date, so you can delete the ones you no longer need.

Launch price · −50%Final price €58

€29+ VAT at checkoutLicence agreement

345 licences left at the launch price

The problem

The port does not free itself

Port 3000 is taken and you don't know by which process. The alternative is lsof -i :3000 followed by kill, every single time.

node_modules does not clean itself up. It accumulates in every project you have ever worked on, and Finder will not tell you which ones are stale and which are in use.

How it works

Six steps, in the order they happen, from opening the app to a freed port. Every step runs locally, on your Mac.

01ScanOpens straight onto the dev ports currently held by Node processes — the most common ones (3000, 5173, 8080, 4200, 19000, 4321, 24678, …) get a card of their own.
02IdentifyFor each port, shows what process holds it, how long it has been running and from which folder.
03FlagProcesses that look left behind are flagged — with the exact reason each was flagged, not just a warning triangle.
04ConfirmBefore anything is stopped, you see the targeted processes: kind, pid, uptime, port, working directory and the reason each was flagged.
05Free itFree port sends SIGTERM. A second button sends SIGKILL when the process is wedged.
06Clean upSeparately, scan a folder for forgotten node_modules and send them to the Trash, with the reclaimed space confirmed up front.
// screens

The app's screens

Before it frees a port, PortClear shows the Node process holding it and why it was flagged, and sends SIGTERM only when you confirm.
Type a port into the search box and only its holder stays: a Vite server, its folder, and how long it has been up.
Disk cleanup scans a folder for node_modules, shows the size and last use of each, and moves the ones you select to the Trash.
// screen tour

What each screen shows

  1. 01 / 03

    Free the port once you see what you are stopping

    • Before anything stops, the confirmation lists the targeted process: kind, pid, uptime, port and working directory.
    • Under it is the exact reason it was flagged, because the detector is a heuristic and can be wrong.
    • SIGTERM goes out only when you confirm, and the dialog warns that unsaved work in these dev servers will be lost.
    • Every held port gets a card of its own, with a Free port button and, next to it, a force kill (SIGKILL) for a wedged process.
  2. 02 / 03

    Search for a port and see exactly what is on it

    • Type the port number into the search box and only the process holding it stays in the Node process table.
    • Its row shows the kind (here, Vite), how long it has been up, the pid, memory, the command and the folder it started from.
    • The search outranks the “Only suspicious” filter, so a port you ask about never hides a process behind a heuristic.
    • It is also how you find a port that is not on the fixed list used for automatic flagging.
  3. 03 / 03

    Which node_modules are filling your disk

    • Choose a folder and Disk cleanup finds every node_modules inside it, with the project, path, size on disk and last-accessed date.
    • At the top you see how many folders it found and how much space can be reclaimed; columns sort, and results can be grouped by folder.
    • Deleting moves them to the Trash by default, so they can be put back; permanent deletion is a separate button with its own confirmation.

What it does

Three modules, one purpose

You got Error: listen EADDRINUSE: address already in use :::3000 and don't know which process is holding the port. PortClear solves that at a glance — and it also cleans up the dozens of forgotten node_modules folders scattered across old projects.

  1. 01PortClear finds the Node processes on your Mac — Next.js, Vite, NestJS, nodemon, npm — with their PID, the ports they are listening on, how long they have been up and how much memory they use. You can stop them from there, instead of hunting through a terminal for whatever is holding port 3000.
  2. 02The second module solves a related problem: the dozens of forgotten node_modules folders in directories you have not opened in months, each one hundreds of megabytes. PortClear scans a folder you choose and shows every node_modules it finds: how much space it takes, when it was last accessed, and which project it belongs to. Sort them, group them by project, reveal them in Finder, and delete them — one at a time or in bulk, with the reclaimed space confirmed.
  3. 03The third shows the space distribution across projects, so you can see at a glance where it accumulated.

Features

Ports and space, in one place

01

Finds Node processes left running: PID, ports, uptime, memory

02

Stop them straight from the app, no terminal needed

03

Recursive scan with size and last-access date per folder

04

Grouped by project, with subtotals and sortable columns

05

Delete one or many, with the reclaimed space confirmed up front

06

A chart of how space is distributed across projects

07

Skips hidden directories and symlinks, so it cannot loop

08

Scanning and deleting run locally — no account, no telemetry

The licence

See for free, free the port with a licence

Without a licence, PortClear shows you everything it has to show: who holds the port, for how long and from which folder, and how much each node_modules takes. The licence unlocks the two actions: stopping the process and deleting the folders.

Free, no licence

  • The dev ports held by Node processes, with the process, its pid, how long it has run and its working directory
  • The reason a process is flagged as left behind
  • Scanning a folder for node_modules, with the size, the last-used date and the chart by project

With an activated licence

  • Free port: stopping the process that holds the port, with SIGTERM and, when the process is wedged, SIGKILL
  • Deleting node_modules folders, to the Trash or permanently

How the licence works

  • One payment, no subscription. One licence activates one Mac.
  • Activation happens online: me-digital.ro receives the key, a machine identifier and the Mac's name.
  • At launch, when you are online, the app checks that the licence is still active on your Mac. With no internet, it keeps working.
  • Changing Macs? Release the licence from the app on the old Mac and activate it on the new one.

Why you can trust it

What it does, exactly as described

Six things you can rely on.

It says why before it acts

Every kill confirmation lists the targeted processes — kind, pid, uptime, port, working directory — and the exact reason each was flagged, before you press stop.

It sends nothing about you

Scanning and deleting run entirely on your own Mac: your ports, processes and folders go nowhere, and there is no telemetry. The app contacts me-digital.ro only to activate the licence (the key, a machine identifier and the Mac's name), to release it, and at launch to check that the seat is still yours, plus the update check you start from the menu.

The scan never descends into what it found

A node_modules it has found is not walked into, and a cancelled scan stops exactly where it was — both pinned by tests that work on real folders, created and removed inside the test, not on mocks.

Symlinks are never followed on delete

Deleting a node_modules that is a symbolic link removes only the link; the target folder stays intact — verified, in both deletion modes.

Universal binary, macOS 14+

The shipped build runs natively on Intel and Apple Silicon, with no Rosetta emulation.

Signed by us, notarised by Apple

The build you download here is signed with a Developer ID and notarised by Apple — it opens on an ordinary double-click the first time, with no right-click and no macOS warning.

What it does not do yet

Today's limits

A tool that states what it cannot do is easier to trust about what it can.

Only sees and stops Node-ecosystem processes. If a port is held by Docker, Rails, Postgres or a stale JVM, the app does not list that process; it only tells you the holder is not a Node process and points you to lsof -i :PORT.Scope
Automatic flagging works off a fixed list of dev ports, written into the code; a port that is not on the list is not flagged on its own and has to be looked up through the search box.Fixed list
Automatic update checks exist in the code (Sparkle), but are switched off by default.Off by default

This list reflects the current version of the app and is updated with every new release.

Requirements

System
macOS 14.0 or later
Binary
Universal — Intel and Apple Silicon
Network
Only for the licence and, on request, updates — scanning runs locally

Questions

Frequently asked questions

The detector is a heuristic and can be wrong — which is why every kill confirmation shows the process (kind, pid, uptime, folder) and the exact reason it was flagged, not just a "stop everything" button.

Nothing you scan or stop. Everything you see comes from ps and lsof, run locally, on your Mac. The only connections are the licence (the key, a machine identifier and the Mac's name) and, when you ask, updates.

Only the link is deleted; the target folder stays intact. It is marked separately in the list and counts as 0 B reclaimable, so the number cannot mislead you.

No. The app only sees Node-ecosystem processes; a port held by Docker or any other non-Node process does not appear in the list. When it finds nothing on a known dev port, it tells you the holder is something else and points you to lsof -i :PORT.

No. The app is signed with a Developer ID and notarised by Apple, so an ordinary double-click opens it the first time — no right-click, and no warning from macOS.

Get the app

Free the port now

Built with

SwiftSwiftUImacOS

A native macOS app — no browser, no middleman server.

Launch price · −50%Final price €58
€29

+ VAT, calculated at checkout for your country

345 licences left at the launch price

Licence agreement

Activation

How to activate your licence

Download the app

Download version 1.0.2

2.6 MB

Open the app, click “Activate licence” in the toolbar, paste the key from the email and press Activate.

On X

What PortClear has posted on X. Each post opens on X.