ntfy
Send push notifications to your phone or desktop via simple HTTP.
Open the official app on ntfy.sh
This tool is hosted by its maintainers. Click below to open ntfy.sh in a new tab — it's their official demo.
Browse text & tools tools →What's next with ntfy?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is ntfy?
ntfy is an open-source HTTP-based pub-sub notification service that enables users to send push notifications to their phones or desktops via scripts or REST APIs. Developed under the Apache-2.0 license, it developers and power users to trigger alerts for automation workflows, system events, or custom applications without requiring complex infrastructure. The tool is particularly valuable for those needing real-time updates across devices, such as monitoring system health, tracking file transfers, or notifying about security incidents. Its simplicity and flexibility make it popular among DevOps engineers, scripters, and developers who want lightweight, customizable notification solutions. By eliminating the need for app integrations or proprietary services, ntfy streamlines the process of delivering timely alerts through a single, unified interface.
How it works
ntfy is a notification service that leverages HTTP protocols to broadcast messages to subscribed devices. It operates as a server that accepts PUT or POST requests, allowing users to publish messages to specific topics. These topics act as unique identifiers, functioning similarly to passwords when used without sign-up. The primary purpose of ntfy is to bridge the gap between automated systems and user devices. It enables communication between scripts, applications, and end-user devices, ensuring critical information is delivered instantly. This makes it ideal for scenarios requiring real-time feedback, such as monitoring server statuses or triggering alerts for automation workflows. ntfy supports rich notification features including priority levels, action buttons, emojis, and attachments. For example, a script can send a high-priority alert with a vibration pattern and a custom icon. Topics are dynamically created by publishing to them, and users can subscribe via webhooks or client libraries to receive notifications. The tool also allows for self-hosting, giving users full control over their notification infrastructure.
How to use it
- 1Choose a deployment method: Use ntfy.sh for quick one-off notifications via curl, or self-host the server using binaries, Docker, or package managers. 2. Create a topic: Generate a unique identifier (e.g., 'mytopic') that acts as a password for your notification channel. 3. Subscribe to the topic: Configure a client (e.g., a mobile app, web interface, or script) to listen for messages on the topic. 4. Send a notification: Use curl or an API to POST data to ntfy.sh/mytopic, including optional metadata like priority or emojis. Practical tips include using HTTPS for security, avoiding guessable topic names, and leveraging the CLI for automation. For self-hosted instances, configure the server with a domain name and SSL certificate to ensure reliable delivery.
What it can do
- push notifications
Use cases
Assumptions and limitations
Assumptions
- source: https://github.com/binwiederhier/ntfy
- license: Apache-2.0 — free to use
- privacy: Self-hosted — you control your data
Limitations
- Requires manual topic management without Pro subscription
- Lacks built-in authentication mechanisms for public topics
- Depends on internet connectivity for both sending and receiving notifications
- Limited customization options for notification appearance without Pro features
- No native support for push notification services like Firebase Cloud Messaging
Understanding the result
Send push notifications to your phone or desktop via simple HTTP.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by (Apache-2.0).
- Built with
- (binwiederhier/ntfy)
- License
- Apache-2.0
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Query
- Output
- Text
Built with binwiederhier/ntfy. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- License
- Apache-2.0
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- / — GitHub Repository
Upstream project · GitHub
- Apache-2.0 License
Upstream project
Frequently asked
How does ntfy handle notification delivery without a sign-up process?
ntfy uses topics as temporary passwords for notifications. When a user sends a message to a topic (e.g., ntfy.sh/mytopic), anyone with access to that topic URL can subscribe and receive notifications. This simplifies usage but requires users to manage topic security, as public topics can be accessed by anyone guessing the URL. The Pro version allows reserved topic names to mitigate this risk.
How does ntfy's pub-sub model work technically?
ntfy operates as a message broker where publishers send HTTP POST/PUT requests to specific topics. Subscribers connect to the same topic via webhooks or client libraries, receiving messages in real time. The service scales horizontally, allowing multiple subscribers to receive the same message simultaneously. Messages are delivered as raw text or JSON, with metadata like priority and attachments handled through headers or payload fields.
How do I send a notification with an emoji and action button?
Include the emoji directly in the message payload and use headers to define action buttons. For example: curl -d 'Backup successful 😊' -H 'Title: Backup Complete' -H 'Btn: View Logs' ntfy.sh/mytopic. This sends a notification with the emoji and a clickable button that triggers a predefined action when tapped.
How does ntfy compare to alternatives like Pushover or Firebase?
ntfy differs from Pushover and Firebase by using HTTP/REST APIs instead of proprietary SDKs, making it more flexible for custom integrations. Unlike Firebase, it lacks real-time database capabilities but focuses solely on notifications. Pushover offers built-in authentication and priority levels, while ntfy requires manual topic management. ntfy's open-source nature allows deeper customization but lacks the managed infrastructure of cloud-based alternatives.
What should I do if I get a 404 error when sending a notification?
A 404 error indicates the topic URL is invalid. Verify the topic name is correctly spelled and matches the subscription URL. If using ntfy.sh, ensure the topic exists by testing with curl. For self-hosted instances, check the server logs for errors and confirm the topic is properly configured in the server's routing settings.