Telegram Archive: Where Chats Go and How to Find Them

A chat you were in the middle of is gone. Not deleted, because you would remember doing that, and not muted, because you would still see it. It has simply left the list. You scroll to the bottom, you scroll to the top, you find the little folder sitting above everything with a number on it, and there the conversation is, sitting quietly where you never put it.

The archive collects two kinds of chat. The ones you deliberately swiped away, which nobody has trouble understanding, and the ones that arrived there on their own because of a setting made months ago and forgotten. The second kind is where the frustration lives, and it is also where the real cost lives, because for anyone whose work involves messages from people who are not in their contact list, the archive is exactly where the replies go.

This article treats the archive as what it actually is in the protocol, which is not a bin but a second list with a number. It covers why chats land there without you, the three settings that decide whether they come back, how to find and move one, the pinning limits that differ by a factor of twenty depending on where you pin, how folders are a completely separate mechanism that people confuse with the archive, and the full set of published limits on both. Every number, flag and refusal below was pulled from Telegram's own documentation and live configuration on 9 August 2026 rather than remembered.

The Archive Is Folder Number One

Not a bin, a second list

The documentation is unusually plain here. Telegram has a mechanism for grouping peers, and it says that in Telegram apps these peer folders are used only to implement the chat archive, identified by folder number one. Everything else sits in folder zero by default. The archive is not a special state a chat can be in, it is the other list.

Every chat carries a number

Because the grouping is a real field rather than a flag on the interface, the documentation notes that most peer related structures, including updates and chat information, carry the folder number assigned to that chat. So the question of whether something is archived has a literal answer attached to the chat itself. Nothing is hidden or inferred.

There is no third folder

The same sentence closes the door on the obvious next idea. No other folder number is allowed at the moment. You cannot build a second archive, a holding pen, or a set of nested bins out of this mechanism. There are two lists, numbered zero and one, and that is the entire structure. Anything that looks like more than two lists in your app is built from something else, which is the subject of the second half of this article.

One more detail follows from the archive being a real list rather than a state. The protocol lets a client refer either to one specific chat or to every chat in a peer folder using the same kind of reference. So an instruction that applies to the whole archive at once is a single call rather than a loop over its contents, which is why marking the entire archive as read is instant in a good client and slow in a bad one.

Why Chats Arrive There Without You

The setting that does it

Among the global privacy settings there is a flag whose documented purpose is to archive and mute new chats from non-contacts. Not archive. Archive and mute, as one action, for anyone who is not already in your contact list. If you have ever turned this on during a wave of unwanted messages and then forgotten about it, you have the explanation for most of what follows.

It is a single decision with two effects

The pairing matters more than it looks. An archived chat is out of sight, and a muted chat makes no sound, so a new conversation from somebody you have not saved arrives with both of its ways of getting your attention removed at once. There is no half state where it is quiet but visible, or visible but silent. The flag does both.

Muting itself is a separate call when you do it deliberately, with its own settings object and its own refusal for invalid settings. That is worth separating in your head, because muting a chat by hand and having one arrive pre muted are the same end state reached by different mechanisms. Only one of them leaves you a memory of having chosen it.

The setting is not always available

There is a refusal on the call that writes these settings saying the auto archive setting is not available at this time, and pointing at a configuration value that says whether it currently is. On the day of writing that value read true, so the setting was live. It is worth knowing the refusal exists, because an app that fails to turn the option off is not necessarily broken.

There is a second refusal on the same call worth naming, which says a paid account is required. Not every global privacy setting is available on a free account, so a settings screen that shows an option and then refuses to save it is reporting a tier rather than a fault. Reading the refusal instead of retrying saves a lot of time.

What This Costs Anybody Doing Outreach

Replies from strangers go to the quiet list

Here is the practical consequence, and it is expensive. If you message people who have not saved you, then by definition every one of them is a non-contact when they reply. With that flag on, their answer is archived and muted the moment it arrives. You did not miss it because you were careless. You missed it because you asked to.

The person who replied looks like they never did

From the outside this is indistinguishable from silence, which is the worst possible failure mode. You conclude the message did not land, or the copy was wrong, or the list was bad, and you change something that was working. Anyone measuring reply rates while that flag is on is measuring the wrong thing entirely, which is why it is the first thing to check before rewriting anything. The rest of that argument sits in managing direct messages at scale.

