DEV Community: Emerson Skaggs

TikTok Viewer: 6 Ways to View TikTok Profiles, Videos, and Stories More Privately in 2026

Emerson Skaggs — Wed, 02 Sep 2026 03:53:16 +0000

The more I looked into TikTok’s privacy settings, the more I realized there are several different things going on behind the scenes. Profile views, post views, and Story views don’t all follow the same rules.

That’s also why some of the advice you’ll find online can be confusing. A method that works for browsing a public profile doesn’t necessarily work for watching a Story anonymously.

So I spent some time testing the practical options and ended up with 5 approaches worth knowing about.

First, What Do People Mean by “TikTok Viewer”?

When people search for a TikTok viewer, they usually mean a website or tool that lets them look at public TikTok content without going through the normal TikTok app.

Some let you paste a username and see public videos.

Others work more like profile viewers, showing basic profile information and posts without requiring you to log in.

Then there are Story viewers that claim to retrieve public Stories.

You’ll also find browser extensions and standalone apps making similar promises.

This is where I’d be a little careful.

A third party viewer can be convenient, but I wouldn’t treat it as a magical anonymity button. If a website asks for your TikTok password just so you can view a public profile, that’s a pretty easy “no” for me.

The basic process

Most TikTok viewers work roughly like this:

Open the viewer in your browser.
Paste the TikTok username or profile link.
Select the profile you’re looking for.
Browse the public content available through the service.
Don’t enter your TikTok password or unnecessary account credentials.

That’s it.

The important distinction is that you’re accessing public content without using your normal TikTok session. That can reduce the amount of activity directly connected to your usual account, but it doesn’t mean you’re completely invisible.

1. My Favorite Approach: Keep TikTok in a Separate Browser Environment

This is probably the approach I’d use if I expected to do this regularly.

Instead of constantly opening and closing Incognito windows, I prefer having a completely separate browser environment for a specific type of activity.

Think of it like having another desk.

Your normal browser has your usual cookies, saved sessions, extensions, cache, and other browsing data.

A separate profile keeps those things from getting mixed together.

I’ve used anti detect browsers for this kind of separation, and BitBrowser is one example that makes the setup fairly straightforward. The useful part isn’t some promise of being “invisible.” It’s simply having control over separate browser profiles and their browsing data.

How I set up a separate TikTok profile

The setup is pretty simple.

Open BitBrowser and create a new browser profile.
Give it a recognizable name, such as TikTok Browsing.

Configure the browser fingerprint and other environment settings.
If your particular setup requires it, add a proxy to the profile.
Launch TikTok from that profile.
Browse public TikTok content from there.

Now your TikTok cookies, cache, and session data aren’t sitting alongside everything else in your everyday browser.

That separation becomes even more useful if you have several different accounts.

2. Just Use a TikTok Viewer

If you’re only trying to check one public profile, there’s no reason to overcomplicate things.

A TikTok viewer is probably the quickest option.

You can use one to:

Check a public profile
Watch public videos
Find public Stories if the service supports them
Browse without opening your main TikTok account

The catch is that not every viewer does the same thing.

Some only show profiles and videos. Others offer Stories or downloading.

So check what the service actually supports before assuming it can do everything.

And I’d avoid connecting your TikTok account unless there’s a very good reason to do so.

3. Don’t Log In at All

If the content is public, you may not need a TikTok account to view it.

TikTok allows public account content to be visible to people on or off the platform, including people who don’t have an account, depending on the creator’s privacy settings. Public content can also show up in search engines and other websites.

So before installing another tool, I’d simply try the TikTok website.

Here’s the process

Open your browser.
Go to TikTok’s website.
Search for the username or profile you’re interested in.
Open the public profile or post.
Browse whatever is available without signing in.

For public content, this is about as simple as it gets.

Obviously, it won’t let you see a private account’s content. That’s the whole point of a private account.

But if all you want is a quick look at something that’s already public, logging in may be unnecessary.

4. Incognito Mode Is Useful, Just Not for What People Think

I still use Incognito mode.

I just don’t think of it as an anonymity tool.

If you’re using a shared computer, private browsing is genuinely useful because it helps prevent your TikTok browsing history from being stored in the normal browser profile.

But websites can still see requests coming from your browser. Your network provider doesn’t suddenly stop knowing that you’re connected to the internet either.

So I’d describe Incognito as local privacy, not complete online anonymity.

5. Sometimes Google Is Enough

This one sounds almost too simple, but it works surprisingly often.

If I’m looking for a public TikTok profile rather than trying to browse TikTok for hours, I’ll sometimes start with Google.

Try:

site:tiktok.com/@username

Replace username with the creator's actual username.

You can also combine a username with a topic, phrase, or video title if you’re looking for a particular post.

How to find a TikTok profile through Google

Open Google or another search engine.
Search for site:tiktok.com/@username.
Replace username with the username you're looking for.
Open a relevant public TikTok result.
View the content that’s publicly accessible.

This is particularly useful when you don’t even want to start by opening the TikTok app.

Can They See You Viewed Their Profile?

This is where things get more interesting.

TikTok has a feature called Profile View History.

When it’s enabled for both people, TikTok may show that you visited the other person’s profile. The feature generally covers visits from the previous 30 days.

Fortunately, you can turn it off.

Here’s how Profile View History works

If your Profile View History is ON, your profile visit may appear to people who also have the feature enabled.

If you turn it OFF, you won’t appear in other people’s profile view lists.

There’s a trade off, though.

When you turn it off, you generally can’t see who viewed your own profile either.

So if you’re specifically worried about someone knowing that you opened their profile, this is the first setting I’d check.

How to Turn off Profile View History

Open TikTok and go to Profile.
Tap the Menu ☰.
Open Settings and privacy.
Tap Privacy.
Find Profile views.
Turn Profile view history OFF.

There’s one big catch.

This does not apply to Story views.

And that’s where a lot of TikTok privacy advice gets confusing.

TikTok Posts and Stories Are Different

There are separate mechanisms for profiles, posts, and Stories.

Post Views

TikTok has a separate Post View History feature.

According to TikTok, it can show certain post views and covers posts published during the previous seven days.

It’s available to eligible users who are at least 16 years old and have fewer than 5,000 followers.

So turning off Profile View History doesn’t necessarily settle the question of whether someone can see that you viewed a post.

Story Views

Stories are even more straightforward.

TikTok explicitly says that someone can see that you viewed their Story even if your account is private or Profile View History is turned off.

So if you’re thinking:

“I’ll just turn off Profile View History and watch their Story.”

That’s not enough. Story views are handled separately.

The Takeaway

After trying to make sense of all these options, I don’t think there’s one perfect “anonymous TikTok viewer.”

There are different levels of privacy, and they solve different problems.

If you just want to look at public content, not logging in is often the simplest answer.

If you need to keep your local browsing history private, Incognito mode does the job.

If you want to separate accounts and browsing sessions, a dedicated browser profile makes more sense.

And if you’re using a second TikTok account, remember that you’re separating the activity from your main account, not becoming anonymous to TikTok.

Most importantly, don’t assume that one privacy setting covers every type of TikTok activity.

Profile views, post views, and Story views are different things.

That’s the part I’d keep in mind before trying any TikTok viewer or privacy trick. Once you know exactly what you’re trying to hide or separate, choosing the right method becomes much easier.

6 Ways to View TikTok More Privately in 2026

Emerson Skaggs — Mon, 31 Aug 2026 05:51:52 +0000

Sometimes you may want to check a TikTok profile, watch a video, or browse public content without using your main TikTok account.

There are several ways to do this. Some are useful for simple viewing, while others are better if you want to keep your browsing environment separate.

Here are six practical options to consider in 2026.

1. Use an Anti Detect Browser

An anti detect browser can create a separate browser environment for TikTok.

For example, BitBrowser lets you create dedicated browser profiles with separate cookies, cache, settings, and browser fingerprint information.

This can be useful if you regularly switch between different browsing environments or simply want to keep TikTok activity separate from your everyday browser.

BitBrowser also offers 10 browser profiles for free permanently, which is enough for many casual browsing needs.

2. Use a TikTok Viewer

A TikTok viewer is usually a website where you enter a TikTok username or link to access publicly available profiles or videos.

This can be convenient when you do not want to use your main TikTok session.

However, third party viewers are not all the same. Some only support profiles and videos, while others may offer additional features. Avoid entering your TikTok password or unnecessary account information into an unknown service.

3. Browse TikTok Without Logging In

If you only want to view public content, you may not need a TikTok account at all.

Open TikTok in a web browser and search for the public profile or content you want to see. Depending on the creator's privacy settings, public TikTok content can be accessible without signing in.

For simple browsing, this is probably the easiest method.

4. Use Incognito or Private Browsing

Incognito or Private Browsing mode can help keep your TikTok browsing history from being saved locally on your device.

It is important to understand what this actually does, though. Incognito mode provides local browser privacy, but it does not make you completely anonymous to TikTok, websites, or your network provider.

So it is useful for shared computers or temporary browsing, but it should not be treated as a complete anonymity solution.

5. Use a Secondary TikTok Account

Another option is to create a separate TikTok account for specific activities.

This can help keep your main account separate from other TikTok usage, especially if you manage different interests, projects, or social accounts.

A secondary account is still connected to an identifiable TikTok session, though, so it is not the same as anonymous browsing.

6. Use Search Engines

Sometimes you do not even need to open TikTok directly.

You can search for public profiles and posts through Google or another search engine. For example:

site:tiktok.com/@username

