System Requirements#
System Requirements are a list of conditions to consider before installing and using Afina. The requirements depend on the number of profiles running simultaneously, script complexity, cache size, proxy type, and automation scenarios.
Location: system requirements are checked before installing Afina and before scaling work with a large number of profiles.
Available Actions:
- check OS compatibility
- assess computer resources for profile execution
- prepare sufficient disk space
- check network connection and UDP support if needed for work scenarios
- install a browser version for account launch
- verify correct placement of Afina data folder
Minimum and Recommended Requirements#
The table below summarizes the baseline configuration needed to start Afina and the configuration recommended for stable multi-profile work.
| Parameter | Minimum | Recommended |
|---|---|---|
| Operating System | Windows 10 64-bit (version 1803 or later) or Windows 11 | Windows 11 |
| Architecture | x64 (the MSI installer is 64-bit only) | x64 |
| WebView2 Runtime | required (Microsoft Edge WebView2 Runtime is not bundled with the installer) | pre-installed |
| RAM | 4 GB | 8-16 GB or more |
| Processor | 64-bit, 2 cores | 64-bit, 4 cores or more |
| Disk Space | ~2-3 GB free | 10 GB or more on an SSD |
| Network | stable internet access | stable internet access |
32-bit operating systems are not supported. Afina runs only on 64-bit platforms (x64 or arm64), and the Windows MSI installer is provided only as a 64-bit package for x64.
Operating System#
Operating System determines whether Afina can be installed and launched on the device. Before installation, choose an installer that matches the platform and computer architecture.
| Platform | Support | Considerations |
|---|---|---|
| Windows 10 (64-bit, version 1803 or later) | supported | keep system updates current; Microsoft Edge WebView2 Runtime is required |
| Windows 11 | supported (recommended) | optimal platform for stable operation; WebView2 Runtime is pre-installed |
| macOS Intel | supported | download the Intel build |
| macOS Apple Silicon | supported | download the Apple Silicon build |
Afina runs only on 64-bit systems (x64 or arm64). 32-bit operating systems are not supported, and the Windows MSI installer is provided only as a 64-bit package for x64.
For macOS, separate builds are used depending on the device architecture: Intel or Apple Silicon.
The application also requires the Microsoft Edge WebView2 Runtime to start. The current build uses webviewInstallMode: skip, so WebView2 Runtime is not added to the Afina installer. It is pre-installed on Windows 11 and on most current Windows 10 builds. On a clean Windows 10 system it may be missing, in which case the application will not launch until you install the Evergreen WebView2 Runtime manually.
Before installation, ensure that the downloaded Afina version matches your operating system and device architecture.
On Windows 10, if the Microsoft Edge WebView2 Runtime is not present, Afina will not start. Because Runtime is not bundled with the installer, install Evergreen WebView2 Runtime manually before the first launch.
Processor and RAM#
Processor and RAM determine how many profiles can be launched simultaneously and how stably scripts will perform. Afina does not have a universal fixed limit on the number of active profiles: the actual limit depends on computer resources and the workload of your scenarios.
| Resource | Minimum | Recommended |
|---|---|---|
| RAM | 4 GB | 8-16 GB or more |
| Processor | 64-bit, 2 cores | 64-bit, 4 cores or more |
| Work Scenario | Practical Guideline |
|---|---|
| Basic work with a few profiles | 8 GB RAM as a comfortable guideline |
| More stable multi-profile work | 16 GB RAM or more |
| Mass automation and parallel profile launch | modern multi-core processor, increased RAM |
| Heavy sites, many tabs, or active scripts | reduce the number of parallel profiles or increase device resources |
Each running profile is a separate Chromium process and consumes roughly 300-500 MB of RAM. Because of this, memory and processor load scale with the number of browsers open at the same time, so plan resources according to how many profiles you intend to run in parallel.
Workload factors include:
- number of profiles running simultaneously
- complexity of sites opened in profiles
- number of tabs in each profile
- activity of scripts and automation modules
- amount of data processed during operation
If the interface slows down during operation or profiles launch unstably, reduce the number of concurrently active profiles or increase the resources of the working device.
Disk Space and Data Folder#
Disk space is needed to store the program, browser profiles, cache, logs, backups, extensions, and browser versions. The space occupied depends on the number of profiles and work activity.
| Resource | Minimum | Recommended |
|---|---|---|
| Free disk space | ~2-3 GB | 10 GB or more |
| Drive type | any drive | SSD |
| Stored Data | Considerations |
|---|---|
| Afina application files | take up space after program installation |
| Browser profiles | volume increases with the number of accounts |
| Profile cache | limited by default but can increase significantly |
| Work logs | accumulate during active use |
| Backups | depend on the number of profiles and backup frequency |
| Extensions | add additional disk load |
| Browser versions | each installed Chromium version occupies separate space |
Considerations before scaling:
- for a large number of accounts, allocate sufficient free space in advance
- if the cache limit is disabled, profile size may increase significantly
- for active work with multiple profiles, an SSD is strongly recommended
- store the data folder separately from the Afina installation directory
An SSD is strongly recommended. On slow drives (below 50 MB/s) the speed of profile archiving and backup degrades noticeably, which slows down everyday work with a large number of profiles.
Do not store the data folder in the Afina installation directory. Incorrect data folder placement may result in loss of profiles, cache, or other work files during updates.
A fast SSD is strongly recommended. On a slow disk (under 50 MB/s), profile archiving and backup operations become significantly slower.
Network Connection#
Network connection is required for authorization, license verification, session work, synchronization, browser version downloads, and proxy interaction.
| Requirement | Purpose |
|---|---|
| Stable internet access | authorization, session work, license verification |
| Access to Afina servers | login, subscription check, synchronization, and service functions operation |
| Properly configured proxies | launching profiles with the required network environment |
| UDP support | WebRTC, camera, screen sharing, and related scenarios |
| TCP support | basic operation of most network requests |
If the proxy only allows TCP, functions related to WebRTC, camera, or screen sharing may work incorrectly or be unavailable.
For scenarios involving WebRTC, camera, or screen sharing, use a proxy and network environment with UDP support.
Browser Version#
Browser version is the Chromium core used to launch accounts in Afina. Without the installed browser version, profiles cannot launch correctly.
| Action | Result |
|---|---|
| Open the “Browser Version” section | displays a list of available browser versions |
| Select the required Chromium version | determines the version for installation |
| Start the installation | Afina downloads the browser version |
| Wait for installation status | the version becomes available for account launch |
| Launch an account | the profile opens through the installed Chromium core |
The browser version should be installed after the first login to Afina or after switching to a new Chromium version if needed for profile operation.
Before launching accounts, ensure that the required browser version is installed in the “Browser Version” section.
Additional Recommendations#
Additional recommendations help avoid common issues during installation, updates, and daily work with Afina.
| Recommendation | When Useful |
|---|---|
| Run Afina as an administrator on Windows | if there are issues with file access, extensions, or synchronization |
| Use an SSD | for faster profile launch, cache operation, and better response time |
| Regularly check free disk space | when working with a large number of profiles |
| Store the data folder separately from the installation directory | to reduce the risk of data loss during updates |
| Install the browser version before launching accounts | profiles cannot launch without the Chromium core |
| Check UDP support in the proxy | if using WebRTC features, camera, or screen sharing |
For stable operation with a large number of profiles, it is recommended to use a modern multi-core processor, 16 GB RAM or more, an SSD drive, and sufficient free space for profiles, cache, and backups.
Work Scenario#
Step 1: Check the operating system
Ensure that the device runs on Windows 10 (64-bit, version 1803 or later), Windows 11, or macOS. Only 64-bit systems (x64 or arm64) are supported. On Windows, the Microsoft Edge WebView2 Runtime must be installed. For macOS, select the build according to the device architecture: Intel or Apple Silicon.
Step 2: Assess computer resources
Check the amount of RAM and processor capabilities. The minimum is 4 GB RAM with a 64-bit dual-core CPU; for stable multi-profile work, aim for 8-16 GB RAM or more. Each running profile is a separate Chromium process that uses about 300-500 MB of RAM.
Step 3: Prepare the disk
Ensure there is sufficient space on the disk for profiles, cache, logs, backups, and browser versions. Place the data folder separately from the Afina installation directory.
Step 4: Check the network
Ensure Afina has stable internet access and access to Afina servers. If WebRTC, camera, or screen sharing are needed, use a proxy and network with UDP support.
Step 5: Install the browser version
After installing Afina, open the “Browser Version” section, select the required Chromium version, and install it. Accounts cannot launch without the browser version.