How to Pin a Message on Telegram and Who Gets Told

Pinning is the one feature everybody uses and nobody reads about. You hold a message, you pick pin, and a bar appears at the top of the chat. That is the whole of it for most people, and it is also where three genuinely useful options are hiding.

Here is the short version. Pinning sets a flag on the message rather than moving it anywhere. One call does pinning and unpinning, and it carries a flag that pins without notifying anybody. In a one-to-one chat there is a flag that pins the message only on your side. And in a group, pinning is a permission that can be granted and taken away separately from everything else.

What follows covers what pinning changes, the call behind it, the silent option, the one-sided pin, who is allowed to pin, how channels differ, pinning more than one message, unpinning one or all of them, pins inside forum topics, what the room sees, finding pinned messages later, why pinning a chat is a different feature, and what teams running many rooms get wrong. Every rule quoted below was pulled from Telegram's own documentation on 13 August 2026.

What Pinning Actually Does to a Message

The mechanism is smaller than the interface suggests, and knowing it explains the rest.

A flag on the message

Every message object carries a pinned flag, and pinning sets it. The message does not move, it is not copied to the top of the chat, and its identifier does not change. What changes is one bit and the bar your client draws from it. Everything else about the message is exactly as it was a second earlier.

That is why a pinned message keeps its place in the history. Scroll far enough back and it is still sitting where it was sent, with the same timestamp and the same neighbours. The bar at the top is a shortcut to it rather than a second copy of it. Tapping it jumps you to the original rather than opening anything new, which is why the surrounding conversation comes with it.

A pointer on the chat

The full information object for a user, a group and a channel each carries a field holding the identifier of the pinned message. That field is how a client knows what to show in the bar before it has loaded any history at all. It is a pointer rather than a copy, so the bar is always describing a message that exists somewhere in the room. When the pointer and the message disagree, the message wins.

Nothing is protected by it

Pinning does not stop a message being deleted, edited or expired. Unpinning happens automatically when the message stops existing, and nothing about the pin preserves the content. It is a signpost rather than a safe. Nothing about the flag makes the content more durable than any other message in the room.

People treat a pin as a backup, which is the one thing it is not. If the content matters, forward it to Saved Messages as well, because that produces an actual second copy under your own control rather than a reference to somebody else's. That habit costs two seconds and it is the only version that survives somebody else tidying up.

The One Call Behind Every Pin

There is a single method for the whole feature, and its parameters are the interesting part.

Pin and unpin are the same method

The call takes the chat and one message identifier, plus an unpin flag that decides which direction the operation runs. There is no separate unpin method, which is why the two actions always behave identically in every client. One method means one set of permissions, one set of refusals and one place for the behaviour to be defined.

The same call is documented as usable by bots as well as by people. A bot with the right permission can pin, which is how welcome messages and rules end up pinned automatically in a lot of rooms. The bot needs the pin right explicitly, and having other administrative powers does not include it. Keeping track of which bot holds which right across a set of rooms is the kind of thing our Bot Manager exists for.

Three flags, and two of them are useful

Besides unpin, the method carries a flag for pinning silently and a flag for pinning only on your own side of a one-to-one chat. Both are covered below because both answer questions people search for and almost nobody answers correctly. Neither is hidden in a settings screen, and both live in the same dialogue you already use.

It works over a business connection

The documentation notes the method can be invoked over a business connection, meaning a connected bot can pin inside a chat on behalf of a business account. That is a small detail with a real consequence for anybody wiring up automated support. A support bot can promote the current answer to the top of a customer's chat without a human touching anything.

Pinning Without Sending a Notification

By default a pin is loud, and the option to make it quiet has been there the whole time.

The silent flag

The method carries a flag documented as pinning the message silently, without triggering a notification. Clients expose it as a checkbox in the pin dialogue, usually worded as notifying members or not. The wording differs between platforms, and the flag underneath is the same one everywhere.

Read the default carefully, because it is the opposite of what people assume. Pinning normally does notify everybody in the room, which is why pinning three things in a row is a good way to annoy several thousand people in a minute. The notification arrives with the pinned text, so it reads like a fresh message rather than like an administrative action.

When to use it

Use it for housekeeping. Re-pinning the rules, tidying a stale pin, or pinning something that is useful to have at the top but not urgent are all cases where the notification adds nothing and costs attention. None of those are events, and treating them as events is how a room teaches people to mute it.

The notification is not the pin

A silent pin is still a real pin. It appears in the bar, it is visible to everybody, and it shows up in the pinned list exactly like a loud one. The only thing the flag suppresses is the alert. Nothing about the pin itself is hidden, downgraded or temporary.

