Comma

WeTransfer alternatives for sending a report

WeTransfer exists because email attachment limits are absurd, and at that job it is flawless: drop a file, send a link, done.

It is also completely indifferent to what happens next — which is a problem when the file is an HTML report rather than a video. The recipient downloads Q3-analysis.html, double-clicks it, and gets a text editor, a security warning, or a page with no styling.

What breaks when the payload is HTML

  • A downloaded HTML file often doesn't open. Corporate machines block or unassociate it; browsers flag "file downloaded from the internet"; on iOS and Android it usually downloads rather than renders. See opening an HTML file on iPhone.
  • Relative assets vanish. Charts, fonts and images that lived in a sibling folder do not travel with a single file, so the report arrives half-drawn. See why the CSS is missing.
  • Links expire. Fine for a deliverable, bad for a reference document.
  • No comments, no versions. Feedback arrives as an email describing a chart. The corrected version arrives as Q3-analysis-final-v2.html.
  • No idea whether they read it. A transfer service tells you a file was downloaded, not whether the number on page four was seen.

The shortlist

1. Comma — send a page, not a file

Publish the report and send its URL. The client opens a rendered page in a browser — no download, no file association, no missing CSS:

  • Assets included. Upload a zip bundle and relative paths resolve exactly as they did on your machine.
  • Access you choose. Private, team, your email domain, any signed-in user, or an unlisted link — so an external client needs the link, not an account. Password and expiry options exist on top of that at the higher tier, as an addition to identity rather than a substitute for it.
  • Comments where the disagreement is. They select the number and leave a thread on it; you reply in the same place. See commenting on HTML.
  • Revisions at one URL. Send the corrected version by re-publishing to the same id. The link you already emailed shows the new version, and the old ones stay diffable — no -final-v2 in anyone's downloads folder.

Not for: sending a 4 GB video or a folder of raw footage. Use a transfer service; that is what it is for.

Pricing: Free — unlimited reports, unlimited viewers and commenters.

Share an HTML report with a client →

2. Google Drive / Dropbox — durable storage, wrong renderer

Both give you real identity-based sharing and neither renders HTML usefully: Drive serves it as a download or a stripped preview, Dropbox shows a preview page rather than your report. Good for the source files, a dead end for the deliverable. See Dropbox HTML preview and Google Docs, for HTML.

3. Export to PDF — the honest low-tech answer

If the report is static and the client just needs to read and archive it, PDF opens everywhere and needs no explanation. You lose every interactive chart and any table wider than a page, and comments live in whatever PDF tool they happen to run. Worth it sometimes.

4. Email the HTML inline

Some reports are small enough to send as an HTML email body, which sidesteps downloads entirely — and email clients strip most CSS and all JavaScript, so anything interactive dies. See emailing an HTML report.

At a glance

Option Opens for the recipient Assets survive Expires Comments
Comma Yes — a web page Yes No Yes
WeTransfer Downloads a file Only in a zip Yes No
Drive/Dropbox Download or preview Only in a zip No On the file
PDF Yes Flattened No In a PDF tool
HTML email Sometimes Inline only No By reply

Checked September 2026.

How to choose

Related