TL;DR: We build, tweak, and maintain the tools that make Telegram fun to play with.
Ever found an amazing open-source project only to realize the original author ghosted it three years ago? Yeah, we hate that too. Telegram Playground was born out of necessity—we fork, maintain, and heavily customize Telegram libraries and bots to suit modern needs. Because sometimes, if you want something kept alive and kicking, you just have to do it yourself. ☕️
We have quite a few repos, so we curated them into a few distinct vibes to help you find what you need:
Keeping the heavy hitters updated and functional.
- pyroTGfork — Our active fork of Pyrogram.
- pyrogram-documentation & pyrogram-tgcrypto
- Telethon — Tweaks for the popular asyncio Telegram client.
- build-tdlib & webogram
Everything you need to track and parse Telegram's TL schemas.
Automations, reactions, and massive movie/series indexing tools.
From speed testing to media parsing, plus a sandbox of experimental bots.
- bmt — Telegram Clients Speed Test.
- youtube-search-python & parse-torrent-name
- wa-tg-bridge — WhatsApp to Telegram bridge.
- The Sandbox: OtherBots, bg, wj, tk, jw, bw, io, fpCt, shashi, itnwj.
Bookmark these. You'll probably need them:
- 📖 PyroTGFork Docs: telegramplayground.github.io/pyrogram/
- 📡 TG-APIs: telegramplayground.github.io/TG-APIs/
- 🏎️ Telegram Clients Speed Test: telegramplayground.github.io/bmt/
- 🍿 IMDb API: imdb.iamidiotareyoutoo.com
- 💬 Support Chat: @ReQuestChat
We’re all ears for suggestions on how to make these tools better. You don't even need to have a pull request ready to kick off a discussion—just slide into our Support Chat.
One quick favor before you pitch: Please take a quick scroll through previous discussions to see if someone else has already suggested your idea. If they have, just drop a reaction or reply to that thread to boost it, rather than starting a new one. It helps keep things organized!
Just some standard housekeeping: Any statement in this repository that isn't purely historical is considered a forward-looking statement. These are based on information available to the author right now, and nobody assumes any obligation to update them as things change.
The comments and plans in our discussions don't represent a hard commitment, guarantee, or promise to deliver a specific product or feature by a specific date—they just outline our general development vibes and roadmaps. Please don't rely on these public discussions to make purchasing decisions!