Documentation
Web Inbox: receive and reply in your browser
Authorize a browser from your iPhone or Android phone, read new encrypted messages and answer questions on a larger screen.
Updated
Connect an existing Topic
#Open the Web Inbox on the computer. On your primary phone, open the Topic’s connection action and scan the browser’s current QR code. Confirm the expected browser and Topic. Codes expire after five minutes; create a new one if it expires. The Web Inbox is an optional receiver, while the iPhone remains the management device.
- Open app.ntfyx.me and display its connection QR.
- Open the protected Topic’s menu > Connect browser on your phone, then scan and confirm the browser.
- Keep the Web Inbox open to receive new messages and send replies.
Read and answer
#A connected browser receives new messages addressed to it and decrypts them locally. It can answer Allow / Deny, choice and text requests, using its own signing key. An answer is not permission for an unrelated action. A newly connected browser cannot see the earlier phone history. Browsers are subject to the same service limits; adding one does not require creating a second Topic.
Revoke browser access
#Use the primary phone’s Topic settings to revoke a browser you no longer trust. Revocation stops future authorized access and delivery. It cannot erase content already delivered to that browser. Clear the local browser data separately when leaving a shared computer. Do not share your recovery code or pairing links.
Only the sources you choose
#The Web Inbox shows new encrypted messages addressed to this authorized browser, from your authorized agents and tools or official public-content subscriptions you explicitly choose. Each subscription Topic needs separate phone authorization for a browser receiver. It does not insert advertisements or unrelated content.
A new browser cannot obtain earlier phone history.
Session conversations
#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.
Chrome notifications and 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.
Plain and rich messages
#CLI 0.6.0 independently sends ordinary text, Markdown and native metric/table/chart messages, with local validation before sending. See the guide for receiver version requirements and store availability.