Browser Profiles

Browser Profiles are isolated browser environments with their own cookies, cache, fingerprints, and stealth settings. Think of each profile as a completely separate browser installation — what happens in one profile doesn’t affect any other profile.

If you’re running multiple automations for different clients, different websites, or different purposes, browser profiles let you keep each one completely separate. Each profile can have its own proxy configuration, CAPTCHA solving settings, humanoid behavior level, and browser extensions.

Why Use Browser Profiles?

Without browser profiles, all your automations share the same browser state:

Without Profiles	With Profiles
All automations share the same cookies	Each profile has its own isolated cookies
All automations use the same proxy settings	Each profile can use different proxies
All automations use the same CAPTCHA settings	Each profile can use different CAPTCHA solvers
All automations share the same browser fingerprint	Each profile has a unique fingerprint
Logging into one site affects all automations	Each profile maintains separate login sessions
One blocked IP blocks all automations	Each profile can use a different IP

Common Use Cases

Use Case	Why Profiles Help
Multiple client projects	Each client gets a separate profile with their own settings
Different websites with different protection	Each site gets its own sensitivity and proxy configuration
Testing different configurations	Test different stealth settings without affecting your main setup
Maintaining separate login sessions	Log into different accounts on the same site without conflicts
A/B testing automation approaches	Run the same automation with different settings side by side
Client isolation	Ensure one client’s data never leaks into another’s automation

Creating a Browser Profile

Steps

1. Go to Browser Profiles in the sidebar.
2. Click New Profile in the top-right corner.
3. The Create Profile modal opens.
4. Fill in the profile settings (see below).
5. Click Save.

The new profile appears in the profile list immediately.

Profile Settings

Each browser profile has the following settings, organized into sections:

General Settings

Setting	Type	Required	Default	Description
Profile Name	Text	✅ Yes	—	A descriptive name for this profile. Shown in the profile list and when assigning to projects.

Proxy Settings

Setting	Type	Required	Default	Description
Enable Proxies	Toggle	No	Off	Master toggle for proxy routing in this profile.
Proxy List	Textarea	If enabled	—	Newline-separated list of proxy URLs. Format: http://user:pass@host:port
Proxy Level	Dropdown	If enabled	Context	How proxies are applied: Context Level (per-session) or Browser Level (shared).
Align Browser Fingerprint	Toggle	No	Off	Matches timezone and locale to the proxy’s geographic location.

CAPTCHA Settings

Setting	Type	Required	Default	Description
Enable CAPTCHA Solving	Toggle	No	Off	Master toggle for automatic CAPTCHA solving.
Provider	Dropdown	If enabled	2Captcha	The CAPTCHA solving service. Currently only 2Captcha is supported.
API Key	Text	If enabled	—	Your API key for the CAPTCHA solving service.

Human-like Interaction Settings

Setting	Type	Required	Default	Description
Enable Human-like Simulation	Toggle	No	On	Master toggle for humanoid behavior in this profile.
Sensitivity	Dropdown	If enabled	Medium	Randomization level: Low, Medium, or High.

Extensions Payload

Setting	Type	Required	Default	Description
Extension URLs	Textarea	No	—	Newline-separated list of Chrome Web Store extension URLs to inject.

See Extensions Payload for details on how extensions work.

Profile Settings Table (Complete Reference)

Here’s every setting available in a browser profile:

Section	Setting	Type	Default	Description
General	Profile Name	Text	—	Display name for the profile
Proxies	Enable Proxies	Toggle	Off	Enable proxy routing
Proxies	Proxy List	Textarea	—	Proxy URLs, one per line
Proxies	Proxy Level	Dropdown	Context	Context or Browser level
Proxies	Align Fingerprint	Toggle	Off	Match timezone/locale to proxy
CAPTCHA	Enable CAPTCHA Solving	Toggle	Off	Enable auto-solving
CAPTCHA	Provider	Dropdown	2Captcha	Solving service
CAPTCHA	API Key	Text	—	Service API key
Humanoid	Enable Simulation	Toggle	On	Enable humanoid behavior
Humanoid	Sensitivity	Dropdown	Medium	Low, Medium, or High
Extensions	Extension URLs	Textarea	—	Chrome Web Store URLs

