Telegram QR code — channels, bots, groups, usernames

A Telegram QR code does the same job a WhatsApp QR does in São Paulo — but in Tehran, Moscow, and the parts of Indonesia where Telegram has taken hold. Point a phone at the square, the Telegram app opens at the right screen, and the visitor is one tap from joining a channel, talking to a bot, or saving your username. No app store detour, no copy-paste, no figuring out how to find you. The audience that uses Telegram as their default messenger already knows what to do.

This post covers the t.me URL anatomy that every Telegram QR code encodes, the four destination types worth knowing (channels, bots, groups, public usernames), the regional pockets where Telegram outranks WhatsApp, and the practical setup decisions that separate a Telegram QR that earns its print from one that gets ignored. By the end you'll have the URL patterns memorised, a sense of which destination fits which campaign, and the regional read on whether your audience actually opens Telegram before any other messenger.

A Telegram QR code is a t.me URL in a printed square#

Telegram doesn't ship a special QR format. A Telegram QR code is a normal QR code whose encoded text happens to be a t.me URL — Telegram's official short-link domain. The phone's operating system decodes the URL like any other, recognises t.me as a host the Telegram app claims, and opens the app at the right screen. If Telegram isn't installed, t.me falls back to a web page with a "Open in Telegram" button and a link to the App Store or Play Store.

The four destination patterns worth knowing:

https://t.me/channelname           — public channel
https://t.me/botname               — bot
https://t.me/+invitehash           — private channel or group (revocable invite)
https://t.me/username              — direct chat with a person or business

The plus sign in the third one is load-bearing. t.me/+invitehash is the invite-link format for private channels and groups — the hash is generated by the admin from inside Telegram and can be revoked at any time. t.me/channelname (no plus) is the public-username format, which never expires because public usernames are claimed in Telegram's namespace the same way a Twitter handle is.

There's also the older tg:// URL scheme — tg://resolve?domain=channelname — which works inside Telegram's own scanner and on some Android cameras. iOS Safari refuses to open tg:// URLs from a QR scan for the same security reasons it refuses whatsapp:// URLs. The https://t.me/ form is the only one to print. It works on iPhone, Android, every desktop browser, and any in-app browser that handles HTTPS — same universal compatibility logic that applies to QR codes for WhatsApp, just with a different host.

What happens when someone scans it#

The flow runs slightly differently on each platform and ends the same place.

iPhone. Camera detects the QR, decodes the t.me URL, recognises the host as one Telegram claims, and shows the yellow notification banner with "Open in Telegram." One tap. Telegram launches at the channel preview, bot chat, group invite, or user profile encoded in the URL. If Telegram isn't installed, the banner offers Safari, which loads a t.me landing page with a clear "Continue in Telegram" button and an App Store link.

Android. Google Lens, Samsung Bixby Vision, OEM camera, or third-party scanner — all decode identically and route to Telegram via the standard intent system. Telegram's package handles the t.me host claim, so the routing is consistent across launchers. Older budget Androids without auto-recognition in the camera require a dedicated scanner app, which adds one tap to the flow.

Desktop. A user clicking a t.me URL on a laptop lands either in the Telegram Desktop app (if installed) or on the t.me web page with a QR pairing prompt. The pre-fill behaviour varies by client; the destination resolution does not.

The friction is one tap on iPhone, one or two on Android, and acceptable on desktop. The encoded URL is short — under 30 characters for most channels and bots — which means the printed QR can stay small and still scan from a metre away.

Channels — the broadcast destination#

A Telegram channel is one-to-many: admins post, subscribers read, no public conversation between subscribers. It's the format that put Telegram on the map for trading communities, news aggregators, and any creator who wanted a newsletter without the inbox tax.

The QR pattern is the simplest of the four. Public channels have a username; the URL is https://t.me/channelname. Encode that, print the square, and a scan drops the visitor into the channel preview screen where they can read the last few messages and tap "Join" once they decide. No invite token, no permission step, no expiry — the URL works as long as the channel exists under that username.

Private channels work differently. They have no public username; the admin generates an invite link of the form https://t.me/+aB3xZ9q1m2K from the channel's admin panel. The hash is unique and revocable. Print a QR encoding that link and any scanner taps through to the channel preview with a "Join Channel" button. The catch: the admin can rotate the link any time — usually after spam — and every printed QR breaks. For private-channel placements, encode a dynamic short link that you can update from a dashboard when the invite rotates. Print the short link; let the redirect carry the current invite hash.

A working channel QR pattern for a crypto trading community:

• Public channel @tradedesk_daily with a clear pinned message describing the channel rules and the cadence of posts.
• QR encoding https://t.me/tradedesk_daily printed on event signage, t-shirts, and the back of business cards at the conference.
• The pinned message includes a "Reply to the bot to verify and join the private channel" link, which routes serious followers to the deeper, private destination.

The same shape works for newsroom alerts, sports-club fixture notifications, restaurant specials, and any case where the relationship is "we post, they read." It is not the right shape for two-way conversation — that's what bots and groups are for.

