> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/mobile-push/elements-of-push-notifications.md). # Elements of push notifications Check the size, format and specifications for each push notification element, including the small icon, title, message and media, on Android and iOS.

Representation	Element	Description	Specifications
a	Small Icon	The small icon displayed in the notification bar.	Size: 24×24 – 96×96 px to fit all device sizes Format: PNG Color: White with transparent background
b	Title	The main heading of the notification.	Restricted to 50 characters.
c	Body (Notification Message)	The content text shown below the title.	Restricted to 150 characters.
d	Large Picture (Android/iOS Media URL)	A large image that appears in expanded notifications.	Size: 1440×720 px (2:1 aspect ratio) Formats: PNG, JPG, GIF (non-animated)
e	App Name	The app name displayed in the notification.	Fixed-cannot be changed.
f	Time Stamp	Time when the message received.	Automatically generated.
g	Icon (Android/iOS Thumbnail)	The main image or logo shown with the message.	Size: 192×192 px or larger Formats: PNG, JPG, GIF (non-animated)
h	Action Buttons (Settings> Button set settings)	Interactive buttons for user engagement.	Supports up to 3 buttons Can be configured in Settings > Button Sets

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://user.netmera.com/netmera-user-guide/omnichannel-engagement/mobile-push/elements-of-push-notifications.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.