If your job repeatedly runs JavaScript to extract HTML or JSON, its result may not need rendered pixels. Mimic offers a separate runtime lane for those supported workloads: V8 execution, browser state and CDP without embedding Chromium. Chromium remains the full browser option. Mimic is a source-available public beta with partial CDP and Web API compatibility.
Choose by the output and required browser behavior
| Workload requirement | Runtime choice |
|---|---|
| Plain HTTP response, with no browser JavaScript or state needed | Start with an HTTP client; a browser runtime may be unnecessary. |
| Repeated DOM or JavaScript extraction producing HTML or JSON | Evaluate Mimic if the required CDP commands and Web APIs are supported. |
| Rendered screenshots, video, PDF or full Blink behavior | Use Chromium; Mimic does not supply these rendering capabilities. |
| Unknown site behavior or unsupported browser features | Keep a Chromium fallback and validate the extracted result. |
Reading DOM HTML or structured values from JavaScript is different from proving that a page looks correct. Mimic's modeled DOM, style and geometry observations are bounded; they do not replace full browser rendering.
Memory evidence from one controlled run
The September 29, 2026 benchmark compared a particular Mimic development executable with Chrome 152.0.7977.82 in headless mode on Windows 11, an Intel i7-14700KF and 31.83 GiB RAM. These observations are not release-wide promises or a measurement of your production workload.
| Measured metric | Mimic | Chrome 152 |
|---|---|---|
| Ready process-tree RSS | 45.79 MiB | 379.54 MiB |
| Active RSS, completed 50 static Pages series | 748.11 MiB | 4102.04 MiB |
| Throughput, same 50 static Pages series | 108.67 sessions/s | 18.09 sessions/s |
RSS sums the process tree and can count shared pages more than once; ready RSS is not incremental Page memory. Throughput includes setup and teardown. The binary was built from changes later committed as 04ac211, with SHA-256 db82f1c85faca672e7225260e4d0cc603d6a867effb7ca60a540e9e14eceabc4. It is not automatically the v0.1.9 release binary.
All 12 correctness gates and 360 measured single-page attempts passed in these fixtures. Six concurrency series stopped or contained a failure; stopped levels are not successful scaling results. Chrome was faster in multiple warm completion workloads, including DOM mutations and React. These data do not establish general website compatibility, universal speed gains or a lower infrastructure bill. See the full benchmark context.
Use a separate lane with a Chrome fallback
- Define a result contract: required fields, acceptable HTML, errors and session boundaries.
- Validate a representative set of target pages against the same contract in Mimic and Chrome.
- Route proven nonvisual jobs to a separate Mimic worker pool. Independent Pages and Contexts allow isolated jobs; choose concurrency from measurements.
- Route jobs needing rendering or unsupported behavior to Chromium. Record why a job falls back; do not silently accept incomplete extraction.
- Measure total completion time, CPU, peak memory, failure rate and fallback rate before changing capacity.
If replaying a job could repeat a purchase, submission or other side effect, design that retry explicitly. The fallback is a routing policy you build, not an automatic feature promised by Mimic. Site rules and normal access controls still apply.
Begin with the runnable Playwright guide and check compatibility boundaries before moving a production workload.