This can be useful when you simply want to find a public TikTok profile or a specific piece of content.

Can People See That You Viewed Their TikTok?

This is where things get a little more complicated.

TikTok has separate systems for profile views, post views, and Story views.

With Profile View History enabled, eligible users may be able to see profile visits from other users who also have the feature enabled. Turning Profile View History off can prevent your profile visit from appearing in those lists.

However, this does not apply to every type of TikTok view.

TikTok Stories are different. The Story owner can see that you viewed their Story even if your Profile View History is turned off.

TikTok also has a separate Post View History feature for certain users and posts.

So if your goal is to browse TikTok more privately, it is worth checking which type of content you are viewing rather than assuming one privacy setting covers everything.

Which Method Should You Use?

It really depends on what you need.

For simple public content: browse TikTok without logging in.

**For viewing profiles through another service: **consider a TikTok viewer, but choose third party services carefully.

For local privacy: use Incognito or Private Browsing.

For separating TikTok activity: use a secondary account or a dedicated browser profile.

For more control over browser environments: an anti detect browser such as BitBrowser can keep cookies, cache, and other browsing data separated between profiles.

There is no single method that makes every type of TikTok activity completely anonymous. The best approach is to understand what each method actually protects and choose the one that fits your situation.

Cloud Phone Farm vs Physical Phone Farm: Which One Should You Choose in 2026?

Emerson Skaggs — Tue, 25 Aug 2026 08:54:22 +0000

Managing multiple mobile devices at scale can be done in two main ways: using physical phones or cloud phones.

A physical phone farm gives you direct access to real devices, but it also means dealing with hardware costs, power, cables, space, cooling, and maintenance.

A cloud phone farm moves those devices into virtual mobile environments that can be accessed and managed remotely.

Physical Phone Farm

With a physical setup, you purchase and connect multiple smartphones yourself.

Pros

Real physical hardware
Full control over the devices
No recurring cloud subscription
Suitable for workflows that require specific hardware features

Cons

High upfront costs
Requires physical space and power
Regular maintenance and repairs
More difficult to scale
Devices and batteries can wear out over time

Managing 50 or 100 phones can quickly become a hardware management job rather than an operational one.

Cloud Phone Farm

Cloud phones provide Android or iOS environments that you can access remotely without owning the physical devices.

Pros

Lower upfront investment
No hardware to maintain
Easy to create or remove devices
Remote access
Centralized management
Easier to scale
Better suited for distributed teams

The main tradeoff is the recurring subscription cost. Some hardware specific features may also be difficult to reproduce in a cloud environment.

Physical vs Cloud Phone Farm

Which One Should You Choose?

A physical phone farm makes sense if you need direct access to real hardware, specific device features, or long term ownership.

For most software based workflows, a cloud phone farm is more flexible. You can start faster, manage devices remotely, and scale without dealing with racks of phones, charging cables, batteries, and repairs.

Services such as BitCloudPhone provide cloud Android and iOS environments that can be managed from a central dashboard.

The right choice ultimately depends on your workflow. If hardware control is the priority, go physical. If flexibility, scalability, and easier management matter more, cloud phones are worth considering in 2026.

How to Connect an AI Tool to a Local MCP Server: A Practical Example

Emerson Skaggs — Mon, 24 Aug 2026 07:28:12 +0000

Model Context Protocol (MCP) is making it easier for AI assistants to interact with external tools and applications.

Instead of manually clicking through every setting, you can connect an MCP server to a compatible AI tool, describe what you want in natural language, and let the assistant handle the individual operations.

A practical example is BitBrowser 7.1.5, which added MCP support through its local API.

This article walks through the setup and shows how MCP can be used for everyday browser management tasks.

What You Need

For this example, you need:

BitBrowser 7.1.5 or later
An AI tool that supports MCP
BitBrowser's Local API enabled
An MCP configuration generated by BitBrowser

The same basic approach can also be applied to other applications that expose their functionality through MCP.

1. Enable the Local MCP Server

Open BitBrowser and go to:

Settings → Browser Settings → Local API

Enable Authentication Control.

BitBrowser will generate an API token and display the required request header:

x-api-key: <YOUR_API_TOKEN>

The default endpoints are:

Local API: http://127.0.0.1:54345
MCP: http://127.0.0.1:54345/mcp

If you use a different Local API port, use the address shown in your settings.

2. Get the MCP Configuration

Scroll down to the MCP section.

BitBrowser provides configurations for several compatible AI tools, including:

Codex
Cursor
OpenCode
WorkBuddy
Qwen
Hermes
OpenClaw
General
Claude Code

Select your AI tool and copy the generated configuration.

Using the generated configuration is usually the simplest option because the endpoint and authentication settings are already included.

For a generic MCP client, the configuration looks similar to:

{
  "mcpServers": {
    "bitbrowser": {
      "url": "http://127.0.0.1:54345/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_TOKEN>"
      }
    }
  }
}

Replace

<YOUR_API_TOKEN>

with your actual token.

Keep the x-api-key header name unchanged.

3. Connect the MCP Server

Open your AI tool's MCP settings.

Depending on the application, this may be called:

MCP Servers
Custom MCP
Tools
Integrations
Connectors

Add a new MCP server and paste the configuration.

After saving, check that the server is enabled and that its tools are available.

4. Start with a Read-Only Request

Before asking the AI to make changes, test the connection with a read-only request.

For example:

Show me my current BitBrowser setup.

List all existing Browser Profiles and cloud phones, including their names, groups, and status.

Do not make any changes.

If the AI can retrieve the information correctly, the MCP connection is working.

Starting with a read-only request is also a good way to avoid accidental changes while testing a new integration.

5. Create Browser Profiles with Natural Language

Once the connection works, you can ask the AI to perform actual operations.

For example:

Create 3 new Browser Profiles named MCP_Demo_01, MCP_Demo_02, and MCP_Demo_03.

Use English (US) as the browser language.

Create a group called "MCP Demo" and add all three profiles.

Do not modify any existing profiles.

Verify that all three profiles were created successfully and added to the correct group.

A single request can cover several operations:

Create profiles → configure settings → create a group → assign profiles → verify

You don't have to manually select each underlying MCP tool.

6. Configure Proxies

MCP can also be used for proxy configuration.

For example:

Configure the following SOCKS5 proxies for the three profiles in the "MCP Demo" group.

MCP_Demo_01 → proxy 1
MCP_Demo_02 → proxy 2
MCP_Demo_03 → proxy 3

Keep all other Browser Profile settings unchanged.

Verify each proxy after updating.

A useful pattern is to clearly specify two things:

What should change

and

What should remain unchanged

This reduces the chance of unintended modifications.

Never include real proxy passwords, API tokens, or other sensitive credentials in public prompts or examples.

7. Make Targeted Changes

MCP doesn't have to be used for large workflows.

It can also handle small maintenance tasks.

For example:

Change the browser language of MCP_Demo_01 and MCP_Demo_02 to French.

Keep their proxy settings, group assignments, and other fingerprint settings unchanged.

Verify the changes after updating.

Another example:

Randomize the browser fingerprints for MCP_Demo_02 and MCP_Demo_03.

Do not change their proxy settings, language, or group assignments.

This makes natural language useful for both routine maintenance and more complex workflows.

8. Combine Multiple Operations

The more interesting use case is combining several operations into one request.

For example:

Create 5 new Browser Profiles named Project_01 through Project_05.

Use English (US) as the browser language.

Create a group called "Project Profiles" and add all five profiles.

Configure the proxy assigned to each profile.

Verify that all five profiles exist, are in the correct group, have the correct proxy, and use English (US).

Do not modify existing profiles outside this group.

The AI can break this request into multiple operations and then check the resulting state.

The basic idea is simple:

Describe the desired result. Let the AI handle the individual operations.

Troubleshooting

If the AI cannot connect, check the following:

BitBrowser is running
BitBrowser is version 7.1.5 or later
Local API is enabled
Authentication Control is enabled
The MCP endpoint is correct
x-api-key is included
The API token is correct
The MCP server is enabled in your AI tool

If the AI connects but an operation fails, start by asking it to inspect the relevant item without making changes.

For example:

Check the current status of MCP_Demo_01.
Do not make any changes.

If the AI reports that an operation succeeded but the interface does not appear to have changed, refresh the application and query the item again before repeating the operation.

Security Considerations

Local MCP integrations still involve credentials and access permissions.

Keep the following private:

API tokens
Proxy usernames and passwords
Other authentication credentials
Private configuration files

Don't publish them in screenshots, repositories, public prompts, or social posts.

It's also a good practice to begin with read-only requests and explicitly tell the AI what it should not modify.

Final Thoughts

MCP adds a different way to interact with software.

Instead of navigating through every routine operation manually, you can describe the task and let an AI assistant coordinate the available tools.

The BitBrowser MCP integration is one practical example of this approach, covering browser profiles, proxies, fingerprints, groups, cloud phones, and other management operations.

If you're trying MCP for the first time, keep it simple:

Connect → test with a read-only request → try one small task → build larger workflows.

How to Unblock Websites on iPhone in 2026: 8 Easy Ways

Emerson Skaggs — Sat, 22 Aug 2026 05:46:37 +0000

If a website won't open on your iPhone, the problem isn't always the website itself. Screen Time, Wi‑Fi filtering, DNS settings, Safari, mobile carrier restrictions, or network settings can all affect website access.

In this guide, you'll learn how to unblock websites on iPhone using 8 simple methods. Start with the easiest checks first, then move on to network and browser troubleshooting.

