How can I enable Telegram’s auto-delete messages for all new chats after 30 days?

What the 30-day auto-delete switch actually does

Telegram’s auto-delete is a server-side eraser: once the timer expires, the copy on Telegram’s cloud is physically removed and disappears from every synced device. Flipping the switch does not touch anything you have already sent; it simply attaches a 30-day countdown to every new message you create from that moment onward. The feature is free for all accounts and works in private chats, groups, and the “Saved Messages” folder, but the way it is activated—and who controls it—differs slightly between chat types.

Empirical observation: the countdown starts at send time, not read time. A user who opens Telegram after 29 days will still have roughly one day to see the text before it evaporates. If you need tighter control (e.g., 24 h or 1 week) you can override the global default inside any single chat.

Feature matrix: who can turn it on and what they get

Premium subscribers do not get shorter minimums or longer maximums; the only advantage is the ability to send 4 GB files that will also respect the same 30-day timer once enabled.

Fastest path: enable 30-day auto-delete on every new chat

The setting lives under Privacy rather than Chat Settings because Telegram treats it as a data-minimisation preference, not a display tweak. Exact labels shift with language packs, so look for the clock icon instead of memorising text.

Android (Telegram 10.x)

1. Open hamburger menu → Settings
2. Privacy and Security → Auto-Delete Messages
3. Choose “30 days” → Confirm

iOS (Telegram 10.x)

1. Settings tab (bottom right) → Privacy and Security
2. Auto-Delete Messages → 30 days → Done

Desktop (Windows/macOS/Linux, official client)

1. ☰ → Settings → Privacy & Security
2. Auto-Delete → pick 30 days → Save

Once the toggle turns green, a one-line banner appears inside every new private chat: “Auto-delete is set to 30 days.” Open an old conversation and the banner is absent—proof that history remains untouched.

Groups and channels: why admins must vote twice

In groups, the global 30-day default is only a suggestion until an admin taps “Enable for this group”. Until then, messages live forever. This two-step design prevents a rogue moderator from silently nuking a 100 k-member archive.

Empirical observation: if you want every future group you create to start with 30-day deletion, create the group, immediately go to ⋮ → Auto-Delete → 30 days, then pin a note explaining the policy. New joiners see the banner as soon as they send their first message, eliminating retroactive surprises.

Edge cases that break the 30-day promise

• Forwarded copies: if someone forwards your text to a chat without auto-delete, the forwarded copy stays.
• Screenshots and saved media: auto-delete removes the in-app file reference but does not reach the Downloads folder or camera roll.
• Bot messages: bots can override the timer by sending with disable_auto_delete=False; check each bot’s documentation.
• Export before expiry: any participant can export the chat (Desktop → ⋮ → Export chat history) while the messages still exist.

If compliance requires guaranteed destruction, combine the 30-day timer with secret chats (E2E, no cloud) and disable screenshots on Android where the OS allows it.

When not to use the blanket 30-day setting

Support teams that search past tickets by keyword will lose visibility once messages evaporate. A workable compromise is to keep the global default at 1 year and shorten only the high-volume social groups. Conversely, NFT drop channels that want scarcity marketing can drop the timer to 24 h, but remember that early adopters who quote-tweet your channel post on X create a permanent mirror outside your control.

Checking that the timer is really active

Desktop offers the clearest audit: open the chat, click the name bar, and look for the small clock icon labelled “Auto-delete”. On mobile, long-press any of your own messages → Info; if the timer is set you will see “This message will be deleted in …” followed by a live countdown. No line means no timer.

Reproducible verification: send a test note to yourself in Saved Messages with 30-day auto-delete enabled. Return after 48 h and confirm the countdown shows “28 days left”. If it still says nothing, revisit the global setting—sometimes the toggle UI updates but the API call fails on flaky connections.

Turning it off again without losing history

Disabling the global switch only stops new messages from receiving the timer; anything already ticking continues to its doom. To rescue an ongoing conversation, enter the chat → ⋮ → Disable Auto-Delete → Apply to all existing messages. This extra prompt is deliberate; Telegram wants you to think twice before you keep 200 k voice notes forever.

FAQ – quick answers in schema form

Key takeaways and next steps

Telegram’s 30-day auto-delete is a fire-and-forget privacy tool, but it is not a retroactive shredder. Flip the switch under Settings → Privacy and Security, verify the clock banner appears in new chats, and remember that groups need a second confirmation. If your workflow relies on searchable archives, keep the default at 1 year and shorten only the high-traffic rooms. Test with Saved Messages first, export anything you must keep, and advise contacts to disable forwarding if you need stricter control.