That distinction matters when people ask whether a silent pin is somehow private. It is not private in any sense, it is simply undelivered as a notification, and anybody opening the chat sees it immediately. The bar looks identical whichever way it was pinned.

Pinning in a Private Chat, Just for You

This is the answer to one of the most common questions on the subject, and the answer is yes.

The one-sided flag

The method carries a flag documented as pinning the message only on the local side of a one-to-one chat. Set it and the pin exists for you, in your copy of the conversation, and the other person's chat is untouched. It is the closest thing the platform has to a private bookmark inside somebody else's conversation.

Clients expose this as a choice when you pin in a private chat, typically asking whether to pin for both of you or only for yourself. It is easy to miss because it appears as a second button rather than a checkbox, and the default is usually the shared one. Reading the two buttons before tapping is the whole skill here, because the wrong one is a notification you cannot recall.

What the other person sees

Nothing. No bar, no notification and no service message. As far as their client is concerned the message was never pinned, which makes this the only genuinely private pin on the platform. No trace of it reaches them at any point, now or later.

Bots cannot do it

The documented refusal is unusually blunt, stating that bots cannot pin messages in a private chat just for themselves. The flag is a human feature, and an automation trying to use it gets a specific error rather than silent failure. That is a friendlier failure than most, because the message names the exact thing that is not allowed.

That refusal is also a hint about intent. The one-sided pin exists so a person can bookmark something inside a conversation, and bookmarking is not a thing a bot needs to do. A bot with something worth remembering has a database for it.

Who Is Allowed to Pin

Pinning is a permission in its own right, on both sides of the line.

The admin right

Administrator rights are a set of flags, and one of them is specifically pinning messages. It can be granted without granting anything else, so a moderator can be allowed to pin without being allowed to ban, delete or add other administrators. That is a genuinely useful piece of granularity and most rooms never use it. Our guide on Telegram admin rights covers the full set.

The restriction

The banned rights structure has a matching flag, which means pinning can be taken away from ordinary members. In most groups the default permissions decide this for everybody at once, and in some rooms members can pin until somebody notices. Checking that default is worth doing once, because the room may have shipped with it open.

Both directions exist on purpose. A room can hand pinning to a trusted member without promoting them, and it can remove pinning from everybody without restricting anything else about how they participate. Both changes are reversible and neither is announced.

In a private chat

The full user object carries a flag saying whether you can pin a message in that particular chat. It is a server side answer rather than a client assumption, so a greyed out pin option in one conversation and not another is not a bug. Bots and some restricted accounts are the usual reason it comes back false.

Pinning in a Channel Is Different

Channels use the same call and feel completely different because of who can reach it.

Only administrators pin

Subscribers cannot pin in a channel, since they cannot post either. The distinction between a channel and a supergroup decides this, and our guide on the Telegram supergroup covers why they are separate objects. Pinning is a broadcast action here, aimed at everybody reading, which makes each pin a much heavier decision than it is in a group. There is no discussion around it to soften the interruption either.

The silent flag matters more here for the same reason. A channel with fifty thousand subscribers turns every loud pin into fifty thousand notifications for something that was already published once. Doing that twice in a week is how a channel loses the people who were only mildly interested.

The pin is the closest thing to a homepage

Most channels use the pin as a permanent header, holding the rules, the offer, or the link that matters. It is the first thing a new subscriber reads, and it is the only part of a channel you fully control after the fact. Everything else moves down as you publish, and this does not. Our note on Telegram content ideas covers what usually earns that spot.

Discussion groups pin separately

A channel and its linked discussion group are two rooms with two independent pin bars. Pinning in one does nothing to the other, which is why a rules message often has to be pinned twice. People forget the second one, and the discussion group is usually where the rules were needed.

More Than One Pin at a Time

The documentation opens by stating that multiple messages can be pinned on top of a chat, and most people never use it.

Pins are a list, not a slot

Pinning a second message does not replace the first. Both carry the flag, the bar becomes a counter, and tapping it moves through them in order. The update the server sends when things are pinned carries a vector of message identifiers rather than a single one, which is the protocol saying the same thing. A list rather than a value is a design decision, and it was made deliberately.

How many is too many

There is no small published ceiling for ordinary chats, so the practical limit is attention rather than the platform. A bar that says one of eleven is a bar nobody reads, and the first pin is the only one most people will ever see. Each additional pin makes the previous ones less likely to be read rather than more.

Three is usually the honest maximum for a room people actually use. Anything beyond that is an archive pretending to be a header, and an archive belongs in a message you link to rather than in the bar. One pinned index post beats five pinned posts every time.

Order is by message, not by pinning

