Understand how to navigate the bot interfaces, utilize advanced download bypasses, and perfectly configure your Google Cloud BYOC project without getting stuck.
A complete breakdown of the commands and buttons you will see inside Telegram.
/start
Boot up the bot and initialize your user session.
/logout
Disconnect your Google Drive from the bot securely.
π Drive Explorer: Browse your uploads. (Restricted strictly to the Bot's App Folder in the Free tier).
βοΈ Help & Settings: Access support links and basic configuration.
π Web upload: Generate secure web upload links directly from the bot.
π Upgrade: View Pro plans and activate your lifetime or monthly access.
/start
Launch the Pro bot and load the main menu.
/set_creds
Crucial: Use this to configure your Google Cloud Client ID and Secret.
/logout
Disconnect your drive from your current API project.
π Drive Explorer & ποΈ Info: Unrestricted full access to browse and manage your entire Google Drive directory.
π My Stats: View lifetime analytical data (transfer volume, speeds, active pipeline time).
π Web upload: Create high-speed bypass links for uploading massive files via browser.
π΄ Clear All: Instantly clear and abort all of your ongoing background tasks and active transfers.
Turn literally any file or URL into a blazing-fast, unrestricted direct download link.
From Telegram: Forward any massive file to the bot, and it instantly spits out a direct download link.
From External URLs: Paste any standard download link from the web, and the bot converts it into our own high-speed, server-optimized link.
From Google Drive: Paste a public Drive link to instantly bypass Google's annoying preview screens and "File too large to scan for viruses" warnings.
Why this matters: These aren't standard links. They are raw, unrestricted server links. The millisecond you click them, the download starts. Plug them straight into IDM (Internet Download Manager) or 1DM to max out your WiFi bandwidth without any platform restrictions.
Receive massive files from anyone, anywhereβand fast-track them to your Drive or VLC.
Click "Secure Web Upload" and send the custom webpage link to a friend. They can upload massive 50GB raw files directly from their browser, completely bypassing Telegram's strict file size caps.
Once they upload the file, the bot hands you a premium Direct Download link. You can use this link inside the bot to push the file directly into your Google Drive at server-to-server speeds. You never have to download the file to your phone first.
Don't want to save it to your Drive? Paste that exact same direct link into the VLC Media Player app (Open Network Stream). You can stream massive 4K raw videos instantly without eating up a single megabyte of storage.
Extract heavy archive files directly in the cloud without ever downloading them.
No more downloading massive zip files to your phone just to unpack them. This feature utilizes our server architecture to handle the extraction process for you.
.zip, .rar, etc.).Why we ask you to Bring Your Own Credentials.
If we hosted 10,000 users on a single, central Google Cloud Project, Google would severely throttle our API limits. Everyone's uploads would slow to a crawl, and centralizing that much access is a privacy nightmare. BYOC (Bring Your Own Credentials) turns you into your own server admin. You get dedicated, unthrottled API bandwidth, and absolute privacy because your data flows strictly between Telegram and your personal Google Cloud project. We never see it.
Think of a Client ID as a username or a digital badge that identifies your app to Google. The Client Secret is the password that proves your app is legitimate. Together, they authorize the bot to ask you for Drive access.
You should treat your downloaded credentials.json file securely, just like a password. However, if you ever accidentally leak or share it, do not panic! Having the JSON file alone isn't enough to steal your files. You can simply log back into your Google Cloud console, delete that specific credential, and generate a brand new one in exactly 10 seconds. Your files remain perfectly safe.
Follow this detailed, foolproof guide to perfectly set up your Google Cloud Console without getting stuck on Branding pages, Unverified App errors, or expiring tokens.
DS GDrive Pro and hit Create. Wait a few seconds, then make sure it is selected in the top bar.Google Drive API, select it, and click the blue Enable button.Go to APIs & Services > OAuth consent screen. Choose External and click Create. You are now on the App Branding page. Fill out these specific fields to trick Google into letting you publish the app later:
π App Name: DS GDrive Pro
π§ User Support Email: Select your own Gmail address.
πΌοΈ App Logo (Crucial): Google absolutely requires you to set an App Logo (Display Picture/DP) if you want to publish the app to avoid 7-day token expiries. Just upload any random image from your phone or download our bot's logo and upload it here.
π Application Homepage & Privacy Policy: You don't need to own a website! Just paste our domain: https://dsgdrivebot.in into both fields.
π§ Developer Contact Info: Type your email again at the bottom, then click Save and Continue all the way to the end.
You are now back on the summary dashboard. You have to make a choice regarding your "Publishing status".
If you didn't upload a logo in Step 2, you are stuck in Testing mode. In Testing mode, Google forces your login token to expire every 7 days. You will have to log in via Telegram weekly.
If you uploaded a logo and pasted the URLs in Step 2, you can click the Publish App button right now. We highly recommend this!
/set_creds, and upload this file.If you chose the recommended "Publish" route in Step 3, clicking the login link in Telegram will take you to a scary red page that says "Google hasnβt verified this app."
Why does this appear? Google flags any published app asking for Drive access to protect normal users from phishing scams.
Why doesn't the developer remove it? To remove this screen, a developer must pay thousands of dollars for an annual third-party security audit (CASA Tier 2). Since this BYOC project is entirely for your own personal use, paying for an audit is impossible and unnecessary.
Is it safe? Yes! It is 100% safe because you are the developer of the app. You are simply authorizing the Cloud Project you just built for yourself.