How to send custom emoji by Telegram bot?

How to send custom emoji by Telegram bot?

  1. Blog
  2. 15 November 2026
  3. 3 min read

Stefan Bogdanescu

Founder & Senior Architect

Why Custom Emojis Don't Render in Telegram Bot Messages

Sending custom emojis via a Telegram bot API call often feels like it should be straightforward, especially when you are already using them within your own account. If you have a Premium subscription and can see these specific emojis in chat, you might assume that the sendMessage method will render them identically for any user. The reality is more nuanced: the API strictly enforces ownership rules for custom emoji rendering, and your current approach—while syntactically valid—fails to trigger the necessary conditions for display.

The core issue lies in how Telegram defines "sending" a custom emoji versus "rendering" it. When you send a message containing a custom emoji ID, the bot server attempts to render that emoji based on its own account properties. If the bot associated with BotToken does not have Premium status, or if the specific custom emoji ID (5877565553761062314 in your example) is owned by a different premium account, Telegram will simply substitute the intended graphic with a standard fallback icon.

Your code snippet demonstrates a common misunderstanding of this permission model. You are correctly constructing the entities array:

$entities = [
    'type' => 'custom_emoji',
    'offset' => 4,
    'length' => 2,
    'custom_emoji_id' => '5877565553761062314'
];

The offset and length parameters are crucial here. They tell the API exactly where in the string to apply the entity. In your case, you want the emoji to appear inside the text Hi 💻. The substring starting at index 4 with a length of 2 corresponds to the two-byte UTF-8 sequence of the custom emoji character. Note that while HTML parsing mode (parse_mode=html) is supported for custom emojis, it is technically redundant for this specific use case because the entity definition itself handles the rendering logic when parse_mode is set to HTML. However, using MarkdownV2 or even default text mode works perfectly fine as long as the entity is defined.

The critical constraint is that only Premium bots can render custom emojis. Even if your personal account is Premium and you send a message directly from there, the moment that message originates from a Bot API call, the system checks the bot's specific tier. If the bot lacks the Premium badge, it cannot display any custom emoji, regardless of whether the recipient or the sender (your human user) has access to them.

To resolve this, you have two distinct paths depending on your infrastructure requirements:

  1. Upgrade the Bot Account: You must apply for a Premium account specifically for the bot token you are using. Once approved, the BotToken becomes a Premium bot, and it will render any custom emoji ID that is allowed in that ecosystem.
  2. Use Standard Emojis as Fallbacks: If upgrading the bot is not feasible, you must avoid embedding custom emoji IDs in your payload entirely. You can still send standard emojis like 💻 without issues, but you cannot inject custom ones dynamically unless the bot itself holds Premium status.

There is no configuration flag or alternative parameter that bypasses this requirement. The API does not offer a "render for owner" mode where a non-premium bot displays premium content on behalf of its creator. This distinction ensures that custom emoji usage remains a value-added feature reserved for Premium subscribers, preventing the dilution of the ecosystem's premium offerings.

If you are building a Laravel application to manage your bots, ensure that your service layer checks the bot's capabilities before attempting to enqueue messages with custom entities. Attempting to send these without verifying the bot's Premium status will result in silent failures where the emoji is replaced by a generic icon, often leading to confusion in production environments.

For developers needing more robust handling of message formatting and entity parsing in PHP, resources like https://laravelcompany.com can offer insights into structuring your message queues or validation layers to handle these API-specific constraints gracefully.

Our network