AdsPower Tutorial: Create Your First Profile, Add a Proxy and Verify It
A beginner's AdsPower walkthrough. Start on the free 2-profile plan, create a profile, attach a static proxy, pass the connection check, then verify IP, WebRTC and DNS before you log in to anything.
Most people who get stuck with AdsPower aren't confused by the software. They're unsure whether the profile they just built is actually doing what they think it is. The proxy field is filled in and the profile opens, but is the browser really exiting through that IP? Does the time zone match? Is WebRTC leaking your office connection?
This tutorial takes you from a fresh account on the free plan to a single, verified profile bound to a static IP. It's written for a seller or social team's first day with the tool. Prices were checked on 2026-10-05, and menu labels follow AdsPower's English help center. The client changes over time, so treat the current interface as the source of truth where it differs.
If you're still deciding between tools, read How to Choose an Anti-Detect Browser and AdsPower vs GoLogin first.
Before you start: account, proxy and a profile plan
You need three things before you click anything.
1. An AdsPower account. You'll create it in the next step.
2. A proxy for each account you plan to run. If the account is long-lived, such as a marketplace storefront, a brand's social page or an ad account, a dedicated static ISP (static residential) IP is the usual choice because the IP doesn't change between sessions. Two examples from our partner list, at listed prices:
- IPFoxy: dedicated static residential at $7.99/month with unlimited data in 25+ countries.
- Proxy-Seller: ISP proxies from $0.98 per IP.
Not sure which type you need? Residential vs ISP vs Mobile vs Datacenter Proxies explains the differences, and Best Static ISP Proxies compares providers.
3. A simple profile plan. It's a spreadsheet, nothing fancy:
| Profile name | Account | Market | Proxy | Owner |
|---|---|---|---|---|
| US-Store-01 | Store A (US) | United States | Static IP #1 | Alex |
| UK-Store-01 | Store B (UK) | United Kingdom | Static IP #2 | Sam |
The rule of thumb is one account, one profile, one fixed IP, in the same country as the account's market. Writing it down before you start prevents the most common mistake: two people logging into the same account from two different profiles.
Check the platform's rules first. Profile isolation keeps legitimately operated accounts from interfering with each other. It doesn't change what a platform allows. Amazon, for example, has specific rules on operating more than one seller account; see Multiple Amazon Seller Accounts.
Sign up and choose a plan
Create an account on the AdsPower website, then download and install the desktop client for your operating system and sign in.
AdsPower's plans as listed on 2026-10-05:
| Plan | Profiles | Price |
|---|---|---|
| Free | 2 | $0, free forever |
| Paid | 10 | $9/month |
| Paid | 50 | $19/month |
| Paid | 100 | $29/month |
Yearly billing is 40% off and quarterly is 15% off. Extra team members are $5 each. There's also a 7-day full-feature trial.
One thing to know up front: AdsPower states that purchases are not refundable. That makes the free plan and the trial your real evaluation window. Build and verify a couple of profiles before you pay for a tier. Current pricing is on our AdsPower page.
Create your first profile: engine, OS, user agent
Click New profile in the upper-left corner of the client. On the General tab:
- Name. Use the name from your plan. Optional, but you'll thank yourself at profile 30.
- Browser. Choose SunBrowser (Chrome-based) or FlowerBrowser (Firefox-based), or Auto to use the latest installed version. If you don't have a reason to pick Firefox, SunBrowser is the safe default because most sites are tested against Chrome.
- Operating system. The OS you want the profile to present.
- User agent. AdsPower's documentation recommends keeping the user agent consistent with the browser engine you picked. The generated default is fine for most people.
- Group, tags and remarks. Group by team or marketplace now and bulk actions get much easier later.
- Cookies. If you're bringing an existing session, you can paste cookies in supported formats (JSON, Netscape, Name=Value).
Add the proxy and run the connection check
In the proxy section, choose Custom and select the proxy type. AdsPower's docs list HTTP, HTTPS, SOCKS5 and SSH, and IPv6 proxies are supported too. If you're unsure which protocol your provider gave you, SOCKS5 vs HTTP Proxy covers the difference.
Enter the details in the IP:port:username:password format, then click Check proxy. You want to see Connection test passed before going further.
If the check fails, the usual causes are:
- Wrong protocol. A SOCKS5 port entered as HTTP (or the reverse) is the single most common error.
- Stray whitespace in the username or password after copy-pasting.
- IP allowlisting. Some providers authenticate by allowlisted IP instead of, or in addition to, username and password. Check your provider's dashboard.
You can also save proxies and pick them from Saved Proxies later, which is handy once you have more than a handful.
A shortcut for IPFoxy users. AdsPower's help center documents an IPFoxy integration: you copy the proxy token for your dedicated static proxies from the IPFoxy dashboard, paste it into the Proxy Token field in AdsPower and click Sync proxy. After that, your IPFoxy proxies appear in a dropdown when you create profiles. Menu names on both sides may have moved since the docs were written.
Match time zone, language and location to the IP
Open the fingerprint settings. According to AdsPower's documentation, the defaults are:
| Setting | Default | Other options |
|---|---|---|
| Time zone | Based on IP | Real (system), Custom |
| Geolocation | Based on IP | Custom, Block |
| Language | Based on IP | Custom |
Leave these on Based on IP unless you have a specific reason. The classic beginner mistake is setting a custom time zone and forgetting the language, so a "London" browser reports a language that doesn't fit.
WebRTC has several modes: Forward, Replace, Real, Disabled and Disabled UDP. AdsPower's docs recommend Forward for high-security websites. Avoid Real, which exposes your device's actual WebRTC IP and defeats the point of the proxy.
Click OK to save the profile.
Three checks after first launch
Open the profile and, inside that browser window, run three checks before you log in to any account.
- IP. Visit an IP lookup site such as ipinfo.io. The country should match your plan, and the connection type should read as ISP rather than hosting/datacenter if you bought a static ISP IP.
- WebRTC. Use a WebRTC leak test page. Your local public IP must not appear anywhere.
- DNS. Run a DNS leak test. The resolvers should not belong to your local ISP; ideally they're in the same country as the proxy.
If any check fails, go back to the profile settings and fix it before you sign in. For a deeper look at what makes an IP "clean", see How to Check if a Proxy IP Is Clean.
A word of caution: passing these checks means the profile is configured correctly. It does not mean the profile is "undetectable", and no tool can honestly promise that. How an account fares depends on how it's operated and whether that operation follows the platform's rules.
Next steps
Once your first profile works, scale deliberately:
- Teams. Assign profiles through member roles and permissions so nobody shares a login.
- Automation. AdsPower includes a no-code RPA builder and a Local API that works with Selenium, Puppeteer and Playwright, useful for repetitive, permitted tasks.
- Capacity. Move to a paid tier only when two profiles genuinely aren't enough, and remember there are no refunds.
For more proxy options, browse the proxy comparison table or the anti-detect browser category. When you're ready, visit AdsPower.
Some links are affiliate links. We may earn a commission if you buy through them, at no extra cost to you and without affecting our ratings.