Assigning a Profile to a Project

Once you’ve created a browser profile, you need to assign it to a project for it to take effect.

Steps

1. Go to Automation Projects in the sidebar.
2. Select the project you want to configure.
3. Click Profile in the ribbon toolbar.
4. The Browser Profile Selection modal opens.
5. Choose a profile from the dropdown (or select “Default” to use global settings).
6. Click Save & Continue.

What Happens When You Assign a Profile

When a profile is assigned to a project:

1. The project’s browserProfileId is set to the profile’s ID.
2. When the project runs, it uses the profile’s settings instead of global defaults.
3. The browser launches with the profile’s isolated environment.
4. Cookies, cache, and extensions are specific to this profile.
5. Proxy, CAPTCHA, and humanoid settings come from the profile.

What Happens When No Profile Is Assigned

When no profile is assigned (the project uses “Default”):

1. The project uses global default settings from Preferences → Stealth & Proxies.
2. The browser launches with the default profile environment.
3. Global proxy, CAPTCHA, and humanoid settings are used.

Default Profile

The Default profile is the built-in profile that uses your global settings. It cannot be deleted or edited directly.

Aspect	Default Profile	Custom Profiles
Settings source	Preferences → Stealth & Proxies	Profile-specific settings
Can be deleted?	❌ No	✅ Yes
Can be edited?	❌ No (edit global settings instead)	✅ Yes
Data location	~/.rtila-x/profiles/default/	~/.rtila-x/profiles/<profile-id>/
Applies to	Projects with no profile assigned	Projects with this profile assigned

To change the default profile’s settings, edit your global settings in Preferences → Stealth & Proxies.

Profile Data Location

Each browser profile stores its data in a separate directory on your computer:

~/.rtila-x/profiles/
├── default/           ← Default profile data
│   ├── cookies/       ← Browser cookies
│   ├── cache/         ← Browser cache
│   ├── extensions/    ← Injected extensions
│   └── config/        ← Profile configuration
├── <profile-id-1>/    ← Custom profile 1
│   ├── cookies/
│   ├── cache/
│   ├── extensions/
│   └── config/
├── <profile-id-2>/    ← Custom profile 2
│   └── ...
└── proxy_ext_<hash>/  ← Auto-generated proxy auth extensions
    └── ...

What’s Stored in Each Profile

Directory	Contents
cookies/	Browser cookies for this profile. Includes login sessions.
cache/	Browser cache (images, scripts, CSS). Speeds up page loads.
extensions/	Chrome extensions injected into this profile.
config/	Profile configuration and settings.

Profile Isolation

Each profile’s data is completely isolated:

Data Type	Isolation
Cookies	Each profile has its own cookie jar. Logging into a site in one profile doesn’t affect other profiles.
Cache	Each profile has its own cache. No shared cached resources.
Extensions	Each profile can have different extensions.
Local Storage	Each profile has its own localStorage.
IndexedDB	Each profile has its own IndexedDB.
Service Workers	Each profile has its own service workers.

This isolation ensures that:

• Logging into Site A in Profile 1 doesn’t log you into Site A in Profile 2.
• Clearing cookies in one profile doesn’t affect other profiles.
• Different clients’ data never mixes.
• Different proxy configurations don’t conflict.

Clearing Profile Data

If you need to reset a profile’s data (cookies, cache, etc.):

Method 1: Delete and Recreate the Profile

1. Go to Browser Profiles.
2. Click the trash icon next to the profile.
3. Confirm the deletion.
4. Create a new profile with the same settings.

Warning: This permanently deletes all cookies, cache, and login sessions for that profile. Any websites you were logged into will require re-login.

Method 2: Clear the Default Profile

1. Go to Browser Profiles.
2. Click Clear Default button.
3. The default profile’s cache and cookies are cleared.
4. The default profile itself is not deleted.

Method 3: Manual File Deletion

For advanced users who want to clear specific data:

