Share Playwright HTML reports without zip files or broken attachments

Playwright’s HTML reporter already has the traces, screenshots, and filters your team needs. ReportArk hosts that finished output so reviewers open one link instead of downloading another archive.

Uploading a finished Playwright HTML report package

Export a shareable Playwright HTML report

ReportArk does not replace Playwright. Keep generating reports in CI or locally, then upload the folder Playwright already knows how to build.

Enable the HTML reporter
In playwright.config.ts set reporter: [['html', { open: 'never' }]] (or the CLI equivalent). After the run, Playwright writes an interactive report under playwright-report/ by default.
Keep attachments next to index.html
The report folder contains index.html plus data/, trace zips, screenshots, and videos. Zip the whole directory so relative paths stay valid after upload.
Upload once, share the link
Upload the zip to ReportArk. Viewers open /reports/{id} and get the same filters, flaky markers, and trace viewer entry points—no local npx playwright show-report required.

Why teams host Playwright here

CI artifacts expire. Review conversations should not.

Playwright HTML is excellent locally and in short-lived CI storage. Sharing for triage across timezones needs a stable link, optional password, and comments that point at the failing test—not another Slack thread of screenshots.

Full interactivity preserved

ReportArk serves the static report as-is: suite filters, retry history, and attachment links keep working inside the secure viewer.

One link for stakeholders

Product and QA can open the same URL. Forwarding the link grants view access; commenting still requires an approved signed-in account.

Discuss next to the failure

Pin comments on the relevant row or attachment context so “which test?” is never ambiguous when someone joins hours later.

FAQ

Playwright report sharing questions

Practical details when moving from show-report to a durable share link.

What exactly should I zip?

Zip the HTML report output directory (commonly playwright-report/) so index.html sits at the archive root along with its data and trace assets. Do not zip only index.html.

Will traces and videos still open?

Yes, as long as those files were part of the uploaded package. ReportArk hosts the static files; it does not regenerate traces.

Can I replace a report without changing the link?

Owners can upload a new content version on the same report URL, which is useful when CI re-runs the same build and you want reviewers on one bookmark.

Is the report indexed by search engines?

No. Report pages and assets are served with noindex. Sharing is for people with the link, not public search results.

Turn the next Playwright run into a review link

Generate the HTML report you already trust, upload the folder, and send one controlled link to the people who need to decide.