How to uninstall Medis on Mac
Medis is a Redis client. Before deleting its local settings, record connection names, host details and authentication material using a secure method you control. If a Redis server contains data, back it up through the server’s own procedure; removing the Mac client is not a Redis database backup or deletion.
The recorded test used the official Mac package; the Homebrew route below is separate.
Remove the app
Quit Medis and move Medis.app from Applications to Trash. Check any saved connection profile before removing local support data, especially if it is the only place you recorded a server address. Do not run Redis deletion commands as part of this app uninstall.
Review local data
The current Homebrew cask uses li.zihua.medis* family patterns, while the recorded installation uses the exact li.zihua.medis2 paths below. Do not remove another version just because its prefix matches. In Finder, use Go › Go to Folder to inspect it. Do not remove its parent directory or another product’s data.
| Location | Decision |
|---|---|
~/Library/Application Support/li.zihua.medis2 |
Exact bundle-ID support folder observed in the test; it was selected and removed. Inspect connection settings first. |
~/Library/Caches/li.zihua.medis2 |
This version’s cache, if present. |
~/Library/HTTPStorages/li.zihua.medis2 |
This version’s HTTP storage, if present. |
~/Library/Preferences/li.zihua.medis2.plist |
This version’s preferences, if present. |
After quitting, COPY wanted state from the existing own table paths to an independent private backup outside sync and all removal folders and verify it. Open each confirmed unwanted app item in Finder and move it to the Trash; keep shared parents and retained versions' data.
The tested package uses bundle ID li.zihua.medis2. Review only files that actually appear on this Mac. A missing path needs no cleanup.
Check what remains
Run these read-only commands after quitting the app:
pgrep -il 'Medis'
ls -d "$HOME/Library/Application Support/li.zihua.medis2"
No process output means this process-name pattern did not match; also inspect Activity Monitor for confirmed app processes, and do not treat it as proof every helper is gone. A listed process needs its owner checked. If ls prints the path, that item remains and needs review. “No such file or directory” means this path is absent; a permission error means its state was not established.
If you installed it with Homebrew
The current medis cask has a zap list covering Medis support, cache, HTTP storage and preference paths matching the medis bundle-name family. A direct brew command with --zap applies the cask list without consulting Mole’s checkboxes. After backing up, use this command without --zap:
brew uninstall --cask medis
Mole checks each zap path against your selections, other installed apps, and protected locations. An unchecked, shared, or unverifiable path suppresses --zap; selected remnants can still use Mole’s own removal flow. This cask was not the recorded installation channel.
What Mole lists
Mole selects this exact bundle-ID Application Support folder by default, so uncheck it if its connection profiles are still needed. With Remove data and settings with apps off, existing display-name-only review rows start unchecked; with it on, an eligible own unshared row may start checked. Broader medis-family matches still need ownership checks, and another version’s data must be retained. Mole does not connect to a Redis server to inspect its data.
What this test covered
The official ZIP build 2.16.1 was installed and removed on September 20, 2026, with the li.zihua.medis2 support row selected. The test never connected to Redis, so it says nothing about server data or saved production credentials.