Why Are Websites Blocked on iPhone?

A website may not load on your iPhone for several reasons:

Screen Time restrictions may block certain websites or categories.
School or work Wi‑Fi may filter specific websites.
DNS filtering may prevent a domain from resolving.
Mobile carrier restrictions may limit certain content.
Safari data may cause loading or login problems.
iCloud Private Relay may affect some IP‑based security checks.
IP or regional restrictions may prevent access.
Browser settings or extensions may interfere with the website.

Before trying more complicated solutions, it's useful to identify which layer is causing the problem.

How to Unblock Websites on iPhone: Quick Overview

Method	Best For	Difficulty
Check Screen Time	Device level restrictions	Easy
Switch Wi‑Fi to mobile data	Wi‑Fi filtering	Easy
Change DNS	DNS‑based blocking	Medium
Use a VPN	Network or IP restrictions	Easy
Try Cloudflare WARP	DNS and connection issues	Easy
Check Private Relay	IP and Safari compatibility	Easy
Clear Safari data	Cookies and cached data	Easy
Try another browser	Safari specific problems	Easy

1. Check Screen Time Restrictions

If a website is blocked on both Wi‑Fi and mobile data, Screen Time may be responsible.

Go to:

Settings → Screen Time → Content & Privacy Restrictions → Web Content

Depending on your iOS version, you may see options such as:

Unrestricted Access
Limit Adult Websites
Allowed Websites Only

If Allowed Websites Only is enabled, websites that aren't on the approved list may not open.

If Screen Time is managed by a parent, school, or organization, you may not have permission to change these settings.

2. Switch From Wi‑Fi to Mobile Data

This is one of the quickest ways to determine whether your Wi‑Fi network is blocking a website.

Turn off Wi‑Fi and open the same website using cellular data.

If the website works on mobile data but not Wi‑Fi, the problem may be related to:

School or workplace filtering
Router settings
DNS filtering
Public Wi‑Fi restrictions
Network firewall rules

If the website still doesn't work on mobile data, check your iPhone, browser, DNS, or the website itself.

3. Change DNS on iPhone

DNS is responsible for translating website domains into IP addresses. If your network uses a filtered DNS service, some websites may fail to load.

To change DNS for a Wi‑Fi connection:

Settings → Wi‑Fi → ⓘ → Configure DNS → Manual

Remove the existing DNS servers and test a public DNS provider.

For example:

Cloudflare DNS

1.1.1.1

1.0.0.1

Or:

Google DNS

8.8.8.8

8.8.4.4

Save the settings and try opening the website again.

Changing DNS won't bypass every type of restriction. If the network uses stronger filtering or firewall rules, you'll need to troubleshoot the connection itself.

4. Use a VPN

A VPN routes your connection through another server and gives you a different network path.

A VPN may help troubleshoot:

Network‑based restrictions
IP‑based restrictions
Some regional access problems
Certain public Wi‑Fi filters

To test this method, install a reputable VPN app on your iPhone, connect to a nearby server, and reload the website.

If the VPN connects but the website still doesn't load, the problem may be caused by the website itself or by stronger network restrictions.

Tip: If you're using a school or workplace network, make sure VPN use is permitted by the network administrator.

5. Try Cloudflare WARP

Cloudflare WARP provides another way to test whether DNS or your current network connection is causing the problem.

You can install the 1.1.1.1 app from Cloudflare and enable WARP.

Then reopen the website.

If the website works with WARP but not with your normal connection, the issue may be related to your current DNS or network path.

WARP won't necessarily solve restrictions imposed by a website, organization, or service provider.

6. Check iCloud Private Relay

iCloud Private Relay can hide your IP address when browsing with Safari. Some websites may have compatibility problems with Private Relay or IP‑based security checks.

To test whether it is affecting access:

Settings → [Your Name] → iCloud → Private Relay

Temporarily turn Private Relay off and try the website again.

If the website starts working, Private Relay may be affecting the site's IP or security checks.

You can also review Safari's IP address settings under:

Settings → Apps → Safari → Hide IP Address

7. Clear Safari Data

If only one website refuses to load, the problem may not be a network block at all.

Old cookies, cached redirects, or broken sessions can sometimes prevent a website from loading correctly.

To clear Safari data:

Settings → Safari → Clear History and Website Data

For data from a specific website, go to:

Settings → Safari → Advanced → Website Data

Search for the domain and remove its stored data.

Then reopen Safari and try the website again.

8. Try Another Browser

Sometimes a website works normally but has problems with your current browser configuration.

Try opening the website with:

Google Chrome
Mozilla Firefox
Microsoft Edge

If the website works in another browser, check Safari settings, extensions, content blockers, or stored website data.

You can review Safari extensions under:

Settings → Apps → Safari → Extensions

Temporarily disabling a content blocker can also help identify the problem.

How to Unblock Websites on School or Work Wi‑Fi

School and workplace networks may use filtering systems to restrict websites based on security, productivity, or organizational policies.

If a website doesn't work on Wi‑Fi but works on mobile data, try:

Switching to mobile data.
Testing another Wi‑Fi network.
Checking whether DNS filtering is involved.
Trying WARP or a VPN if permitted.
Asking the network administrator for access if the website is required for legitimate work or study.

If the restriction is intentional and managed by an organization, changing your iPhone settings may not remove it.

Can BitBrowser Help With Website Access?

BitBrowser is primarily designed for isolated browser profiles, not for changing iPhone network restrictions.

It can be useful when the problem is related to browser environments, cookies, sessions, or website testing.

For example, separate profiles can keep browser data isolated when you're testing:

Different browser sessions
Cookies and Local Storage
Browser fingerprints
Multiple account environments
Website behavior across different profiles

BitBrowser won't override a network administrator's firewall or a website's own access rules. It's better suited to browser and session troubleshooting than iPhone network troubleshooting.

Quick Troubleshooting Guide

What Happens	Possible Cause	What to Try
Website fails on Wi‑Fi but works on mobile data	Wi‑Fi filtering	Check network or DNS
Website fails on both connections	Device, browser, or website issue	Check Screen Time and browser
Website works after changing DNS	DNS filtering	Use a different DNS provider
Website works in Chrome but not Safari	Safari issue	Clear data or check extensions
Website works after disabling Private Relay	IP compatibility	Review Private Relay settings
Website works on another network	Network restriction	Check the original network
VPN or WARP fixes the connection	Network or IP issue	Check your normal connection

FAQ

Why won't a website open on my iPhone?

Common causes include Screen Time restrictions, Wi‑Fi filtering, DNS problems, Safari data, Private Relay, browser settings, carrier restrictions, or website‑level restrictions.

How do I unblock a website on iPhone without a VPN?

Start by checking Screen Time, switching from Wi‑Fi to mobile data, changing DNS, clearing Safari data, or trying another browser.

Why does a website work on mobile data but not Wi‑Fi?

This usually indicates that the problem is related to your Wi‑Fi network, router, DNS, or network filtering.

Does changing DNS unblock websites on iPhone?

Changing DNS can help when a website is being blocked at the DNS level. It won't bypass every type of network or website restriction.

Why does a website work in Chrome but not Safari?

Safari settings, cookies, extensions, content blockers, or cached website data may be causing the problem.

Final Thoughts

When a website won't open on your iPhone, don't assume that you need a VPN immediately.

Start with the simplest tests:

Wi‑Fi vs. mobile data → Screen Time → DNS → another browser → Safari data → Private Relay → another network.

These steps can help you identify whether the problem is coming from your iPhone, browser, DNS, network, or the website itself.

If you're troubleshooting browser sessions or testing websites across separate browser environments, an isolated browser such as BitBrowser can provide additional control over browser data and profiles.

Note: Only access websites and services you're authorized to use, and follow applicable laws, terms of service, and network policies.

7 Sneaker Proxy Providers in 2026: Comparing Residential, ISP, and Mobile Proxies

Emerson Skaggs — Mon, 17 Aug 2026 05:59:38 +0000

If you work with online sneaker stores, you have probably noticed that the network connection is only one part of the setup.

During a popular release, traffic can increase quickly. Different stores may also use different rate limits, session rules, geographic configurations, and security systems. A proxy can help you work with different network locations and keep separate sessions organized, but choosing the right type of proxy is just as important as choosing the provider.

I compared seven proxy providers that are worth considering in 2026:

Decodo
Oxylabs
Bright Data
SOAX
Webshare
IPRoyal
HighProxies

This guide focuses on proxy quality, session stability, geographic coverage, pricing, and practical browser profile management.

What Makes a Good Sneaker Proxy?

There is no single metric that tells you whether a proxy is good.

For online shopping and other web based workflows, I would look at five things first.

1. IP quality

The reputation and type of an IP can affect how a website treats a connection.

Residential and ISP proxies are often preferred for normal web traffic because they are associated with internet service providers or residential networks rather than traditional datacenter infrastructure.

2. Speed

A slow proxy can make a simple browsing session frustrating.

Latency is particularly important when your workflow involves multiple page loads or interactive sessions. However, speed should not be considered in isolation. A very fast proxy that frequently disconnects is not very useful.

3. Session stability

Some tasks work better when the same IP remains connected throughout a session.

Sticky sessions can be useful when you need to maintain a consistent connection while browsing a store or moving between several pages.

4. Geographic coverage

If you need to test a US storefront, for example, you may want a US IP. The same applies to European or Asian storefronts.

A provider with broad geographic coverage gives you more flexibility.

5. Pricing

Proxy pricing can vary dramatically depending on the proxy type, location, bandwidth, and number of IPs.

