A Telegram bot to generate direct link for your Telegram files.

Press the below button to fast deploy to Heroku

Click Here to know how to add / edit environment variables in Heroku.

• Head over to releases tab, from the pre release section, download the one for your platform and architecture.
• Extract the zip file to a folder.
• Create an a file named fsb.env and add all the variables there (see fsb.sample.env file for reference).
• Give the executable file permission to execute using the command chmod +x fsb (Not required for windows).
• Run the bot using ./fsb run command. ( ./fsb.exe run for windows)

• Clone the repository

git clone https://github.com/EverythingSuckz/TG-FileStreamBot
cd TG-FileStreamBot

• Create an a file named fsb.env and add all the variables there (see fsb.sample.env file for reference).

nano fsb.env

• Build and run the docker-compose file

docker-compose up -d

OR

docker compose up -d

docker run --env-file fsb.env ghcr.io/everythingsuckz/fsb:latest

Where fsb.env is the environment file containing all the variables.

git clone https://github.com/EverythingSuckz/TG-FileStreamBot
cd TG-FileStreamBot
go build ./cmd/fsb/
chmod +x fsb
mv fsb.sample.env fsb.env
nano fsb.env
# (add your environment variables, see the next section for more info)
./fsb run

and to stop the program, do CTRL+C

git clone https://github.com/EverythingSuckz/TG-FileStreamBot
cd TG-FileStreamBot
go build ./cmd/fsb/
Rename-Item -LiteralPath ".\fsb.sample.env" -NewName ".\fsb.env"
notepad fsb.env
# (add your environment variables, see the next section for more info)
.\fsb run

and to stop the program, do CTRL+C

If you're locally hosting, create a file named fsb.env in the root directory and add all the variables there. You may check the fsb.sample.env. An example of fsb.env file:

API_ID=452525
API_HASH=esx576f8738x883f3sfzx83
BOT_TOKEN=55838383:yourbottokenhere
LOG_CHANNEL=-10045145224562
PORT=8080
HOST=http://yourserverip
# (if you want to set up multiple bots)
MULTI_TOKEN1=55838373:yourworkerbottokenhere
MULTI_TOKEN2=55838355:yourworkerbottokenhere

Before running the bot, set these mandatory variables:

• API_ID : Telegram API ID from https://my.telegram.org.
• API_HASH : Telegram API hash from https://my.telegram.org.
• BOT_TOKEN : Bot token from @BotFather.
• LOG_CHANNEL : Telegram channel ID where bot messages/files are stored for streaming links.
  • How to get it: Create a channel, send a message, forward it to @missrose_bot, then reply with /id.

In addition to required variables, these optional ones are available:

• DEV (default: false)

  • Enables development logging behavior.

• PORT (default: 8080)

  • HTTP port used by the stream server.

