On a shared IP, you and many other customers of the VPN service leave the server with the same address.
On a dedicated IP, the address is assigned to you alone. Shared is the default and the better choice for privacy, because your activity is mixed with everyone else's. Dedicated is the better choice when services need to recognize you consistently: banking that dislikes changing addresses, remote access to systems that allow only known IPs, or simply fewer captchas. The trade is anonymity for reputation.
shared dedicated blend into a crowd ✓ ✗ captchas and logins ✗ ✓ allowlists at work ✗ ✓ costs extra ✗ ✓ tied to you alone ✗ ✓
How a shared VPN IP works
A VPN server has one or a few public addresses, and every customer connected to it appears to the internet with those. Hundreds of people, one address. Websites see the address and know from databases that it belongs to a data center and is probably a VPN.
Advantages: your traffic can't be told apart from other users' by address alone; the address changes when you switch servers; nothing about the address is tied to you. Disadvantages: the address may carry a bad reputation from other users, so sites show captchas, block sign-ups, or flag logins; and some services refuse data-center ranges outright.
many customers behind one address ├─ your traffic blends in ├─ so does everyone else's └─ one abuser gets it blocked anonymity by crowd, reliability by luck
How a dedicated VPN IP works
The provider assigns you an address that only your connections use, usually in a location you choose. To the internet it still looks like a data-center address, but its history is your history alone.
Advantages: consistent identity for services that watch for address changes; a clean reputation you control; the ability to add the address to allowlists for remote access, corporate tools or your own server. Disadvantages: everything you do from that address is attributable to one account, so the anonymity of the crowd is gone; and it typically costs extra.
one address, one customer ├─ nothing to blend into ├─ nobody else to get it listed └─ the provider knows it is yours
Both kinds run on the same hardware doing the same forwarding, described in what a VPN server is. The difference is how many people share one address.
Who benefits from a dedicated IP
- Banking and payments. Some banks freeze accounts or demand re-verification when a login comes from a new address every day. A fixed address stops that.
- Remote work and servers. IT departments and cloud consoles often allow access only from listed addresses. A dedicated IP is the only way to use a VPN and stay on the list. The company-VPN side of this is in VPN for remote work.
- Email deliverability. Sending mail from a shared VPN address that others have abused gets messages flagged; a dedicated address doesn't carry their history.
- Fewer captchas. Shared addresses trigger challenges on many sites; a clean dedicated one mostly doesn't.
- Hosting something at home and reaching it through the VPN by a fixed address.
Who should stay on a shared IP
- Anyone whose goal is privacy from websites and the network: the crowd is the protection.
- Everyday browsing, travel, public Wi-Fi. Shared does the job and costs nothing extra.
- Anyone who doesn't have a specific service that needs a fixed address.
remote access to a work network a service that blocks shared ranges running a server behind it banking that flags new addresses
The dedicated IP privacy trade-off
With a dedicated IP, a website that sees the address twice knows it is the same customer, even without cookies. Combined with a browser fingerprint, that is a persistent identifier; how fingerprints work is in browser fingerprinting explained. The provider also knows which account holds which address, so what its policy says about connection data matters more than on shared servers. Read the specifics, as described in what does no logs mean.
A sensible pattern is to use both: the dedicated IP for the two or three services that need it, a shared server for everything else, switching in the app.
dedicated at a provider └─ points at their data center static at home └─ points at your flat they solve different problems
Dedicated IP versus a static home IP
They solve different problems. A static IP from your ISP is fixed but exposes your home connection and location. A dedicated VPN IP is fixed and sits in a data center of your choosing, with the tunnel protecting the path from your device. For remote access to home systems, a dedicated VPN IP is usually safer than opening ports on a home router.
shared harder to single out
more often blocked
dedicated rarely blocked
trivially yours alone
└─ you are choosing which
problem you preferWhich side of the trade-off suits you depends on what keeps breaking.
Help me decide between a shared and a dedicated
IP address.
What keeps going wrong: (sites block me / captchas
constantly / my bank flags the login / a work
system rejects me / nothing, I am just curious).
What I use the tunnel for: (privacy / access /
both).
Would I run any service behind it: (yes / no).
Say which option fits and state the privacy cost
of a dedicated address plainly.
If neither would fix what is going wrong, say so
and name the actual cause.Questions to ask before getting a dedicated IP
- Is the dedicated IP truly single-user, or a small pool?
- Which locations are available?
- Does it work with all protocols in the app, or only some?
- Can it be combined with shared servers in the same subscription?
- What connection data is kept for dedicated addresses?
404 VPN runs on shared servers only and has no dedicated IP option. It offers VLESS in its Android and macOS apps, WireGuard configs for Istanbul and Marseille from the dashboard, DNS inside the tunnel, and a kill switch in the Android app. Plans are on the home page; what is stored is in the privacy policy.
