How do you create and use a passkey?-Help Center

1. Scope of Application

Note: Passkey is only supported in Patch v2.9.0.1 and later, and in Chrome 156 and later. This feature is not enabled in Firefox or unsupported versions of Chrome.

⚠️ You will need to upgrade your JavaScript version to use this feature
Manages only credentials created via the ‘Current AdsPower environment’; Passkeys saved using other methods are not automatically migrated.
Environments are stored independently; each environment can store Passkeys for multiple websites and multiple accounts. Sharing and copying environments do not support Passkeys.
Even if data synchronisation is not enabled, you can still create, save and use files on this device.
Incognito mode uses the same Passkey data as normal mode. Closing an incognito window does not delete the Passkey created via the ‘Current AdsPower Environment’; synchronisation, backups and cleaning are still carried out in accordance with the existing rules for that environment.

2. Creating and using a passkey

When adding or creating a Passkey within the website, you can select ‘Current AdsPower environment’ on the authentication method selection screen.

Once selected, a confirmation pop-up will appear, explaining that a Passkey will be created for the current website and saved to the current environment; account details are subject to the information provided by the website. Upon confirmation, the Passkey will be saved to the current environment; users do not need to select a file path. Once saved successfully, the creation result will be returned to the website.

The login box displays the Passkey login option

Confirmation pop-up

3. Enable data synchronisation

The “Passkey” synchronisation option is unchecked by default; users can enable it as required.

Set location	Rules on Entry into Force
Global Settings → Data Synchronisation	By default, neither ‘New teams’ nor ‘Existing teams’ is ticked. Once ticked, synchronisation will follow the global environment settings and occur at the existing synchronisation times; files will not be uploaded immediately upon saving the selection.
New/Edit Environment → Data Synchronisation	This option has been added to the interfaces for creating and editing items individually, quickly and in bulk. When following global settings, changes take effect according to team configurations; when using custom settings, the option is handled according to the ticked status saved in the environment. New items are unticked by default, and existing custom environments are not automatically enabled.
Preferences	Add this item, whilst retaining the existing saving and pre-filling rules

4. View the cache and restore the backup

The maximum file size for Passkey uploads is 60 MB. If this limit is exceeded, the existing over-limit notification and upload restrictions will apply.

5. Clear Passkey

Entrance

Processing Rules

Environment Management → Clear cache

‘Type’ has been expanded to include ‘Passkey’, with the option to select ‘This PC’ or ‘Cloud’; existing single and batch operations remain unchanged.

Global Settings

／New Profile → Profiles settings → Clear cache data

‘Delete specified types’ now includes Passkey; ‘Delete all’ includes Passkey, and this change also applies to existing environments where ‘Delete all’ has already been enabled.

If you select ‘Delete Passkey before launch’ or ‘Delete All’, the local Passkey will be deleted before launch; the cloud-based Passkey will not be downloaded during this launch, and cloud data will not be deleted directly; when the app is closed, uploads will still be handled in accordance with the existing synchronisation settings and permissions.

6. Local API and Automation

The cache-clearing API (`POST /api/v2/browser-profile/delete-cache`) has been updated to include a `Passkey` type, allowing for the deletion of local Passkeys within a specified environment. This addition adheres to existing parameter validation, environment state restrictions, and deletion rules. If this type is not specified, Passkeys will not be deleted; the scope of this feature does not extend to cloud-based data clearing.
The `start`, `stop`, and `stop-all` interfaces will follow existing rules for synchronization, recovery, automatic cleanup, and backup; no new parameters specific to Passkey will be added for start/stop operations. When the existing `delete_cache` parameter is enabled for the `start` interface, Passkey data will be handled according to the established scope and sequence for post-shutdown cleanup.
The `create` interface continues to follow existing configuration initialization and global inheritance rules; the `update` interface does not reset Passkey configurations or credentials when updating other fields. This release does not introduce the ability to configure Passkey synchronization via the API.