Practical guide

Collect relatives’ photos into an intake area

Last materially reviewed 2026-09-28

Quick answerCollect contributions separately from accepted masters, then review ownership, duplicates and context before merging.
What to know

Give contributors a clear request

Specify the event or date range, preferred original files and any context that would help identification. Ask them not to send unrelated private material. A vague request for all family photos can produce compressed copies, repeated exports and information nobody intended to distribute. Keep instructions short enough that a nontechnical contributor can follow them.

What to know

Use a separate intake location

pCloud describes file requests that let contributors upload without seeing a folder’s existing contents. Confirm the actual settings and plan before using that route. Regardless of tool, keep new contributions apart from accepted masters until reviewed. An incoming file should not silently overwrite a same-named original already in the archive.

What to know

Review before acceptance

Record the source privately, check whether the contributor is entitled to share the image, and distinguish originals from edited or social-media copies. Preserve uncertainty about dates and people. Do not publish identifiable images merely because someone could upload them. This publication supplies an organization framework, not legal permission to use another person’s photographs.

What to know

A fictional collection round

For a reunion, ask for original files from a defined weekend and a short description. Label the intake by contribution batch, review apparent duplicates and create an approved sharing selection. Keep unreviewed material out of the public pack. When the collection period ends, review whether the intake route should remain open under the provider’s available controls.

What to know

Close the collection loop

Tell contributors what was accepted, what remains uncertain and whether more material is needed. Keep that communication proportionate and private. Do not publish a list of contributors or personal details merely to document provenance. When the requested scope is complete, review the intake route and separate unreviewed leftovers from accepted masters. A folder full of uploads is the beginning of review, not its completion.

Continue when useful

Next: Staged uploads

Use labelled batches with a start and finish check; a running upload is not an accepted archive.

Open Staged uploads →

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.

  1. pCloud file sharing — Merchant documentation · pcloud.com · Merchant-controlled · checked 2026-09-28
  2. pCloud uploading and organizing — Merchant documentation · help.pcloud.com · Merchant-controlled · checked 2026-09-28