[Feature]: Allow specifying output file name

[FF-Brown]

🚀 Feature Request

I'd like to be able to specify my own name for the output file. Anything other than index.html.
Opening because #17407 was closed without resolution, and I'd really like this feature.
If it's approved, I'll implement it. I've pretty much got it written already.

Example

No response

Motivation

Improved flexibility, and a feature that's very common in similar software, so users expect it. I certainly did.

[github-actions]

Hi, I'm the Playwright bot and I took a first look at this.

Valid request — not currently possible. The HTML reporter hardcodes index.html; only the containing folder is configurable via outputFolder. I confirmed this on macOS against tip-of-tree (@playwright/test@next, 1.64.0-alpha-2026-09-14): a run with ['html', { outputFolder: 'my-report' }] produces exactly one entry, my-report/index.html. The workarounds in #17407 all rename the folder, which is why PandharabaleAniketJohnDeere's comment there still stands.

One thing worth flagging for whoever picks up the design: the file name isn't just an output detail, it's baked into how the report is consumed. Renaming it after the fact breaks show-report, and the report-zip loader hard-requires index.html at the top level.

What I ran on macOS

// playwright.config.ts — @playwright/test 1.64.0-alpha-2026-09-14
import { defineConfig } from '@playwright/test';
export default defineConfig({
  reporter: [['html', { outputFolder: 'my-report', open: 'never' }]],
});

$ ls -1 my-report
index.html

Adding a speculative fileName: 'custom.html' to the reporter options is rejected by the types and silently ignored at runtime — the run still emits index.html, with no warning.

Renaming the file by hand breaks serving:

$ mv my-report/index.html my-report/custom.html
$ npx playwright show-report my-report --port 9323
$ curl -o /dev/null -w '%{http_code}' http://127.0.0.1:9323/           # 404
$ curl -o /dev/null -w '%{http_code}' http://127.0.0.1:9323/custom.html # 200

So show-report only works if the visitor knows the custom name and types it into the URL. Same constraint applies to static hosts (GitHub Pages, S3, nginx), which serve index.html as the directory index.

Current option surface

HtmlReporterOptions (packages/playwright/types/test.d.ts) is outputFolder, open, host, port, attachmentsBaseURL, title, noSnippets, noCopyPrompt, doNotInlineAssets, mergeFiles — no file-name knob. The write path is packages/playwright/src/reporters/html.ts, where both _writeStaticAssets() and the report-index path join 'index.html' onto the report folder unconditionally. The zip loader at html.ts:250-253 throws No "index.html" found at the top level of "<zip>", so show-report/merge-reports would need plumbing too, not just the writer.

The feature question for the maintainers is therefore narrower than "allow a name": what should show-report, merge-reports and static hosting do when the entry point isn't index.html? Worth answering before any implementation lands.

_{Triaged on macOS by the Playwright bot - agent run}

[FF-Brown]

"Not currently possible" is misleading. The change is very possible. All these issues are now addressed on a local branch of mine. Here's the current approach:

• Added a fileName option to the HTML reporter so the report file name is no longer hardcoded to index.html
• show-report now accepts a direct path to a custom-named HTML file and serves it correctly
• The zip report archive path now also supports a custom name. If index.html isn't present at the top level, it looks for a single HTML file there, erroring clearly if there's not exactly one. We could add a param to this command to specify the name of the file to look for, but it shouldn't be necessary.
• With the current approach, merge-reports also works. It gets the name automatically through HtmlReporter.

Static hosting behavior is the responsibility of the hosts. With these changes, everything playwright controls respects a custom name.

[dcrousso]

can you please explain more about why you want to rename the file?

does mv path/to/index.html path/to/rename.html not suffice?