Bots — the conversational destination#

Telegram's Bot API is the part of the platform most outsiders underestimate. A Telegram bot is a programmable conversational endpoint with a public username, addressable at https://t.me/botname. Scan a bot QR, the app opens the bot's chat, and the bot can immediately greet the visitor, present a menu, or kick off a flow.

What that buys a business that prints a QR:

• Pre-flow entry. A QR on a hotel-room door opens the concierge bot. The bot's first message is "Welcome — what can I help with?" with quick-reply buttons for housekeeping, room service, late checkout. The visitor taps a button instead of typing.
• Deep linking. Telegram supports a start parameter — https://t.me/botname?start=room301 — that the bot receives on first open. The bot sees room301 and pre-fills the conversation: "I see you're in room 301. What can I help with?" One QR per room, all pointing at the same bot, all routing on the start parameter.
• Order taking. Coffee shop QR on the table opens an order bot. Bot lists today's menu, takes the order, sends a confirmation when ready. No app install, no signup — the visitor's existing Telegram account is the auth layer.
• Customer support. Print a "Scan to chat" QR. The bot triages, collects basic details, hands off to a human agent through Telegram's standard inbox. Same conversational surface, no separate ticketing tool to learn.

The deep-link start parameter is the most underused mechanic on Telegram and the closest equivalent to WhatsApp's pre-filled message — the visitor's first interaction is shaped by the URL they scanned, not by what they choose to type. The bot picks up the parameter, runs the routing logic, and the conversation is already loaded with context. Track which parameters convert by routing through a dynamic short-link platform — same one-host-many-destinations idea, applied to the messenger layer.

Groups — the two-way destination#

Telegram groups are many-to-many: every member can post, every member can read. Useful for community signup, event coordination, study groups, neighbourhood watch, anywhere the relationship isn't "we broadcast, they listen."

Group QR patterns mirror channels with one important difference. Public groups use a username https://t.me/groupname. Private groups use the same https://t.me/+invitehash invite-link format as private channels, with the same revocation caveat. Print a static QR encoding a private-group invite and the day the admin rotates the link, every printed code breaks.

The right pattern for a printed group QR is a dynamic redirect on your own short domain. The redirect carries the current invite hash; the QR encodes only your short URL. When the invite rotates, you update one field in a dashboard and every printed code keeps working on the next scan. The same architecture rule applies to every Telegram destination type — public usernames are stable, invite hashes are not, and the safe printed default treats every Telegram QR as if the destination might change.

The other group-specific note: Telegram caps free groups at 200,000 members. Past that, the channel format makes more sense anyway, because at that size the conversation is one-to-many in practice even if it's technically many-to-many.

Public usernames — the personal destination#

The simplest Telegram QR pattern is a direct link to your Telegram username — https://t.me/your_handle. A scan opens the chat screen with you, ready for the visitor to type a first message. No invite, no channel intermediary, no bot logic. It's the Telegram equivalent of a business-card phone number, with the difference that the visitor scans the square and the chat opens without anyone reading or typing a number.

When this works well:

• Service providers in Telegram-heavy regions. Lawyers, accountants, freelance consultants in Tehran, Moscow, or Jakarta who already do most client comms over Telegram. The QR on a business card replaces "ask for me by name" with "scan to chat."
• Crypto and finance professionals globally. Trading communities have settled on Telegram as the default for one-to-one chat, regardless of region. A QR on a conference badge or in an email signature lands directly in the right surface.
• Sales reps at trade shows. Same logic as a trade-show booth WhatsApp QR, different messenger. The visitor's already-installed app is the lead-capture surface.

The one note worth flagging: Telegram usernames are visible to anyone who has the URL. There's no privacy distinction between "I gave them my number" and "I gave them my username" — the username is public. For high-volume customer-facing chat, a bot with proper routing is a better surface than a personal username. The username pattern is for relationships where one-to-one is the point.

Regional defaults — where Telegram outranks WhatsApp#

The same Telegram QR converts wildly differently across markets. The rule from WhatsApp QR regional defaults applies in reverse — print the channel your audience already uses, not the one you wish they'd switch to.

The regions where Telegram is meaningfully ahead of WhatsApp as the default messenger:

• Iran. Telegram is the dominant messenger across nearly every age group, with adoption shaped by the early ban on competing platforms and a long stretch of Telegram itself being technically restricted but practically universal via VPN. Channels are how news propagates, how shops advertise, how communities organise. A WhatsApp QR on a Tehran shop window gets ignored; a Telegram QR doesn't.
• Russia. Telegram overtook WhatsApp for business and news consumption around 2022 and has held the lead since. The market is split — WhatsApp still has large personal-chat share — but for any business-to-customer channel (news, services, shops), Telegram is where the audience is. Reuters and Financial Times messenger-market coverage tracks this shift in detail.
• Ukraine. Similar dynamics to Russia for similar reasons, with Telegram channels playing an outsized role in wartime information distribution. Channel subscriptions reach into the millions for major outlets.
• Uzbekistan, Kazakhstan, Belarus. The same Central Asian and CIS pattern.
• Crypto-trading communities anywhere. Telegram is the global default for trading groups, project announcements, signal channels, and DEX support chats — regardless of the user's country. A crypto-adjacent product printing a QR for community signup uses Telegram first and other messengers second, even in WhatsApp-strong regions.
• Parts of Indonesia. WhatsApp leads overall, but tech and crypto communities cluster on Telegram. A QR placed in a Jakarta co-working space or a Bali nomad bar converts on Telegram in a way it wouldn't in a São Paulo cafe.