A premium provider is not automatically the best choice for every user. Start by estimating how much traffic and how many locations you actually need.

1. Decodo

Decodo is a strong all around option if you want a balance between proxy quality, stability, and ease of use.

The provider offers residential, ISP, and mobile proxy options, although availability can vary depending on the plan.

One of the biggest advantages is that it does not feel unnecessarily complicated for everyday use. You can choose a proxy type based on your workflow without spending hours configuring advanced infrastructure.

Best for

General online shopping workflows
Shopify based stores
Multiple geographic locations
Users who want a balanced solution

Proxy types

Residential
ISP
Mobile

My take

Decodo is probably the easiest provider to recommend if you are not sure where to start.

It offers enough flexibility for more advanced workflows while remaining relatively approachable for beginners.

The main downside is that premium proxy pools can become expensive when traffic requirements increase.

2. Oxylabs

Oxylabs is better suited to users who need scale and broad geographic coverage.

Its network includes residential, ISP, and mobile proxies, making it possible to build different configurations depending on your requirements.

The main strength here is infrastructure. If you are working across multiple regions or managing a larger number of connections, having access to a large proxy pool can make a significant difference.

Best for

Large scale projects
Multiple geographic regions
Teams
Users who prioritize infrastructure and consistency

Proxy types

Residential
ISP
Mobile

My take

Oxylabs is a strong choice when you have already outgrown smaller proxy providers.

The biggest drawback is the price. For a small personal project, the additional cost may not be justified.

3. Bright Data

Bright Data is the power user option on this list.

It provides a wide range of proxy configuration options and detailed geographic targeting. This makes it useful when proxy behavior is part of a larger technical workflow.

The tradeoff is complexity.

If you only need a couple of proxies for browsing, you probably do not need all of the controls Bright Data provides.

Best for

Advanced users
Detailed geographic targeting
Automation infrastructure
Technical teams

Proxy types

Residential
ISP
Mobile

My take

The flexibility is the biggest advantage.

You can build much more specific proxy configurations than you can with a basic proxy provider.

The downside is that the platform can take some time to understand, especially if you are new to proxy infrastructure.

4. SOAX

SOAX focuses heavily on residential and mobile proxy traffic and provides useful session management features.

For workflows where session consistency matters, this can be useful.

The provider is not necessarily the first choice for someone looking for the largest possible IP pool. Instead, it makes more sense if you value controlled sessions and predictable connections.

Best for

Stable residential sessions
Mobile proxy workflows
Regional testing
Users who prioritize consistency

Proxy types

Residential
Mobile

My take

SOAX is a good middle ground when you care more about session quality than maximum scale.

The main limitation is cost. It is not the cheapest option on this list.

5. Webshare

Webshare is an interesting choice if budget and simplicity are important.

The service offers a free tier for testing as well as paid proxy plans. It is relatively easy to get started without dealing with a complicated enterprise setup.

That makes it useful for development, testing, monitoring, and smaller projects.

Best for

Beginners
Testing
Budget conscious projects
Lightweight workflows

Proxy types

Datacenter
Residential
Other options depending on the current product lineup

My take

The biggest advantage is accessibility.

You can start small and increase your usage later if necessary.

The important thing is to choose the proxy type carefully. Datacenter proxies can behave differently from residential or ISP proxies, so they should not automatically be treated as interchangeable.

6. IPRoyal

IPRoyal is another provider worth considering when price matters.

It offers residential and ISP proxy options and tends to position itself as a more affordable alternative to some premium providers.

The performance you get can vary by location, so I would recommend testing the exact regions you need before committing to a larger plan.

Best for

Smaller projects
Budget conscious users
Residential proxy usage
Mixed proxy setups

Proxy types

Residential
ISP
Mobile, depending on the current offering

My take

IPRoyal offers a useful balance between cost and functionality.

It may not provide the same infrastructure depth as the largest enterprise providers, but that is not necessarily a problem for smaller projects.

7. HighProxies

HighProxies has been around for a long time and is particularly interesting if you need US focused ISP proxies.

Its ISP and residential offerings can be useful when you want a stable connection from a US location.

The main limitation is geographic coverage. Compared with larger global providers, the network is more focused.

Best for

US focused workflows
ISP proxies
Stable connections
Online stores with US locations

Proxy types

ISP
Residential

My take

If your project is primarily US focused, HighProxies is worth testing.

It is less attractive if you need a very large number of locations around the world.

Residential vs ISP vs Mobile Proxies

The provider is only part of the decision. Choosing the right proxy type is equally important.

Residential Proxies

Residential proxies use IP addresses linked to real residential internet connections. They are commonly used for browsing, regional testing, price monitoring, and other web tasks that require geographic diversity.

They offer wide location coverage and work well for many general-purpose workflows, especially when IP rotation is needed. However, they can be more expensive, connection quality may vary by location, and bandwidth costs can increase quickly.

For most general web activities, residential proxies are usually the easiest option to begin with.

ISP Proxies

ISP proxies provide IP addresses associated with internet service providers while offering more stable connections. They are a good choice for tasks that require longer sessions without frequent IP changes.

Their main advantages are stable connections, lower latency in many regions, and better performance for session-based workflows. The downsides are smaller IP pools in some cases, higher costs than basic datacenter proxies, and limited availability depending on location.

If connection stability matters more than frequent IP rotation, ISP proxies may be a better fit.

Mobile Proxies

Mobile proxies route traffic through mobile carrier networks. They are usually more expensive and may not deliver the same speed as other proxy types, but they can be useful for specific scenarios involving mobile network environments.

They provide access to mobile carrier IP ranges and additional geographic options, making them suitable for mobile-focused testing. However, their higher cost and potentially lower speed mean they are unnecessary for most basic use cases.

For most users, mobile proxies are a specialized option rather than the default choice.

How to Manage Proxies with Browser Profiles

Once you start working with multiple proxies, another problem appears.

You need to keep sessions separated.

A browser stores much more than just your login information. Cookies, local storage, cached data, browser settings, and other session information can remain connected to a particular browsing environment.

Using separate browser profiles can make this easier to manage.

For example:

Profile A → Proxy A → Session A

Profile B → Proxy B → Session B

Profile C → Proxy C → Session C

This structure is easier to troubleshoot than putting everything into one browser profile.

It also makes it easier to test different geographic connections without constantly changing the configuration of your main browser.

Using Anti-detect Browser for Profile and Proxy Management

For workflows that require multiple isolated browser environments, a tool such as BitBrowser can simplify the process.

Instead of managing everything inside one browser, you can create separate profiles with their own browser settings, cookies, local storage, and proxy configuration.

A basic setup looks like this:

Step 1: Create a browser profile

Create one profile for each separate working environment.

Give each profile a clear name so you can identify it later.

For example:

US_Shop_Profile_01
US_Shop_Profile_02
EU_Test_Profile_01

Step 2: Add the proxy

Configure the proxy directly inside the browser profile.

Depending on the provider, you may use HTTP, HTTPS, or SOCKS5.

Enter the host, port, username, and password provided by your proxy service.

Then test the connection before using the profile.

Step 3: Check regional settings

If you are testing a website from a specific region, keep the browser environment reasonably consistent with that location.

For example, check:

Timezone
Browser language
WebRTC behavior
Location permissions

You do not need to randomly change everything. In fact, unnecessary changes can make testing less consistent.

Step 4: Keep profiles separate

Avoid constantly moving the same session between unrelated profiles.

A simple structure is easier to maintain:

Profile 01 → Proxy 01
Profile 02 → Proxy 02
Profile 03 → Proxy 03

This also makes it easier to identify whether a connection or browser configuration is causing a problem.

Final Thoughts

Choosing a sneaker proxy is less about finding a magic provider and more about matching the infrastructure to your actual workflow.

Residential proxies are useful for general browsing and geographic diversity.

ISP proxies are often a better choice when stable sessions and low latency matter.

Mobile proxies are more specialized and make sense when you specifically need mobile carrier connectivity.

Among the providers I compared, Decodo is a strong general purpose choice, Oxylabs is better suited to scale, Bright Data stands out for advanced configuration, and Webshare is attractive for smaller budgets.

Whichever provider you choose, test before scaling.

A reliable setup is usually built from several simple pieces: a suitable proxy, a consistent browser profile, isolated sessions, and clear configuration management.

And as always, use these tools for legitimate web access, testing, research, and online shopping while following the terms of the websites you use.

Run iOS Apps on Windows: 10 Best iOS Emulators & Cloud iPhones for PC in 2026

Emerson Skaggs — Mon, 10 Aug 2026 04:07:02 +0000

If you have ever searched for an iOS emulator for Windows, you probably noticed something confusing.

Many tools claim to bring iPhone apps to your PC, but the reality is more complicated. Some are simulators. Some provide remote access to real devices. Others only create an iOS-like interface.

Apple does not offer an official iOS emulator for Windows. iOS is tightly connected to Apple hardware, and the complete iPhone environment cannot simply be installed on a Windows machine.

However, there are still practical ways to access iOS apps from Windows in 2026.

Depending on your goal, you might need:

A real iPhone environment for daily app usage
A testing platform for mobile development
A remote Mac for Xcode and iOS development
A cloud device solution for managing mobile environments

This guide explains the differences and covers the most useful options available today.

Emulator vs Simulator vs Cloud iPhone: What Is the Difference?

Before choosing a tool, it is important to understand what you are actually getting.

A true emulator tries to reproduce both the hardware and software of another device. For iOS, this is extremely difficult because Apple controls both the operating system and the hardware ecosystem.