Pinned messages appear in the order they were sent rather than the order you pinned them. That surprises people who pin something important last and expect it to sit at the top, and there is no way to reorder them. The only workaround is to repost the message so it becomes the newest one, then pin the copy.

Unpinning, One and All

Removing pins has two paths and one of them needs permission you may not have.

Unpinning one

The same method with the unpin flag removes a single pin. Anybody who could pin the message can unpin it, and in a private chat that includes both sides unless the pin was one-sided. A one-sided pin can only be removed by the person who set it, since nobody else knows it exists.

Unpinning everything

A separate method unpins every message in a chat at once. It answers with the number of affected messages, and its documented refusal says administrator rights are required, so it is not something an ordinary member can do to a room. That refusal is the same one used across the administrative surface, so it is not specific to pinning.

It also carries a flag for a forum topic, which lets you clear the pins inside one topic without touching the rest of the group. That is the tidy way to reset a busy topic without disturbing anything else. Forums accumulate pins faster than groups do, because every topic has its own.

Unpinning is not deleting

The message stays exactly where it was, still readable, still searchable. Unpinning removes the bar and the flag, and people who expect it to remove the content are thinking of a different operation entirely. The two get confused because both are reached from the same menu.

This trips up moderators clearing something they should not have pinned. Removing the pin removes the prominence, and if the content itself is the problem, it has to be deleted separately. Doing only the first leaves the message findable by search, which is usually not what was intended.

Pins Inside a Forum Topic

Forums add a second layer of pinning, and the two are easy to confuse.

Pinned messages inside a topic

Each topic has its own pins, which is why the unpin-everything method takes a topic identifier. A pin inside one topic does not appear in another, and the group's main bar is separate again. That is three independent places a pin can live in a single forum.

Pinned topics are a different thing

A forum can also pin whole topics to the top of its topic list, and the published ceiling for that is five. It is a navigation feature rather than a message feature, and it shares nothing with the pin bar except the word. The five is a published configuration value rather than an observation. Our guide on Telegram topics covers how the list behaves.

Mixing the two up produces a very specific confusion. Somebody pins a message expecting the topic to rise in the list, or pins a topic expecting a bar at the top of the conversation, and neither happens because they are unrelated features.

The general topic

The default topic behaves like the group itself for pinning purposes, which means a pin there is the closest thing a forum has to a room-wide header. It is the right place for rules in a forum, and the wrong place for anything topic-specific. Members reach it by default, which is exactly why it should stay short.

What Everyone Else Sees

Pinning is a public act in a group, and it produces two separate things.

The service message

The protocol has an action for a pinned message with no parameters at all, which becomes the grey line in the chat saying somebody pinned a message. It names the person who did it, and it is a real message in the history rather than an overlay. Anybody scrolling past later sees who pinned what and when.

Because it is a message, it can be deleted like any other. Admins tidying a room often remove those lines afterwards, and doing so does not unpin anything. The pin and the announcement of the pin are separate objects with separate lifetimes.

The update

Separately, the server pushes an update carrying the room, a flag saying whether things were pinned or unpinned, and the list of message identifiers. Clients use it to redraw the bar without reloading the conversation. It arrives whether or not the notification was suppressed, because the two are unrelated.

The notification

Unless the silent flag was set, members receive a notification naming the pinned message. That is three distinct signals from one action, which is why an unnecessary pin feels so much louder than an ordinary message. A normal post produces one of the three.

Counting them is a useful discipline before pinning something. A pin costs a notification, a line in the history and a slot in the bar, and plenty of things that seem worth pinning are not worth all three.

Finding the Pinned Messages Later

There is a proper way to list them, and it is better than scrolling.

The pinned filter

Message search accepts a filter that returns only pinned messages, which is how clients build the pinned list screen. It works in any chat you can search, so the full set is always one screen away rather than buried in the bar. That is also how clients count the pins for the bar rather than guessing.

The stored pointer

The full object for the chat carries the identifier of the pinned message, which is what the bar draws before anything else loads. When a client shows a pin instantly on opening a cold chat, that field is the reason. Without it the bar would appear a second later, after the history arrived.

It also explains a common glitch. If the pointer is stale, the bar can briefly show something that has since been unpinned, and it corrects itself as soon as the update arrives. Restarting the app fixes it faster than waiting, though waiting also works.

Hiding the bar

Dismissing the bar is a local action. It hides the reminder for you, changes nothing for anybody else, and the pin is still there when you look for it in the list. Dismissing is per device as well, so hiding it on a phone leaves it visible on a desktop.

Pinning a Chat Is a Different Feature

Half the people searching for this want the other pin, and the two share nothing but a name.

Pinning a conversation to the top

