Paste an APNs, FCM or Web Push payload. See roughly how it draws on each platform, and — more usefully — which fields are going to do nothing at all.
Runs entirely in your browser. Nothing is uploaded, nothing is logged, and there is no account. Paste a real payload if you want to.
Every push API will happily accept a payload that displays nothing, and none of them tell you. The three that catch people most often:
data block. A message with no
notification object is not displayed by the system — your app is expected
to build the notification itself, and if it is not in the foreground on Android, or
lacks content-available on iOS, nothing appears. The send reports success.channel_id the app has not created is dropped by the
system. FCM still reports it delivered.mutable-content. Attachments are
fetched by a Notification Service Extension, and the extension only runs when
mutable-content is set. Without it the notification arrives, correctly,
with no picture.The previews above are approximate — every platform and OEM styles notifications its own way, and some fields only take effect once your app handles them. The findings are the part worth reading.
The authoritative sources, since this tool is a convenience and not a specification: Apple, generating a remote notification · FCM HTTP v1 message reference · MDN, showNotification options.
We send push, email, SMS, in-app messages and an in-app inbox to one audience through one API, on your own Firebase, APNs and SMTP credentials. The docs are at notibase.dev — including every field a message can carry and what each delivery error actually means. If you are moving from somewhere else, the migration guide says what travels and what cannot.