macOS
8.4.3
macOS (Apple Silicon) ↓macOS (Intel) ↓AdsPower Fingerprint Browser Download
AdsPower desktop clients run on supported desktop systems and chip architectures. After installation, each browser Profile can store its own proxy, cookies, local storage, fingerprint settings, tags, and automation configuration.
AdsPower supports Windows 10 and later, macOS 11 Big Sur and later, and Ubuntu Desktop 22.04 and later. Available client builds depend on the operating system and device architecture.
Get Windows CLI
irm https://adspowerapp.org/install.ps1 | iex
Get macOS CLI
curl -fsSL https://adspowerapp.org/install.sh | bash
Get Linux CLI
curl -fsSL https://adspowerapp.org/install.sh | bash
The CLI and desktop client run independently and do not share local cache or browser kernels. If a command fails, check shell permissions, network access, and the current system environment before using the desktop client instead.
AdsPower 8.4.3 Client Changes
Browser engine: Chrome 147 support was added, while Chrome 145 and 146 received changes to mobile parameters, virtual camera behavior, and WebRTC-related settings.
Accounts and proxies: Team deletion was added, account closure and email change flows were adjusted, proxies can be purchased while creating or editing a Profile, and batch renewal supports up to 300 proxies.
Local API: API calls can update the JavaScript package and query the list of browser kernels currently available to the client.
View more
Browser engine upgrades
- Chrome 147 engine: Chrome 147 can be selected when creating or editing a Profile, alongside other available browser engine versions.
- Chrome 145 and 146: Mobile parameters, virtual camera behavior, and WebRTC-related settings were adjusted for these engine versions.
Account and proxy changes
- Team management: Teams that are no longer needed can be removed.
- Account management: Account closure and email update flows were adjusted.
- Profile proxy settings: Proxies can be purchased and bound while creating or editing a Profile.
- Proxy order details: Purchase and renewal dialogs show proxy type, quantity, duration, and price information.
- Batch proxy renewal: Up to 300 proxies can be renewed in one batch.
- Proxy status: Expiring and invalid proxy states are shown in the proxy list.
Local API changes
- Local API updates:
- Update the JavaScript package through API calls.
- Query the list of browser kernels currently available to the client.
Desktop client and system architecture
Different operating systems and chip architectures use different client builds. System information can be checked before installation to identify the matching build.
Create a browser Profile
After signing in, a Profile can be created with its own proxy, cookies, fingerprint settings, tags, groups, and account notes.
Manage multiple Profiles
Profiles can be grouped by account, project, region, or member and used with Window Synchronizer, RPA, Local API, and member permissions.
AdsPower download and installation questions
Which AdsPower client build should I use?
The available client build depends on the operating system and device architecture. Windows builds are separated by system architecture, while macOS builds distinguish between Apple Silicon and Intel devices.
Which operating systems does AdsPower support?
AdsPower supports Windows, macOS, and Linux desktop environments. The supported system version and device architecture determine which client build can run on the device.
What can be configured after installation?
After installation and sign-in, users can create browser Profiles and configure proxies, cookies, fingerprint settings, groups, tags, account notes, and automation-related settings.
How do I choose between Windows and macOS versions?
Windows builds are separated by system architecture, while macOS builds are separated by Apple Silicon and Intel processors. The current device architecture can be checked in system information.
Why do I need the AdsPower desktop client?
Browser Profile creation and launch, proxy binding, cookies, local storage, fingerprint settings, and some local automation functions run through the desktop client.
What is the difference between CLI and desktop installation?
CLI installation runs through shell commands, while the desktop client uses a graphical installer and interface. The CLI and desktop client run independently and do not share local cache or browser kernels.