Telegram group auto-delete: timers, old messages and bot limits

Telegram group auto-delete applies to new messages after you enable the timer. It does not sweep through the group's existing history. If yesterday's conversation remains after you turn on a one-day timer, first check when those messages were sent.

Removing selected old messages, setting a future retention policy and cleaning up bot commands are separate jobs. Choose the intended result before using Clear History, changing a timer or issuing a bot's /purge command.

Start with the result you need

New conversations should expire: review the group's native auto-delete timer.
Specific existing messages should disappear for everyone: use an authorized deletion action and check its scope before confirming.
Join notices and commands clutter the chat: configure selective cleanup for those categories.
Telegram takes too much space on your phone: review local storage and cache settings.

Clearing a media cache frees device storage without deleting the cloud conversation. Telegram describes this distinction in its storage advice. Removing something only from your own view also does not establish that other members lost access. Always read the actual confirmation rather than interpreting “clear” as a shared deletion promise.

Understand the timer with a timeline

Telegram's auto-delete announcement states that the countdown begins when an applicable message is sent, regardless of when it is read. Earlier messages remain outside a newly enabled timer.

Illustrative one-day test:

Monday, 09:00: send sample A while auto-delete is off.
Monday, 10:00: enable a one-day timer.
Monday, 10:05: send sample B.
Tuesday, after 10:05: check B's expiry; A should remain unless another action removed it.

Use these timestamps as a way to organize your observations. Write down the configured interval and the send time, rather than comparing message age with the moment someone opened the chat. If another moderator changes the timer during your test, record that change before interpreting the outcome.

Check the right setting and the right permissions

Open the intended group in an up-to-date official Telegram app. Inspect its profile, menu or management settings for Auto-Delete. The exact location and available duration choices vary by client; old screenshots are not a reliable map of every current version. Note the existing value before changing it.

Have an authorized administrator handle the change, but avoid the blanket rule that only admins can ever enable it. Telegram documents an exception for small private groups: members allowed to change the group's name and picture can enable the timer. Review those permissions if somebody unexpected changed the setting. Telegram's permissions update

The account-wide default is another setting. It applies to new chats and newly created groups; existing chats are not automatically changed. Check the particular group instead of assuming that a personal default updated every group you administer. The same announcement explains that distinction.

Agree on retention before deleting useful context

Choose an interval around how members actually use the group. In a volunteer event chat, someone checking once a week may still need travel instructions posted several days earlier. In a fast-moving coordination chat, yesterday's status reports may have little value. These are policy decisions, not reasons to select the shortest available timer automatically.

Before changing the policy:

Identify instructions, decisions and reference files that people still need.
Decide where approved long-term reference material should live and who can access it.
Tell members when the new rule starts and whom to ask about missing context.
Give moderators the same instructions for exceptional, one-off removals.

Do not copy the entire conversation into a new archive by default. Retention includes deciding which material should stop circulating. If a reference needs a separate maintained copy, preserve only what the group has agreed to keep and review its audience.

Treat old-history deletion as a separate operation

For an old message that genuinely needs removal, select the exact original in the official client and inspect the available delete action. Check the group, topic, selection and wording about who will lose access. If the confirmation does not establish the intended scope, cancel and investigate rather than experimenting on real history.

Treat deletion for everyone as irreversible. Before a wider selection, have another moderator check the boundaries: an announcement between unwanted posts can be easy to include accidentally. Do not approve a whole-history action merely because a tutorial used a similarly named button.

After an authorized removal, verify a few specific originals with a consenting member who previously could open them. A surviving forward or screenshot is a separate copy. Conversely, one person's empty view does not prove the original disappeared for everyone; use the missing-history guide when accounts disagree.

What the bot's 48-hour limit actually means

For ordinary Bot API deletion, deleteMessage requires the message to be less than 48 hours old. Deleting others' messages requires administrator status in a basic group, or the delete-messages administrator right in a supergroup. Creation notices for supergroups, channels and forum topics cannot be deleted by this method. Batch deleteMessages inherits the deletion restrictions.

This is not a universal time limit on human Telegram clients or native auto-delete. A bot command's name does not change its API restrictions.

Adding a bot today also does not provide an unrestricted historical archive. Telegram's client-level history retrieval method is restricted to user accounts. The client-level timer-setting method is separate too. Their existence does not establish that a moderation bot can browse every old post, erase a date range or expose those operations as commands.

Run a safe test with disposable messages

Use a separate test group containing only harmless sample material and consenting participants. Keep unrelated moderation rules from interfering with the experiment.

Record the group type, current timer, relevant permissions and client versions.
Post a clearly labelled sample before enabling the timer.
Enable a duration the client supports and record the change time.
Post a second labelled sample and record its expected expiry time.
After that time, compare both originals from two accounts already in the group.
Test a single-message deletion separately with a fresh disposable post, checking the confirmation first.
Record the outcome before attempting any range deletion.

For example, use “Before timer: sample A” and “After timer: sample B”, not copied customer conversations. A test with different group settings can teach the workflow, but it does not prove what happened in your production group last month.

Where Defendy cleanup fits

Defendy's message cleanup settings cover selected service messages and command noise. They are useful when routine notices interrupt conversation. Review one category at a time; enabling all-command cleanup can affect commands intended for other bots.

For targeted deletion and range commands, use the moderation command guide. Check its targeting instructions and limits before acting. A range cleanup is not a standing rule to erase everything older than a chosen date. These controls do not replace Telegram's native retention timer or restore deleted history.

Telegram also has ephemeral bot messages, visible only to the relevant person and bot. That visibility feature should not be confused with the group's retention timer; it does not establish Defendy support for ephemeral replies.

If the result still looks wrong

Compare the message's send time with the timer's activation, then check the exact action used. For a bot failure, record the message age, current rights and actual response. For a disappearance nobody expected, investigate the available moderation records rather than blaming the timer automatically.

Keep the report narrow: group type, settings, timestamps, one sample and what each checked account sees. Avoid another destructive cleanup while the first result is unexplained.

Primary Telegram sources checked on 6 October 2026. Interface placement is described cautiously; this guide does not claim a hands-on test of every Telegram client.