Jacob Morrow
Updated: 2026-07-06
Your promo reads perfectly in the campaign editor. On a user's Lock Screen it stops at "Get 20% off your first..." and the code never shows. That gap is the push notification character limit at work: iOS, Android, and each browser render titles, body text, images, and buttons differently, so the same message can land clean on one device and truncate on another.
This guide gives practical writing targets for iOS app push, Android app push, desktop web push, and mobile web push, then separates those visible-copy targets from the backend payload-size checks that APNs and FCM actually enforce.
Quick answer
Start with a 35 to 50-character title and an 80 to 120-character body for broad cross-platform safety. For iOS-heavy campaigns, keep the title closer to 25 to 35 characters ; for Android collapsed views, a 90 to 150-character body can work after testing. Payload size is a separate engineering check: Apple APNs allows 4 KB for most remote notification payloads, and Firebase Cloud Messaging lists 4096 bytes for notification and data messages.
Last updated: July 2026.
Push Notification Character Limits: 2026 Cheat Sheet
Start with the shortest surface your campaign must support, not the largest possible API payload. A promo that looks fine in an expanded Android view may lose the offer on iOS. A web push with an image may show less body copy than the same push without an image.
| Platform | Safe visible title | Safe visible body | Payload / API limit | What usually causes truncation |
|---|---|---|---|---|
| iOS app push | 25 to 35 characters | 90 to 120 characters | APNs payload: 4 KB for most remote notifications; 5 KB for VoIP | Lock-screen layout, long app name, subtitle, image, notification summary |
| Android app push | 40 to 50 characters | 90 to 150 characters collapsed | FCM maximum payload: 4096 bytes for notification and data messages | Launcher skin, notification style, icon, image, action buttons |
| Desktop web push | 35 to 50 characters | 80 to 120 characters | Browser and service-worker implementation varies | Browser UI, OS notification center, image support, action buttons |
| Mobile web push | 30 to 45 characters | 60 to 100 characters | Browser implementation varies | Small screen, home-screen web app behavior, icon and image placement |
Treat these ranges as copy targets rather than legal limits. The safest pattern is simple: put the value, urgency, or status in the first half of the title, then use the body for one supporting detail and one action cue.
- Icon and image sizes:
plan around an 80x80px notification icon and a 360x180px
hero image. Larger rich media pushes visible text further down the card.
Push Notification Title, Body, and Message Length
Most truncation problems are not caused by the total push notification message length. They happen because the title, body, image, and action labels compete for the same compact card. Plan the notification as three separate writing fields:
| Field | Safe target | Best use |
|---|---|---|
| Title | 35 to 50 characters, shorter for iOS-heavy campaigns | Put the status, offer, or trigger here: order shipped, price drop, payment received. |
| Body text | 80 to 120 characters for broad cross-platform safety | Add one useful detail and one action cue. Do not bury the main value in sentence two. |
| Action labels | 1 to 2 short words | Use direct verbs such as View, Track, Pay, Reply, or Open. |
This split also keeps app push notification character limits under control across markets. Translated copy usually runs longer than English, so hand translators a short source message rather than a long sentence they have to squeeze back down.
Display Length vs. Payload Size
Many push articles mix two different ideas. Display length is what the user can read before the OS or browser cuts off the notification. Payload size is the amount of data your push service accepts before the request is rejected. You need both, but they solve different problems.
The practical rule
Payload limits tell engineering whether a request can be sent. Character limits tell marketing and product whether the message can be understood. A 300-character body may fit in a payload, but users may only see the first 90 to 120 characters until they expand it.
Apple says APNs refuses a notification when the total payload exceeds 4 KB for most remote notifications and 5 KB for VoIP notifications. Firebase says the maximum payload for FCM notification and data messages is 4096 bytes . MDN documents web notification fields in the Notification API , but final display still depends on the browser and operating system.
- Web notification fields:
Use title , body , icon , image , and actions
as display inputs, then test the final rendering by browser.
iOS Push Notification Character Limit
For iOS app push, write as if the user will only skim one compact card. A title near 25 to 35 characters and a body near 90 to 120 characters gives the message a strong chance of staying readable on the Lock Screen and in Notification Center. Longer messages may still be accessible after expansion, but the first impression is short.
- Title: keep the main status or offer short, such as "Order shipped" or "Price drop today".
- Body: add one useful detail, such as item name, amount, time window, or next action.
- Subtitle: use only when it clarifies context; it competes with title and body for visible space.
- Rich media: images and notification summaries can reduce how much text is visible at first glance.
Send through APNs directly and the platform constraint is JSON payload size. For campaign writing, the question that matters is whether the user grasps the message before tapping, so the copy should carry its essential meaning before the body reaches 100 characters.
Android Push Notification Character Limit
Android gives teams more layout flexibility, but it also has more variation across devices, launchers, and manufacturer skins. A practical safe target is a 40 to 50-character title and a 90 to 150-character body in the collapsed view.
- Collapsed notification: optimize for the first line. Users may never expand the card.
- Big text style: useful for service alerts or receipts, but the expanded copy should still begin with the decision-making detail.
- Action buttons: keep labels short, such as "View", "Track", "Pay", or "Reply".
- Images: rich push can improve recognition, but it can also compress visible text on smaller screens.
FCM payload size is measured in bytes, not marketing copy characters. Multi-byte characters, custom data, tracking fields, and localization keys all count toward the payload. If your message uses multiple languages or custom payload fields, engineering should test the byte size while marketing tests visible copy length.
iOS vs. Android Push Notification Character Limits
For teams comparing the push notification character limit on iOS and Android, the difference that matters is first-view layout, not backend payload size. iOS is usually stricter in the collapsed lock-screen view, while Android gives more room but varies by device maker, launcher, and notification style.
| Question | iOS practical answer | Android practical answer |
|---|---|---|
| How short should the title be? | 25 to 35 characters is safest for lock-screen readability. | 40 to 50 characters can work in many collapsed views. |
| How much body text is visible? | Plan around 90 to 120 characters before expansion. | Plan around 90 to 150 characters, then test on common OEM skins. |
| What breaks the layout fastest? | Long app names, subtitles, images, notification summaries, and crowded first lines. | Images, action buttons, BigPicture/BigText styles, icons, and manufacturer UI changes. |
| Best default copy pattern | Short title plus one complete body sentence. | Short title plus a body that still works before the user expands it. |
If one campaign must cover both platforms, write for iOS first and let Android benefit from the extra room. If Android is your dominant audience, test a richer body variant, but keep the first 100 characters meaningful enough to stand alone.
Web Push Notification Character Limit
Web push is the least consistent surface because Chrome, Edge, Firefox, and Safari each render notification cards differently. Desktop operating systems also affect the final layout. For broad compatibility, keep the title around 35 to 50 characters and the body around 80 to 120 characters .
| Web push surface | Safe writing target | Copy note |
|---|---|---|
| Chrome / Edge desktop | Title 35 to 50, body 80 to 120 | Works well for campaign alerts, cart recovery, content updates, and price drops. |
| Firefox desktop | Title 30 to 45, body 80 to 120 | Be conservative with action labels and rich media assumptions. |
| Safari desktop | Title 30 to 45, body 70 to 110 | Keep the brand/context clear because visual treatment differs from Chromium browsers. |
| Mobile web push | Title 30 to 45, body 60 to 100 | Use the shortest version of the message when the campaign must work on small screens. |
Web push copy should avoid relying on the second sentence. If the push needs an image, button, or deep link, write the title and first body phrase as a complete message on their own.
Push Notification Examples That Fit the Character Limit
A useful push notification has one job. It either confirms a status, creates urgency, reminds the user of an unfinished action, or pulls them back into a relevant moment. These examples use safe lengths that can survive iOS, Android, and web push with minimal rewrites.
| Use case | Better title | Better body | Why it works |
|---|---|---|---|
| Cart recovery | Your cart is waiting | Checkout in 10 minutes to keep today's offer. | The value and timing are visible before truncation. |
| Order update | Order shipped | Track package EL-2048 from your account. | Status first, detail second, clear next action. |
| Fintech alert | Payment received | $128.40 arrived in your wallet at 09:42. | The user gets the essential trust signal quickly. |
| Content app | New report is live | Read the 2026 retention benchmark in 4 minutes. | Specific enough to beat generic "new update" copy. |
| Reactivation | Still planning your trip? | Flights to Seoul dropped 18% this week. | Relevant trigger plus a measurable reason to return. |
How to Write and Test Push Copy Without Truncation
Character-limit work is easier when the campaign builder forces a preview and the analytics loop tells you what happened after delivery. In EngageLab AppPush , build the message around the same sequence your team will use in production: write the notification, target the audience, test a short and long variant, then compare delivery and conversion data.
Step 1. Write the Short Version First
Open Create Push and draft the message in the notification content area. Start with the shortest cross-platform version: one title, one body, one destination. If the push needs an image or Android/iOS-specific settings, add those only after the core message reads clearly without them.
A good review rule is simple: if the title alone does not explain the notification, shorten the idea before adding more body text. Treat a push as a doorway. Give users just enough to step through, then let the app carry the detail.
Step 2. Test Two Lengths Before Scaling
Create an A/B Test when the message has enough volume to learn from. Use one concise version and one richer version. Keep the audience, send time, image, and destination consistent, so the main difference is copy length and phrasing.
Compare short vs. long variants by open rate, click rate, and downstream action. A longer body can win when users need context, but many promotional and transactional messages perform better when the first line carries the decision.
Step 3. Measure Conversion, Not Just Delivery
After sending, use Conversion Analysis to review the funnel from target users to delivered messages, clicks, and conversion events. A copy variant that produces fewer clicks but more completed actions may be the better campaign.
Need one place to create, test, and measure push campaigns?
- Compose app push campaigns with iOS, Android, and audience targeting controls.
- Run A/B tests for short vs. detailed copy before scaling to the full audience.
- Review delivery, click, and conversion data from one AppPush reporting view.
Push Notification Character Limit Best Practices Checklist
Use this checklist before sending a campaign that must work across iOS, Android, and web push:
- Write the title first: keep it around 35 to 50 characters, or shorter for iOS-heavy campaigns.
- Make the first body line complete: assume users may only see the first 80 to 120 characters.
- Test with and without rich media: images and action buttons can reduce visible copy.
- Localize by meaning, not literal length: German, Spanish, Arabic, and other languages may need shorter source copy.
- Separate payload QA from copy QA: engineering checks byte size; marketing checks display readability.
- Track action completion: delivery and open rate are not enough if the push is meant to drive a purchase, verification, or return session.
Push Notification Character Limits FAQ
What is the character limit for a push notification?
There is no single character limit for all push notifications. A safe cross-platform target is a 35 to 50-character title and an 80 to 120-character body. Platform payload limits are separate: APNs allows 4 KB for most remote notification payloads, while FCM lists 4096 bytes for notification and data messages.
What is the iOS push notification character limit?
For visible copy, aim for a 25 to 35-character title and a 90 to 120-character body. iOS may show more after expansion, but the lock-screen preview is compact. APNs payload size is a byte limit, not a promise that all text appears on screen.
What is the Android push notification character limit?
For Android, keep the title around 40 to 50 characters and the collapsed body around 90 to 150 characters. Some Android styles can show more expanded text, but OEM skins and notification layouts vary, so the most important words should come first.
How long should a web push notification be?
For web push, a safe target is a 35 to 50-character title and an 80 to 120-character body on desktop. Mobile web push should be shorter, usually a 30 to 45-character title and a 60 to 100-character body, because browser and OS layouts vary more.
What is the push notification title and body character limit?
A practical push notification title character limit is 35 to 50 characters across platforms, with 25 to 35 characters safer for iOS-heavy audiences. A practical push notification body character limit is 80 to 120 characters for broad safety. Android can often show more text, but the first line should still communicate the main value.
How do I test push notification truncation?
Send test notifications to real iOS, Android, desktop Chrome, and Safari devices before a full campaign. Screenshot the collapsed view, expanded view, and notification center view. Then run A/B tests on short vs. longer copy and compare conversion rate, not only opens.
Bottom Line
Push notification character limits are best handled as a writing and testing discipline, not as one fixed number. Keep the title short, make the first body line useful, and validate the message on the devices your audience actually uses. Payload limits matter to engineering, but visible copy length is what determines whether the user understands the notification.
If your team wants to write, test, target, and measure push campaigns from one workflow, EngageLab AppPush gives product and growth teams a practical way to manage iOS, Android, and cross-channel push journeys without treating every campaign as a custom engineering project.
