✓ Independent creative professionals
✓ Small studio client handovers
✓ Bounded final-file releases
— Regulated-data suitability certification
— Legal acceptance or retention advice
— Specialist video proofing
— Household photo archives
Estimate the incoming package
Ask about the largest likely file and the approximate total, not just the number of attachments. A short set of source files can be much larger than many reference images. Check current service and plan limits against that package. Avoid discovering a predictable limit only after a client has spent time preparing an upload that cannot complete.
Leave room in the destination
Incoming files can consume the request owner’s storage. Account space used by other projects still matters. Keep a practical buffer for duplicate submissions and working copies, but do not promise an unlimited intake simply because the subscription has a large advertised capacity. The client’s successful selection of files does not establish that all bytes reached the destination.
Make the deadline intelligible
Use a date, time and time zone when timing matters. Explain whether the deadline closes the technical route or merely marks the production cutoff. Those are different commitments. Allow a clear route for reporting an upload problem before the deadline; do not treat a technical failure as proof that the client deliberately missed an obligation.
A fictional intake window
A client is expected to provide a 3 GB source package by Tuesday afternoon. The studio checks the actual per-file and total-space limits, supplies the time zone and asks for confirmation after upload. If only the first part arrives, the request remains incomplete. The studio records the missing part and its effect on production instead of assuming a notification means the full package was accepted.
Put the decision into practice
Record the largest expected item, available destination space, technical closing time and production cutoff separately. If those values are uncertain, say which one needs confirmation. This prevents a client from interpreting a successful upload after the production cutoff as proof that the new material has already been incorporated.
Where the safety evidence stops
This guide draws on pCloud file requests, Dropbox file requests. Merchant-controlled records describe the provider’s own capabilities, terms or standards; they do not independently validate those claims. These records do not establish independent confirmation of the product claims.
Verify any current price, plan limit, label direction, compatibility rule, or commercial term that would materially change the decision. The dated source ledger shows the underlying records so this conclusion can be checked and updated.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- pCloud file requests — Merchant documentation · help.pcloud.com · Merchant-controlled · checked 2026-09-29
- Dropbox file requests — Merchant documentation · help.dropbox.com · Merchant-controlled · checked 2026-09-29