Your File Is in Drive. Why Download It Just to Upload It Again?

The Four-Step Shuffle Nobody Should Have to Do

A colleague shares a DOCX on Google Drive. You need it as a PDF. So you download it to your laptop, find it in your Downloads folder, upload it to a converter, download the result, then upload that back to Drive. Two files you didn't want are now sitting on your disk, and you'll forget to delete them.

Convert.Online cuts that down to two clicks. Pick the file where it already lives, convert it, and send the result straight back — without a single file landing on your device.

Four Places to Pull a File From

In the upload area of any converter page, next to Select Files, there's a small row of icons. Each one opens the official picker for that service:

• Google Drive — the standard Google file picker, with folder browsing and multi-select
• Dropbox — the Dropbox Chooser
• OneDrive — Microsoft's own file picker
• From URL — paste a direct link and the file is fetched server-side

These are the vendors' real pickers, not a re-implementation asking for your password. You sign in to Google, Dropbox, or Microsoft on their page, not ours.

Five Ways to Send the Result

Once the conversion finishes, the same choice appears on the way out. You aren't forced into a download:

That last one solves a genuinely annoying problem. You've converted a HEIC photo to JPG on your computer, and now you need it on your phone. No cable, no emailing yourself, no messaging app that recompresses it. Scan the code.

What Actually Travels Where

Plenty of tools describe this as "converting without downloading", which is worth being precise about, because it isn't the whole truth and you may be on a metered connection.

On the way in, the file does pass through your browser. When you pick something from Drive, Dropbox, or OneDrive, your browser fetches it from that service and forwards it to our servers. It's held in memory for those few seconds and never written to your disk — but your connection carries it, the same as a download would. We're not going to claim otherwise.

On the way out, two of the three genuinely are cloud-to-cloud. Saving to Google Drive or Dropbox hands the destination a link, and their servers collect the converted file from ours directly — your connection carries nothing at all. OneDrive's picker works differently, and the result passes back through your browser on its way up.

So the honest summary: you skip the file management, not always the bandwidth. Nothing lands in your Downloads folder, nothing is left behind to clean up, and half the round trip disappears entirely.

Where This Actually Helps

Once you know what's really happening, the wins are easy to place:

1. No Downloads folder archaeology. The intermediate copies never exist. You don't rename document (3).pdf, you don't delete anything afterwards, and you don't lose track of which version is the converted one.
2. Shared team folders. Convert a DOCX to PDF and save it straight into the Dropbox folder your team already watches. They see it appear; you don't send a "here's the PDF" email. And that upload leg costs you no bandwidth.
3. Devices with little storage. Chromebooks, tablets, and phones that are always near-full never have to find room for two temporary copies of a large video. Memory during the transfer, yes; disk space, no.
4. Fewer steps to get wrong. Every manual hop is somewhere to upload the wrong file, or the original instead of the result. Picking and sending removes both.

What Connecting Your Cloud Actually Grants

"Connect your Google Drive" is a sentence that deserves suspicion, so it's worth being precise there too.

With Google Drive, Convert.Online requests the drive.file permission — the narrowest scope Google offers. It grants access to the individual files you select in the picker, and to nothing else in your account. The rest of your Drive stays invisible; there is no "read all your files" consent screen because that access is never requested.

With Dropbox, it's narrower still. The Chooser hands back a temporary direct link to the file you picked. Convert.Online never receives a token for your Dropbox account at all — just a link to one file, the same as if you had pasted a URL yourself.

With OneDrive, saving a converted file asks for Files.ReadWrite — your own OneDrive, and that's the extent of it. Microsoft offers a broader variant, Files.ReadWrite.All, which would also cover every file other people have shared with you and every other drive you can reach, including your organisation's document libraries. Convert.Online doesn't ask for it, because writing one converted file into a folder you chose yourself doesn't need it.

In every case the picker is hosted by the service, so your password is typed on Google's, Dropbox's, or Microsoft's page and never passes through us. Once the file arrives, it's handled exactly like any other upload — which is a longer story, told in Is My File Safe When I Use an Online File Converter?

Convert.Online Inside Google Workspace

If Drive is where your work lives, there's a tighter option: Convert.Online is listed on the Google Workspace Marketplace. Installing it puts conversion within reach of the Drive you already have open, instead of a separate tab you have to remember exists.

It Works With Everything Else, Too

Cloud import isn't a special mode with a reduced feature set. A file pulled from Dropbox goes through exactly the same pipeline as one dragged off your desktop — the same format support, the same settings panel. You can pick a video from Drive and still choose your codec, resolution, and frame rate before converting. You can pull a PDF and turn it into a Word document, or grab a folder of WEBP images and convert them to JPG in one batch.

Conclusion

Shuffling files between your disk and two clouds to change one format is busywork the browser should have solved years ago. If your files already live in Google Drive, Dropbox, or OneDrive, pick them where they are, convert them, and leave the result where it belongs — with nothing left on your device to tidy up afterwards.