Most solutions fall into three categories.

iOS Simulators

Simulators recreate the iOS software environment using your computer's resources.

They are mainly used by developers for:

Testing app interfaces
Debugging code
Checking different screen sizes
Building iOS applications

The limitation is that simulators do not fully reproduce real iPhone hardware behavior.

Real Device Cloud Services

Cloud device platforms provide access to actual iPhones hosted remotely.

They are useful when you need:

Real iOS behavior
App Store access
Hardware testing
Camera, GPS, and sensor features

The device runs somewhere else, but you control it through your Windows computer.

Remote Mac Services

Another approach is renting access to a Mac.

This allows Windows users to:

Run Xcode
Use Apple's official iOS Simulator
Build and test iOS applications

It works well for development, but it is not the same as running iOS directly on Windows.

Best Ways to Use iOS Apps on Windows in 2026

BitCloudPhone-iOS: A Real iPhone Environment from Windows

If your goal is to use a real iOS environment from Windows, BitCloudPhone-iOS takes a different approach from traditional emulators.

Instead of creating a virtual iPhone, it provides access to real iPhones hosted in the cloud.

The apps run on actual iPhone hardware, while users control the device remotely from a Windows computer.

This approach avoids many limitations of traditional iOS simulators because the environment is based on real devices.

How BitCloudPhone-iOS Works

BitCloudPhone-iOS uses real-device cluster technology with physical iPhone SE2 and SE3 devices running native iOS.

Each device includes:

Real A-series chip resources
Genuine iOS system environment
Real device identifiers
Hardware sensors such as GPS, accelerometer, and gyroscope

From the application's perspective, it behaves like a normal iPhone because it runs on real hardware.

This makes it different from browser-based simulators or virtual iOS interfaces.

Main Features

Feature	Description
Native iOS System	Runs genuine iOS instead of a simulated interface
App Installation	Supports App Store and app installation
Multiple Devices	Manage multiple iOS cloud phones from one PC
Proxy Support	Supports SOCKS5 proxy configuration
Device Transfer	Move sessions to physical iPhones through QR code
Batch Management	Organize devices and workflows

Who Uses BitCloudPhone-iOS?

Social Media Managers

Managing multiple mobile accounts often requires separate device environments.

A cloud iPhone setup can help organize:

TikTok accounts
Instagram profiles
Facebook pages
Other mobile-first platforms

E-commerce Operators

Mobile applications are becoming increasingly important for:

Marketplace management
Mobile shopping tools
Store operations

A dedicated cloud device environment makes it easier to separate workflows.

App Developers and Testers

Developers can use real iOS devices to check:

App behavior
Mobile UI performance
Device-specific issues

Real hardware testing is especially useful when simulators cannot reproduce actual device behavior.

Why Choose a Real Device Instead of a Simulator?

The biggest difference is accuracy.

A simulator may be enough for checking layouts or basic functionality.

A real iPhone environment is better when you need:

Actual iOS behavior
Real hardware sensors
Native app compatibility
A production-like environment

BitCloudPhone-iOS belongs to the real-device cloud category, combining physical iPhone hardware with remote access.

Getting Started with BitCloudPhone-iOS on Windows

The basic setup process is straightforward:

Install the BitBrowser client and sign in.
Open the iOS cloud phone section and choose a device.
Configure a SOCKS5 proxy if needed.
Start the device and wait for initialization.
Install apps from the App Store and use the iOS environment from Windows.

For developers, testers, and users who need access to real iOS hardware without owning multiple devices, a cloud iPhone solution provides a practical alternative.

Other iOS Cloud Testing Platforms for Windows Users

Besides real-device cloud solutions, there are several platforms designed mainly for developers and QA teams.

These services provide access to real iPhones and iPads through a browser or remote testing environment. They are useful when you need to test app compatibility without owning multiple physical devices.

BrowserStack

BrowserStack is a popular cloud testing platform that provides access to real mobile devices, including iPhones and iPads.

It is mainly used for:

Mobile app testing
Website testing on different devices
Automated testing workflows
Cross-browser compatibility checks

Developers can upload apps, select an iOS device, and test how their applications perform in different environments.

Key Features

Real iPhone and iPad access
Browser-based testing
Automated testing support
Integration with development tools
Screenshots and debugging tools

BrowserStack works well for teams that need quick access to multiple device models without maintaining a physical device lab.

Sauce Labs

Sauce Labs provides cloud-based testing solutions for web and mobile applications.

Its real device cloud allows developers to test iOS apps on different Apple devices and iOS versions.

Common use cases include:

Automated mobile testing
Continuous integration workflows
App performance testing
Regression testing

Key Features

Real iOS devices
Automated testing frameworks
CI/CD integration
Detailed test reports
Team collaboration tools

Sauce Labs is often used by larger development teams that need structured testing workflows.

Kobiton

Kobiton focuses on mobile app testing using real devices and AI-powered testing tools.

The platform provides access to real smartphones, including iOS devices, through the cloud.

It is designed for:

Manual app testing
Automated testing
Bug reporting
Mobile experience monitoring

Key Features

Real device access
App performance testing
Session recording
Test automation
Device management

Kobiton is useful for teams that want to combine manual testing with automated workflows.

HeadSpin

HeadSpin provides a global mobile testing platform that combines real devices with performance monitoring.

It allows developers to test applications across different locations and network conditions.

Common uses include:

Mobile app performance testing
Network condition testing
User experience monitoring
Global app testing

Key Features

Real mobile devices
Global testing locations
Performance analytics
Network simulation
Automated testing support

HeadSpin is more focused on enterprise-level testing and application performance analysis.

Corellium

Corellium is a platform designed for advanced iOS research and security testing.

Unlike traditional cloud testing platforms, Corellium provides virtualized iOS devices that allow researchers to analyze iOS environments.

It is commonly used for:

Security research
Malware analysis
iOS development research
System-level testing

Key Features

Virtual iOS devices
Debugging capabilities
Security research tools
Developer-focused features

Corellium is mainly targeted at security researchers and advanced developers rather than everyday users.

Remote Mac Services for iOS Development

For developers who need Apple's official tools, renting a Mac is another option.

Since Xcode only runs on macOS, Windows users often use remote Mac services to access:

Xcode
iOS Simulator
Swift development tools
App Store build tools

Popular remote Mac providers include:

MacStadium
MacInCloud
AWS EC2 Mac instances

This approach is usually better for building and publishing iOS applications.

However, it requires more technical setup compared with browser-based cloud devices.

Choosing the Right Solution

The best option depends on what you are trying to do.

For App Development

Use:

Remote Mac services
Xcode
iOS Simulator
Real device testing platforms

This provides the tools needed to build and debug applications.

For App Testing

Use:

BrowserStack
Sauce Labs
Kobiton
HeadSpin

These platforms are designed for testing different devices and iOS versions.

For Real iPhone Usage on Windows

Use:

Real-device cloud phone solutions

These provide a more natural iOS experience because they run on actual iPhone hardware.

For Security Research

Use:

Specialized platforms like Corellium

These provide deeper system-level access for advanced analysis.

What About Traditional iOS Emulators for Windows?

Many websites advertise iOS emulators that can run iPhone apps directly on Windows.

However, most of these tools have significant limitations.

Common issues include:

Limited app compatibility
No App Store support
Missing hardware features
Poor performance
Outdated software

Many so-called "iOS emulators" are actually simulators or interface wrappers rather than full iOS environments.

For most users, cloud-based solutions are a more practical choice.

Choosing the Right iOS Solution for Windows

The best option depends on what you want to do.

For iOS Development

Developers usually need:

Xcode
iOS Simulator
Real device testing

A remote Mac is the most practical choice because Apple's official tools only run on macOS.

For App Testing

Cloud testing platforms like BrowserStack, Sauce Labs, Kobiton, and HeadSpin are useful for checking:

Different iPhone models
iOS versions
App performance
Compatibility issues

For Using iOS Apps on Windows

If you want a real iPhone experience from Windows, a cloud iPhone solution is usually more practical than traditional emulators.

It provides access to a remote iOS environment without needing multiple physical devices.

For Security Research

Advanced platforms like Corellium are designed for iOS research and system-level testing rather than everyday app usage.

Setting Up an iOS Cloud Device

Most cloud iPhone services follow a simple process:

Create an account and choose a device.
Connect to the cloud iPhone from your Windows PC.
Configure network settings if needed.
Install apps and start using the iOS environment.

The exact steps vary by platform, but the overall workflow is similar.

Common Questions About iOS Emulators for Windows

Can I install Apple's iOS Simulator on Windows?

No. The official iOS Simulator is included with Xcode and requires macOS.

Can iOS apps run directly on Windows?

No. iOS apps are built for Apple's ecosystem and cannot normally run as native Windows applications.

Are online iOS emulators real?

Many online tools only provide limited simulations. For a more reliable experience, use cloud testing platforms or real-device solutions.

What is the closest option to an iPhone emulator for Windows?

A real-device cloud solution is usually the closest experience because it runs on actual iPhone hardware remotely.

Final Thoughts

There is no true iOS emulator for Windows that fully replaces an iPhone.

The best choice depends on your needs:

Use a remote Mac for iOS development
Use cloud testing platforms for app testing
Use real-device cloud solutions for accessing iOS apps remotely

Choosing the right approach is more practical than searching for a perfect Windows iOS emulator.

Running a Real iOS Environment in the Cloud – Beyond the Simulator

Emerson Skaggs — Sat, 25 Jul 2026 04:28:45 +0000

