Legacy: Browser Push Best Practices

here are common layout guides to follow for push notifications across all platforms notification content details character limits https //documentation onesignal com/docs/push notification guide#character limits how many characters are allowed and recommended per platform emoji https //documentation onesignal com/docs/push notification guide#emojis support is available across all platforms 👍 images https //documentation onesignal com/docs/web push notification icons#image large images that appear with the notification supported by chrome on windows, macos, and android icons https //documentation onesignal com/docs/web push notification icons#badge supported on all platforms customizable for chrome and firefox sounds not customizable on web push web push badges https //documentation onesignal com/docs/web push notification icons#badge small icons on chrome for android that appear in top notification center when push is received action buttons https //documentation onesignal com/docs/action buttons custom buttons that can support different actions or links character limit since each platform uses a different visual layout, the amount of content that is visible varies the following are approximations for how many characters are in a notification based on the browser platform platform title limit body limit ℹ️ aiq recommendation ℹ️ 20 ℹ️ 60 windows chrome 60 (chrome 68+) 40 (chrome 67 and lower) 120 (chrome 68+) 150 (chrome 67 and lower) windows firefox 40 190 mac chrome, firefox, safari 40 20 80 emojis count as a single character simply copy paste the emoji you want into the message or title some limitations on windows 7 and older operating systems