What to do instead

Turn the flag off on any account that exists to receive replies, and handle the noise with the tools built for noise rather than with a setting that hides everything indiscriminately. Block and report the accounts that deserve it, keep the ones you are working with in a folder, and let the main list stay honest. Teams running this at volume usually move the inbox into a proper account tool so that no reply depends on somebody remembering to open the archive.

The Two Flags That Decide Whether Chats Come Back

Keep archived unmuted

The first of the pair controls whether an unmuted chat stays in the archive when it receives a new message, or climbs back out into the main list. That single flag explains the two behaviours people describe as bugs. Some accounts have chats that quietly resurface, others have chats that stay put, and neither is a fault. They have different values on the same switch.

Keep archived folders

The second one is narrower and cleverer. It controls whether unmuted chats that are always included in a folder, or pinned inside one, stay in the archive when a new message arrives. So a chat can be archived and simultaneously be a permanent member of a folder you look at every day, and this flag decides which of those two facts wins when somebody writes to you.

Why the defaults surprise people

Because most people never set either of them, and then read the resulting behaviour as the archive being unpredictable. It is not unpredictable, it is two booleans they have never seen. If chats keep coming back out and you want them to stay, or they keep staying and you want them back, these are the two switches, and they sit in the same place as the auto archive one.

It is worth checking all three together rather than one at a time, since they are stored in the same object and read in the same call. An account that behaves oddly around the archive usually has an unexpected combination rather than one wrong value, and seeing them side by side turns a mystery into a configuration you can describe out loud.

Finding a Chat That Went Missing

Ask the archive directly

The call that returns your dialog list takes a folder number as an optional parameter. Pass one and you are asking for the archive rather than the main list. That is why a well built client can show you the archive as a complete list rather than as a preview, and why an app that cannot show you the archive properly is choosing not to rather than being unable to.

Search does not care which list

The important practical point for anybody hunting a lost conversation is that searching is not scoped to the visible list. A chat sitting in folder one is still a chat, and searching by name or by a phrase you remember will surface it. Scrolling is the slow way to find something the search box answers instantly.

The dialog list call also takes a flag to exclude pinned chats and a hash used for caching, which together explain a behaviour people notice without naming. Your pinned chats and your ordinary list are fetched with different intent, and an unchanged list can be answered without sending it again. When a client shows the archive instantly the second time you open it, that is the cache doing its job rather than the list being small.

The wrong folder number is its own refusal

Ask for a folder that does not exist and you are told the folder number is invalid. It appears on the dialog list call, on the peer moving call and on the pinned dialogs call. Since only zero and one exist, that refusal is mostly a sign that something in a tool has been built on the assumption that more folders were coming.

Getting a Chat Back Out

Moving a peer between folders

The operation that archives or unarchives is a single call that edits which folder a set of peers belongs to. It takes a list of peer and folder number pairs, so archiving is not a separate action from unarchiving. Both are the same call with a different number, which is a fair description of what the archive really is.

It comes back as an update

The call returns an update carrying the new folder number of the moved peers. That is worth knowing because it means the archive state is broadcast rather than inferred. Your other devices do not have to notice that a chat vanished, they are told which folder it moved to.

Other clients can move things too

The same update also arrives as an ordinary update when another client makes the change. So a chat that archives itself while you are looking at it is usually your phone acting on a swipe your tablet made, or a setting applying. This is the mechanism behind the disconcerting experience of watching a conversation leave the list while you are reading it.

The update also carries a running event count, which is how a client knows whether it has missed anything between one connection and the next. That is the difference between an app that quietly drifts out of sync until you restart it and one that notices a gap and asks for what it missed. Archive state is part of that stream rather than something polled on the side.

Pinning: Five in One List, a Hundred in a Folder

The main list ceiling is small

The live configuration puts the pinned limit in the ordinary chat list at five, rising to ten with a paid account. Five is not many if you are running anything with more than a handful of live conversations, and it is the number most people bump into first and assume is the only rule.

The folder ceiling is twenty times bigger

The same configuration puts the pinned limit inside a folder at one hundred, rising to two hundred with a paid account. That is not a rounding difference, it is a different order of magnitude, and the documentation for folders says plainly that folders can have unlimited pinned chats relative to the ordinary list. If pinning is how you keep track of live work, the folder is where you should be doing it.

