Quick Answer
Telegram widgets turn bot messages into small interactive HTML apps that run inside private chats, rather than opening a separate web page. Telegram added the feature in Bot API 10.4 on November 9, 2026, with tight sandbox and size limits. Use widgets for simple polls, codes, or live indicators, but do not treat them as full web apps or payment guarantees.
Key Takeaways
- Telegram Bot API 10.4 added the Widget class and sendWidget method on November 9, 2026.
- Telegram widgets render directly inside a chat message instead of opening a separate page.
- Production widgets currently work only in a user’s private chat with a bot.
- Widget HTML is capped at 32,768 bytes and compressed widget data is capped at 4,096 bytes.
- Telegram blocks network requests, external scripts, fonts, images, and WebSockets inside widgets.
What are Telegram widgets?
Telegram widgets are small interactive blocks that appear directly inside a bot message. Telegram’s November 12 documentation describes each widget as a self-contained HTML document with inline CSS and JavaScript, which means a user can interact with a poll, game, ticker, or promotional code without leaving the chat.
Telegram widgets differ from ordinary links and traditional bot buttons because the interactive interface renders within the message itself. The approach reduces the number of app or browser transitions required for a narrow task, although the feature does not replace a normal website or a full Telegram Mini App.
Telegram’s documented examples include moving poll bars, price tickers, two-player board games, and tap-to-copy promo codes. Those examples show the intended scope: short, contained interactions that fit naturally into a message thread instead of complex interfaces that need unrestricted storage, media, or network access.
How did Telegram add HTML widgets to messages?
Telegram added HTML widgets through Bot API 10.4 on November 9, 2026. The update introduced a new Widget class and sendWidget method, giving bot developers a defined way to attach interactive content to a message. Telegram’s Bot API changelog also lists new widget-query types for data, TON-wallet-signed data, and notices that a TON-wallet transaction was sent.
Telegram framed the launch as a broader change to how messages can work. Pavel Durov said that “Any Telegram message can now become an app,” pointing to instant downloads, native rendering, payments, and viral mechanics in a Telegram Bot News announcement. The practical meaning is more limited than that slogan suggests, because production widgets have strict placement, size, and networking restrictions.
Telegram widgets therefore give bots a new presentation layer rather than unrestricted app access. A bot can show information in a compact interactive format, but the bot remains responsible for sending the widget and handling the limited requests that the widget returns.
Where do Telegram widgets work today?
Telegram widgets currently work in production only in a user’s private chat with a bot. Telegram’s November 12 documentation says that group-chat widgets, inline-mode widgets, and forwarded widgets remain limited to the test server, so developers cannot assume that a widget sent in a group will work for normal users.
Telegram also automatically applies protected content to production widgets sent in private chats. Protected content prevents the message from being forwarded, which matters because a widget may contain a personalized state, a limited-use code, or information that is only useful in the original bot conversation.
| Widget capability | Current production status | What the limit means |
|---|---|---|
| Private chat with a bot | Available | Users can receive and interact with widgets in one-to-one bot chats. |
| Group chats | Test server only | Developers cannot rely on group distribution for a public bot rollout. |
| Inline mode | Test server only | Widgets cannot currently be inserted through normal inline bot results. |
| Forwarding | Blocked in production private chats | Protected content keeps the widget message in the original chat. |
The private-chat requirement makes Telegram widgets better suited to direct bot interactions than shared social experiences. Users who want broadly shareable content still need ordinary messages, links, or other Telegram features that can travel between chats.
What can Telegram widgets do inside a chat?
Telegram widgets can display lightweight interactions that fit inside a message, including live-looking indicators, choices, short games, and copyable information. The documented examples of poll bars, price tickers, board games, and promo codes show that the feature supports visual state changes and user input within a deliberately constrained message container.
Telegram widgets can also send a request of up to 64 bytes to the bot. That limit means the widget can return a compact instruction, selection, or identifier, but it cannot send large forms, media files, or detailed records directly through the widget request channel.
Only the bot can update a widget’s data or shared state. That architecture gives the bot the authoritative role in the interaction, while the widget serves as the interface shown to the user. For a poll, for example, the bot can update displayed bars after receiving a user action, rather than allowing the HTML block to independently change shared results.
Telegram widgets may make bot conversations feel more immediate, particularly for tasks that normally require a separate page. At the same time, users should treat the widget as part of a bot interaction and verify what the bot is asking for before approving a payment-related or wallet-related action.
What limits do Telegram widgets have?
Telegram widgets have strict file-size limits and browser-like features are intentionally absent. Telegram caps the HTML document at 32,768 bytes and caps the widget after zlib level-9 compression at 4,096 bytes. Those limits require developers to keep interfaces small and avoid the large assets and libraries commonly used by conventional web pages.
Telegram widgets run in a QuickJS sandbox rather than a WebView. Telegram’s documentation says that fetch, XMLHttpRequest, WebSocket, external scripts, fonts, and images are disabled. The restriction prevents a widget from behaving like an ordinary network-connected page, while also limiting dynamic content, third-party tracking components, and externally hosted visual assets.
The sandbox design means a ticker or game must work through the widget’s limited interaction model and bot-controlled updates. A developer cannot build a widget that independently loads a new image, calls a remote API from the message, or opens a persistent WebSocket connection for continuous live data.
Telegram widgets are therefore most useful when the core interaction is compact. Developers should keep the HTML, styling, and logic focused on one task, then use the bot for state changes and any broader workflow that the platform supports.
Are Telegram widgets private and secure?
Telegram widgets have meaningful privacy and security boundaries, but users should still evaluate the bot behind the widget. Production widgets in private chats use protected content and cannot be forwarded, while the QuickJS sandbox blocks several common web capabilities, including remote network requests and external scripts.
Telegram’s design reduces the scope for a widget to operate as an unrestricted web page, but it does not establish that every bot is trustworthy. A widget can still ask a user to make a choice, send a short request to a bot, or proceed with a wallet-related flow. The most sensible response is to use widgets from bots you recognize and to review any payment or wallet prompt before confirming it.
Telegram users should also keep the main app updated because messaging-platform security depends on both feature design and client updates. The recent Telegram Android call security issue illustrates why a newly introduced feature does not remove the need to install available security fixes.
How should bot developers plan a Telegram widget?
Telegram widget developers should design for a private-chat, low-bandwidth interaction from the beginning. The feature’s production placement rules, 32,768-byte HTML cap, 4,096-byte compressed limit, and blocked network APIs mean that a conventional responsive web page is not an appropriate starting point.
- Choose one contained task. Build around a single interaction, such as selecting a poll response, copying a code, or making a move in a board game.
- Keep the document self-contained. Place required HTML, CSS, and JavaScript inside the widget because external scripts, fonts, and images are disabled.
- Minimize returned data. Design interactions around a request of no more than 64 bytes, using compact values that the bot can interpret.
- Test the private-chat flow. Confirm that the experience works in a direct conversation with the bot, because groups, inline mode, and forwarding are not production paths.
Telegram widget developers should also explain what a widget will do before asking for a user action. Clear labels and narrow interactions matter because the message format can make a bot feature feel native to the chat, even when the bot’s service, policies, and any transaction are separate from Telegram itself.
Users who are unsure how to assess a suspicious bot should start with the basic principles of safe account and device security: verify the sender, avoid entering sensitive information into unexpected prompts, and stop if a request does not match the bot’s stated purpose.
Telegram widgets are not a reason to move every bot workflow into a message. A normal web page or a broader app experience remains more appropriate when a service needs rich media, ongoing network data, extensive forms, account management, or information that users need to share widely.
What do Telegram widgets mean for messaging apps?
Telegram widgets make chat messages more capable without requiring a separate browsing step for every small task. The feature gives bot developers a compact interface for interactions that would otherwise appear as static text, buttons, or external links, and independent launch coverage has described the change as a move toward message-level mini apps. Digital Trends’ launch coverage notes the same shift toward in-chat experiences.
Telegram’s current restrictions are as important as the new interface. Private-chat-only production support and the sandbox limitations mean that Telegram has introduced a controlled message component, not a general-purpose browser inside every conversation.
For most users, Telegram widgets will matter when a bot uses them to reduce friction on a simple task. A poll that updates inside a message or a code that copies with one tap can be useful. A complex service that needs a large form, continuous data, or broad sharing will still need another interface.
FAQ
What are Telegram widgets?
Telegram widgets are small interactive HTML blocks that bots can render directly inside a chat message. Telegram widgets can support compact experiences such as polls, price tickers, board games, and tap-to-copy codes without opening a separate web page.
Do Telegram widgets work in group chats?
Telegram widgets do not currently work in production group chats. Telegram’s documentation says group support remains available only on the test server, alongside inline-mode and forwarding support.
Can Telegram widgets access the internet?
Telegram widgets cannot make ordinary network requests from the embedded interface. Telegram disables fetch, XMLHttpRequest, WebSocket, external scripts, fonts, and images because widgets run in a QuickJS sandbox rather than a WebView.
Can Telegram widgets be forwarded?
Telegram widgets sent to private chats cannot be forwarded in production. Telegram automatically applies protected content to those widget messages, which keeps the interaction in the original bot conversation.
How much data can a Telegram widget send to a bot?
Telegram widgets can send requests of up to 64 bytes to their bot. Telegram limits that channel to compact selections or identifiers, while only the bot can update widget data or shared state.