Drive File Request is a tool for collecting files into your own Google Drive. You sign in with Google, create an upload link, and send it to whoever has the files. They upload through a single page with no account and no sign-up, and every file lands in a folder inside your Drive.
What it accesses in your Google Drive
Signing in grants the narrow drive.file OAuth scope and nothing wider. That scope only ever gives an application access to the files and folders it creates itself — the rest of your Drive stays unreadable to it. It is the reason the app can write uploads into a folder for you without being able to browse anything you already had there.
Disconnecting Google reverses it: every link stops accepting uploads, the stored Google credentials are deleted, and active sessions are signed out. Files already delivered to your Drive are yours and are left alone. The full detail is in the privacy policy.
Where files go on the way through
An upload is written first to a private Vercel Blob store, then transferred into the link owner's Google Drive. The temporary copy is deleted once the transfer succeeds. Splitting it in two is what lets a large upload resume instead of restarting when a sender's connection drops mid-file.
- Senders need no account, no password, and nothing installed.
- Senders see only their own upload page — never the destination folder or anyone else's submissions.
- Uploaded files are owned by you, in storage you already pay for, as soon as they arrive.
- A keyed hash of an uploader's IP address may be kept for abuse prevention; raw IP addresses are not stored.
What it costs
A 24-hour trial covers the complete workflow with no card required. After that it is $10 per month, flat, with no seat licences — the full feature list is on the pricing page.
Contact
Questions, bug reports, and deletion requests go to hello@drivefilerequest.com. Drive File Request is an independent product and is not affiliated with or endorsed by Google.