The refusal when you go over

Exceed either ceiling and you are told there are too many pinned dialogs. The refusal appears both on the pinning call and on the dialog list call, which is a small hint about how tightly pinning and listing are bound together underneath.

There is a third pinning ceiling that catches people running a business account, since saved messages have their own limit of five by default and a hundred on the paid tier. Three different pinning limits in three different places, all called pinning, is exactly the kind of thing that reads as inconsistency until you notice each one belongs to a different list.

Anyone keeping notes or files for themselves in saved messages runs into that third ceiling without ever touching the archive, and the jump from five to a hundred on the paid tier is the largest of the three. Whether that matters depends entirely on whether you use saved messages as a scratchpad or as a filing system, and most people discover which one they are doing at exactly the moment they hit five.

Two Pinning Rules That Catch People

An empty chat cannot be pinned

There is a refusal saying you cannot pin an empty chat with a user. So the natural move of opening a conversation with somebody you are about to contact and pinning it before you write does not work. Something has to have been said first. It is a small thing that turns into a confusing failure if you are setting up a working list in advance.

Reordering can silently unpin

The call that reorders pinned chats carries a flag whose documented effect is that dialogs pinned on the server but missing from the order you send will be unpinned. That is the correct behaviour for a client syncing a full list, and a quiet disaster for a tool that sends a partial one. If pins keep disappearing after a sync, this is almost certainly why.

Pinned chats live in the folder that holds them

Both the pinned list call and the reorder call take a folder number, so pinning is per list rather than global. A chat pinned in the archive is pinned in the archive. Moving it out does not carry the pin with it in the way people expect, and the two ceilings above apply separately.

Folders Are a Different Machine Entirely

Two mechanisms, one word

This is the confusion worth clearing up, because the same English word covers two unrelated things. Peer folders are the numbered lists, and there are exactly two of them. The folders you see as tabs across the top of the app are a separate mechanism, stored per account as a set of rules rather than as a place chats are moved to.

What a folder actually stores

A folder is a saved description. It carries a number, a name, an optional emoji icon, an optional colour, a list of chats to include, a list to exclude, and a set of flags. Nothing is moved when you build one. The chats stay exactly where they are and the folder is a question asked against them, which is why a chat can appear in several folders at once without being copied.

Because a folder is a saved description rather than a container, deleting one destroys nothing. The chats it matched are untouched and still in whatever list they were in. That is the single most reassuring fact about folders and the reason it is safe to experiment with them, which is not true of most things that look like organising your account.

Suggested folders exist

There is a call for fetching suggested folders, which is where the ready made options come from when you create your first one. Worth knowing mostly so you understand that those suggestions are served rather than generated on your device, and that they are a starting point rather than the shape you are stuck with.

There is also a call purely for reordering folders, and a special marker used in that ordering to stand for the default all chats folder. That marker exists because the main list is a tab like any other in the interface but is not a saved rule underneath, so the ordering has to name it somehow. It is a small piece of plumbing that explains why the first tab behaves differently from the ones you made.

What Goes in a Folder Without Naming Anything

Five inclusion flags

A folder can include all contacts, all non-contacts, all groups, all channels and all bots, each as its own flag. These are categories rather than lists, so a folder built on them keeps working as your account changes. A folder set to all non-contacts is populated by people you have never spoken to, automatically, which is a genuinely useful thing for anybody doing outreach.

Three exclusion flags

On the other side there are flags to exclude muted chats, exclude read chats and exclude archived chats. The middle one is the interesting one, because a folder that excludes read chats is a folder that empties itself as you work through it. That is a to do list built out of a filter, with no maintenance at all.

The pairing of those two sides is where the real power sits. A folder that includes all non-contacts and excludes read chats is a queue of strangers who have written to you and not yet been answered, built once and correct forever. Nobody has to add anybody to it, and nothing has to be cleaned out of it, because both halves are rules rather than lists.

Excluding the archive is its own switch

Note that excluding archived chats is a separate flag rather than the default. A folder will happily include chats that are sitting in folder one unless you tell it not to. This is the other half of the keep archived folders behaviour described earlier, and the two together are why a chat can be both archived and visible in a tab at the same time.

Folder Limits, Published as Numbers

Ten folders, thirty with a paid account

