by William Sanders
Last winter, a home office setup hit an unexpected wall. A network-attached printer had worked perfectly for months — until a brief power outage forced the router to reboot. The printer reappeared on the network with a new address, and every saved connection path stopped working. That frustrating scenario happens more often than most people expect. Learning how to set up a static IP address on Windows eliminates the problem at its source. A static IP (a fixed network address that does not change on its own) keeps every device reliably reachable after reboots, outages, or router restarts. For more practical networking and Windows guides, visit the tech tips section on PalmGear.
By default, Windows uses DHCP (Dynamic Host Configuration Protocol) to receive an IP address automatically from your router each time the device connects. DHCP is convenient for most situations, but it means your device's address may change after a reboot or reconnection. A static IP removes that unpredictability entirely. Your device always appears at the same address on the network.
This guide covers two reliable methods for assigning a static IP: directly through Windows network settings, and through your router's DHCP reservation feature. Both methods work well. The right choice depends on your setup and how many devices you need to manage. You will also find a cost breakdown, a myth-busting section, and long-term maintenance advice.
Contents
No special hardware or software is required to assign a static IP on Windows. Everything you need is already built into the operating system and your router. The most important preparation step is collecting accurate network values before you start. Entering even one incorrect number will break your internet connection until you fix it.
Before opening any settings panel, gather the following four values from your current active connection:
The fastest way to retrieve all of these at once is through the Command Prompt. Press Win + R, type cmd, and press Enter. Then type ipconfig /all and press Enter. The output lists every value listed above for each network adapter on your machine. Write them down before proceeding.
According to Wikipedia's overview of IP addressing, every device on a TCP/IP network must have a unique address within its local subnet. Choosing an address that is already in use by another device on your network will cause a conflict — both devices lose connectivity until the issue is resolved.
You do not need to install anything. Windows provides every tool required for this task:
ipconfig /all to look up current network valuesTwo methods accomplish the same goal. Method 1 configures the static IP directly on the Windows machine. Method 2 assigns the reservation at the router level while keeping the PC set to automatic. Each approach has advantages, and neither requires advanced technical knowledge.
This method works on Windows 10 and Windows 11. The steps are nearly identical on both versions.
After saving, open a browser and load any website to confirm the connection is working. If the page does not load, return to the settings panel and verify each entry. A single digit out of place — especially in the gateway or DNS field — will prevent the connection from working. Correct the value and save again.
Pro tip: Choose a static IP address that falls outside your router's DHCP range to prevent address conflicts. Most routers assign dynamic addresses starting at .100 or higher — so an address like 192.168.1.20 is typically a safe choice.
This method keeps Windows set to automatic (DHCP) but instructs the router to always assign the same address to your specific device. The router recognizes the device by its MAC address (a unique hardware identifier built into every network adapter). This approach is preferred in multi-device setups because all reservations are managed in one place.
To find your device's MAC address, run ipconfig /all in Command Prompt and look for the line labeled Physical Address under your active network adapter. It appears as a series of pairs of characters separated by hyphens (e.g., A1-B2-C3-D4-E5-F6). If this is your first time logging into your router's admin panel, the guide on how to set up a home router for the first time walks through the login and navigation process in detail.
Assigning a static IP on your local network costs nothing. It is a configuration change, not a service. However, there are two distinct types of static IP addresses, and the distinction matters when budgeting for your network setup.
| IP Type | Scope | Typical Cost | Best Use Case |
|---|---|---|---|
| Local static IP (LAN) | Visible only inside your home or office network | Free | Printers, NAS drives, smart home hubs, gaming consoles |
| Public static IP (WAN) | Visible from anywhere on the internet | $5–$25/month (varies by ISP) | Hosting a server, remote desktop access from outside the network |
| DHCP reservation | Inside your home or office network | Free | Any device requiring a consistent local address |
For the vast majority of home and small office users, a local static IP is all that is needed. This guide focuses entirely on local network configuration. No ISP fees apply, and no subscription is required.
If you do need a public static IP — for example, to run a web server or access your home computer remotely — contact your ISP directly. Some providers include a public static IP as part of a business plan. Others charge a modest monthly add-on fee. For remote access without paying for a static public IP, a DDNS (Dynamic DNS) service is a commonly used free alternative that maps a fixed domain name to your changing public IP address.
Several persistent myths cause people to avoid static IPs unnecessarily or to misuse them. Examining the most common misconceptions leads to better decisions about your network setup.
Myth 1: A static IP makes your network less secure.
A fixed local IP address does not inherently reduce security. Network security depends on your firewall rules, router password strength, encryption settings, and general access controls — not on whether your local address changes. A device on a dynamic IP with a weak router password is more vulnerable than a device with a static IP behind a properly secured router.
Myth 2: Static IPs are only necessary for businesses or servers.
Home users benefit from static IPs in many common scenarios. Setting up a network printer for multiple computers becomes far more reliable when the printer holds a fixed address. The same applies to home media servers, smart home hubs, and local network-attached storage devices.
Myth 3: The process requires advanced technical knowledge.
Both methods covered in this guide require only the ability to navigate settings menus and enter numbers. No command-line expertise, no coding, and no special hardware are involved. If you can set up a Wi-Fi connection, you can assign a static IP.
Myth 4: A static IP slows down your internet connection.
Your IP address has no effect on internet speed. Bandwidth is determined by your ISP plan, router hardware, and network congestion — not by whether your local address is static or dynamic. This myth is entirely unfounded.
Assigning a static IP is a one-time task. But networks evolve — new devices are added, routers are replaced, and configurations drift. A few simple maintenance habits prevent small oversights from becoming larger problems.
An IP address conflict occurs when two devices share the same address on the same network. Both devices lose connectivity until the conflict is resolved. Conflicts can develop when a new device joins the network and the router's DHCP pool overlaps with a manually assigned static address.
If you ever perform a factory reset on your router, all DHCP reservations are erased. You will need to recreate them from scratch. The guide on how to reset a router to factory settings explains exactly what is cleared during that process and what steps to take afterward to restore your configuration.
Replacing your router with a new model introduces a similar risk. If the new router uses a different IP subnet — for instance, 10.0.0.x instead of 192.168.1.x — every static IP assignment on your Windows machines will need to be updated to match the new address range before network connectivity is restored.
When you configure a static IP manually through Windows settings, your DNS server addresses are also fixed at the values you entered. If you later want to switch to a faster or more privacy-focused DNS service, you must update those entries manually. The operating system will not refresh them automatically the way DHCP does. The guide on how to change your DNS server for faster internet explains your options and provides step-by-step instructions for making that change on Windows.
A static IP assignment is most effective when it fits into a broader plan for your network. Assigning addresses arbitrarily across multiple devices leads to conflicts, confusion, and wasted troubleshooting time as your setup grows. A minimal amount of planning upfront pays dividends for years.
A simple IP addressing scheme divides your router's address range into zones based on device type. One practical approach for a home or small office network on the 192.168.1.x range:
This structure prevents your static addresses from overlapping with the DHCP pool. It also makes it easier to interpret an IP address at a glance — if you see a connection from 192.168.1.15, you know immediately that it belongs to a shared infrastructure device. Adjust the boundaries to fit the number of devices you actually have.
Undocumented networks become sources of confusion over time. When a static IP is left unrecorded and the device it belongs to is decommissioned, that address sits in limbo — neither in the DHCP pool nor clearly available for reuse. This situation multiplies if multiple people manage devices on the same network.
A simple spreadsheet works well. Record the device name, its MAC address, the assigned IP, the method used (Windows settings or router reservation), and the reason the static IP was assigned. Store it somewhere accessible — shared cloud storage or a note pinned near the router both work. This documentation is especially valuable during troubleshooting, when identifying every device on the network quickly can save considerable time.
New routers, upgraded network adapters, additional computers, and retired devices all warrant a brief review of your IP scheme. An address reserved years ago for a device that no longer exists is harmless in isolation, but a pattern of stale reservations erodes the clarity of your addressing scheme and makes conflicts harder to diagnose. A quick annual review of your router's DHCP reservation list takes under ten minutes and keeps your network organized. This kind of proactive upkeep is the same mindset that prevents issues like those covered in guides such as how to remove bloatware from a new Windows PC — staying ahead of problems rather than reacting to them.
About William Sanders
William Sanders is a former network systems administrator who spent over a decade managing IT infrastructure for a mid-sized logistics company in San Diego before moving into full-time gear writing. His years in IT gave him deep hands-on experience with networking equipment, routers, modems, printers, and scanners — the kind of hardware most reviewers only encounter through spec sheets. He also has a long background in consumer electronics, with a particular focus on home audio and video setups. At PalmGear, he covers networking gear, printers and scanners, audio and video equipment, and tech troubleshooting guides.
You can get FREE Gifts. Or latest Free phones here.
Disable Ad block to reveal all the info. Once done, hit a button below