ntfy · macOS

Forward macOS notifications to ntfy

ntfy makes it easy to publish from a script. The alerts your Mac apps post are harder to reach, because macOS offers no public way to read them. This is how to get those into an ntfy topic too.

brew install --cask n2ctech/tap/notiferry

Updated · macOS 15.0 or later · 7-day free trial · €9.99 once (2 Macs)

In short

  • For your own scripts, publish to ntfy directly with curl. No helper app is needed.
  • For alerts that Mac apps post, NotiFerry watches Notification Center and publishes each new entry to your ntfy topic.
  • It works with ntfy.sh by default and with a self-hosted ntfy server over HTTPS, using an access token or a username and password.
  • NotiFerry publishes only. It is not a way to receive ntfy messages on a Mac.

First: which direction do you need?

Searches for ntfy on macOS mean two opposite things, so it is worth being clear about which one this page covers.

  • Receiving ntfy messages on a Mac. ntfy has no official native Mac app. The usual answers are the ntfy web app, which can show desktop notifications from a browser, and the ntfy command line, which can run a command for each message. NotiFerry does not do this.
  • Sending what happens on a Mac to ntfy. This is the subject here: getting the alerts your Mac apps post into an ntfy topic, so your phone or anything else subscribed to it can receive them.

Scripts publish themselves; apps cannot

For anything you run yourself, ntfy needs no helper. A single curl at the end of a command publishes to your topic; the guide to sending a notification from Mac to iPhone has the patterns.

Applications are the gap. A video export, a backup, a download, or an AI client tells you it is done with a macOS notification and nothing else. Turning those into ntfy messages means reading Notification Center, which macOS does not expose through a public API. You can build that yourself against the undocumented database, and some people do. NotiFerry is the packaged version: a sandboxed menu-bar app that watches Notification Center with read-only access to one folder and publishes each new entry to your topic.

What NotiFerry publishes

Each forwarded notification is one standard ntfy publish request in JSON. With the full-notification privacy mode it looks like this:

POST https://ntfy.sh/
Content-Type: application/json

{
  "topic": "nf-…",
  "title": "<source app> — <notification title>",
  "message": "<subtitle and body>",
  "priority": 3,
  "tags": ["computer"]
}
  • Title starts with the installed app's name, followed by the notification title. If the app name is unavailable, NotiFerry keeps the source recorded by macOS.
  • Message is the subtitle and body. In the default title-only mode, and in generic mode, the message is replaced by “New notification” before anything leaves the Mac.
  • Priority and tag are fixed at the default priority and the computer tag.
  • Not included: icons, images and attachments, action buttons, click URLs, and the original sound.

Long titles and bodies are truncated to stay within ntfy's message size limit.

Server, authentication, and topic

NotiFerry uses the public https://ntfy.sh server by default and generates a topic for you: the prefix nf- followed by 60 random hexadecimal characters. You can rotate it at any time or replace it with a topic of your own.

In Settings, under Connection, you can point NotiFerry at your own ntfy server instead. Three things to know:

  • The server URL must use HTTPS.
  • Authentication can be none, an access token, or a username and password. Credentials are stored in the macOS Keychain.
  • After you change the server, topic, or credentials, forwarding pauses until you confirm a new phone test.

If you self-host and use the ntfy iPhone app, read the ntfy documentation on iOS instant notifications. Without the upstream setting it describes, the iPhone app may show messages from your server late.

Pacing, limits, and retries

  • On ntfy.sh, NotiFerry sends about twelve messages a minute so a burst of Mac notifications does not trip the public server's rate limits. When delivery is at least 30 seconds behind and five or more queued alerts come from the same app, NotiFerry folds them into the newest alert with a count of earlier ones.
  • ntfy.sh documents a limit of 250 messages a day for anonymous publishing. NotiFerry keeps a local count and warns you as you approach it. It is meant for a handful of meaningful alerts, not a log stream.
  • If the server is unreachable, up to 1,000 privacy-filtered notifications wait in a local queue and are retried with increasing delays of at most a minute. A notification still unsent 10 minutes after it appeared is dropped rather than delivered late.
  • Pausing forwarding discards what arrives during the pause. Nothing is replayed when you resume.

NotiFerry is built and tested for delivery to the ntfy iPhone app. It publishes ordinary ntfy messages, so other clients subscribed to the same topic receive them too, but those combinations are not tested or supported.

The menu-bar app

See how NotiFerry runs on your Mac

Grant read-only access to the Notification Center folder (no Full Disk Access), subscribe to your private ntfy topic in the free iPhone app, and confirm that a real test arrived to start your 7-day trial.

Download 7-day free trial
brew install --cask n2ctech/tap/notiferry
What arrives on iPhone (in ntfy)
ntfynow

Claude Code — Permission required

Allow Bash tool in notiferry? · Full notification or Title only

ntfy · burst folded2m ago

Xcode — Build Succeeded (+4 earlier alerts)

NotiFerry dashboard on macOS with forwarding switched on, nine notifications forwarded this session, privacy mode, and buttons to send a phone test and copy the private topic link
NotiFerry on macOS: forwarding status, privacy mode, and one-click phone test confirmation.

Questions

Is NotiFerry an ntfy client for macOS?

No. NotiFerry publishes to ntfy; it does not subscribe. To receive ntfy messages on a Mac, use the ntfy web app in a browser or the ntfy command-line tool.

Does NotiFerry work with a self-hosted ntfy server?

Yes. Enter your server's HTTPS URL in Settings under Connection and choose no authentication, an access token, or a username and password. NotiFerry does not operate or audit your server.

Do I need an ntfy account?

Not for the default setup. NotiFerry publishes to a long random topic on the public ntfy.sh server without an account. An account or token is only needed if your own server, or a reserved topic, requires one.

Can ntfy read the forwarded notifications?

Yes. Transport is not end-to-end encrypted, and the ntfy server processes the text it relays; the public service may cache it for about 12 hours. Choose the title-only or generic privacy mode for anything sensitive, or use your own server.

Is NotiFerry affiliated with ntfy?

No. ntfy is an independent open-source project and service. NotiFerry is a separate commercial Mac app that publishes to it.

Founding release

A menu-bar route from Notification Center to ntfy.

The trial starts only after you confirm that a real test reached your phone. Keep NotiFerry with a one-time €9.99license for up to 2 Macs. Purchases include a 30-day full-refund window; mandatory consumer rights remain unaffected.

Download the 7-day free trialOr buy a license now · €9.99
brew install --cask n2ctech/tap/notiferry
One-time purchase · up to 2 Macs · periodic online license validation