Download Ntfyx for Windows, macOS, Linux and your phone

As of 2026-10-29, confirmed public releases are iOS 1.8.3 and Android 1.8.2. Update from your store, then use the public Topic or private connection entry on your phone. Android background push requires Google Play services.

• Connect Claude Code / Codex to your phone
• Existing public Topic: first message
• HTTPS push
• Quickstart and mode choice
• Creation and notification troubleshooting

On a computer, choose App Store or Google Play above to scan a download QR code with your phone camera. On a phone, the button opens the store directly. Direct store links also work without JavaScript. Download codes are public store links, not pairing or authorization codes.

Ntfyx 1.8.3 is publicly available for iOS 18.4 or later. Confirm requests or write quoted replies; related task messages stay in one conversation. Your phone authorizes CLI and browser connections. No Ntfyx account is required.

• Download on the App Store

Ntfyx 1.8.2 is publicly available for Android 10 or later. Confirm requests, choose options or send a text reply. Google Play services are needed for push; foreground Inbox use remains available without notification permission.

• Get Ntfyx on Google Play

Open Discover on your phone, choose a notification source, then review its scope, schedule and notification preference before confirming. Free includes one shared subscription slot for a notification source or public Topic follow. Topic count is not a paid entitlement; every plan has a 1,000-Topic technical limit.

No computer, CLI or pairing scan is required for subscriptions. Pause or unsubscribe whenever you want.

• Browse the notification marketplace

Complete CLI and local MCP for Windows x64 / ARM64, macOS Apple silicon / Intel and Linux glibc x64 / ARM64, including phone-authorized monitor and webhook management. Every binary and archive is authenticated by the Ntfyx release signature. macOS Developer ID signing and notarization are recorded separately from native runtime acceptance.

• macOS Apple silicon
• macOS Intel
• Linux glibc x64
• Linux glibc ARM64
• Windows x64
• Windows ARM64
• Windows x64 executable
• Windows ARM64 executable

Six release targets are available: macOS Apple silicon / Intel, Linux glibc x64 / ARM64 and Windows x64 / ARM64. Both Mac binaries carry Developer ID signatures and accepted Apple notarization. Linux x64 and Apple silicon completion hooks were tested using the actual signed release input and an isolated encrypted receiver.

Native installer and upgrade checks are recorded separately; Linux ARM64 native execution and receipt on the user’s own phone were not verified in this release.

The encrypted Web Inbox and API are live. A compatible primary iPhone or Android phone authorizes the browser as an additional receiver with independent keys. The browser does not acquire the phone management identity or earlier message history.

• Open the Web Inbox

The installer checks the release signature and the exact binary checksum before replacing an executable. The application remains proprietary; third-party licenses and runtime replacement rights are included with the release.

• Signed release manifest
• Manifest signature
• SHA256 checksums
• Checksum signature
• Release public key
• License
• Third-party notices
• Runtime library replacement instructions

CLI 0.1.3 and current clients group related messages into Sessions within a Topic. Confirm or choose on the original message; select Reply for a quoted text answer. CLI 0.1.3 includes --session-id and --session-name; run ntfyx upgrade to update. Read the guide for examples, standalone-message defaults and availability.

• Sessions and message replies

Chrome extension 0.2.4 is publicly listed on the Chrome Web Store. The current protected-message protocol requires Chrome 0.4.0, submitted and still under review as of 28 October 2026. The public 0.2.4 listing does not establish compatibility with that protocol. Use the phone-authorized Web Inbox while waiting for the compatible extension.

The extension provides desktop notifications, a phone-authorized Inbox and original-message replies. Each Topic needs its own phone authorization; Chrome must stay running for background checks. The current Web Inbox remains available.

• Chrome extension: setup and publication status

Runtime requirements: Windows 10 1809+, macOS 13+, and glibc-based Linux. x64 CPUs require Nehalem / SSE4.2 or newer; AVX2 is not required. These are the official requirements for the embedded Bun 1.4.2 runtime; tested systems are recorded separately.

• Bun 1.4.2 official system and CPU requirements

Rich rendering requires iOS/Android 1.8.0, Chrome 0.4.0 or the updated Web Inbox. Verified public store versions are iOS 1.8.3, Android 1.8.2 and Chrome 0.2.4. Upgrade when the required version is available in your store. Rich rendering is already live in the Web Inbox.

• Rich-message formats and complete example