WorkTech Atlas

A client has a 1.4 GB video, a revised brief, and no account in your company’s cloud storage. You need the files by Friday. Sending a shared-folder link seems easy, until the client asks whether other customers can see what they upload.

That is the narrow job of file requests: outsiders can submit files without becoming members of your storage workspace. Dropbox File Requests and Microsoft OneDrive Request Files both support this, but the more useful question is what happens before and after the upload.

Short answer: Dropbox is the more straightforward starting point when you need an account-free upload link and do not control a Microsoft 365 tenant. OneDrive Request Files is a strong fit for an organization already using Microsoft 365, provided its administrator allows the required anonymous-link settings. Neither is a full client intake or approval system.

Documentation reviewed November 3, 2026. This article analyzes published product documentation, not hands-on testing. No affiliate links are used.

Dropbox File Requests vs OneDrive Request Files at a glance

Decision point	Dropbox File Requests	OneDrive Request Files
Uploader needs a service account?	No	No
Where uploads go	Chosen Dropbox folder	Chosen OneDrive or SharePoint folder
Can uploaders see other files?	Destination is private by default; verify sharing settings	No, on the request link
Who can create a request?	Available on all Dropbox plans	Work/school OneDrive; admin policy must permit
Published per-file limit	2 GB on Basic/Plus/Family; up to 250 GB on listed higher plans	Depends on Microsoft 365 upload/storage limits; check tenant policy
Operational catch	Storage quota and plan-specific size caps	Anyone-link policy can remove the feature

Dropbox says file requests are available across its plans and accept uploads from people without Dropbox accounts. Its current file-request help page lists a 2 GB limit for Basic, Plus and Family and up to 250 GB on specified higher plans. These are file-request limits, not a promise that every browser, network or account can transfer a maximum-size file successfully.

Microsoft says a person with a request link can upload without a OneDrive account and cannot browse, download, edit or delete other submissions. Its request-files guide also explains that repeated filenames are disambiguated rather than simply replacing the earlier file. That matters when clients submit a correction.

The biggest difference is not the upload page

For a freelance designer, small agency or consultant, a request link may be a temporary front door. Dropbox gives you that door on a personal or business plan, subject to its file-size and storage constraints. You can create a named request, choose the destination, send a link, and close it after delivery. The upload destination is private by default, but sharing that folder later changes who can access the collected material.

OneDrive’s door is attached to an organization’s sharing policy. Microsoft’s administrator documentation says Request Files requires OneDrive for work or school, enabled Anyone links and compatible folder permissions. A company that prohibits anonymous links for security reasons cannot assume an employee can simply turn on Request Files. The right decision may be to keep that policy and choose an approved alternative, not weaken the tenant to accommodate one client.

This distinction changes purchasing logic. If you already have a suitable Microsoft 365 business subscription and the feature is enabled, an additional file-request subscription may be unnecessary. If you only have personal OneDrive, Microsoft says Request Files is not available there. Dropbox can be a practical fallback, but check whether your organization permits storing customer documents outside its existing approved system.

Three client-upload situations that reveal the trade-offs

1. The client sends a large media file. Dropbox Basic’s published 2 GB request limit accommodates a 1.4 GB file in principle, assuming sufficient storage space. For a 6 GB video, that plan is not suitable; an eligible higher Dropbox plan may be. For OneDrive, check your tenant’s upload limits and browser behavior rather than borrowing Dropbox’s 250 GB figure. Do not advertise a maximum that you have not validated with a representative test file.

2. The client sends a revised version. Treat the first upload and the revision as separate evidence. OneDrive automatically numbers duplicate filenames, according to Microsoft. Dropbox also allows a client to upload a corrected file to the request, leaving both submissions for the recipient. In either system, ask the client to include a version label and mark which version is approved. A folder full of files is not an approval history.

3. The client must answer questions with the attachment. A file request is intentionally sparse. If you need a project ID, consent checkbox, due date, or structured requirements alongside the file, use an intake form and link the upload to a specific request record. Our Zapier Forms vs Fillout client intake comparison explains why collecting a file and updating the correct record are separate design decisions.

A safe six-step handoff for a three-person client team

• Name the request by client and project. Avoid a single perpetual link labeled “Upload here” for unrelated customers.
• Keep one restricted destination. Limit internal folder access to people who need the files; a request link is not permission to expose the destination.
• Test as an outsider. Open the link in a private browser session, submit a harmless test file, and confirm you cannot see anyone else’s uploads.
• Record a receipt. Capture the client, project, expected files, receipt time and internal owner. A notification is not proof that the content is complete.
• Review before acting. Check the file type, scan according to your organization’s policy, verify the version, and request clarification where needed.
• Close the link. Dropbox supports closing a request; OneDrive documents deleting the request link to stop further uploads. Retain or delete the received files according to your organization’s policy.

The receipt should not claim approval. A simple message can say “We received your files and will review them,” while the actual acceptance remains a separate step. The distinction is covered in our client intake confirmation-email workflow.

When file requests are the wrong tool

Do not use a public upload link as a substitute for identity verification when receiving highly sensitive material. Both products let people submit without authenticating to the storage service; a name typed on a form is not proof of identity. Use an organization-approved secure portal or authenticated transfer workflow when contractual, legal or regulatory requirements call for it.

Likewise, neither tool is a client-facing review workspace. A customer cannot use an upload-only request to inspect prior deliverables, leave a structured decision, and approve a particular revision. For that, build a portal or an approval record with explicit identity, version and decision fields. Our Airtable approval-log guide describes why a revision history alone is insufficient.

For team communication, keep the incoming-file owner visible. If the client emails a shared address about a missing attachment, the team needs one person responsible for the follow-up. Our Google Workspace shared inbox vs Collaborative Inbox guide addresses that separate ownership decision.

What about automation and cost?

There is no useful universal “three-person price” here: file-request availability depends on the storage subscription, storage capacity and organizational settings, not simply the number of staff who see the link. A Dropbox account on an eligible plan may suffice for occasional collection; Microsoft 365 may already cover the use case if an administrator permits it. Compare the incremental subscription cost after verifying your current entitlements and governance requirements.

Automation adds another boundary. You can route a received file into a task or project record, but do not automatically interpret the upload as a completed or approved deliverable. Also verify integration prerequisites: Zapier’s Dropbox connection guide, updated October 1, 2026, states that connecting Dropbox to Zapier requires a paid Dropbox plan. That is distinct from Dropbox’s own file-request availability on all plans.

For a simple workflow, assign a human reviewer and record an explicit status such as Received → Needs review → Accepted / Revision requested. Add automation only when the team has a reliable project identifier, a clear owner and a way to handle duplicate submissions. This avoids turning a second upload into a second project by accident.

How to choose in ten minutes

Start by checking what your team already owns. In Microsoft 365, ask your administrator whether Request Files is enabled and whether anonymous request links are permitted. In Dropbox, check the account plan, remaining storage and the largest file you expect to receive. Then test with one external recipient, a harmless file, a second version and a closed link. The winner is the tool that passes your actual workflow without weakening security policy or creating a second untracked storage location.

For occasional client uploads, favor the simplest compliant request link. For recurring intake with forms, approvals, reminders and file revisions, choose a structured intake system and treat the storage link as only one component.

Sources and editorial scope

Official documentation: Dropbox file requests; Dropbox recipient instructions; Microsoft OneDrive Request Files; Microsoft administrator prerequisites; Zapier Dropbox connection requirements. Features and policies may change. This guide does not claim live product testing, upload speed benchmarks or verified subscription checkout prices.