1. Close RTILA X completely.
2. Navigate to ~/.rtila-x/profiles/<profile-id>/.
3. Delete the cookies/ directory to clear cookies.
4. Delete the cache/ directory to clear cache.
5. Restart RTILA X.

Warning: Manual file deletion should only be done while RTILA X is completely closed. Deleting files while the application is running can cause data corruption.

Editing a Profile

Steps

1. Go to Browser Profiles.
2. Click the edit icon (pencil) next to the profile.
3. The Edit Profile modal opens with the current settings.
4. Modify the settings.
5. Click Save.

Note: You cannot edit a profile while a project using that profile is currently running. Stop the project first.

Deleting a Profile

Steps

1. Go to Browser Profiles.
2. Click the trash icon next to the profile.
3. A confirmation dialog appears.
4. Click Delete to confirm.

What Happens When You Delete a Profile

1. The profile record is removed from the database.
2. The profile’s data directory is deleted (cookies, cache, extensions).
3. Any projects assigned to this profile will fall back to the default profile.
4. Login sessions stored in the profile are lost.

Warning: Deleting a profile is permanent. All cookies, login sessions, and cached data for that profile are lost. Make sure you don’t need any login sessions before deleting.

Launching a Profile’s Browser

You can launch a profile’s browser independently for testing or manual browsing:

Steps

1. Go to Browser Profiles.
2. Click the play icon next to the profile.
3. A new browser window opens with the profile’s settings applied.
4. You can browse manually, test selectors, or debug issues.
5. Click the stop icon to close the browser.

Use Cases for Manual Browser Launch

Use Case	Description
Testing selectors	Open the target site and test selectors manually
Debugging issues	See what the automation sees
Testing proxy configuration	Verify the proxy is working correctly
Manual CAPTCHA solving	Solve a CAPTCHA manually to test the flow
Inspecting page structure	Use browser dev tools to find selectors

Profile Settings vs. Global Settings

Here’s how profile settings interact with global settings:

Setting	Global Location	Profile Override
Proxies	Preferences → Stealth → Proxies	Profile → Proxy Settings
CAPTCHA Solving	Preferences → Stealth → CAPTCHA	Profile → CAPTCHA Settings
Humanoid Behavior	Preferences → Stealth → Humanoid	Profile → Humanoid Settings
Extensions	N/A (global only)	Profile → Extensions
Fingerprint Alignment	Preferences → Stealth → Fingerprint	Profile → Align Fingerprint

Priority Order

When a project runs:

1. If the project has a Browser Profile assigned, the profile’s settings are used.
2. If the project has no profile assigned, global settings from Preferences are used.
3. Settings are not merged. It’s one or the other, not a combination.

Tips and Best Practices

Tip	Description
Name profiles descriptively	Use names like “Client A - Amazon” or “E-commerce - High Protection”
Create one profile per client	Keeps client data completely separate
Use different proxies per profile	Prevents IP-based blocking across different projects
Test profiles before production	Launch the browser manually and verify settings work
Don’t delete profiles with active sessions	You’ll lose login sessions
Use High sensitivity for protected sites	Assign a High-sensitivity profile to heavily protected sites
Use Low sensitivity for speed	Assign a Low-sensitivity profile to simple, unprotected sites
Clear cache periodically	Large caches can slow down browser startup
Back up profile data	Copy the profile directory if you have important login sessions
Use extensions for ad blocking	Inject an ad blocker to speed up page loads

Troubleshooting

Problem	Solution
Profile not applying to project	Make sure the profile is assigned to the project via the Profile button in the ribbon
Cookies not persisting	The profile may have been deleted and recreated. Check that the profile ID hasn’t changed.
Proxy not working	Test the proxy using the Test Proxies button in the profile settings
CAPTCHA not being solved	Verify the API key is correct and has sufficient balance
Extensions not loading	Verify the Chrome Web Store URL is correct and the extension is available
Browser won’t launch	Close any existing browser windows using this profile
Profile data taking too much space	Clear the cache directory manually
Login sessions lost	The profile may have been deleted. Recreate it and log in again.