If you've ever developed or tested iOS applications, you're probably familiar with the iOS Simulator provided by Xcode. It's fast and convenient – but it's not a real iPhone. The simulator runs on your Mac's x86_64 architecture, emulating iOS APIs at a high level. It lacks many hardware‑dependent features: GPS, accelerometer, cellular radio, Bluetooth, push notifications (in some cases), and unique device identifiers (UDID, serial number, etc.). More importantly, many apps – especially those dealing with advertising, social media, or fraud detection – can detect the simulator environment and behave differently, or even refuse to run.

This is where iOS cloud phones come into play.

What Is an iOS Cloud Phone?

An iOS cloud phone is a remotely accessible instance of a genuine iOS system that runs on real hardware or on a virtualization layer that closely mimics physical hardware. Each instance is assigned its own A‑series chip (or equivalent), authentic device identifiers, and full sensor data – making it nearly indistinguishable from a physical iPhone for both network requests and app sandbox checks.

Unlike simulators, cloud phones allow you to:

Test real‑world push notifications and in‑app purchases.
Run apps that rely on device fingerprints (e.g., TikTok, Instagram, banking apps).
Manage multiple isolated accounts without buying dozens of physical devices.
Automate tasks via remote control and scripting.

How Does It Work Under the Hood?

Most iOS cloud phone services are built on a cluster of physical iPhones (or iPhone‑grade SoCs) connected to a management platform. When you request a new instance, the platform allocates an available physical device or a virtualised partition that boots a full iOS stack. Your computer connects to it over the internet via a secure tunnel, and you interact with the iOS screen through a browser or a dedicated client.

Key technical elements include:

Hardware‑level emulation – each instance has its own unique MAC address, Wi‑Fi chip, motion coprocessor, and even ambient light sensor readings.
Proxy‑first design – because the device is remote, all network traffic must go through a proxy (typically SOCKS5) that you supply, to ensure proper geolocation and IP reputation.
State persistence – the device retains its data across reboots, unless you explicitly reset it.
Batch management – you can control multiple instances programmatically or through a dashboard.

A Concrete Example: BitCloudPhone iOS

To illustrate the full workflow, let's look at BitCloudPhone iOS – one available implementation. I'll walk through the prerequisites, setup, and common operations, keeping the focus on how such a system actually works in practice.

Prerequisites (Important)

You must have a SOCKS5 proxy. The service does not provide proxies; you are responsible for sourcing and configuring one. The proxy is used for all outbound traffic from the cloud phone.
Proxy must be set before first boot. If you power on the device without a working proxy, it may fail to initialise.
After boot, do not change Apple ID, device name, or system parameters (e.g., in Settings → General) – doing so can break the environment or trigger security locks.
Auto‑renewal is enabled by default on the purchase page – double‑check if you prefer manual renewal.

Getting an Instance

Inside the BitBrowser client (the companion tool for managing these devices):

Go to Phone Profiles and switch to the iOS tab.
Click “Buy Phone” – the default model is iPhone SE; you can adjust duration and quantity.
Complete the payment – the instance appears in your list immediately.

Configuring the SOCKS5 Proxy (Mandatory)

Before you can power on the device, you must enter your proxy details:

In the device list, hover over the instance and select “Proxy IP Settings”.
Fill in the proxy host, port, and authentication (if any).
Click “Check Proxy” to test connectivity – the service will verify that the proxy is reachable.

Save only if the test passes. If the proxy is unreachable, the cloud phone will not boot.

Troubleshooting: If later you see a stuck loading screen, the first thing to check is your proxy configuration – incorrect host, port, or credentials are the most common causes. Avoid repeatedly restarting the device before checking the network.

Launching and Accessing the Device

After a successful proxy test, click “Open” on the device. A separate window appears:

Left side: the iOS screen.
Right side: a toolbar with controls – volume, power, file operations, network info, and a “Transfer to Real Device” button.

First boot triggers an initialisation process; the wait time depends on network latency. Once the iOS desktop loads, open Safari to test web connectivity before installing any apps.

Installing Applications

Inside the cloud phone, you can install apps just like on a physical iPhone:

Tap the App Store icon (bottom‑right corner of the window).
Browse the available app list.
Click “Install” next to the desired app – it downloads and installs automatically.

Transferring Your Session to a Physical iPhone

If you need to continue working on a real device, the platform offers a “Transfer to Mobile” feature:

Click the “Transfer to Mobile” button on the toolbar.
A QR code appears – scan it with your physical phone.
Follow the prompts – the cloud phone session is mirrored to your real device, and you can also upload files from your physical phone to the cloud instance.

Batch and Team Management

For teams or power users, the dashboard supports:

Tagging / grouping – individually or in bulk via “More Actions”.
Transferring ownership – assign devices to other team members, with temporary sharing options.
Bulk renewal – extend multiple instances at once.

When Would You Use an iOS Cloud Phone?

Based on common user feedback, here are typical scenarios:

Social media account management – isolate TikTok, Instagram, Facebook, or X accounts on separate devices to avoid cross‑account flags.
Mobile app testing – validate login flows, push notifications, and real‑device behaviour that simulators cannot replicate.
Ad verification and affiliate marketing – access mobile‑only tools and check landing pages from various IPs.
E‑commerce operations – manage TikTok Shop, Shopify seller dashboards, and customer messages from dedicated iOS environments.
Temporary iOS access – spin up an iPhone for a short project without buying physical hardware.

Documentation and Further Reading

If you're interested in trying this specific implementation, the official resources are:

User Guide: https://doc.bitbrowser.net/cloud-phone/bitcloudphone-ios
Basic Features: https://doc.bitbrowser.net/cloud-phone/bitcloudphone-ios/basic-features

Final Thoughts

iOS cloud phones offer a practical bridge between the convenience of simulators and the accuracy of physical devices. They are not a replacement for all testing needs – but for scenarios where device identity, sensor data, and network fingerprinting matter, they are a valuable tool.

Android Emulators Explained: How They Work, Their Limitations, and When to Use Cloud Phones

Emerson Skaggs — Fri, 24 Jul 2026 04:21:31 +0000

Android emulators have become an essential part of modern Android development. They allow developers to test applications, debug interfaces, and simulate different device configurations without owning dozens of physical phones.

For many development workflows, an emulator is enough.

But when teams move beyond basic testing into large scale automation, long running app operations, mobile testing across many environments, or workflows that depend on real device behavior, emulator limitations become much easier to notice.

This article explains how Android emulators work, where they struggle, and when cloud based Android environments can be a better fit.

How Android Emulators Work

An Android emulator is a software layer that recreates an Android environment on another operating system.

At the core, most Android emulators rely on virtualization technology and hardware acceleration. The official Android Emulator from Google, for example, uses QEMU (Quick Emulator) to simulate Android hardware components and run Android system images.

Instead of interacting with a physical phone, the Android operating system runs inside a virtual environment that provides simulated hardware, storage, networking, and sensors.

The Technical Components Behind Android Emulation

1. CPU Architecture Translation

One of the biggest challenges in Android emulation is the difference between mobile and desktop hardware architectures.

Most Android devices use ARM based processors, while many developer computers use x86_64 CPUs.

Because of this difference, an emulator may need to translate instructions between architectures.

Modern solutions improve performance through:

Binary translation
Instruction caching
Hardware accelerated virtualization
Native x86 Android system images when supported

Without these optimizations, running a mobile operating system on desktop hardware would be significantly slower.

2. Hardware Acceleration

Pure software emulation requires a lot of computing power. To improve performance, Android emulators use virtualization extensions provided by modern CPUs.

Examples include:

Intel VT-x
AMD-V
KVM on Linux
Hyper-V on Windows
Hypervisor.framework on macOS

GPU acceleration is also used to improve graphics performance through technologies such as OpenGL and Vulkan.

This allows many Android applications to run smoothly during development and testing.

3. Virtual Device Components

An emulator creates a complete virtual device environment, including:

Virtual storage
RAM allocation
Virtual SD card
Network interfaces
Simulated GPS location
Virtual sensors

Developers can configure different device models, Android versions, screen sizes, and hardware profiles.

However, these components are software simulations rather than physical hardware.

Where Android Emulators Have Limitations

Although emulators are powerful, they cannot perfectly reproduce every aspect of a real Android device.

Missing Hardware Signals

Many physical device features are difficult to simulate accurately:

Bluetooth behavior
NFC communication
Fingerprint sensors
Face unlock hardware
Mobile radio behavior
Carrier specific features

For normal application testing, this may not matter.

However, apps that depend on hardware authentication, sensors, or mobile network behavior may produce different results on an emulator.

Network Behavior Is Different

A virtual Android device does not experience the same network conditions as a real phone.

For example:

Mobile network switching cannot be perfectly reproduced
Signal changes are simulated
Carrier restrictions are difficult to test
Real world latency patterns may differ

Applications that rely heavily on network conditions may need additional testing on physical devices.

Scaling Multiple Emulator Instances

Running one emulator is usually easy.

Running dozens is a different challenge.

Each instance requires:

CPU resources
Memory allocation
Storage space
GPU resources

As the number of instances increases, performance can quickly become a bottleneck.

This is why large scale mobile testing often moves from local machines to cloud infrastructure.

Session Persistence Challenges

Local emulators are usually tied to the host computer.

If the host system restarts or crashes, active sessions can be interrupted.

Snapshots can help, but they do not always provide the same persistence as a continuously running device environment.

For workflows that require long running sessions, this becomes an important consideration.

