Why doesn't Dropbox render my HTML file anymore?

Dropbox removed HTML rendering from shared links — for Basic and Pro accounts in September 2017, and for Business accounts shortly after. Shared `.html` links now show a preview page with a download button instead of the rendered document. It was withdrawn deliberately, as an abuse and phishing mitigation, so it is not coming back.

Does the ?raw=1 or dl=1 trick still work for HTML?

Not for rendering. `?dl=1` forces a download, and `?raw=1` serves the file's bytes but with headers that stop the browser treating it as a page you are visiting. Both were commonly used to host small pages from Dropbox before 2017; neither renders HTML now.

What about the public folder?

The Public folder was retired even earlier — Dropbox ended it for existing accounts in 2017. There is no folder in a modern Dropbox account whose contents are served as web pages.

How do I share an HTML report so it just opens?

Publish it to a URL. Drop the file, or the whole output folder, into Comma and you get a link that renders in any browser. Assets upload alongside the entry file and relative references are rewritten, so the report keeps its styling and its interactive parts.

Can I still use Dropbox for the raw files?

Yes, and that is a reasonable split — Dropbox for storage and version history of the source artifacts, a published URL for the rendered report people actually read and comment on.

Dropbox stopped rendering HTML files

You dropped report.html into Dropbox, copied the share link, and the person who opened it got a Dropbox preview page with a download button — not the report.

Nothing is misconfigured. The feature was removed.

What happened

Dropbox used to render HTML shared links in the browser, and a lot of people used it as a zero-effort static host for one-off pages and reports. It was withdrawn in September 2017 for Basic and Pro accounts (Business accounts followed), as an anti-abuse measure — the same rendering that served your coverage report served a convincing fake login page just as well.

The two workarounds people still post don't bring it back:

?dl=1 forces a download. That is what it was always for.
?raw=1 returns the file bytes, but not with the headers a browser needs to treat the response as a page it is visiting. You get a download or a plain-text dump, not a rendered document.

The old Public folder, which did serve files directly, was retired for all accounts around the same time.

The second problem, which storage was never going to solve

Most tools that emit "an HTML report" emit a folder: index.html plus a sibling directory of CSS, JavaScript and JSON. Playwright, Allure, genhtml, nbconvert, Sphinx and Storybook all do this.

Share just the .html and every reference in it resolves to nothing — that's the blank or half-styled version of the same failure. See why the report lost its CSS.

And even in the best case, you have shipped a copy. Everyone who wants to discuss it has their own download, and the only way to say "this number is wrong" is a screenshot with an arrow on it.

The fix: publish it, don't store it

Drag the file — or the whole output folder, or a zip — into Comma:

index.html becomes the report body.
Sibling assets upload with it and relative src/href references are rewritten to the uploaded copies.
Scripts run inside a sandboxed iframe (allow-scripts, no allow-same-origin), so filters, sortable columns and charts keep working. See interactive HTML reports.

One URL, and it opens on a phone too — which the Dropbox app never did for HTML.

Who can see it

Per report: private, team, anyone signed in at your domain, or anyone with the link, with view / comment / edit rights for link holders. Full model in sharing & access control.

This is per-report rather than per-folder, which is usually what you actually wanted from the Dropbox share dialog anyway.

If the report regenerates, publish from the job

curl -fsS -X PATCH "https://commareports.com/api/v1/reports/$REPORT_ID" \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html report.html '{html: $html}')"

PATCH one saved id and every run appends a revision at the same URL, so the link you pasted in a doc six months ago still shows the current report. See publishing from CI and API tokens.

Then: comment instead of screenshot

Once it has an address, feedback goes on the report — select the cell, leave a thread, and it stays anchored across revisions. See commenting on HTML.

Limits

Entry HTML: 5 MB. Assets: 25 MB per file, 250 MB and 500 files total.
Scripts run, sandboxed — no same-origin access to your session.
60 requests/minute per token.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Publish your HTML file →