LoginToolsPricing
BirdProxies
BirdProxies
Login
Back to Blog
Guides

Dolphin Anty proxies: which settings keep each profile consistent?

BirdProxiesNovember 19, 202610 min read

A BlackHatWorld thread title asks which antidetect browser "holds up" for 10 to 15 profiles. The snippet carries the plan: "Dolphin Anty (free tier, 10 profiles), but open to GoLogin or AdsPower One residential/mobile proxy per profile, never shared." Two details in that sentence deserve a check. One is out of date. The other is the right instinct, with traps.

This post covers the Dolphin side: the profile settings that decide whether the IP, the browser and the account tell the same story, which is a narrower question than which browser to buy or whether to use the bundled proxies (that argument has its own post).

How many profiles does the Dolphin Anty free plan include?

Since October 22, 2026, the Dolphin Anty free plan includes 3 browser profiles, down from 5, with 20 new profile creations per month. Source: Dolphin's pricing page and its free plan update post. The forum's "10 profiles" is older still.

Three details matter for planning:

  • Profiles over the limit are not deleted, but they cannot be opened or launched until you are back within 3.
  • Deleting a profile does not give the creation back. The counter resets on the 1st of each month.
  • The free plan has no API access. Local API, Remote API, Selenium, Puppeteer and Playwright are all marked unavailable on Free, and Dolphin's automation docs say profiles with the automation flag will not start there. Paid plans begin with Starter (20 to 60 profiles).

So 10 to 15 profiles means paying. And every profile needs its own exit.

What does "one proxy per profile, never shared" actually mean?

Every profile gets its own exit IP, and no two profiles that must stay unconnected ever leave through the same address. The poster has this right. The traps are in the setup.

With sticky residential, "one proxy" is really one session. Each profile gets its own session ID in the proxy username, and each session ID maps to its own exit. On our standard residential plan you set the sticky lifetime in the dashboard, from 5 minutes up to 60 minutes. When the window ends, the exit IP can change. That is fine for a profile you open for a short task. It is not one fixed address for months.

With static ISP proxies, one proxy is one IP that is yours for the whole rental. Put each IP in exactly one profile and leave it there.

Dolphin also has a bulk "Choose proxy" action. It can assign proxies manually or randomly, and it can distribute them sequentially or "Every N profiles", which Dolphin's own example describes as "one proxy for every 3 profiles." Fine for throwaway profiles. Wrong for accounts that must stay apart. If you bulk-assign, keep one proxy per profile and check the result in the list before you launch anything.

WebRTC in Dolphin Anty: Altered, No UDP, Real or Off?

With a proxy in the profile, Altered is the mode that makes WebRTC report the proxy IP instead of your own, and No UDP is a separate option that blocks UDP traffic in WebRTC altogether. Here is how Dolphin's own August 2026 update post describes the four modes:

  • Off: WebRTC is fully disabled and the peer connection is not even initialized.
  • Real: the profile behaves like stock Google Chrome.
  • Altered: the public IP always matches the proxy IP, and local addresses no longer leak.
  • Manual: you set a custom public IP that shows consistently without local IP leaks.

The No UDP mode (another Dolphin post calls it "Disable UDP") blocks UDP traffic in WebRTC at the profile level. You can set it in profile settings and during bulk imports. Dolphin's older fingerprint guide calls Off "not recommended."

Now the BHW question. In a thread titled "Sorry, this post was removed by Reddit's filters", a poster asked: "I'm using the Dolphin Anty browser. WebRTC is currently set to 'Altered', should I switch it to 'Disable UDP' instead?" We only have the title and that snippet, not the replies. Our take: Altered already does the job WebRTC settings exist for. It keeps your real address out of WebRTC and shows the proxy IP. Open a WebRTC leak test inside the profile. If it shows the proxy's address and no local one, WebRTC is not your leak. Then switching modes is unlikely to change what a content filter decides.

Avoid Real behind a proxy. The fingerprint guide describes it as showing your device's real IP through WebRTC. Exactly the mismatch a profile should prevent.

Should timezone, language and geolocation follow the proxy?

Yes, and in Dolphin that is what the Auto setting does. Dolphin's fingerprint guide says Auto picks the time zone "based on your proxy's country". It says Auto language adjusts "to match your proxy" and Auto geolocation picks coordinates from the proxy. Manual coordinates are allowed "as long as they don't conflict with the IP."

Three things break that consistency in practice:

  1. Changing the proxy country on a live account. Auto follows the new proxy, so the account gets a new country, time zone and language overnight. That reads as a different person.
  2. Mixing manual and Auto. A profile with a manual New York time zone and an Auto language on a German proxy contradicts itself.
  3. Rotating where you meant sticky. A rotating residential proxy gives a new exit per connection. Country targeting keeps the country, but the address moves under the account all session long.

Before a profile touches a real account, open it once, look at what an IP lookup site reports for country, time zone and language, and compare that with what the profile claims about itself. Then check the address on our IP fraud score tool. Clean and matching is the baseline. Not a guarantee.

Which proxy type fits which Dolphin profile?

Match the proxy to how long the account lives. Static ISP suits accounts that live for months, sticky residential suits short sessions, and mobile suits platforms built around phones. Another BHW snippet says it in one line: "Dolphin anti is the best for me coupled with mobile proxies. Static residential or ISP proxies are usually a better fit for long-term accounts."

  • Static ISP: one fixed IP held for the whole rental, unmetered traffic. Best for client accounts, brand pages and stores that log in every day for months from the same place. Swapping ISP IPs needs a paid IP Refresh Pass, once per billing period, and it swaps the whole plan. Pick your locations with that in mind.
  • Sticky residential: a household IP held for 5 to 60 minutes, with country and city targeting. Good for research profiles, one-off tasks and anything that does not need the same address tomorrow. The bandwidth does not expire.
  • Mobile: rotating or sticky (5 to 60 minutes), with a 4G/5G pool in DE, GB, US and JP. It makes sense where the platform mostly sees phone traffic. Neither mode holds one mobile IP for days. So mobile is not a substitute for a fixed address on an account you log into daily.

