BriefGate vs Dropbox file requests: a folder link is not a checklist
Introduction
Dropbox file requests are the simplest way to let someone drop files into your Dropbox: you create a request, send the link, and anyone can upload without an account. The files land in a folder you chose, you get an e-mail for every upload, and on paid plans you can set a deadline and put your logo on the page. For "send me the photos from Saturday" it is hard to beat.
Projects rarely need just "the files". They need the logo in SVG, the copy for three pages, the brand colours, a yes or no on the hero layout, and the hosting password, and they need all of it, from a client who answers one thing a week. BriefGate treats that as a checklist with a chase engine: your coding agent or you define the items with define_intake, the client gets a branded portal that shows what is still missing, BriefGate reminds them on a schedule until everything is in, and get_intake_results returns typed data the agent can build with.
This page is for people who use Dropbox file requests for client work and keep chasing clients by hand.
Side-by-side comparison
| Feature | Dropbox file requests | BriefGate |
|---|---|---|
| What it collects | Files only | 12 typed items: files, images, text, URLs, choices, booleans, colour lists, structured JSON, encrypted secrets |
| Required items and progress | No per-item state; a request is open or closed | Each item is pending, submitted, needs revision, approved, or waived; the portal shows progress |
| Automatic reminders | None found; one invite, then a deadline with optional late uploads on paid plans | Chase engine per intake: preset cadences, a custom interval on paid plans, quiet hours, reminder cap, e-mail, SMS credits on Agency |
| Asking for a re-upload | Delete the wrong file so the uploader can send another | request_revision with a note on Solo and Agency; the client sees what to fix |
| Credential collection | No; only a password on the request itself | Encrypted secrets vault with one-time reveal (Solo and Agency) |
| Uploader needs an account | No | No |
| File size | 2 GB per file on Basic, Plus, Family; 250 GB on Professional and team plans | Per-plan storage; uploads go straight to object storage |
| Branding | Logo and colours on Professional and Essentials, and for admins on some team tiers; Dropbox states it is not available for file requests on Standard and Business accounts | Your logo and accent colour on Solo and Agency; custom portal domain on Agency |
| Notifications | E-mail on send and on every upload | Webhooks for item.submitted, intake.completed, client.viewed, chase.bounced, and more |
| API | Dropbox HTTP API file_requests endpoints |
REST API with OpenAPI spec, llms.txt |
| MCP server | None found | Yes, npx @briefgate/mcp |
| Pricing | Part of Dropbox: Basic free with 2 GB; team plans from about 12 EUR per user per month | Free plan; Solo 29 USD; Agency 79 USD per month |
Facts about Dropbox were checked on 3 September 2026 against Dropbox's help centre, plan pages, and developer documentation. Links are at the end of this page.
When to choose Dropbox file requests
- You need files and nothing else, from people who already know what to send
- Your team lives in Dropbox and wants the uploads in a specific shared folder with no extra tool
- The uploads are big: raw photo sets or video, where the 250 GB per-file limit on paid plans matters
- You already have a Dropbox plan and do not want another subscription
When to choose BriefGate
- The client owes a mix of files, text, decisions, and credentials, and you need to see what is still missing
- Nobody has time to chase clients by hand; reminders have to go out on a schedule over e-mail and, on Agency, SMS
- Your coding agent needs the results as typed data, not a folder to open and interpret
- You need to send something back for a fix without deleting it
- You need EU data residency and a portal in your own branding
- You want an MCP server or an API that describes the collected assets, not just the bytes
Using both
If your team keeps deliverables in Dropbox, let BriefGate collect and Dropbox store:
- Define the intake with
define_intake, including the files and every non-file item the project needs. - On
intake.completed, have your agent callget_intake_resultsand copy the files into the project's Dropbox folder with the Dropbox API. - Set BriefGate's retention to
on_deliveryso the copies on BriefGate's side are removed shortly after your agent collects them.
The client fills in one portal; your files still end up where your team looks for them.
Sources
- Creating a file request, deadlines, size limits, notifications: https://help.dropbox.com/share/create-file-request
- Uploading to a file request without an account: https://help.dropbox.com/share/received-file-request
- Branding availability, including the Standard and Business exception: https://help.dropbox.com/share/branded-sharing
- Team plan prices: https://www.dropbox.com/business/plans-comparison
- Personal plan prices: https://www.dropbox.com/plans
- File request API: https://dropbox.tech/developers/streamline-file-collection-with-the-file-request-api and https://dropbox-sdk-python.readthedocs.io/en/latest/api/file_requests.html