Should I replace Playwright tests?

No. PageCapture produces artifacts; it is not a test runner and does not replace assertions or multi-browser coverage.

Does the API use Playwright?

The initial engine uses Chromium controlled by Playwright, but the public contract is the HTTP API rather than Playwright internals.

When should I keep my worker?

Keep it when browser control is core, the pool is already reliable, or the job requires Firefox, WebKit or arbitrary interaction.

Playwright operations

Move screenshot jobs out of your Playwright serverless function

Playwright remains the right tool for tests and unrestricted browser sessions. The API covers the narrower job of turning hostile input into a delivered artifact.

Run the live demo Configure the live request

Capture settings

Enter the source, choose your options, then run the capture.

Result

Your capture will appear here and stay in view.

waiting

No result yet

Complete the settings and run the tool. Images, PDFs, text, and video all preview in this panel.

Send this exact request

cURL, TypeScript and Python are generated from the same configuration as the demo.

curl --fail-with-body "https://api.pagecapture.dev/v1/take" \
  -H "X-Access-Key: $PAGECAPTURE_KEY" \
  -H "Content-Type: application/json" \
  --data '{"url":"https://example.com","format":"png","full_page":true,"full_page_scroll":true}' \
  -o capture.png

Smaller application deploy

The app no longer packages a browser binary and its native dependencies for screenshot jobs.

Backpressure outside the process

Browser contexts are admitted by quota and queues instead of consuming unbounded function memory.

Keep testing in Playwright

Assertions, Firefox/WebKit and unrestricted evaluation are explicitly outside this migration.

Contracted action order

The public capture sequence is stable, versioned and part of the resulting cache key.

Use this when

Cold starts, browser binaries, memory or queueing dominate a screenshot endpoint.
The output job fits the PageCapture action contract.

Do not use this when

You are running end-to-end tests or need assertions over page state.
Firefox, WebKit or unrestricted Playwright APIs are requirements.

Workflow

From input to verified artifact

01
Keep the fixture
Use the same URL and readiness signal from the current Playwright job.
02
Replace the runner
Send those values to /v1/take instead of launching a local browser.
03
Migrate gradually
Compare artifacts and error handling before removing the existing worker.