5 items
Record browser interactions as Playwright traces. Saved locally, no backend needed. Download and replay at trace.playwright.dev. Record any browser session and instantly produce a Playwright-compatible trace — no backend, no Node.js, no CLI setup required. What it does Playwright Trace Recorder captures every click, keystroke, scroll, and form input you make in Chrome and packages them into a standard .zip trace file — the exact format used by Playwright's built-in tracing API. Each trace includes: Screenshots at every action (before and after) DOM snapshots so you can inspect the full page state at any point Console logs and errors from the page Network requests and responses A complete timeline of all interactions When you're done recording, click Download to save the trace, then drop it onto trace.playwright.dev to replay and inspect it in Playwright's full trace viewer — step through every action, see what the page looked like, and drill into network activity. Why install it No setup — works entirely inside Chrome. No server, no npm install, no configuration. Debug faster — reproduce exactly what happened during a session, including the DOM state and network traffic at each step. Share bug reports — hand a trace file to a developer and they can see precisely what you did and what the app showed. Bridge manual testing and automation — record a flow manually, then use the trace as the reference for writing Playwright tests. Works on any website — captures interactions on http and https pages across any web application. Traces are stored locally in your browser and never sent anywhere. You control when to download or delete them.
Apr 15, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.