The live configuration puts the folder limit at ten by default and thirty for a paid account. Ten is generous for personal use and tight for anybody organising work by client or by campaign, which is the first place the paid tier starts to look like a business expense rather than a badge.

A hundred chats per folder

Each folder holds up to one hundred chats by default and two hundred with a paid account. Note this counts named chats rather than chats matched by the category flags, which is the reason a folder built on flags scales past the limit while a folder built by hand does not. Building on categories is not just less work, it is the only version that grows.

The name is twelve characters

The folder name is documented as a maximum of twelve characters. That is short enough to be a real constraint and it is the reason every folder tab you have ever seen is a single word or an abbreviation. Plan for it rather than discovering it halfway through naming twelve folders.

Alongside the name a folder carries an optional emoji icon and an optional colour identifier for its tag. Since the name is so short, those two are doing more work than they look like they are. A colour and a symbol carry the distinction the twelve characters cannot, which is worth deciding deliberately if you are going to live in ten of these.

The Refusals You Meet Building One

An empty include list

Try to save a folder with nothing in the include list and you are told that list is empty. A folder therefore cannot be defined purely by what it excludes. There has to be something positive in it, whether that is a category flag or a named chat, which is a reasonable rule that still surprises people building a folder as a way to hide things.

An empty name

There is a separate refusal for an empty title. Combined with the twelve character ceiling, the name is a required field with a narrow range, so any tool that creates folders needs to handle both ends of that rather than passing through whatever the user typed.

An invalid folder

Alongside those sit refusals for an invalid filter identifier and for invalid exclusions. These are the ordinary ones, but they are worth naming because a tool reporting a generic failure when the real answer is that a folder no longer exists sends people looking for problems that are not there.

Shared Folders Are a Separate Feature

Only channels and groups can be shared

A folder can be turned into a link that other people import. The documentation is specific about what may go in one, saying only channels and groups or supergroups may be specified. Private conversations cannot be shared this way, which is the correct design and also the answer to the question people ask first.

Public, or you manage the invite links

The rule on top of that is that the channels and groups must be public, or the user must have permission to manage invite links in them. So sharing a folder of private rooms is possible, but only if you are the one running them. If you need the mechanics of those links themselves, the invite link breakdown covers expiry, member caps and join requests.

Basic groups get converted

One consequence is easy to miss. Basic groups are automatically converted to supergroups when the export call is made. That conversion is not reversible and it changes how the group behaves, so exporting a folder containing an old small group quietly upgrades it. If you have been avoiding that conversion deliberately, do not put the group in a shared folder. What changes on conversion is part of splitting a group that grew too big.

Importing has its own edge worth knowing. The person joining picks which channels and groups to join, inaccessible ones are excluded automatically, and if they cannot join any of the peers at all then the folder cannot be imported. So a folder link handed to somebody banned from every room in it fails as a whole rather than arriving empty.

Limits on Sharing and Joining

Three links by default

The configuration allows three folder links by default, rising to a hundred with a paid account. There is a refusal for creating too many, and a second one for exceeding the per folder ceiling, so the two limits are enforced separately. Three is a small number if you were planning to run link based distribution off this.

Two imported folders by default

From the other side, an account may join two shared folders by default and twenty with a paid account. That asymmetry is worth reading carefully if you were planning to hand a folder link to an audience, because your reader may be at their own limit and the failure will look like your link is broken.

Links expire, and the refusal says so

There is an explicit refusal for a chat folder link that has expired, and it appears on the check call, the join call and the delete call. Checking before importing is a documented step with its own method, which exists precisely so a client can tell somebody the link is dead rather than failing halfway through joining.

A second refusal on the join call says you have joined too many channels and supergroups, and the ceiling for that is published as five hundred by default and a thousand on the paid tier. A folder link containing thirty channels can therefore fail for a reason that has nothing to do with the link. That is a good thing to be able to explain to somebody rather than guess at.

Keeping a Shared Folder Alive

Updates once an hour

An imported folder does not update itself continuously. There is a call for fetching new chats added to a shared folder, and the documentation says it must be invoked at most every hour, with the exact period published in the configuration. So a shared folder is a subscription with a defined refresh rate rather than a live mirror.

Dismissing what you do not want

New chats appear as pending rather than joining silently, and there is a separate call to dismiss them. That is the right design, because a folder link would otherwise be an open door into somebody's account. The person who imported the folder decides each time whether the new room comes with it.

