A static IP is an address that stays the same every time your device or network connects to the internet. A dynamic IP is one your internet provider lends you and can swap for a different one later.
Most home connections run on dynamic IPs, and for browsing, streaming, and gaming that's perfectly fine. You only need a static IP when something on the internet has to find you at the same address every time: a server you host, a camera you check from work, or a company system that only lets in approved addresses.
A static IP address is an IP address that doesn't change. Every device on the internet needs an IP address so data knows where to go, the same way a parcel needs a street address. With a static one, that address is fixed. It's either set by hand or permanently reserved, and it stays yours until someone deliberately changes it.
IP addresses come in two formats. IPv4 is the familiar one: four numbers from 0 to 255 separated by dots, like 203.0.113.42. There are only about 4.3 billion possible IPv4 addresses, which sounds like plenty until you count every phone, laptop, and smart TV on the planet. IPv6 is the newer format, written as groups of hexadecimal digits like 2001:db8:85a3::8a2e:370:7334, and it has so many addresses that running out isn't a realistic concern. Either format can be static or dynamic.
Most of the confusion around static IPs comes from this, so it's worth sorting out first. You actually have two kinds of IP address at home.
Your public IP belongs to your whole network. Your internet service provider (ISP) assigns it to your router, and it's what websites see when you visit them. Your private IP is the one your router gives each device inside your home, usually starting with 192.168, 10., or somewhere from 172.16 to 172.31. Those private ranges are reused in millions of homes and never appear on the internet directly.
Both kinds can be static or dynamic, and they're controlled in completely different places. Giving your printer a fixed address in your router's settings makes its private IP static. It does nothing to your public IP, which only your ISP controls. So when people ask what a static IP is in the context of hosting or remote access, they almost always mean a static public IP, and that's the kind you have to request (and usually pay for).
A dynamic IP address is assigned automatically, for a limited time, by a system called DHCP (Dynamic Host Configuration Protocol). The DHCP standard describes it as handing a device an address "for a limited period of time." That period is called a lease.
Here's what happens in practice. When your router connects, it asks your ISP's DHCP server for an address. The server lends it one from a pool, on a lease that commonly runs anywhere from a few hours to a week. Before the lease runs out, your router quietly asks to renew it, and the server usually agrees and hands back the same address.
That's why a "dynamic" IP can stay put for weeks or even months. It typically changes when:
your router is off long enough for the lease to expire, during a power outage or a move
you replace the router or modem, since the ISP sees a new device asking
your ISP reshuffles its address pools during network maintenance
Your phone is a different story. Mobile carriers, and a growing number of home ISPs, use carrier-grade NAT (CGNAT). One public IP gets shared by dozens or hundreds of customers at once, and the carrier keeps track of whose traffic is whose. Behind CGNAT you don't really have a public IP of your own at all, static or dynamic.
Because IPv4 addresses ran out. A static IP ties up one address for one customer around the clock, even while that customer is asleep. Dynamic assignment lets an ISP recycle addresses across customers who come and go, which matters a lot when the supply is fixed.
And the supply is gone. ARIN, the registry that hands out IP addresses in North America, issued the last addresses in its free IPv4 pool on September 24, 2015. Since then, ISPs mostly get more IPv4 addresses by buying them from other organizations on a transfer market. That turns every static address into a real cost, which is why it shows up as its own line on your bill.
IPv6 solves the shortage, and adoption is real but incomplete. Google's measurements put IPv6 at roughly 45 to 50 percent of its users as of April 2026. Until IPv4 fades out, dynamic addresses and CGNAT are how ISPs stretch what they have.
The difference between a static and a dynamic IP comes down to whether the address stays fixed or can change. Almost everything else follows from that.

