Proxies

VeilBrowser supports assigning a proxy per profile. Traffic for that profile is routed through the configured proxy when the browser launches.

Supported protocols

HTTP

Standard HTTP proxy.

HTTPS

TLS-wrapped HTTP proxy.

SOCKS5

Full TCP tunnelling, DNS resolved locally.

SOCKS5H

SOCKS5 with remote DNS resolution.

Prefer socks5h over socks5 when the proxy should also resolve DNS. With plain socks5, name resolution happens on the worker host, which can reveal your real resolver to anyone correlating DNS with traffic.

Assigning a proxy

Set a proxy when creating or updating a profile. The create body uses ProfileSpec fields (name, os, browserVersion) — there is no separate profileId on create:

profile.json

{
  "name": "marketing-us",
  "os": "win",
  "browserVersion": 147,
  "proxy": {
    "type": "socks5h",
    "host": "proxy.example.com",
    "port": 1080,
    "username": "user",
    "password": "secret"
  }
}

Matching the proxy to the identity

The proxy on a profile is not just a route. VeilBrowser hands it to the browser as the browser's own proxy setting, so the browser resolves the exit IP's region itself and derives the region-dependent signals from it at launch. Assign a proxy and the timezone, locale, Accept-Language header and geolocation follow the exit IP with no further configuration.

Signal	Who controls it
Exit IP and ASN	Your proxy provider
Timezone	Derived from the exit IP at launch
Locale and `Accept-Language`	Derived from the exit IP at launch
Geolocation	Derived from the exit IP at launch
WebRTC candidates	Constrained to the proxy route
DNS resolution	Resolved at the proxy when you use `socks5h`
Canvas, WebGL, audio, fonts	Fixed by the profile you selected

A profile with no proxy has no exit IP to read, so the host's own network position applies to timezone, locale and geolocation. See Network and leak prevention for how alignment, WebRTC constraint and DNS resolution work in detail.

Alignment is not a substitute for a good proxy

Automatic alignment removes an entire class of tell — the timezone, locale and geolocation mismatches that give most proxied browsers away. It cannot make a datacenter ASN look residential, and it cannot rescue a region story you chose badly, such as an android profile on a corporate datacenter range. Use residential or mobile proxies, and give each profile its own proxy so two identities never share an exit IP.

Next steps

Network and leak prevention — alignment, WebRTC, QUIC and DNS.
Fingerprints — what the profile fixes and what the route derives.
Connect — start a profile with its proxy.
Learn why network signals matter in WebRTC leaks and proxy consistency.