Skip to content

Browser Profiles

Browser Profiles are isolated browser environments with their own cookies, fingerprints, and stealth settings.

Use Case Description
Different stealth settings Different proxies, CAPTCHA keys, or sensitivity per project
Multiple accounts Run different accounts without cookie conflicts
Client separation Keep client data separate
Testing Test different configurations without affecting defaults
  1. Go to Browser Profiles in the sidebar.
  2. Click New Profile.
  3. Configure the profile settings.
  4. Click Save.

Browser Profiles page showing profile list and New Profile button

Setting Description
Profile Name Display name for the profile
Enable Proxies Route traffic through proxies
Proxy List One proxy per line
Proxy Level Context Level or Browser Level
Align Browser Fingerprint Match timezone/locale to proxy IP
Enable CAPTCHA Solving Auto-solve CAPTCHAs
CAPTCHA Provider CAPTCHA solving service
CAPTCHA API Key API key for the provider
Enable Human-like Simulation Simulate human behavior
Sensitivity Level of human-like randomness
Extensions Payload Chrome Web Store extension URLs to inject
  1. Go to Automation Projects.
  2. Select the project.
  3. Click Profile in the ribbon.
  4. The Profile Selection modal opens.
  5. Choose a profile (or “Default” for default settings).
  6. Click Save & Continue.

Profile Selection modal showing profile dropdown

If no profile is assigned, the project uses the default settings from Preferences → Stealth & Proxies.

Profile data (cookies, cache, settings) is stored locally in:

~/.rtila-x/profiles/<profile-id>/

To reset a profile’s data:

  1. Go to Browser Profiles.
  2. Click Clear Default to clear the default profile cache.
  3. For specific profiles, delete the profile and recreate it.

You can inject Chrome Web Store extensions into a profile:

  1. Enter extension URLs, one per line:
    https://chromewebstore.google.com/detail/extension-name/abcdefghijklmnop
  2. RTILA automatically downloads, extracts, and injects the extension.

Note: Extensions are injected when the Visual Builder is launched for a project using this profile.