Dropbox file requests: collect files without accounts

A Dropbox file request lets an event organizer collect speaker materials without asking each speaker to create a Dropbox account. The request link gives speakers a way to submit files to the organizer. To find out who still owes a slide deck or portrait, keep a separate list of what each person was asked to send and compare it with what arrived.

Create the request

At dropbox.com, open File requests and choose New request. Add a title and description, choose a destination, create the request, then copy and share its link. File requests are available on all Dropbox plans, and uploaders do not need an account. An administrator may disable the feature for an account. Dropbox’s file request instructions

For a speaker intake, a title such as “October event speaker materials” identifies the collection. Put the deadline, required deliverables, and contact for upload problems in the message you send with the link. Give each speaker a nonsecret submission ID so the files can be matched to the right request.

Choose where uploads go

Dropbox says the request destination is private by default. If you choose a shared folder as the destination, its members can access the uploaded files. Check the destination before distributing the link, especially if portraits or presentation drafts should stay with the event team. Dropbox’s file request instructions

A shared folder serves a different purpose. Joining one requires a Dropbox account, while a shared link can allow someone without an account to read or download. Use a file request when you need that person to submit a file. Dropbox’s account guidance

Check file limits and available space

The per-file upload limit depends on the owner’s plan. Dropbox lists a 2 GB limit for Basic, Plus, and Family, and a 250 GB limit for Professional, Essentials, Business, Business Plus, Standard, Advanced, and Enterprise. The latter listed plans also have request deadlines and a late-upload option. Collected files use the owner’s Dropbox space. Dropbox’s file request instructions

A per-file limit is not a promise that enough total space remains for the intake. As a planning example, 12 speakers sending a 40 MB slide deck and a 4 MB portrait each would submit 528 MB in decimal units: 12 × (40 + 4). Corrected copies would add to that amount. Check the space available in your own account before inviting submissions; this example does not assume a particular plan’s storage allowance.

Tell speakers exactly what to submit

Specify the deliverables, versions, formats, deadline with time zone, and a contact for problems. A filename convention makes follow-up easier, though the organizer still needs to check the files themselves.

Here is editable copy from the sample request and follow-up messages:

Subject: [event] speaker files due [date, time, time zone]

Upload to [file-request URL]. No Dropbox account is required. Your submission ID is [ID]. We need [ID]_slides_v2.pdf and [ID]_portrait_v1.jpg. Please upload both files by [date, time, time zone]. If you revise a file, use the next agreed version and tell [contact] which earlier file it replaces. If upload fails, send the exact visible message and file size to [contact]. Do not send identity documents or payment details.

Replace every bracketed field before sending. Assign an ID through your existing contact list; the example IDs below are illustrative and do not identify real speakers.

Make a list of expected items

Create one row per required deliverable, not one row per person. Three speakers who each owe slides and a portrait produce six expected rows. That makes a missing portrait visible even when the same speaker has sent slides.

You can start with the blank intake register. Import the CSV into a spreadsheet, then fill in the submission ID, deliverable, required version and extension for each item. As files arrive, record the received filename and date, whether you opened and checked the content, the status, and any follow-up. Spreadsheet import menus vary by application.

Keep the working register to the minimum information needed to contact and identify submitters. Do not put personal contact details in a public sample CSV. Match a received file against both its submission ID and deliverable: an extra slide deck cannot fulfill a missing portrait. If someone sends a correction, record the new version separately and identify which earlier file it replaces instead of silently erasing the earlier entry.

Reconcile the sample intake

A local CSV reconciliation run on October 7 compared six expected item rows with six illustrative received rows. The result file keeps all six expected items; an unmatched file holds the extra row.

Expected item	Recorded submission	Reconciliation result
S01_slides_v2.pdf	S01_slides_v2.pdf	Ready for content check
S01_portrait_v1.jpg	S01_portrait_v1.jpg	Ready for content check
S02_slides_v2.pdf	S02_slides_v1.pdf	Replacement needed
S02_portrait_v1.jpg	None recorded	Missing
S03_slides_v2.pdf	S03_slides_v2.pdf	Ready for content check
S03_portrait_v1.jpg	S03_portrait_v1.png	Replacement needed
No expected item for X99	X99_slides_v2.pdf	Unmatched; confirm the ID

Three filenames match the expected version and extension, two need replacements, and one expected item is missing. The seventh table row is the unmatched received record, not another expected deliverable. These are illustrative CSV records, not actual Dropbox uploads. “Ready for content check” means the recorded filename matches; it does not mean the deck opens, contains the agreed content, or is approved. Open and check a known sender’s file, then mark it complete only after confirming the accepted version.

Follow up on the specific gap

The register gives S02 a precise follow-up: the slides are an older version, and no portrait is recorded. The reusable message says:

Subject: S02: updated slides and portrait still needed

We received S02_slides_v1.pdf. We need the agreed v2 slides and have no portrait recorded. Please upload S02_slides_v2.pdf and S02_portrait_v1.jpg at [file-request URL] by [date, time, time zone], or tell [contact] if you need an extension.

For S03, request an exported JPG portrait. Merely renaming .png to .jpg does not convert the image. For X99, ask through a known contact channel which assigned ID the submission belongs to before opening an unknown file or crediting it to a speaker. An unmatched ID alone does not establish that the file is malicious.

Close the intake after review

Dropbox lets the owner close a request to stop uploads and reopen it later. Keep the received files and review register when closing. Check the whole intake first: closing a request because one speaker is finished could stop others who still need to submit. If someone is late, contact them through the channel you already use and decide when to reopen the request. Dropbox’s file request instructions

Source note: Dropbox steps come from the linked help pages. The October 7 reconciliation was a local CSV exercise, with no Dropbox account trial or file-content test.