Static IP | Dynamic IP | |
|---|---|---|
How it's assigned | Set manually or permanently reserved | Leased automatically by DHCP |
Does it change? | No, unless you or your ISP change it | Can change when the lease expires or the router reconnects |
Cost | A paid add-on, billed monthly | Included in your plan |
Setup | Request from your ISP, sometimes configure by hand | Nothing to do |
Hosting and remote access | Simple, the address never moves | Needs a workaround like Dynamic DNS |
Privacy | Ties your activity to one address for years | Address shifts from time to time |
Who it suits | Businesses, self-hosters, remote workers on allowlists | Almost every home and mobile user |
One thing that isn't in the table: speed. A static IP doesn't make your connection any faster (more on that in the FAQ).
A static public IP earns its cost when other people or systems need to reach you, rather than you reaching them. The common cases:
Hosting something. A website, a game server, a file server, or a home lab your friends connect to. With a static IP, you point a domain name at your address once and it stays pointed.
Remote access. Checking security cameras, connecting to your home computer with remote desktop, or reaching a NAS (a network storage drive) while you're traveling.
Allowlists at work. Some company systems only accept connections from approved IP addresses. If your home office needs to be on that list, a changing address locks you out every time it changes.
Running your own mail server. Residential dynamic IP ranges are routinely listed on spam blocklists, so mail sent from them tends to bounce. A static business IP with proper reverse DNS has a fighting chance.
Business phone systems. Some VoIP (internet phone) setups are configured to trust one fixed address.
If none of those sound like you, a static IP is extra money for a feature you'll never notice.
The biggest downside is cost, closely followed by availability. ISPs charge for a static IP as a monthly add-on, and some also make you rent their business gateway to use one. Many residential plans don't offer static IPs at all, so getting one can mean switching to a business plan, which costs more across the board.
Then there's exposure, and this is where the common claim that static IPs are "more secure" needs a caveat. For a business, a fixed address does make security easier to manage, because firewall rules and allowlists stay accurate. For a home user it cuts the other way. If someone learns your static IP (from a game lobby, a server log, an email header), it stays valid for as long as you keep it. That makes you an easier target for a DDoS attack, which floods your connection with junk traffic until it drops, and easier to recognize across websites over months or years. A dynamic IP can sometimes be shaken off with a router restart. A static one is yours for good.
Finally, anything you expose through a static IP is your responsibility to keep patched. An open camera or remote desktop port on a fixed address is exactly what automated scanners look for, so locking down your router and home network matters even more once you have one.
The quickest way to check is your router's admin page. Log in (the address is usually printed on a sticker on the router, often 192.168.0.1 or 192.168.1.1) and find the WAN or Internet status page.
If the connection type says DHCP or Dynamic IP, your public address is dynamic. If it says Static IP with an address filled in, you have a static one.
PPPoE connections, common on DSL and some fiber lines, are usually dynamic unless your ISP told you otherwise.

