VeilBrowserDocs

Profiles

Create and configure browser profiles: OS target, browser version, proxy and storage.

A profile is a saved browser identity. Each profile has its own fingerprint, proxy, cookies and storage, fully isolated from every other profile.

Anatomy of a profile

Create requests use the ProfileSpec shape (name required on create):

Prop

Type

Browser versions are bounded

browserVersion must be between 135 and 150. Values outside that range are rejected with a VALIDATION_ERROR before the profile is created.

Creating a profile

Pick an OS target

Choose win, mac, linux, or android. The OS target drives the user-agent, platform, fonts and device metrics. Keep it stable for the lifetime of the identity — changing it swaps the underlying browser build and breaks the identity's continuity.

Android profiles take a device model

Choosing android unlocks the optional model field, which pins bundle selection to a specific handset so every launch presents the same device. Workers expose GET /profiles/android-models to discover the models available for a given browser version. Leave model empty to accept any Android device the worker has.

Set a browser version

browserVersion is a required integer major between 135 and 150 (for example 147). It selects which browser build the worker launches for this profile.

Choose a profile type

persistent profiles are kept after the session ends and reused on the next launch. one-time profiles are soft-deleted as soon as their session ends — useful for throwaway scraping identities that should never be reused.

Isolation guarantees

  • Cookies, localStorage, IndexedDB and cache are per-profile.
  • No shared browser state leaks between profiles.
  • Deleting a profile removes its stored state.

One launch per profile

A profile represents a single device. Launch a given profile once at a time so its cookies and storage stay coherent.

Managing profiles at scale

Beyond create and delete, the cloud API supports listing with filters and pagination, bulk deletion, and duplication. See Profiles in the API reference for the full parameter set.

Next steps

  • Fingerprints — what the OS and version criteria actually select.
  • Proxies — network routing.
  • Connect — launch a profile on your own machine.
Was this page helpful?

On this page