The regions where Telegram QRs convert harder:

• Brazil, Mexico, Argentina, India, Nigeria, Kenya, Indonesia (mainstream segment). WhatsApp is the default. A Telegram QR scans technically but doesn't get reached for. Run the local default first and add Telegram only if the specific audience (crypto, news consumers, tech workers) leans that direction.
• United States, Canada, UK, Australia. SMS, iMessage, and Signal dominate personal chat; business chat splits across email, WhatsApp, and a long tail. Telegram exists for niche audiences (crypto, news, expat communities from Telegram-heavy regions) but isn't the cultural default.
• China. Telegram is not generally accessible. WeChat owns the channel. The question doesn't arise.

The same regional-default thinking applies on the tourism side, where the messenger a visitor reaches for shifts at the border. A heritage venue in Yerevan that adds a multilingual tourism placard also benefits from a Telegram channel QR for Russian-speaking visitors, because Russian-language tourism in the region runs largely on Telegram — same logic the post applies to language detection, applied to messenger choice.

Pick a Telegram target — the widget#

Four destination types, four URL shapes, four placement defaults. The widget below walks the choice and surfaces the exact t.me URL plus the recommended placement for each. Selection persists in this browser.

Skip the encoding entirely with the Telegram QR code generator, which writes the t.me URL and the matching QR from the destination type and handle — one fewer manual step before the printed code lands on a poster.

Static or dynamic — why dynamic almost always wins#

A static Telegram QR encodes the full t.me URL directly. The QR works without any server in the loop — scan, open Telegram, done. The cost is permanence. Change channels, regenerate an invite hash, switch from a bot to a different bot, and every printed code is wrong. The fix is a reprint.

A dynamic Telegram QR encodes a short URL on your own domain — something like lnks.work/k/telegram — that redirects to the t.me URL on every scan. The QR pattern is fixed at print time; the destination is editable forever. Four things this buys:

1. Switch destinations without reprint. Start with a public channel, graduate to a private one when the community is mature, and change the redirect once. Every printed code points at the new destination on the next scan.
2. Rotate invite hashes. Private channels and groups have revocable invite hashes. A static QR encoding a +hash dies the day the admin rotates. A dynamic QR keeps working — update the redirect, the printed code is unaffected.
3. A/B placement. Run two destinations for a month — a channel for one half of the audience, a bot for the other. The dashboard records scan counts; whichever produces more sign-ups or chats wins.
4. Track scans. A static t.me QR opens Telegram with no server hop, so the scan is invisible to your analytics. A dynamic one logs every scan with timestamp, device class, and rough region. Same pattern as tracking WhatsApp QR scans, different messenger.

The trade-off is a network hop at scan time, which fails in environments without signal — basements, aircraft cabins, remote-site signage. For consumer-facing placements (cafe tables, packaging, business cards, posters in well-connected areas), the network is reliably there. The full editing-versus-permanence comparison lives in static vs dynamic QR codes. For Telegram specifically, dynamic wins almost every time because invite hashes rotate and channel preferences shift.

Print and scan-test the same way you would any QR#

Same pre-flight as any printed QR.

1. Print one proof at final size. Not at A4. Not at the screen preview. At the actual printed dimensions. Sizing rules are in the wider QR posts.
2. Scan with three phones. A current iPhone, a recent Android, and a budget device. The t.me URL should open Telegram on all three without any "do you want to open this?" disambiguation screen.
3. Test the no-Telegram fallback. Use a phone with Telegram uninstalled. The scan should land on a t.me web page with a clear "Open in Telegram" button and a store link, not an error.
4. Worst-light test. Outdoor noon, fluorescent office, dim restaurant. Same as any QR.
5. Confirm the destination is what you expected. For bots with a start parameter, scan the printed QR and confirm the bot received the parameter — not all scanner apps preserve query strings cleanly on first open.

The failure mode you'll hit most often isn't "the QR doesn't scan." It's "the invite hash expired six months after the QR went to print." Print Telegram QRs through a dynamic redirect on your own short domain and that failure mode goes away — see the link infrastructure ownership levels post and the QR-code domain ownership reasoning for the full case. The redirect domain is the one part of the stack that has to survive every channel rotation, bot rebuild, and invite-hash change.

A QR code that takes someone where they already are converts better than one that takes them somewhere new. In Tehran and Tbilisi, that place is Telegram.

FAQ#