A few other ways to tell:
Check your bill. If you never asked for a static IP and aren't paying for one, you almost certainly don't have one.
Watch your public IP over time. Look it up on any "what is my IP" site, note it down, restart the router, and check again. If it changed, it's dynamic. If it didn't, that's not proof it's static, since a renewed lease often returns the same address.
Ask your ISP. Support can tell you in a minute.
One mistake to avoid: running ipconfig on Windows or opening Network settings on a Mac shows your private IP, the one your router gave that computer. It tells you nothing about your public IP. And if the WAN address on your router falls anywhere from 100.64 to 100.127, you're behind carrier-grade NAT. That range is reserved for exactly this purpose, and it means your ISP is sharing one public IP between you and other customers.
The route depends on what you need: a fixed public address the outside world can reach, or a fixed address for a device inside your home.
Call your ISP and ask. If your plan supports it, you'll pay a monthly fee and get the address along with the subnet mask, gateway, and DNS details to enter on your router, or the ISP will configure it for you. If your residential plan doesn't support it, ask what the business plans cost. It's worth haggling, because business customers regularly get the static IP fee reduced or bundled in.
If all you need is to reach your home network from outside, you might not need a static IP at all. Dynamic DNS (DDNS) gives you a fixed hostname, something like myhome.ddns.net, and a small client on your router or computer updates it whenever your IP changes. Many routers have a DDNS option built in. It handles remote access, cameras, and small game servers well.
It has two limits. It won't satisfy a mail server or a work allowlist that needs a fixed IP, and it won't work behind CGNAT, because there's no public IP of your own for the hostname to point at.
For devices inside your home, like a printer, a NAS, or a console you're forwarding ports to, the cleanest method is a DHCP reservation on your router:
Log in to your router's admin page.
Open the DHCP or LAN settings. The option is often called Address Reservation or Static Leases.
Pick the device from the list of connected clients, or enter its MAC address (its hardware ID).
Assign the IP you want and save.
The device gets the same address every time, and because the router knows it's taken, nothing else will grab it.
You can also set a static IP on the device itself. On Windows 11, go to Settings > Network & internet, open your Wi-Fi or Ethernet connection, and change IP assignment to Manual. On a Mac, open System Settings > Network, select your connection, click Details, go to TCP/IP, and set Configure IPv4 to Manually. Either way, you'll enter the address, subnet mask, and router address yourself.
The catch with manual setup: choose an address inside your router's DHCP pool, and sooner or later the router hands the same address to another device. Then both of them start dropping off the network. A reservation avoids that, so only go manual if you know your router's DHCP range and pick an address outside it.
A VPN changes the public IP that websites see, whatever kind of IP you have underneath. When you connect, your traffic travels through an encrypted tunnel to a VPN server, and sites see that server's address instead of yours.
That matters more with a static IP than a dynamic one. A static address works like a long-term ID for your home: every site you visit and every service you log in to sees the same number, year after year. A VPN breaks that link. Browsec's servers in 46+ countries give you a shared address that many people use at once, so your browsing doesn't trace back to one fixed IP. The browser extension for Chrome, Firefox, Edge, and Opera covers traffic in that browser, and the desktop app for Windows, macOS, and Linux, included with Premium, covers everything on the computer, games and other apps too.
What a regular VPN won't do is give you a static IP to host from. The shared address belongs to the server, not to you, and it can differ each time you connect. If people need to reach your server or camera from outside, get a static IP from your ISP or set up Dynamic DNS. For everything else, a VPN gets you the privacy without paying for a fixed address. It's one of the practical reasons to use a VPN, along with a few limits worth knowing. A proxy also swaps your visible IP, but proxies work differently from VPNs and usually leave your traffic unencrypted.
No. Speed comes from your plan, your line, and your home network, not from whether your address is fixed. A static IP can feel more dependable for hosted services because nothing breaks when the address changes, but your download speed and ping stay the same.
For a business with firewalls and allowlists, it's easier to secure. For a home user, it's generally the less private option, since the address stays linked to you indefinitely and can't be shaken off once it leaks. Either way, what actually protects you is an updated router, closed ports you don't use, and not exposing devices to the internet without a reason.
Rarely, but it happens. ISPs sometimes renumber customers during network upgrades, or when you move or change plans. They should warn you first. Keep your static IP details somewhere handy so you can update your router and any DNS records if it does change.
Not a regular VPN. You get a shared server address that can change between sessions. Some VPN providers sell a dedicated IP as a paid add-on, a fixed address used only by you. That's handy for work allowlists, but you give up the anonymity of blending in with everyone else on the server.
It won't lower your ping. Where it can help is hosting a game server, or fixing a strict NAT warning on a console. Strict NAT often comes from being behind CGNAT, and the real fix there is getting a public IP of your own, static or not. Some ISPs will move you off CGNAT for free if you ask.
Browsec. "Static IP vs Dynamic IP: What's the Difference?." Browsec Blog, 2026년 09월 11일, https://browsec.com/ko/blog/static-ip.