Pinning a chat uses its own method with its own flag, and it affects your chat list rather than any message. Nobody else can see it and nothing is announced anywhere. It is the most private control on this page and the one most often confused with the loudest.

The two refusals

One says there are too many pinned dialogues, which is the ceiling on how many chats you can hold at the top. The other says you cannot pin an empty chat with a user, which catches people trying to pin a conversation before sending anything in it. Send one message first and the refusal goes away.

Both are limits rather than errors, and neither has anything to do with pinned messages. A room can have a pinned message and not be a pinned chat, and the other way round. The two features share a word and nothing else.

Folders have their own count

Chat folders carry a separate allowance for pinned chats inside them, so the ceiling you hit in the main list is not the ceiling inside a folder. It is a small mercy for anybody organising a busy account. Folders are where heavy accounts end up, and the extra allowance is one reason why.

What Operators Get Wrong About Pinning

At one room a pin is a preference. Across many rooms it is a broadcast channel you already own and mostly waste.

Every pin is a notification you chose to send

Pinning without the silent flag alerts everybody, which means a tidy-up in a large room lands as an interruption. Teams that pin loudly while housekeeping produce a measurable wave of mutes and departures for no content at all. The wave arrives within the hour and it does not come back.

The habit worth building is the opposite of the default. Pin silently unless the point is to interrupt, and reserve the loud pin for the one message a month that deserves everybody's attention. Our note on growing a channel with boosts covers what else competes for that attention.

The pin is the only real estate you keep

Posts scroll away and the pin does not. In a channel it is the one position that keeps working after the post is old, which makes it the highest value slot you control and the one most rooms fill with something stale. A pin from four months ago is telling every new subscriber how much attention the room gets.

Treat it as a landing page rather than as a noticeboard. One clear message with the offer, the link and the rules outperforms three pins that each cover a third of it, and updating it is cheaper than posting again. Our note on writing a Telegram sales post covers what belongs in that one message. Anyone running rooms at scale with Member Adder should be checking pins on the same schedule as anything else.

Pin permission is a delegation, not a promotion

Handing somebody the pin right without any other administrative power is the cheapest way to let a helper keep a room current. Most operators promote to full administrator instead, which hands out banning and deleting to somebody who only needed one button. That is how rooms end up with five administrators and one person who actually posts.

The same logic applies to bots. A bot that pins the rules needs one flag, and giving it more is a habit rather than a requirement. Our guide on automating a Telegram channel covers the rest of what a bot can be trusted with, and teams needing something beyond that end up under Custom Solutions. Knowing which account holds which right in which room is a record rather than a memory, and it is the one our Account Manager keeps.

Frequently Asked Questions

How do I pin a message on Telegram?

Hold or right click the message and choose pin, then decide whether to notify members. The same action works in a private chat, a group and a channel, and the only thing that changes is whether you have permission to do it. The dialogue that appears afterwards is where the useful options live.

Can I pin a message without notifying everyone?

Yes. The pin call carries a flag documented as pinning silently without triggering a notification, and clients expose it as a checkbox in the pin dialogue. The pin is still fully visible, only the alert is suppressed. Use it for housekeeping and keep the loud pin for something that genuinely interrupts.

Can I pin a message only for myself?

Yes, in a one-to-one chat. There is a flag that pins the message only on your local side, so the other person sees no bar and gets no notification. Bots cannot use it, and the refusal says so explicitly. It is the only pin on the platform the other person never learns about.

How many messages can I pin?

More than one, since the platform supports pinning several messages on top of a chat and the pinned bar becomes a counter. There is no small published ceiling for ordinary chats, so the real limit is how many people will read. Three is a sensible working maximum for a room people actually use.

Who can pin messages in a Telegram group?

Anybody holding the pin permission. It exists both as an administrator right that can be granted alone and as a member permission that can be taken away, so the answer depends entirely on how that room is configured. Check the default member permissions if you are not sure which applies.

Does unpinning delete the message?

No. Unpinning clears the flag and removes the bar, and the message stays in the history exactly where it was. If the content itself is the problem, it has to be deleted as a separate action. Unpinning first and deleting second is the order that avoids leaving a bar pointing at nothing.

How do I unpin everything at once?

There is a method that unpins every message in a chat, and its documented refusal says administrator rights are required. It can also be pointed at a single forum topic, which clears that topic without touching the rest of the group. The call reports how many messages it affected, so you can tell whether it did anything.

Why does my pinned message appear in the wrong order?

Pinned messages are ordered by when they were sent rather than by when you pinned them, and there is no way to reorder them. Repost the message if you need it first, then pin the new copy. Unpin the older one afterwards, or the bar will carry both.