Four collection modes, a checker that verifies the usernames you collected with live accounts, segmentation and CSV export. The job is computed on the server, so your machine does not have to stay on.
Updated 20 September 2026
Without a recipient list there is no campaign. A scraper is what builds that list.
A Telegram scraper opens a public chat or channel using an ordinary account and copies out the public profile data it can see there: username, display name, whether the person was active, and their last-seen time when they have not hidden it. What you get is a list of people you can message directly, show a story to or mention in a group post.
It is the only honest way to get a fresh audience for a specific topic. A purchased database is somebody else's contacts of unknown age: half the accounts are deleted, some are bots, and the rest have already received a dozen identical pitches. A list collected today from a topical chat behaves differently — the people are real, the subject is already relevant to them, and the reply rate shows it.
The boundary matters. A scraper sees exactly what Telegram shows any member of that chat. It does not break into private groups, does not extract phone numbers and does not bypass privacy settings. Telegram never hands out the full subscriber list of a channel to anyone — that is a platform limit, and no software removes it. Anything that promises otherwise is either lying or running a grey scheme that your accounts will pay for.
In TGBLAST, scraping lives at /parsing in the Audiences menu. It is wired into the rest of the dashboard: a collected list turns into an audience with one button, the audience is picked inside a campaign, and replies land in the Inbox. There is no separate program to install and no CSV shuffling between tools.
The mode follows the source. Chats take one pair, channels take the other.
The full member list of a public group. The widest reach and the coldest one: it will include people who joined a year ago and never came back. The limit runs from 5,000 to 200,000 and defaults to 50,000. In chats above roughly ten thousand people Telegram does not return the list in full, so the system tops it up with letter-by-letter search — that job takes longer.
The authors of the recent messages. It works even where the admins have hidden the member list, which makes it the fallback that matters.
You set the depth: "Recent messages" from 100 to 20,000 (2,000 by default), a time window, and "Minimum messages per person". That last field cuts out passers-by: set it to 3 and only people who actually took part in the conversation make it into the list.
People who wrote comments under the channel's posts. The warmest selection of the four: the person did not just subscribe, they spent time writing a reply.
You set "Recent posts" from 10 to 500 (100 by default), a window, and a minimum number of comments per person. The channel must have a discussion chat attached — without one the mode returns an error.
The combined mode: members of the discussion chat plus the commenters under the posts. It gives more people than commenters alone and stays tied to the channel's topic. Three settings in the form: post depth, time window and a member limit for the discussion chat. This is the right default if you are working with a channel and are not sure what to pick.
The rule is simple. Source is a group: start with Chat members and switch to People who posted if it fails. Source is a channel: only Channel commenters or Channel audience. Pointing Chat members at a channel always returns "The channel subscriber list is hidden by Telegram".
Six moves from an empty screen to a finished list.
@username, a t.me/name link or an invite link t.me/+… into the Chat or Channel field. The start button activates from three characters. An invite link makes the account actually join the chat — that is visible to the admins, so keep it in mind.Every field, status and error message is broken down in the scraping guide, including what to do about access errors on private chats.
The honest frame the scraper works inside.
A raw list is not a database yet. Two steps sit between scraping and the campaign.
The Checker runs your usernames past live warmed-up accounts and sorts the result into statuses: OK — alive and through the filters, Filtered — alive but excluded (the reason is in the Details column), No — that username does not exist. The Flags column shows premium, bots, restricted and scam. The checker needs one warmed-up account per 20 usernames, and results only live for an hour — save them right away.
Sending a whole database from one account is a reliable way to lose it. Both scraping and the checker can split a list: the Split tab, a "Size of each part" field (25 by default) and a name prefix. What comes out is a set of audiences of 20–50 people each, handed to different accounts in different campaigns.
If you are building one topic out of a dozen chats, create the audience up front and pick it in the "Save to audience" field on every job — people are appended automatically and duplicates are skipped.
Five things almost everyone trips over in the first week.
t.me/+… link makes the account join the chat — admins see it, and in closed communities that ends in a ban.What support gets asked most often.
No. The job runs on the server: you start it and can close the tab. The job list refreshes every 4 seconds, so when you come back you will see the Done status and the result. Each job gets 2 hours; if the chat is huge and the scrape does not finish in time you get the timeout message and whatever was collected is saved partially.
Telegram does not hand the full subscriber list of a channel to anyone — that is a platform limit, not a limitation of the scraper. That is why channels are covered by the Channel commenters and Channel audience modes: they collect the people who wrote comments under posts and the members of the discussion chat. It is a much smaller group than the whole subscriber base, but it is the live, engaged part of it.
Run the same chat in the People who posted mode. It never touches the member list — it reads the recent messages and collects their authors. A hidden member list is the most common reason the Chat members mode fails.
One job uses exactly one account with the Active status. We recommend keeping a dedicated account with its own proxy just for scraping: if Telegram issues a FloodWait, that account turns Restricted and the job ends with an error — better that than losing an account your campaigns are running on.
A finished job has a CSV button and a To audience button. To audience saves the result as one list, or splits it straight away (Split into parts, 25 people by default). Before you launch a campaign, run the list through the Checker: it verifies usernames with live warmed-up accounts and filters out profiles that do not exist, bots and people who have not been online for a long time.
No. Scraping collects the public profile data that any chat member can see: username, display name, activity and last-seen time when the person has not hidden it. Telegram does not expose phone numbers by default and a scraper cannot get around that. We also do not sell ready-made databases — you build the audience yourself and you are responsible for how you use it.
Scraping, the checker, audiences, warm-up and campaigns all sit in one plan — there is nothing extra to buy. Got a promo code: full access for 7 days, no payment.