Request a stable screenshot API that captures the current rendered frame without waiting for page stability

[wuomzfx]

Summary

I'd like to request a more stable screenshot API in playwright-cli.

Today, playwright-cli screenshot can fail on complex pages because of things like font readiness, pending resource loading, or unstable rendering state.

I also tried bypassing it with run-code + CDP Page.captureScreenshot, but that is still not reliable enough on some real pages.

What I need

I need a screenshot API with this behavior:

• do not wait for page stability
• do not wait for fonts or all resources to finish loading
• just capture whatever is currently rendered in the browser right now
• if the page is partially rendered, that is fine
• if resources are still loading, that is also fine
• returning a valid screenshot is more important than waiting for a "perfect" screenshot

Why this matters

For debugging and E2E evidence collection, an imperfect screenshot is often much better than no screenshot.

Right now, there is no reliable "capture now" API:

• the built-in screenshot path can fail
• direct run-code + CDP is also not stable enough as a workaround

Request

Could playwright-cli provide a stable screenshot API or mode whose contract is:

capture the current rendered browser frame as-is, without waiting for page stability, font readiness, or resource completion

Something like:

• playwright-cli screenshot --capture-now
• playwright-cli screenshot --no-wait
• playwright-cli screenshot --best-effort

The exact name is not important. The key is to prioritize operational reliability over screenshot completeness.

[yury-s]

The closes thing to your request that we have today is video recording. See this skill which is installed by playwright-cli install --skills. If you start recording before running your scenario should capture the video in non-disrupting manner. Would this work for you?

Another, low level, option would be to write only the latest screencast frame from the listener in the code.

• the built-in screenshot path can fail

Can you elaborate on what that means in your case?

[wuomzfx]

@yury-s Thanks for the suggestions.

I am already using playwright-cli for both screenshot capture and video recording.

For video recording, one practical issue I am facing is that AI-driven playwright-cli actions can be relatively slow. As a result, the recorded video often contains long periods of idle/blank time between meaningful actions. Currently, I do not see an API or built-in mechanism that lets me mark or record the timestamps of key action points, so it is hard to quickly jump back to the exact frame where a specific action happened.

Because of that, I would like to take screenshots at important action points as lightweight evidence/checkpoints. However, this is where I ran into the screenshot stability issue.

Unfortunately, I asked my coding agent to make several attempts, but we were not able to produce a minimal reproducible HTML demo. What I can say clearly is that the real page is quite complex. It is a large micro-frontend application. In headed mode, taking screenshots has a relatively high chance of hanging or timing out. In headless mode, the same workflow is much more stable.

So in my case, video recording is useful, but it does not fully replace the need for reliable best-effort screenshots at key moments. A supported way to capture the currently rendered frame, even if the page is not fully stable, would still be very helpful.