Key Features of DICloak Antidetect Browser

DICloak Antidetect Browser is a Chromium-based multi-accounting tool from DICloak Technology Limited that isolates each account in its own profile with about two dozen editable fingerprint parameters, per-profile proxy assignment over HTTP, HTTPS or SOCKS5, role-based team permissions, RPA automation and a local API. Plans run from $0 to $138 per month, on Windows, macOS and Linux.

An anti-detect browser isolates each account into its own environment: separate cookies, separate local storage, separate fingerprint parameters, separate proxy. Websites read a set of device and browser signals on every visit (screen resolution, font list, time zone, GPU strings, audio processing quirks) and combine them into an identifier. DICloak lets you set those signals per profile instead of inheriting them from one machine.

What DICloak actually controls

The kernel version is a per-profile setting, not a global one. DICloak’s profile creation guide currently recommends Chromium 134 or 142 on the grounds that newer kernels have better site compatibility. This is worth attention: an outdated kernel paired with a current user-agent string is one of the cheapest mismatches for a site to detect.

The fingerprint editor exposes roughly two dozen parameters:

• Operating system simulation: Windows, macOS, Linux, Android, iOS
• User-agent, browser language and interface language
• Time zone and geolocation, both of which can auto-match the proxy IP
• Screen resolution: custom, real or random
• Font list: custom selection or real
• WebRTC with Substitute, Real and Disable modes
• Canvas, ClientRects, AudioContext, WebGL image and SpeechVoices, each set to Noise or Real
• WebGL metadata as Custom or Real, with a randomize button for vendor and renderer strings
• WebGPU, hardware concurrency (CPU cores), device memory, device name
• Do Not Track, battery state, port-scan protection with an allowed-ports list, hardware acceleration

Noise is not free of cost. Randomizing Canvas and WebGL on every parameter produces a fingerprint that is unique but unstable across sessions, and instability is its own signal. In practice the IP-matching options for language, time zone and geolocation do most of the work, because they remove the mismatches a site can check in a single call.

Profile management and bulk operations

Profiles can be created one at a time or imported in batches, then cloned, exported, updated in bulk, and restored from trash if deleted. Cloud sync is available on every plan, including Free. Teams migrating from another tool can import AdsPower profiles directly, carrying over cookies and user-agent data.

Batch operations are not part of the Free plan. Batch import, batch create, batch update, clone, export and restore all start at the $8 Base tier.

The July 2026 update added three things that matter at scale: a batch filter that accepts multiple profile-name keywords at once, the ability to stop a bulk startup mid-run instead of waiting for unwanted profiles to launch, and account assignment inside social media import templates, so several platform accounts from one template can go to the same profile.

Proxy configuration

DICloak offers four proxy modes: No proxy, Custom proxy, Saved proxies, and API extraction. The proxy documentation covers each in detail.

Custom proxies accept HTTP, HTTPS and SOCKS5 over IPv4 or IPv6, plus two vendor-specific dynamic types. A Quick Input field parses a pasted proxy string into the separate parameter boxes, which saves time when you are loading a list. The built-in check button reports connection status, exit IP, country and time zone, with IP2Location and IP-API selectable as the geolocation source. DICloak’s own documentation also points users to an external proxy checker for independent verification, which is a reasonable habit: a proxy that passes the vendor’s own test and fails a third-party one usually has a geolocation database mismatch rather than a connection problem.

Two details matter once you run more than a handful of profiles. Selecting a saved proxy at random draws first from proxies not yet in use, so the same IP is not silently assigned twice. API extraction has a Duplicate Verification toggle that skips IPs already used anywhere in the team, and it can pull a fresh IP either at profile launch or only after the current one expires.

The January 2026 release added proxy group management and changed WebRTC behaviour: under Substitute, the address exposed through WebRTC always matches the currently assigned proxy rather than the local connection.

One thing DICloak does not do is sell IPs. There are no bundled proxies on any tier, including the $138 plan. Every proxy is sourced externally, which is why the help center carries individual setup pages for more than two dozen providers instead of a purchase flow.

The subscription is the smaller half of the bill. Because no IPs are bundled at any tier, a 50-profile setup on the $8 Base plan needs 50 separate addresses, and at proxys.io rates 50 dedicated foreign IPv4 proxies from $1.47 each come to $73.50 per month, which puts the browser at roughly 10% of the $81.50 total. Shared IPv4 from $0.67 and IPv6 from $0.13 bring that down, but a shared address is used by up to three people, which undoes the point of one profile per IP.

Verifying a profile before you scale

Check every new profile twice, once from the app and once from inside the browser. The Checking proxy button reports exit IP, country and time zone and lets you switch the lookup source between IP2Location and IP-API; the two databases disagree on some ranges, and DICloak keeps a separate FAQ entry for exactly that mismatch. After launch, confirm three things from inside the profile: the address exposed through WebRTC matches the proxy, the browser time zone matches the IP country, and reopening the same profile does not change parameters you left on Real. DICloak publishes a free WebRTC leak test and anonymity check for the first two, and running an independent checker as a second opinion costs nothing.

Team collaboration

