Consistent device memory settings across multiple sessions and profiles are crucial for maintaining a stable and believable online identity. For users who require long-term or repeated interactions—such as managing social media accounts or performing online research—consistent memory settings help build a trustworthy digital persona that withstands scrutiny over time.
In this article we are going to show you how to set the Device Memory settings during the creation of your virtual browser profile through the Local API Clients.
Concept
During the CreateProfileRequest
POST /profiles/new
you can pass the CreateProfileRequest object that has a DeviceMemorySpoofingType property. This can be used to set up the Device Memory. Possible values are:
- Automatic: Use the Device Memory value from the fingerprint for profile consistency.
- Manual:Set a custom Device Memory value to customize the profile further. With the possible options range being: 0.25, 0.5, 1, 2, 4, and 8.
- Off: Use your device's unmasked Device Memory value for a more authentic profile.
We suggest you to either the "Automatic" setting seeing how they provide a more authentic experience. To set the Hardware Concurrency type, use the setDeviceMemory
method in the Local API Clients. Below you can find the examples for Javascript and Python:
Examples
-
const createProfileRequest = BuilderForCreateProfile .forBaseProfile(chromeBaseProfileList[0].id) .setRecommendedDefaults() .setDeviceMemory('manual', 8) # Valid values: 0.25, 0.5, 1, 2, 4, and 8. .build(); const profile = await client.createProfile({ body: createProfileRequest });
-
create_profile_request = BuilderForCreateProfile \ .for_base_profile(base_profiles[0].id) \ .set_recommended_defaults() \ .set_device_memory('manual', 8) \ # Valid values: 0.25, 0.5, 1, 2, 4, and 8. .build() profile = client.create_profile(body=create_profile_request)
For your convenience, this functionality is provided by the Python Builder and JavaScript Builder for Profile Creation in the Local API Clients.