# v2raycollector: A Telegram and Subscription Scraper That Sorts V2Ray Configs by Protocol > Kolandone/v2raycollector pulls V2Ray configs from Telegram channels and subscription links, then stores them in plain-text files grouped by protocol. The project is a raw data source rather than a tool, and its main appeal is the pre-sorted output and a lightweight variant for clients that choke on large lists. **Kolandone/v2raycollector** — این پروژه به صورت خودکار کانفیگ‌های V2Ray رو از کانال‌های تلگرام و لینک‌های سابسکریپشن جمع‌آوری می‌کنه و توی فایل‌های متنی جداگانه بر اساس پروتکل ذخیره می‌کنه. - Repository: https://github.com/Kolandone/v2raycollector - Stars: 65 · Forks: 16 - Language: Unknown - License: not declared - Published: 2026-08-21 · Updated: 2026-08-21 · Language: en - Canonical page: https://hysenlabs.com/projects/kolandone-v2raycollector ## What This Project Actually Solves The problem is mundane but real: V2Ray users often hunt for working configs across Telegram channels and subscription links, and those sources are messy. Each channel posts in its own format, and a single subscription link can contain mixed protocols. v2raycollector automates the gathering step. It collects configs from those sources and writes them into separate text files, one per protocol. That saves a user from manually copying lines or parsing a mixed feed. The intended audience is someone who wants a ready-made list to paste into a client like v2rayN, v2rayNG, or Hiddify. The README is explicit about the use case: copy a file link, add it as a subscription in the client, and update. There is no GUI, no daemon, and no API. It is a data product, not an application. ## The Mechanism: Collection, Sorting, and Output Files The repository layout shows the output: a main config.txt file plus separate files for VMess, VLess, Trojan, Shadowsocks, SSR, tuic, Socks, Juicity, Reality, and hysteria. The README states that all files update every 2 hours. That suggests a scheduled job, likely a GitHub Action, although the repository metadata does not confirm the exact trigger. The collection logic itself is not documented in the README. There is no mention of which Telegram channels are scraped, how subscription links are parsed, or what deduplication happens. The only visible mechanism is the result: text files with configs grouped by protocol. The main file reportedly holds more than 20,000 configs. The lite variant, config_lite.txt, caps at 15 configs per protocol, which is a practical concession for clients that struggle with large subscription payloads. The sorting by protocol is the core value, because it lets a user subscribe only to, say, the trojan.txt file and avoid noise from other protocols. ## Getting It Running: Commands and Configuration There is no installation step. The project is consumed entirely through raw GitHub links. The README lists direct URLs like https://raw.githubusercontent.com/Kolandone/v2raycollector/main/config.txt for the full set, and similar paths for each protocol file. To use it, you copy the link for the file you want, open a V2Ray client, go to the Subscription section, paste the link, and trigger an update. That is the whole workflow. There are no config keys, no environment variables, and no command-line tools to run. If you want to run the collector yourself, the repository does not provide instructions. The README only covers the consumer side. This is a notable gap: the project is called a collector, but the collection script, if any exists, is not described. A user who wants to modify the sources or the update interval has no guidance from the material. ## A Genuine Limitation: Trust and Freshness Are Unverified The biggest limitation is that the project offers no evidence of config validity. The README claims more than 20,000 configs and a 2-hour update cycle, but there is no mention of testing each config for connectivity, removing dead endpoints, or filtering out malicious servers. A config file from a random Telegram channel can contain anything, including servers that log traffic or serve malware. The project does not state any vetting process. Another limitation is the reliance on raw GitHub links. If the repository is taken down or the maintainer stops pushing updates, the subscription links die silently. The README also warns that some clients have trouble with the large config.txt file, which is why the lite version exists. That warning implies a real failure mode: a client may hang or fail to parse a 20,000-line subscription. The lite file mitigates that, but only for users who read the README. Finally, the project has no license listed, which creates legal uncertainty for anyone who wants to redistribute the config lists or build on the code. That is a practical blocker for commercial use. ## The Right Alternative: Run Your Own Subscription Aggregator If you need more control or trust, the alternative is to build your own subscription aggregator using tools like subconverter or a custom script that fetches specific subscription links and merges them. The difference in approach is fundamental: v2raycollector is a centralized, opaque service where you have no say over sources or update frequency. A self-hosted aggregator lets you choose exactly which Telegram channels or subscription URLs to include, run validation checks, and set your own update schedule. It requires more work, but it gives you a clear audit trail. For example, you could write a cron job that runs every hour, downloads a known set of subscription links, filters out duplicate lines, and writes a merged file. That approach does not rely on a third party's maintenance. The trade-off is effort. v2raycollector is zero-effort, but you trade away transparency. For a user who just needs a quick list for a personal client, the convenience may win. For someone who needs reliability or compliance, self-hosting is the safer route. ## Maintenance and Upgrade Cost Maintenance cost is low for the consumer because there is nothing to install or update. The project updates itself every 2 hours, according to the README. But that is also where the cost hides: you depend on the maintainer's schedule and goodwill. The repository metadata shows no recent release and no archived flag, but also no last push date in the provided material. That means you cannot confirm the project is actively maintained. The README mentions a Telegram channel, https://t.me/KOLANDJS, which is the only contact point. If the channel goes silent, you have no way to know if updates stopped. The upgrade path is trivial: re-copy the raw link if the file path changes, but the project gives no versioning. There are no releases, so you cannot track changes. The license is unknown, which is a red flag for any serious use. In practice, the cost is not technical but operational: you must periodically check whether the files are still fresh and whether the project is still alive. ## Who Should Adopt It and What to Verify First This project fits a casual user who wants a quick pool of configs for a personal VPN client and does not mind the lack of guarantees. It does not fit a team, a business, or anyone who needs reliable, vetted connectivity. Before adopting it, verify three things. First, check the raw file URLs to see if they still return content and whether the update timestamp matches the claimed 2-hour cycle. Second, inspect a sample of the configs to see if the protocols are correctly separated and if the lines are well-formed. Third, test the Telegram channel to see if it is still active. If any of those checks fail, the project is likely abandoned. The lite file is a good starting point for testing, because it limits the payload size. But even with the lite file, remember that the configs are untrusted. Use them only for non-critical purposes, and be prepared to switch to a self-hosted solution if the project disappears. ## Conclusion Adopt v2raycollector if you need a quick, protocol-sorted pool of V2Ray configs for testing or personal use, especially if your client can handle large text subscriptions. Do not use it for production or critical connectivity, because the project has no stated update guarantees, no license, and no documented validation of config quality. Before relying on it, verify the freshness of the raw files, check whether the Telegram channel is still active, and confirm that your client supports the plain-text subscription format. The project is a convenience aggregator, not a service, so treat its output as untrusted and test each config yourself. ## FAQ ### Is V2Ray a VPN or a proxy? The repository does not describe V2Ray itself. It collects configurations for ten protocol names, VMess, VLess, Trojan, Shadowsocks, SSR, tuic, Socks, Juicity, Reality and hysteria, and republishes them as text files that a client such as v2rayN, v2rayNG or Hiddify subscribes to. ### Is V2Ray safe to use with v2raycollector configs? The repository says nothing about safety. It collects configurations automatically from Telegram channels and subscription links, republishes them as plain text files, declares no licence and no terms, and publishes no filtering or validation rules, so nothing in it vouches for any individual entry. ### How do I use the v2raycollector config files? Copy the raw link of the file you want, open the subscription section of your client, which the README names as v2rayN, v2rayNG or Hiddify among others, paste the link and update. If the client struggles with the combined config.txt, use config_lite.txt instead. ### What is the difference between config.txt and config_lite.txt? config.txt contains all the collected configurations, described as more than 20,000, while config_lite.txt is a light version capped at a maximum of 15 configurations per protocol. The lite file exists because some clients have trouble parsing the large one, not because its entries are filtered for quality. ### How often are the v2raycollector files updated? Every two hours, which the README states both in the opening description and in the features list. Each protocol also has its own separate file, and the repository publishes no releases, so there is no version to pin and the files on the main branch are the product. ## Sources - [Official README](https://github.com/Kolandone/v2raycollector#readme) - [Project repository](https://github.com/Kolandone/v2raycollector) - [README](https://github.com/Kolandone/v2raycollector/blob/main/README.md) - [Releases](https://github.com/Kolandone/v2raycollector/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/kolandone-v2raycollector