• HOST (default: auto-generated)

  • Base URL used in generated links (for example https://example.com or http://192.168.1.10:8080).
  • If omitted, bot auto-builds it from detected IP + PORT.

• HASH_LENGTH (default: 6, min 5, max 32)

  • Length of URL hash used in stream links.

• USE_SESSION_FILE (default: true)

  • Reuse saved worker sessions to speed startup and reduce login overhead.

• USER_SESSION (default: empty)

  • Optional user session string for userbot features (for example auto-adding bots to LOG_CHANNEL).

• USE_PUBLIC_IP (default: false)

  • If enabled, bot tries to discover public IP for host generation.

• ALLOWED_USERS (default: empty)

  • Comma-separated Telegram user IDs that are allowed to use the bot (access allowlist).

These optional variables allow you to tune the streaming performance. Most users won't need to change these defaults.

• STREAM_CONCURRENCY (default: 4)

  • How many block downloads a single stream request runs in parallel.
  • Effective first-batch request fanout per stream request = STREAM_CONCURRENCY.
  • Higher values can improve throughput and startup latency, but increase Telegram API pressure.

• STREAM_BUFFER_COUNT (default: 8)

  • Capacity of the in-memory block queue between downloader and HTTP writer.
  • It controls how far ahead prefetch can run before the reader catches up.
  • It does not increase parallel download count by itself.
  • Approximate extra memory per request: STREAM_BUFFER_COUNT * blockSize (blockSize is dynamic: 64KB/256KB/512KB/1MB).

• STREAM_TIMEOUT_SEC (default: 30)

  • Per-block timeout for Telegram UploadGetFile request.

• STREAM_MAX_RETRIES (default: 3)

  • Retry attempts per block before failing the stream.

• STREAM_CONCURRENCY = how many Telegram downloads happen at the same time for one stream.

  • Bigger value = video may start faster and download faster.
  • But bigger value also means more chance of Telegram floodwait/rate-limit.

• STREAM_BUFFER_COUNT = how many downloaded chunks are kept ready in memory.

  • Bigger value = smoother playback on unstable networks.
  • It does not create more Telegram requests by itself.

• STREAM_TIMEOUT_SEC = how long to wait before saying a chunk request is too slow.

• STREAM_MAX_RETRIES = how many times to retry a failed chunk.

Quick rule:

• Telegram request pressure is mainly controlled by STREAM_CONCURRENCY.
• Approximate in-flight Telegram calls at peak = active_streams × STREAM_CONCURRENCY.

Safe starting presets:

• Small server / home host:

  • STREAM_CONCURRENCY=4
  • STREAM_BUFFER_COUNT=8
  • STREAM_TIMEOUT_SEC=30
  • STREAM_MAX_RETRIES=3

• Medium VPS:

  • STREAM_CONCURRENCY=6
  • STREAM_BUFFER_COUNT=12
  • STREAM_TIMEOUT_SEC=45
  • STREAM_MAX_RETRIES=3

• High bandwidth + multiple worker bots:

  • STREAM_CONCURRENCY=8
  • STREAM_BUFFER_COUNT=16
  • STREAM_TIMEOUT_SEC=60
  • STREAM_MAX_RETRIES=5

Example configuration for high-performance servers:

STREAM_CONCURRENCY=8
STREAM_BUFFER_COUNT=16
STREAM_TIMEOUT_SEC=60
STREAM_MAX_RETRIES=5

This configuration would allow up to 8 blocks to be downloaded in parallel, with a buffer of 16 blocks, and a longer timeout for slow connections.

You can add worker bots to distribute stream requests across different bot tokens:

• MULTI_TOKEN1
• MULTI_TOKEN2
• MULTI_TOKEN3
• ...

Each active HTTP stream request uses one worker client in round-robin mode. Using multiple workers reduces floodwait risk versus sending all traffic through a single token.

To enable multi-client, generate new bot tokens and add it as your fsb.env with the following key names.

MULTI_TOKEN1: Add your first bot token here.

MULTI_TOKEN2: Add your second bot token here.

you may also add as many as bots you want. (max limit is 50) MULTI_TOKEN3, MULTI_TOKEN4, etc.

To use this feature, you need to generate a pyrogram session string for the user account and add it to the USER_SESSION variable in the fsb.env file.

This feature is used to auto add the worker bots to the LOG_CHANNEL when they are started. This is useful when you have a lot of worker bots and you don't want to add them manually to the LOG_CHANNEL.

The easiest way to generate a session string is by running

./fsb session --api-id <your api id> --api-hash <your api hash>

This will generate a session string for your user account using QR code authentication. Authentication via phone number is not supported yet and will be added in the future.

Feel free to contribute to this project if you have any further ideas

You can contact either via my Telegram Group or you can message me on @EverythingSuckz

• @celestix for gotgproto
• @divyam234 for his Teldrive Project
• @karu for adding image support

Copyright (C) 2023 EverythingSuckz under GNU Affero General Public License.

TG-FileStreamBot is Free Software: You can use, study share and improve it at your will. Specifically you can redistribute and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. Also keep in mind that all the forks of this repository MUST BE OPEN-SOURCE and MUST BE UNDER THE SAME LICENSE.