Leaving suggests what to leave

Deleting an imported folder has a thoughtful step attached. There is a call that returns the pinned or always included chats from that folder which are suggested for leaving, so removing the folder can also offer to remove the rooms it brought. Without it you would delete the tab and quietly stay in thirty channels.

Several of these calls share a refusal saying the specified folder cannot be used in this context, which is the protocol drawing a line between a folder you built and a folder you imported. The two are different constructors and they do not accept the same operations. A tool that treats them as interchangeable will produce a confusing error the first time somebody points it at the wrong one.

The owner can revoke

On the other side, the creator can list every link made for a folder and delete any of them. So distribution is not a one way door. If you have handed a folder link into a place you regret, the link is a revocable object rather than something loose in the world. Anyone building lists at this scale should also read the account safety notes before scaling any of it.

Using All of This on Purpose

The archive is a working surface, not a bin

Pull the three ideas together and the archive stops being where things go to be forgotten. It is a second list with its own pinning ceiling of a hundred, its own membership rules, and two flags controlling what climbs back out. Used deliberately it is a staging area, and the people who find it frustrating are almost always the ones who never chose any of its settings.

Folders carry the load the archive cannot

Since only two peer folders exist, every structure beyond quiet and not quiet has to be built out of filters. A folder per campaign, a folder that excludes read chats so it empties as you work, a folder of non-contacts that fills itself. None of that costs anything and all of it survives your account changing shape. If you are running several accounts at once, the same thinking is in managing multiple accounts.

The same discipline applies to the rooms themselves rather than only the conversations. A folder of the groups you actually watch, built on named chats, is worth more than a bookmark list you never open, and it is the cheapest possible answer to having joined four hundred of them. Finding the ones worth keeping is a separate job, covered in finding groups that are actually active.

Check the settings before blaming the numbers

The single most valuable habit here is to look at the three global flags on any account whose reply rate you care about, before you conclude anything about your message or your list. A muted archive full of answers is a measurement problem dressed as a marketing problem, and it is a five minute check. The outbound half of that conversation is the direct message product, and the list building half is the member tool.

Frequently Asked Questions

Where do archived chats actually go

Into a second list. The documentation describes peer folders as being used only to implement the chat archive, identified by folder number one, with every other chat in folder zero. Archiving moves a chat between those two numbers rather than putting it in a special state.

Why do chats archive themselves

Almost always because of a global privacy flag that archives and mutes new chats from people who are not in your contacts. It does both things at once, so the conversation is hidden and silent from the moment it arrives. Turning that flag off stops it.

Why do some archived chats come back and others stay

Two separate flags decide it. One controls whether an unmuted chat leaves the archive when it gets a new message. The other controls the same thing for unmuted chats that are always included in or pinned inside a folder. Different values on those two switches produce the behaviour people report as inconsistent.

How do I find a chat I cannot see anywhere

Search rather than scroll. A chat in the archive is still an ordinary chat and searching by name or by a remembered phrase will surface it regardless of which list it sits in. The dialog list call also accepts a folder number, which is how a client shows the archive as a full list.

How many chats can I pin

Five in the main list, ten with a paid account. Inside a folder the ceiling is a hundred, and two hundred with a paid account. Going over either produces a refusal saying there are too many pinned dialogs, and the two limits are counted separately.

Why can I not pin a chat I just opened

Because there is a rule against pinning an empty chat with a user. Something has to have been sent in the conversation first. Setting up a list of pinned chats before you have contacted anybody will not work for that reason.

How many folders can I have

Ten by default and thirty with a paid account, with each folder holding up to a hundred named chats, or two hundred on the paid tier. Folders built on category flags rather than named chats are not bounded the same way, since the flags match whole classes of chat.

Why is my folder name being cut off

Because folder names are limited to twelve characters. It is a documented maximum rather than a display quirk, which is why every folder tab in every client is short. There is also a separate refusal for saving a folder with no name at all.

Can I share a folder with someone

Yes, as a link, but only containing channels and groups. Those must be public or you must have permission to manage their invite links. Basic groups are automatically converted to supergroups when the link is created, which is not reversible.

How often does a shared folder update

At most once an hour, with the exact period published in the configuration. New chats arrive as pending rather than joining automatically, and there is a separate call to dismiss them, so the person who imported the folder approves each addition.