How to Move Files from TeleBox (LinkBox) to Google Drive (2026)

Why people move from TeleBox to Google Drive

A free TeleBox account is small (about 5 GB) and it fills quickly, because saving one shared video folder from a Telegram channel can take all of it. Drive's free tier is three times larger, its sharing and search are familiar, and it does not depend on a chain of bonus storage. Moving the files out also protects them: shares that circulate through Telegram tend to vanish when an uploader or a channel is removed, and a copy in your own Drive does not. The trade-off is that TeleBox is where friends and channels expect to find the links you posted, so keep the TeleBox copy until you have moved anything you publicly shared.

TeleBox vs Google Drive: the numbers that matter for this move

Before you start

1. Check how much TeleBox holds. The My Account page at linkbox.to/admin/account shows your used space against your plan.
2. Check room in Drive. Google One's storage page shows what Gmail and Photos already use of the shared 15 GB.
3. Have all three TeleBox credentials ready. The token from the account page, and the email and password you sign in with. If your TeleBox account was created without a password, set one in TeleBox first, because the connection signs in with it.
4. Save any shared links you still need. A link that only exists as someone else's share is not in your account yet; save it into TeleBox first.

Method 1: Download from TeleBox, upload to Drive

Step 1: Download from TeleBox

Sign in to TeleBox in a browser or the mobile app and open My Files. Tick the folders or files, or open the three-dot menu at the end of a row and choose Download In telebox.

Step 2: Upload to Google Drive

In Drive use New → Folder upload or drag the folders into the browser window. Keep the tab open until the upload ends. Everything crosses your own connection twice, once down from TeleBox and once up to Google, which is fine for a few gigabytes and slow for a Standard-plan library.

Method 2: rclone's Linkbox backend

Step 1: Configure two remotes

rclone has a Linkbox backend that asks for the same three credentials: the API token from linkbox.to/admin/account plus your email and password. Its documentation explains the split: "The API token is used for uploads and modifications, while email/password authentication is used for listing and downloading files." Run rclone config twice, once choosing linkbox and once choosing drive (browser authorization for Google).

Step 2: Dry run, then copy

rclone copy linkbox:/ gdrive:TeleBox --progress --dry-run
rclone copy linkbox:/ gdrive:TeleBox --progress
rclone check linkbox:/ gdrive:TeleBox --size-only

copy adds files and deletes nothing, and --size-only is used for the check because rclone's Linkbox documentation does not describe hashes or modification times. rclone lists this backend at Tier 5, its lowest support tier, so treat it as best effort and test on one folder first. The copy runs through the computer that runs rclone, so your bandwidth and uptime matter.

Method 3: Server-side copy with CloudsLinker

CloudsLinker is a third-party web service that copies files between cloud accounts on its own servers. Nothing is downloaded to your computer, the browser tab can be closed once the task runs, and the same task can be scheduled to repeat. It reaches TeleBox through your token and account credentials and Google Drive through Google's public API; neither company endorses it.

Step 1: Connect TeleBox (token, email, password)

Sign in to TeleBox, open linkbox.to/admin/account, choose My Account and copy the value beside Token. The same page shows how much space you have used; a free account has 5 GB.

Then open app.cloudslinker.com, click Add Cloud and choose TeleBox. The dialog has four fields: a display name (pre-filled with TeleBox), the token (hover the ? icon beside it for a link to the TeleBox account page), your TeleBox account email and your TeleBox account password. The yellow notice in the dialog says the same thing: the email and password are required to sign in to TeleBox's web API, and without them file downloads fail. Do not paste the token into public screenshots; it is hidden in the ones on this page.

Step 2: Connect Google Drive (OAuth)

Choose Google Drive in Add Cloud. Google's own consent page at accounts.google.com lists what is requested, including permission to see, edit, create and delete your Drive files. Approve it and Drive appears under My Clouds. Your Google password is never entered in CloudsLinker.

Step 3: Choose folders, filters and schedule

Open Transfer. Under Source, expand TeleBox and tick the folders or files to move. Under Target, expand Google Drive and select or create the destination folder.

• Conflict strategy (the list under Options): by default a file is transferred only if its size differs or the date is more recent. You can also skip files with the same name, or force overwriting.
• Filter: switch it on, then open Files filter to include or exclude extensions and set a minimum and maximum file size in MB.
• Schedule: switch it on to run Once, Weekly (weekdays and a time) or Monthly (a day). Scheduling is available on paid plans.
• Skip Empty Folder is ticked by default, so empty folders are skipped.
• Copy or Move: keep Copy. Move deletes the files from TeleBox once they have been transferred.

Step 4: Start, monitor, verify

Click Create transfer. The job shows up under Task in the Task monitor, first as Preparing, with file counts, completed bytes and Cancel or Retry buttons. When it finishes, open Google Drive, check folders and a few large files, and only then decide what to delete from TeleBox.

Keeping TeleBox from filling up again

Many TeleBox accounts refill on their own: saved shares, phone backups, files forwarded from Telegram. Instead of repeating the migration by hand, set the same task to run Weekly or Monthly (scheduling is a paid-plan feature). Each run copies what is new since the last one, using the same-name policy you picked, and with Copy selected nothing leaves TeleBox until you delete it there. A simple routine is to let the schedule run, glance at the Task list, and delete the TeleBox originals you have seen in Drive.

The three methods side by side

Things to check before you move

• Password use. CloudsLinker uses your TeleBox email and password to sign in to TeleBox's web API so file downloads work. Use a TeleBox password you do not reuse elsewhere, and delete the connection when the migration is done.
• Copy first, delete later. The default Copy option never deletes from TeleBox (Move does delete the source files). Free space there only after you have opened the files in Drive.
• Room in Drive. The 15 GB free tier is shared with Gmail and Photos; a Standard-plan TeleBox library needs a Google One tier and may take more than one day at Google's 750 GB daily upload limit.
• Shares do not travel. TeleBox links and their settings belong to TeleBox. Recreate links from Drive if people still need them.
• Different revocations. Google access is an OAuth grant removed under your Google Account's Security settings; TeleBox access is a login, ended by deleting the connection in CloudsLinker and changing your TeleBox password.

Sources: rclone — Linkbox backend, Google — Files you can store in Google Drive, Google — Storage and upload limits, TeleBox — account page. TeleBox plan prices: TeleBox — App Store listing. Google prices are US list prices checked July 2026.

Related TeleBox and Google Drive guides

• Google Drive to TeleBox — the reverse direction.
• Download or save files from a TeleBox shared link — for links other people sent you.
• TeleBox to Dropbox, TeleBox to MEGA and TeleBox to OneDrive — the same TeleBox-side steps toward other clouds.
• Connector notes: TeleBox and Google Drive.