How Applications Detect Emulator Environments (Condensed)

Certain apps can tell if they’re running on virtual devices via three checks:

Device Info Verification

They pull Android properties like model, brand and build fingerprint. Abnormal parameter combinations signal emulators.

Hardware Validation

Sensors, cameras, Bluetooth and SIM cards are scanned. Missing or simulated hardware proves it’s not a physical phone.

System Behavior Analysis

Judged by performance, file structure, network traits and preinstalled system parts.

Not all apps block emulators, which explains why realistic physical devices are needed for some operations.

Android Emulator vs Cloud Emulator vs Cloud Phone

When local emulators become limiting, cloud based solutions provide another option.

However, not all cloud Android solutions work the same way.

The biggest difference is hardware authenticity.

A cloud emulator is still an emulator running in the cloud.

A cloud phone focuses on providing a more realistic mobile environment with persistent sessions and device level resources.

When Should You Use Each Option?

Local Emulator

Best for:

UI testing
App debugging
Android version testing
Early development

Local emulators are affordable and integrate easily with tools like Android Studio.

Cloud Emulator

Best for:

Automated testing
Testing multiple Android versions
Remote development teams
Large scale test execution

Cloud emulators help teams scale testing without maintaining their own infrastructure.

Cloud Phone

Best for workflows that require persistent Android environments or more realistic device behavior, such as:

Long running mobile tasks
Device specific testing
Remote Android access
Isolated mobile environments

Unlike emulators, cloud phones focus on providing persistent Android instances that stay accessible remotely.

For example, BitCloudPhone provides cloud based Android environments with persistent sessions and remote management, making it useful for teams that need separate Android environments without relying on local devices.

Choosing the Right Android Environment

There is no single solution that fits every situation.

Android emulators remain one of the most important tools for developers because they are fast, flexible, and easy to integrate into development workflows.

Cloud emulators extend this idea by making testing infrastructure easier to scale.

Cloud phones fill a different role by focusing on persistent Android environments and more realistic device conditions.

The right choice depends on what matters most:

Development speed → Emulator
Automated testing at scale → Cloud emulator
Persistent mobile environments → Cloud phone

Understanding these differences helps developers choose the right tool instead of forcing one solution to handle every workflow.

Netflix Error NW‑2‑5: What It Means and How to Fix It (Step‑by‑Step)

Emerson Skaggs — Wed, 22 Jul 2026 08:28:44 +0000

If you see error code NW‑2‑5 on Netflix, don’t panic – it’s almost always a temporary network connectivity issue, not a problem with your account or hardware. In most cases, you can resolve it yourself by following the steps below.

What Does This Error Mean?

NW‑2‑5 indicates that your device can connect to the internet, but cannot establish a stable communication with Netflix servers. Common causes include:

Weak Wi‑Fi signal or broadband fluctuations
DNS resolution problems
Outdated router/modem cache or firmware
Active VPN, proxy, or Smart DNS services (Netflix actively blocks these)
Public Wi‑Fi (hotels, cafés, offices) with access restrictions or uncompleted captive portal logins

Fix Steps (Recommended Order)

Part 1: Basic Restarts (Solves ~60% of Cases)

Close the Netflix app and power off your device (TV, set‑top box, console, phone, etc.) completely.
Wait 30 seconds, then turn it back on.
Restart your router and modem: unplug the power cord, wait 60 seconds, plug them back in, and wait until all indicator lights return to normal.

Part 2: Check Your Network Environment

Turn off VPN / proxy / Smart DNS. If you use any third‑party network acceleration tools, disable or uninstall them temporarily.
Try a wired connection – if possible, connect your device directly to the router via an Ethernet cable to rule out Wi‑Fi interference.
Complete public Wi‑Fi authentication – if you are in a hotel, café, or office, open a browser on your device and visit any website (e.g., 1.1.1.1) to ensure the login/terms page appears and you accept it.

Part 3: Adjust DNS Settings (Core Fix)

Go to your device’s network settings, change DNS to Manual, and enter one of the following public DNS pairs (choose either):

Google: 8.8.8.8 and 8.8.4.4
Cloudflare: 1.1.1.1 and 1.0.0.1

If you are unsure how to set manual DNS, try switching to “Automatic” first, then restart the device and retry.

Part 4: Update Software and Account Refresh

Update your system firmware and the Netflix app – check the app store for any pending updates; outdated clients can cause handshake failures.

Sign out and sign back in to Netflix – this refreshes your authentication token and session connection.

Part 5: Advanced Router Checks

Temporarily disable router firewall / parental controls – Netflix requires TCP ports 80 and 443 to be open. If they are blocked, whitelist them or temporarily turn off those security features.

Reset network settings – on your device, look for “Reset Network” under system settings (note: this will erase saved Wi‑Fi passwords). After resetting, reconnect to your network.

If None of the Above Works – Contact Support in This Order

Test Netflix on another device connected to the same network:

If that device also fails → contact your Internet Service Provider (ISP) and report network restrictions or routing issues.
If only your original device fails → contact Netflix Support directly, mention error NW‑2‑5, and they will provide device‑specific troubleshooting.

Additional Step for Anti-Detect Browser Users

If you are using an anti-detect browser (e.g., BitBrowser, Multilogin, GoLogin, Incogniton) and encounter NW‑2‑5, the issue is almost always related to the proxy configuration inside your browser profile, rather than your local home network. Follow these specific checks:

Check your proxy IP type

Netflix actively blocks datacenter IPs and low‑trust VPN exits. If your proxy is a datacenter IP (common with cheap static proxies), switch to a clean residential ISP proxy or a mobile 4G/5G proxy with a high trust score.

Verify DNS leak within the profile

In your anti-detect browser profile settings, ensure that DNS resolution is set to use the proxy's DNS (not your local ISP's DNS). If your local DNS leaks out while the proxy IP shows a different country, Netflix's geo‑detection will flag the mismatch and trigger NW‑2‑5.

Match timezone, language, and IP location

Netflix cross‑checks your system timezone and browser language against your proxy's geolocation. Make sure your profile's timezone and language settings align with the proxy IP's country – a mismatch can cause the handshake to fail even if the IP itself is clean.

Test the proxy outside the anti‑detect browser

To isolate the issue, take the same proxy IP and test it in a regular (non‑anti‑detect) browser by visiting netflix.com. If NW‑2‑5 appears there too, the proxy itself is blacklisted – replace it. If it works in a regular browser but fails inside the anti‑detect profile, the issue is with your profile's fingerprint or DNS settings.

ISP Proxies vs Residential Proxies: Which One Should You Use for Multi Account Management

Emerson Skaggs — Mon, 20 Jul 2026 03:57:38 +0000

If you are doing multi account management for ecom, affiliate, social media, ad accounts, sneaker stuff, marketplaces, whatever… choosing the right proxy type is one of those decisions that can either make your setup feel stable or feel like walking on thin ice.

So let’s talk about the two that get compared the most for this use case: ISP proxies and residential proxies. What they actually are, how they behave, what they cost you in money and headache. And which one you should use for multi account management depending on what you are doing.

What Are ISP Proxies?

ISP proxies (sometimes called static residential proxies, or ISP residential proxies depending on the provider) are IPs that are hosted on servers in data centers, but they are issued by real Internet Service Providers. That’s the key point.

So instead of looking like a typical datacenter IP block that screams “proxy”, they often look like a normal consumer ISP connection from Comcast, AT&T, Vodafone, etc. But performance wise, they behave more like datacenter proxies because they are sitting on infrastructure that is fast, stable, and always on.

A few practical traits you’ll notice with ISP proxies:

· Usually static: you keep the same IP for a long time (days, weeks, months) unless you rotate it yourself.

· Fast and low latency: great for tasks that involve lots of page loads, lots of tabs, heavy web apps.

· More stable sessions: because the IP does not randomly change mid session.

· More expensive per IP: you are paying for “clean” IP reputation and stability.

People like them because they can be the sweet spot. Less suspicious than pure datacenter IPs, but way easier to work with than rotating residential pools.

What Are Residential Proxies?

Residential proxies are IP addresses that come from real devices on real home networks. In most cases, those IPs are part of a large pool, and you access them through a gateway that assigns you an IP from that pool.

They can be:

· Rotating residential proxies (most common): IP changes on a timer or per request.

· Sticky sessions: you hold the same residential IP for a set duration (like 10 minutes, 30 minutes, 1 hour), then it changes. This type of proxy is discussed in detail here.

The big benefit is obvious. To platforms, these IPs look like normal users browsing from home, because they literally are.

But there are tradeoffs people don’t love talking about until it breaks something:

· Not always stable: IP can drop, slow down, or get reassigned.

· Speed varies a lot: because the underlying connection is a real residential line, not data center fiber.

**· Billing is usually by bandwidth: **you pay per GB, not per IP.

**· Location targeting is better: **you can often target city, region, ISP, sometimes ASN.

Residential proxies are typically what people reach for when they need maximum “normal user” vibes. Especially if a platform is aggressive about detecting proxies.

Which Proxy Is Better for Managing Multiple Accounts?

If you force me to give a clean answer, it’s this:

· For long term multi account management where you log into the same accounts repeatedly, ISP proxies are often the better default.

· For account creation, warming, and high risk platforms, residential proxies can be safer, especially when the platform is strict about proxy detection.

But the best proxy is the one that matches your workflow.

Ask yourself:

Am I logging into the same set of accounts every day?

2. Do I need each account to have a consistent “home” IP?

3. Is the platform paranoid about datacenter patterns?

