Blur a Telegram screenshot

Telegram shows phone numbers more readily than WhatsApp if someone saved the contact that way. Bios add usernames. Forwarded headers add a third identity on top of the two already in the title.

The last bubble is not the whole screenshot. The title, the @username, the “Forwarded from” line, a nearby story mention, and a bot’s start link all sit in the same PNG. Secret chats still screenshot; the lock icon does not redact pixels.

Cover the stack

• Chat title and any phone number shown as the title.
• @username in the profile subtitle.
• Avatar if it is a face you would not publish.
• “Forwarded from” and “From [channel]” labels — a third party’s name.
• Pinned message that reprints a number or an address.
• Composer leftover: a half-typed number or an attached contact card.
• Call bar with duration and names if you captured during a call.

Crop to one bubble when the bubble is the artifact. Telegram’s quoted reply reprints the parent; bar numbers inside the quote even if you already barred the title.

Black bar for numbers and tokens

Phone numbers, login codes, and payment-bot order strings are short. Do not mosaic them. Paint a rectangle over the whole run, including plus signs and spaces. Usernames are identifiers; bar them when the person is not a public channel you are citing.

Bot tokens in start links and t.me URLs with extra query parameters belong under a bar. Treat those strings like API keys. The URL-bar version of the same habit is in hiding keys in URLs.

Channels, bots, and payments

Public channels still have admins in the subscriber list if you opened it. Do not screenshot subscriber lists. Comments on a channel post are other people’s names. Crop comments when you only need the post.

Payment bots echo last fours, addresses, and sometimes a photo of a receipt. Cover the digit strings. Crop the receipt photo or bar the PAN if it is in frame. Do not use a Telegram screenshot as a wallet dump. Invoice messages from bots also repeat a shipping address in the same bubble as a tracking number; bar the address even if you keep the tracking UI for a support ticket.

Desktop vs phone vs Web

Desktop Telegram adds a left list of other chats and a search box. Crop the list. Web Telegram adds a browser bar; cover it if a token or a phone-shaped query is there. Phone captures add a status bar and banners from other apps.

Folders in the sidebar name private circles. Crop the folder rail on desktop. Archived chats that peek in a search overlay are still titles. If you used global search to find the message, clear the query so a phone number is not sitting in the search field in the PNG.

Same capture hygiene as WhatsApp, different chrome. The header-and-OTP checklist for that app is in blurring WhatsApp screenshots.

FAQ: Do secret chats block screenshots?

Some clients warn or block in-app capture. People still use another phone, a desktop client, or a window recorder. If a PNG exists, redact it. The lock is not a black bar.

FAQ: What about Saved Messages?

Saved Messages is a private dump that often includes OTPs and card photos. If you screenshot that chat to move a file, you duplicated the dump. Bar numbers. Prefer exporting the one file you need without capturing the list.

FAQ: People nearby / contacts?

Those screens are rosters with distances or phone-book names. Do not post them. There is no “bug in the map” that requires other people’s names in the shot.

FAQ: Stories and guest sessions?

Story privacy lists are viewer rosters. Guest or anonymous sessions still show a device name in settings screenshots. Cover device names and session IPs if you are showing a settings bug to a forum.

Use the local editor to bar the title, @username, and forwarded-from line, then download PNG. BlurThis runs entirely in the tab.