Profiles

A profile is a persistent identity: a stable device fingerprint plus a user-data-dir that keeps cookies, logins, and localStorage across sessions. Attach one to stay logged in between runs, or omit it for a clean ephemeral browser.

Persistent vs ephemeral

By default a session is ephemeral: you get a clean browser with no prior state, and nothing is kept when you disconnect. Attach a profile to make the session persistent: its user-data-dir is keyed by the profile UUID, so cookies, logins, and localStorage carry over from one session to the next.

What a profile stores

Profiles are created and edited in the dashboard. Each one records:

• Name and whether it is the account default.
• Region and platform (the OS persona).
• Chrome version and the full user agent.
• Screen size, device scale factor, and hardware concurrency (reported CPU cores).
• A fingerprint seed that derives the coherent device fingerprint.

Alongside that configuration, the profile keeps a persistent user-data-dir: the cookies, logins, and localStorage that accumulate as you browse.

Attaching a profile

Add ?profile=<uuid or name> to the connection URL. Profiles are owner-scoped, so only your account can attach them. Omit the parameter for an ephemeral browser.

from playwright.sync_api import sync_playwright

# Attach a persistent profile and route it through a US exit
CDP = "wss://USER:PASS@browser.capzy.ai/cdp?profile=my-identity&proxy=capzy-US"

with sync_playwright() as p:
    browser = p.chromium.connect_over_cdp(CDP)
    page = browser.contexts[0].new_page()
    # Cookies and localStorage from previous sessions are already loaded.
    page.goto("https://example.com/account")
    print(page.title())

Default profile

You can mark one profile as the default in the dashboard. It is the natural attach target when you want a single persistent identity without passing an explicit id in the URL.

Rotating the fingerprint seed

You can rotate a profile's fingerprint seed while keeping the same device identity. The stored persona (platform, screen, user agent, and so on) stays the same, so the profile still looks like the same class of device, while the per-seed rendering noise changes. The user-data-dir is unaffected, so logins and cookies survive the rotation.