Practical guide

A browser preview is not the same as a usable original

Last materially reviewed 2026-09-29

Quick answerCheck the required downloaded file and format; a preview establishes a narrower result than production-ready delivery.
What to know

Name the intended use

A client reviewing an appearance may need a preview. A printer, editor or developer may need the actual production file, including dependencies or a particular format. Write the required use in the manifest. Do not expect the recipient to infer it from the largest file or the first item shown in a web interface.

What to know

Inspect the downloaded result

Use an appropriate local application to check a representative harmless sample through the intended route. Confirm the file is the version and format expected. A browser can show a convenient representation without establishing that the underlying package will open in the client’s working application. This is a workflow distinction, not a claim that pCloud alters every preview or download.

What to know

Keep compatibility separate from transfer

A file may transfer correctly but require software the recipient does not have. Conversely, an application error may reflect an incomplete or wrong download rather than a product defect. Diagnose these separately. Preserve the release and avoid repeatedly exporting different formats until the actual requirement is understood, particularly when a conversion could remove useful structure or fidelity.

What to know

A fictional production check

A client sees a brochure preview and assumes it is ready for the printer. The delivery note instead identifies the print PDF and its intended use, while a separate image is labeled preview only. The studio checks the relevant package against the agreed production requirements. A successful web preview is recorded as preview success, not proof of print approval, color accuracy or acceptance by the printer.

What to know

Put the decision into practice

Label previews and production files by intended use, not only by size. Include a short compatibility note when a specialist application is required. That note should help the client choose the correct route without implying that this publication or the storage provider has certified the production quality of the deliverable.

Continue when useful

Next: Recipient check

Observe the intended recipient task with a harmless sample; an owner’s successful preview does not establish that a client can retrieve and use the release.

Open Recipient check →

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 shared links — Merchant documentation · help.pcloud.com · Merchant-controlled · checked 2026-09-29
  2. pCloud file transfer and organization — Merchant documentation · help.pcloud.com · Merchant-controlled · checked 2026-09-29