4. Am I doing actions that spike security checks? Like adding payment methods, running ads, changing profile details, mass messaging?

If you are managing social profiles, seller accounts, ad accounts, and you want them to stay stable for months, static ISP proxies mapped 1:1 to browser profiles is a very common winning setup.

If you are doing lots of new account creation or you need very specific local IPs to match signup info, residential tends to play nicer.

When to Use ISP vs Residential Proxies for Multi Account Management?

ISP proxies are best for long term account management where stability matters.

They provide static IPs, faster performance, and consistent account environments. They work well for seller accounts, social accounts, ad accounts, and any profile that needs regular logins. A 1:1 setup with one proxy per browser profile helps reduce account connections and makes management easier.

Residential proxies are better when authenticity and location flexibility are the priority.

They are useful for account creation, account warming, strict platforms, and campaigns requiring specific locations. With sticky sessions, residential proxies can also support ongoing account management while keeping each profile on a consistent IP.

Can You Combine ISP Proxies and Residential Proxies?

Yes. This is what a lot of people end up doing once they stop trying to find one perfect proxy type.

A practical combined setup looks like this:

· Residential proxies for account creation and early warming.

· Move stable accounts to ISP proxies for long term management.

· Keep a small residential pool for recovery scenarios — including suspicious login loops, travel style location changes, testing new regions, and emergency rotation when an ISP IP gets flagged.

You can also segment by risk level:

· High value accounts (ad accounts, payment linked accounts) on dedicated ISP proxies.

· Lower value accounts or short lifespan accounts on residential rotation.

The main thing is to keep your mapping clean. Do not randomly swap proxies between accounts. That's when you get the classic problem where one flagged account poisons the rest.

How Anti Detect Browsers Help Manage Multiple Accounts with Proxies?

Proxies are only one part of managing multiple accounts.

A stable workflow also requires separate browser environments for different accounts, projects, or clients. This is where anti detect browsers can help.

For example, tools like BitBrowser allow users to create independent browser profiles with separate settings and environments.

Separate browser profiles

Instead of managing everything in one browser, you can create multiple isolated profiles.

Each profile can have its own cookies, storage, user agent, device settings, timezone, language, screen resolution, fonts, and other browser parameters.

This makes it easier to keep different projects organized.

Proxy binding per profile

Anti detect browsers can also connect different proxies to different profiles.

Example:

· Profile A → ISP proxy A → Account A

· Profile B → ISP proxy B → Account B

· Profile C → Sticky residential session → Account C

Keeping a consistent profile and proxy setup makes daily account management more structured.

Team management and automation

For teams managing multiple profiles, useful features include:

· profile grouping

· tags by platform, region, or project

· access management

Some users also combine anti detect browsers with automation tools for repetitive tasks.

A well organized setup can make workflows easier to maintain, but the tool is only one part of the process. Good planning and responsible usage are still important.

Conclusion

ISP proxies and residential proxies both work for multi account management, but they solve slightly different problems.

· If you want speed, stability, and long term consistency, ISP proxies are usually the better choice. Especially when you map one proxy to one BitBrowser profile and keep it clean.

· If you want maximum authenticity, flexible geos, and safer account creation flows, residential proxies are often the better fit. Just be careful with rotation and session consistency.

And if you’re doing this seriously, you probably end up combining them anyway. Residential to get accounts off the ground, ISP to keep them stable once they matter.

The proxy is not the whole story, but it’s a big part of it. Pair it with proper profile isolation in a tool like BitBrowser, keep your account behavior realistic, and things get a lot calmer. Not perfect. Just calmer.

What Is a VPN Kill Switch and Why Does It Matter

Emerson Skaggs — Thu, 09 Jul 2026 03:17:51 +0000

A VPN is supposed to keep your internet activity private.

But VPN connections can drop without warning. When that happens, your real IP address and online activity may be exposed before you even notice the disconnect.

That is where a VPN kill switch comes in.

In 2026, it is one of the most important VPN features you can enable. Whether you work remotely, travel often, use public WiFi, torrent, or manage multiple accounts, a kill switch helps keep your privacy intact when your VPN connection fails.

What is a VPN kill switch?

A VPN kill switch is a security feature that blocks your internet connection if your VPN disconnects.

When the VPN tunnel is active, your traffic goes through the VPN server. When the tunnel drops unexpectedly, the kill switch steps in and prevents your device or specific apps from sending traffic outside the VPN.

So instead of your laptop quietly switching back to your normal connection and exposing your real IP, everything stops until the VPN is back.

If you care about online privacy, this matters more than most VPN marketing features.

Why does a VPN kill switch matter more in 2026?

The internet in 2026 is faster, noisier, and honestly more aggressive.

Not just in ads. In tracking, fingerprinting, account security systems, and network restrictions. Even normal browsing can involve dozens of silent connections in the background. Apps update themselves. Browsers preload pages. Cloud services sync constantly.

So if your VPN drops for a few seconds, it is not just one website request that leaks. It can be a bunch of background traffic too.

1. Remote work is normal, and networks are messy

People work from everywhere now. Hotels, coworking spaces, trains, mobile hotspots. Those networks are not stable. A stable VPN connection is not guaranteed, even with a good provider. A VPN kill switch helps keep your real IP hidden when the network changes or hiccups.

2. Public WiFi is still a problem

Public WiFi is convenient, but it is also unpredictable. Captive portals, weak signals, random disconnects. If your VPN drops on public WiFi and you do not have a kill switch, you are exposed right when you are most vulnerable.

3. Websites flag unusual IP changes

Websites flag odd IP shifts for fraud checks. If your VPN cuts out and flips between your real and masked IP, you’ll get account locks, verifications, login alerts and payment troubles. A VPN kill switch blocks all traffic mid-disconnect to avoid this.

4. Privacy expectations are higher

More people understand what IP addresses, trackers, and location data mean now. And more people want control. Using a VPN without a kill switch is like locking your front door but leaving it open whenever the wind blows.

How does a VPN kill switch work?

Most VPN kill switches work using firewall rules or network routing rules.

When the VPN is connected, your device is allowed to send traffic only through the VPN interface. If the VPN interface disappears, the rule stays in place, so your traffic cannot go out normally.

Different operating systems do it differently, but the goal is always the same.

Block traffic until the secure tunnel is back.

This is why a real kill switch is better than a simple reconnect button. Reconnecting is helpful, but it still allows leaks during the gap.

Types of VPN kill switch features you will see

Not every VPN kill switch works the same way, and some offer weaker protection than they appear.

1. System wide kill switch

This blocks all internet traffic on your device if the VPN disconnects. It is the safest option, especially if you do not want to worry about potential leaking apps. It works best for privacy focused users, remote work, public WiFi use and torrenting.

2. App level kill switch

This only blocks chosen apps when the VPN drops. You can restrict torrent clients or browsers while letting messaging apps remain online. It fits people who need partial active connections for streaming, browsing and multitasking workflows.

3. Always on VPN plus kill switch

Most mobile devices and some desktops support always on VPN, which makes VPN the default network connection. When paired with a kill switch, this setup delivers solid protection. It can cause inconvenience when accessing local devices or printers on trusted networks. It is ideal for mobile travel and simple set and forget privacy configurations.

Who needs a VPN kill switch the most?

A lot of people do. But if you are in any of these groups, the kill switch should be non negotiable.

1. People using public WiFi often

Airports, cafes, hotels. If you connect to networks like that weekly, you want a VPN kill switch turned on.

2. Remote workers and freelancers

Client work can involve logins, admin panels, file transfers, and private communications. A VPN kill switch reduces the risk of accidental exposure.

3. Torrent users

If your VPN disconnects while torrenting, your real IP can be visible to others in the swarm. If you torrent at all, use a VPN kill switch.

4. Travelers

Network changes are a common cause of VPN drops. Switching from hotel WiFi to mobile data, or moving between routers, can interrupt the tunnel.

5. People managing multiple accounts

If you manage social accounts, ecommerce accounts, ad accounts, or client profiles, IP consistency can matter. A kill switch helps avoid sudden IP flips mid session.

For even cleaner separation, many pair a VPN with an active kill switch and BitBrowser, which creates isolated browsing environments so each account stays in its own protected space.

How to tell if a VPN kill switch is actually working

You do not need to be a technical person to test this. Here is a simple way.

Turn on your VPN and confirm you have internet

2. Turn on the kill switch in your VPN settings

3. While the VPN is connected, disconnect the VPN manually or force close the VPN app

4. Try opening a website

If the kill switch works, the site should not load. Then reopen the VPN and reconnect. Your internet should resume.

A few notes though:

· Some VPNs only block traffic if the connection drops unexpectedly, not if you manually disconnect. That is not ideal, but it happens.

· If your VPN has both system wide and app level kill switch options, test both.

If you want to be extra sure, search for "what is my IP" while connected, then repeat the test during the disconnect. You should not see your real IP appear at any point. Ideally you should see no connection at all.

What to look for in a VPN kill switch in 2026

If you are choosing a VPN or reviewing your current one, here is what matters.

A real system wide kill switch

This is the baseline. App only kill switches are useful, but system wide protection is stronger for most people.

Clear behavior and clear settings

You should be able to understand what is blocked, when it is blocked, and how to recover if something goes wrong. If the setting is buried or vague, that is a red flag.

DNS leak protection plus kill switch

Both matter. DNS leak protection is not the same as a kill switch, but together they cover more scenarios.

Reliable reconnect logic

A VPN that reconnects quickly helps, but again, the kill switch is what prevents leaks during the gap. You want both.