Profiles & Persistent Context

Chrome stores all profile data in the userDataDir folder, including cookies, cache, localStorage, sessionStorage, indexedDB, and other files. One of the main benefits of persistent profiles is automated authentication. By maintaining profile data between sessions, you can avoid repeated login processes for each new browser session.

Another significant advantage of maintaining persistent browser cache is reduced proxy bandwidth usage. When cache is enabled, frequently accessed resources like images, scripts, and stylesheets are stored locally, eliminating the need to download them repeatedly through your proxy. This can substantially decrease your proxy traffic and improve page load times.

Rebrowser manages profile persistence transparently by default. Simply create a new profile in Dashboard / Profiles and use its ID in the API endpoint to maintain data between runs. You can configure browser settings at both profile and group levels, including the option to disable persistence for clean browser starts when needed.

Platform compatibility note: Desktop browsers support full data persistence (cache, cookies, and all other userDataDir content), while mobile browsers have limited persistence (cookies, localStorage, and sessionStorage) due to Android constraints.

You can always contact our support team if you would like to discuss more sophisticated options regarding persistent profiles.