One engine, many sources
The EVdlc engine handles a wide range of sources. The bot exposes that engine through Telegram, so you do not have to pick a tool yourself.
Secure link-to-file automation
Paste a link. Get the file back in Telegram.
EVdlc Bot is a Telegram bot that downloads files for you. Send it a link from any of 10 supported source types — a video, a shared file, a plain download URL — and it works out which engine to use, fetches the file on a server, reports progress in the chat, and hands you the result. Nothing to install and no account to create.
Connect a Google account and a finished download can go straight to your Drive instead.
Access is granted per account while capacity is scaled up. Use the support address below to request access.
View our privacy practicesData use
EVdlc Bot asks for the least it can. Each item below exists only to carry out a download you asked for.
Your Telegram user and chat ID, so EVdlc Bot knows who asked for a download and where to send the finished file back.
The URL you submit, so EVdlc Bot can identify the source and download the file it points to.
The drive.file permission — the narrowest Drive scope Google offers. It covers only files you pick yourself and files EVdlc Bot saves for you. It cannot browse or read the rest of your Drive, and it never touches Gmail, Contacts or Calendar.
When you connect Google, EVdlc Bot also uses the standard sign-in scopes openid, userinfo.email and userinfo.profile. They identify which Google account the Drive connection belongs to — your account’s email address and basic profile details — so a download goes to the right Drive and you can disconnect it later.
Full detail, including how long anything is kept and how to have it deleted, is in the EVdlc Bot Privacy Policy.
Overview
This site is about EVdlc Bot, the Telegram bot. It is built on top of the EVdlc engine, a separate local downloader — that engine is a component, not the app described here.
The EVdlc engine handles a wide range of sources. The bot exposes that engine through Telegram, so you do not have to pick a tool yourself.
A finished job comes back as a file or a clear result, or is placed in your Google Drive if you have connected one.
Google access is limited to the drive.file scope, which covers only the files you pick and the files the service creates for you.
Availability depends on the source and its rules. The service does not attempt to bypass DRM, paywalls, or access controls.
Every link you have ever meant to download, finished and waiting in the one app you already have open.
How it works
You paste a link into a chat with EVdlc Bot. No installation, no browser extension.
EVdlc Bot identifies the source and starts the download workflow that matches it.
The bot reports progress and delivers the resulting file or download result.
Temporary processing data is removed according to the published retention policy — 24 hours at most.
Supported sources
Each category below is supported. Categories that are not part of the public bot are not listed at all.
Available
YouTube plus the wider set of supported media sites handled by the yt-dlp engine.
Available
A plain file URL that responds with a downloadable file over HTTPS.
Available
Files you pick through Google's own picker, and Drive share links you paste, which are fetched as ordinary links.
Available
Public Telegram post and file links you are able to open.
Available
Shared MEGA links, including links that carry a decryption key.
Available
Shared Dropbox file links.
Available
Shared OneDrive and SharePoint file links.
Available
Public posts on social platforms covered by the same media engine.
Available
Android app packages, fetched for the app you name. Paid apps and anything your account is not entitled to are out of scope.
Available
Track, album and playlist links, resolved to audio through the same engine. Nothing behind a paid subscription is bypassed.
Google Drive
EVdlc Bot asks for the narrowest Google Drive permission that exists. It is scoped to the files you choose, and nothing else.
The only Google Drive permission requested
https://www.googleapis.com/auth/drive.file
Privacy and security
The website you are reading has no login, no database and no tracking — that part is true today. The rest are the commitments the bot must meet before it launches.
This website loads no analytics, no tracking pixels, and no third-party scripts, and it stores no request telemetry.
Your data is never sold or rented, and never shared with ad networks.
Nothing you send is used to build an advertising or behavioural profile.
Only the drive.file scope is requested, covering the files you explicitly pick.
Temporary files are removed no later than 24 hours after successful delivery, cancellation, failed-job cleanup, or expiry.
You can revoke Google access at any time, or ask for your stored data to be deleted.
Questions
If something here is still unclear, the support address below reaches a person.
Support
Email the address below. Please include enough detail to identify the issue, and never send passwords, verification codes, OAuth tokens, session files, or private keys.
Messages are reviewed and answered as quickly as reasonably possible. No specific response time is guaranteed.