Field-by-field setup is on the Dolphin Anty page.

Automating Dolphin profiles with the Local API and Playwright

You start the profile through Dolphin's Local API, then attach Playwright to the browser it opened. The proxy stays in the profile, and Playwright never sets one. A BHW poster scaling "Dolphin Anty + residential proxies, mainly for account-based workflows and controlled scraping" asked for best practices. Here is what Dolphin's API docs specify.

The Local API listens on localhost:3001 by default. If that port is busy, Dolphin assigns another, shown in the app's Health window. Requests must come from the same machine, the app must be running, and the documented limit is 1,500 requests per minute. You can authorize by POSTing your API token to /v1.0/auth/login-with-token.

import { chromium } from 'playwright'   // ESM, top-level await

const res = await fetch(
  `http://localhost:3001/v1.0/browser_profiles/${PROFILE_ID}/start?automation=1`
)
const { automation } = await res.json()

const browser = await chromium.connectOverCDP(
  `ws://127.0.0.1:${automation.port}${automation.wsEndpoint}`
)
const context = browser.contexts()[0]   // the profile itself
const page = await context.newPage()

Stop the profile with a GET to /v1.0/browser_profiles/PROFILE_ID/stop. Add &headless=1 to the start URL for headless.

Four rules keep one exit per profile:

  • Use browser.contexts()[0]. That is the profile. A new context starts without the profile's cookies and storage, so the account looks logged out.
  • Read the port from every start response. It varies per session. Dolphin's own guide warns it can change between launches.
  • One worker, one profile, one proxy. Running several workers through one sticky session gives them all the same exit. That is the sharing you were trying to avoid.
  • Set the sticky lifetime longer than the job. If a run takes 40 minutes on a 10 minute session, the exit can change mid-run.

Running plain Playwright outside Dolphin too? The DNS and webdriver leaks are in our Playwright leaks post.

What a proxy does not fix in Dolphin Anty

A proxy sets the IP address your traffic leaves from, and nothing else. Everything below sits outside that.

PayPal pushing signup to the app. One poster wrote: "yes i was using dolphin anty while creating the account using a residential proxy, not exactly sure if it was the anti detect browser thats causing the issue or ..." We cannot see PayPal's risk logic. Nobody posting a confident answer can either. A residential IP is one input among many. A different proxy does not change what the platform decides about the browser, the device or the signup itself.

A platform detecting the browser. A thread titled "The Top 3 Anti Detects Are Busted, as of yesterday, Google detects them instantly" is about the browser layer. If a site recognizes the browser build, a cleaner IP will not hide it. That is between you and the browser vendor.

The antivirus warning. Someone asked: "When i use Dolphin Anti browser i get warnings from Bitdefender: Phishing attempt detected 2 hours ago." We cannot vouch for third-party software. Download Dolphin Anty only from its official site, dolphin-anty.com. Send the warning to Dolphin's support and your antivirus vendor. They can see what triggered it.

We also skip streaming farms on free trials and ad billing workarounds. Those show up next to Dolphin too, and we won't help with them.

FAQ

Is the Dolphin Anty free plan still 10 profiles?

No. Dolphin's pricing page lists 3 browser profiles and 20 creations per month on Free, a change from 5 that took effect on October 22, 2026. Free also has no Local API access.

Should I use Altered or Disable UDP for WebRTC in Dolphin Anty?

With a proxy, Altered makes WebRTC show the proxy IP and hides local addresses. No UDP (also called Disable UDP) blocks UDP in WebRTC entirely. If a leak test in the profile already shows only the proxy IP, WebRTC is not leaking.

Can I use one proxy for several Dolphin Anty profiles?

You can, and Dolphin's "Every N profiles" bulk option does exactly that. Skip it for accounts that must stay unconnected. Profiles on one IP share the IP signal.

What proxy is best for Dolphin Anty long-term accounts?

A static ISP proxy, one IP per profile, held for the whole rental. Sticky residential changes after its 5 to 60 minute window, and mobile does not hold one IP for days.

Why does my Dolphin Anty Local API say the profile won't start?

Check three things. Automation does not run on the Free plan. The port may not be 3001, so look in the Health window. And the request has to come from the machine running Dolphin.

Does Dolphin Anty set timezone from the proxy automatically?

Yes, if timezone is on Auto. Dolphin picks it from the proxy's country, and Auto language and geolocation follow the proxy too.

Get started with BirdProxies

Put this into practice with fast, reliable proxies built for social media, scraping, and automation.

Residential ProxiesReal home IPs across 195+ countries for maximum trust.ISP ProxiesDatacenter speed with residential legitimacy.

On this page

BirdProxies
BirdProxies

Fast, secure, reliable proxies. ISP, Residential, and Mobile, ready when you are.

Products

  • ISP Proxies
  • Residential Proxies
  • Sneaker Proxies
  • Ticket Proxies
  • Crypto Proxies
  • Social Media Proxies
  • Betting Proxies

Company

  • Pricing
  • Partners
  • Imprint
  • Terms

Resources

  • Blog
  • Docs
  • Glossary
  • Integration Guides
  • Compare Providers
  • FAQ
  • Changelog
  • Brand Assets

Connect

  • Dashboard
  • Sign Up
  • Contact

© 2026 BirdProxies. All rights reserved.

Cancel contracts hereWithdraw from contract here
PrivacyCookiesRefunds