Member roles run Super Admin, Admin, Manager and Member, with profile-group authorization and per-operation permission isolation. The global settings list includes member IP restriction, member device-name restriction, a client version limit, a concurrent profile cap, a same-IP login device limit, website access restriction for team members, and a switch that blocks packet-capture software from running alongside the client. Every action is written to an operation log.

Cookie encryption enhancement is sold as an add-on at $50 per month per 100 profiles and is available only on the Share+ plan.

The July 2026 update also added a forced logout when profile groups are reassigned, so a member cannot keep working under permissions that were just revoked, along with a filter separating internal from external members in the member list.

Automation: RPA, API and MCP

RPA task quotas differ sharply by plan: 5 tasks on Free, 5 on Base, 500 on Plus, and 5 on Share+. If automation is the reason you are buying, Plus is the only tier that supports it at volume.

The Local API covers profile create, edit, delete, start and stop, and returns the debug port and process ID, which is what makes external control through Puppeteer or Selenium possible. Sample code ships for Python, Java and Node.js. A second-generation Local API adds separate cookie, fingerprint, extension and bookmark, tag and runtime interfaces. There is also an HTTP API, a browser SDK, a Docker runtime image, and an MCP server that exposes profile creation, start and stop to AI agents through a standard interface.

Open API access is limited to the Plus and Share+ plans. Window synchronization, profile sharing and profile transfer are Plus only.

Who uses DICloak

• Affiliate marketing and media buying. Separate client ad accounts into separate environments, each with its own IP and time zone, so campaign work for one client does not share session state with another.
• E-commerce. Marketplace sellers running several storefronts, plus price and listing monitoring across regions where the visible catalogue depends on the exit IP.
• Web scraping. The debug-port return and Docker image make DICloak usable as a controlled browser layer in a collection pipeline rather than just a desktop tool.
• Crypto and Web3. Wallet and exchange sessions kept in separate profiles with matching proxy geography and time zone.
• Social media management. Agencies handling client accounts where several people need access without password sharing.

Most large platforms restrict multi-accounting in their terms of service, and rules differ by platform and by jurisdiction. An anti-detect browser is a technical isolation tool; whether a given workflow is permitted is a question for the platform’s own terms, not for the software.

How DICloak compares to AdsPower, GoLogin and Multilogin

DICloak’s clearest advantage over the older anti-detect browsers is the size of its free tier. AdsPower’s own pricing page gives 2 permanent free profiles plus a 7-day trial, while DICloak gives 5 profiles and 15 launches a day with no expiry, which is enough to test a real workflow rather than a single account. Where DICloak is behind is track record: AdsPower, GoLogin and Multilogin each carry years of public review history, and DICloak’s Trustpilot profile holds 49 reviews. Do not price the alternatives from comparison blogs. Entry prices quoted for the same plans do not agree between sources, most of those pages are affiliate placements, and the only figure worth acting on is the one on the vendor’s own page on the day you buy.

Pricing

DICloak publishes four plans. Current rates from the official pricing page:

Annual billing is discounted 40%, which brings Base to an effective $4.80 per month and Plus to $17.28. Free includes 1 member; Share+ includes unlimited seats. Payment accepts PayPal, Visa, Mastercard, and Bitcoin, USDT, USDC and ETH.

The plan hierarchy has an odd gap. Share+ costs $138 and is positioned for large teams, but it omits window synchronization, profile sharing and profile transfer, and keeps the 5-task RPA quota. Plus, at $28.80, includes all four. A mid-sized team that depends on window sync ends up on the cheaper plan, and a team that needs both unlimited seats and window sync has to ask for a custom package.

System requirements

The client runs on Windows 10 and later with a dual-core CPU, 2 GB of RAM and 2 GB of free disk, on macOS 11 and later, and on 64-bit Linux from Ubuntu 22.04, Debian 11 or Fedora 38 upward, per the download page.

Treat 2 GB of disk as a floor for the installer only. DICloak’s own troubleshooting page recommends at least 10 GB free on whichever drive holds the .DICloakCache folder and lists low disk space as a common cause of profiles failing to open, alongside antivirus software blocking the cache directory.

As of August 2026, DICloak has published a release every month since October 2024 with no gaps in the update log. Two 2026 changes affect setup directly: the January release made WebRTC under Substitute return the assigned proxy address instead of the local one and added proxy group management, and the July release added a multi-keyword profile-name filter, the ability to abort a bulk startup mid-run, and forced logout when a member’s profile groups are reassigned. The recommended Chromium kernels, 134 and 142, date from the 26 March 2026 revision of the profile guide, so re-check that field on older profiles instead of assuming they are still on a supported build.

Where DICloak falls short

Independent verification is thin. The Trustpilot profile carries a 4-star score from 49 reviews as of August 2026, a small sample for a tool sold to teams running hundreds of accounts, and there is no published third-party audit of the fingerprint implementation or the cloud sync layer.

No proxies are bundled at any price, so the real monthly cost is the subscription plus IP spend. Automation is effectively gated behind the $28.80 Plus plan because of the RPA quota structure. And fingerprint masking reduces the signals a site can read; it does not make an account behave like a long-standing one, which is a separate problem that no browser solves.

Start on the Free plan. Five profiles and 15 launches per day is enough to confirm that time zone, WebRTC output and language stay consistent with your proxies across restarts, but not enough to test window synchronization or the API, both of which sit behind Plus.