Public beta · v0.1.3

Run the web.
Skip the rendering.

The website’s own JavaScript. Browser state. No Chromium.
Built for automation.

Terminal
// Start Mimic separately:
// ./mimic --listen 127.0.0.1:9222 --chrome 152

import { chromium } from "playwright-core";

const browser = await chromium.connectOverCDP(
  "http://127.0.0.1:9222"
);
const context = browser.contexts()[0];
const page = await context.newPage();
await page.goto("https://example.com/");

Quickstart

Get up and running locally in a few minutes.

mimic --listen 127.0.0.1:9222
Read the complete setup guide

Chrome 152 reference

Implements observable Chrome behavior, aligned with Chrome 152.

One event loop per Page

Each Page runs in a single event loop, matching browser semantics.

No GPU required

Runs on CPU. No GPU or system browser installation needed.

Working browser behavior

Use the tools you already know.

Connect stock Playwright or Puppeteer clients over CDP. Mimic owns the runtime; your automation keeps its familiar interface.

01

Navigate and inspect

Load HTTP pages, evaluate JavaScript, query the DOM, and observe lifecycle and network events.

02

Interact with application state

Use locators, fill form controls, click actions, work across frames and Shadow DOM, and observe popup pages.

03

Run concurrent Pages

Each Page owns its runtime and event loop. BrowserContexts isolate profiles, cookies, and connection pools.

Verified checkpoint38/38 checks

Two project regression suites cover navigation, locators, forms, fetch/XHR, frames, Shadow DOM, popups, redirects, cookies, history, multi-page state, and network observation.

Mimic’s own compatibility checks, not the official Playwright test suite.
Measured, not assumed

A lighter runtime for supported workloads.

Fresh Windows build measured September 14, 2026 against Chrome 152.0.7977.82 in controlled local fixtures.

92%lower CDP-ready RSS28.84 MiB vs 376.26 MiB
62%less active RAM at 50 Pages1,568.62 MiB vs 4,079.95 MiB
3.32×throughput at 50 Pages69.64 vs 21.00 sessions/s
Mimic and Chrome CDP readiness and startup memory benchmarkMimic and Chrome static concurrency benchmark

These results describe specific fixtures and this machine, not arbitrary websites or production cost. Some workloads still favor Chrome. Read the methodology →

Configure once

Describe the environment. Then automate.

A versioned profile controls browser-visible screen, locale, hardware, preferences, networking, and supported capabilities before the first page loads.

  • Validated JSON Schema
  • Independent profiles per BrowserContext
  • Native SOCKS5, HTTP, and HTTPS proxies
Explore profile schema v1
profile.json
{
  "schemaVersion": 1,
  "baseProfile": "chrome-152-windows-x64-headful-controlled-v1",
  "hardware": { "logicalProcessors": 8, "deviceMemoryGB": 8 },
  "locale": {
    "languages": ["en-US", "en"],
    "timezone": "America/New_York",
    "intlLocale": "en-US"
  },
  "preferences": { "colorScheme": "dark" }
}
Explicit boundaries

Know when to use a full browser.

Mimic is a public beta and implements a subset of browser APIs and CDP. It is designed for supported execution workflows—not visual output or universal Chrome compatibility.

No screenshots or rendered PDFsNo complete CSS layoutNo Canvas/WebGL pixels or videoNot a sandbox for hostile codeWindows & Linux amd64 onlyTrusted local CDP clients only
Review compatibility boundaries
Public beta

Let the website do the work.

Download Mimic, start the local runtime, and connect your automation.

Download v0.1.3