Repository navigation
[Feature] Add ability to specify video params (like fps) for video recordings #17217
Closed as not planned
Description
Would be good to specify params for video recordings like fps
const context = await browser.newContext({
recordVideo: {
dir: 'videos/',
size: { width: 640, height: 480 },
fps: 25
}
});Reacted by Luca Di Leo, NoChesky, Matthieu, Sarah, Po Chun Chiu, John, Quinn Slack, akhmadshin, Lucas, Oleksii Siryi and 26 more
Activity
[-]Add ability to specify video params (like fps) for video recordings[/-][+][Feature] Add ability to specify video params (like fps) for video recordings[/+]HeDo88TH commentedon Sep 26, 2022
This is a missing piece, we need this.
pavelfeldman commentedon Nov 16, 2023
Why was this issue closed?
Thank you for your involvement. This issue was closed due to limited engagement (upvotes/activity), lack of recent activity, and insufficient actionability. To maintain a manageable database, we prioritize issues based on these factors.
If you disagree with this closure, please open a new issue and reference this one. More support or clarity on its necessity may prompt a review. Your understanding and cooperation are appreciated.
pavelfeldman commentedon Nov 17, 2023
Why was this issue closed?
Thank you for your involvement. This issue was closed due to limited engagement (upvotes/activity), lack of recent activity, and insufficient actionability. To maintain a manageable database, we prioritize issues based on these factors.
If you disagree with this closure, please open a new issue and reference this one. More support or clarity on its necessity may prompt a review. Your understanding and cooperation are appreciated.
terion-labs commentedon Aug 4, 2025
years pass...
angel1254mc commentedon Mar 14, 2026
This would be awesome. Our team has been experimenting with using Playwright to automate demo recordings. The idea is to generate scripted browser walkthroughs that could be regenerated with every release. Configurable FPS would let us produce smoother, more professional output for these kinds of non-test use cases.
Totally acknowledge that Playwright is at the mercy of the browser's devtools protocol when it comes to the count/timing of frames it receives, so we can't really guarantee that a user's desired FPS will be respected.
One approach could be adding an optional
fpsparam torecordVideothat lets users set a target fps for the output video (defaults to today's 25 fps). If the browser sends enough frames, awesome. Otherwise the user just gets repeated frames to fill the gap, which matches how it works today at the hardcoded 25 fps. Thoughts?MuTsunTsai commentedon Apr 27, 2026
Hi Rachit (@rachitm022), Angel Lopez Pol (@angel1254mc), @terion-name — for the FPS / demo recording use case described here,
playwright-recorder-plusmight be useful:fpsoption (default 25), pluggable viaattachRecorder(page, { fps: 60 }).Wraps Playwright 1.59+'s public
page.screencastAPI + ffmpeg-static, no patching needed. Not a Playwright maintainer; sharing in case it unblocks anyone.azmeuk commentedon May 26, 2026
Would like to widen the scope of this issue to cover the sibling encoding parameters that share the same pipeline:
My use case is generating screencasts for library documentation (with sphinxcontrib-screencast, which drives Playwright in headless). The default VP8 encoding produces artefacts on small monospaced text in code blocks so being able to tweak the parameters would help. Also, tweaking would allow to produce smaller artefacts.
Suggested shape, extending the original example:
pavelfeldman commentedon Oct 31, 2026
We're closing all
P3-collecting-feedbackissues and retiring the label. #43813 explains why. This doesn't mean the request is wrong. If it still matters to you, please open a new issue against the latest Playwright version with your concrete use case and link back here.