HowToFixWiFiSimple fixes  •  Better connection
Wifi Guide

Does Windows Prioritize Ethernet Over Wifi? Essential Info Today

Introduction If you have ever plugged an Ethernet cable into a laptop that was already connected to Wi-Fi, you may have wondered what actually happens behind the scenes. Does your computer keep using the wireless connection, or does it quietly switch to the wi

HowToFixWiFi

Introduction

If you have ever plugged an Ethernet cable into a laptop that was already connected to Wi-Fi, you may have wondered what actually happens behind the scenes. Does your computer keep using the wireless connection, or does it quietly switch to the wired one? The question “Does Windows Prioritize Ethernet Over Wifi?” comes up constantly among home users, IT professionals, and gamers alike, and the answer matters more than most people realize. The connection Windows chooses affects your download speeds, latency in games, stability during video calls, and even which network your traffic travels over.

In this guide, you will learn exactly how Windows decides which network adapter to use, whether Ethernet really gets preferential treatment, and how you can take full control of that decision yourself. We will walk through the technical details in plain language, provide step-by-step instructions for both Windows 10 and Windows 11, and share troubleshooting tips for the moments when Windows refuses to behave the way you expect. By the end, you will know not just what Windows does by default, but how to make it do what you want.

Table of Contents

What Does “Prioritization” Mean in Windows Networking?

When people ask whether Windows prioritizes one connection over another, they are usually thinking about a single, simple question: if two networks are available at the same time, which one carries the traffic? In reality, “prioritization” in Windows is not a single on/off switch. It is a collection of rules, metrics, and behaviors that together decide how packets leave your computer and where they go.

Windows can have multiple active network adapters simultaneously. You might have an Ethernet cable plugged in while your Wi-Fi radio is still connected to a wireless network. In that situation, both adapters have IP addresses, both can reach the internet, and both are technically “up.” Windows does not simply pick one and ignore the other. Instead, it consults a routing table and a set of metrics to decide which path is preferred for outbound traffic.

Prioritization therefore means two things: which adapter is chosen as the default route for general internet traffic, and which adapter is used for specific destinations such as local network resources. Understanding this distinction is the first step toward controlling your connection.

Does Windows Prioritize Ethernet Over Wifi?

The short answer is yes, in most default configurations Windows does prefer Ethernet over Wi-Fi. When both connections are active and have internet access, Windows typically routes your general traffic through the wired Ethernet adapter. This happens because of how Windows assigns something called the “interface metric,” which we will explore in detail shortly.

However, the longer and more accurate answer is that it depends. Windows does not hard-code “Ethernet always wins.” Instead, it assigns a lower metric number to connections it considers faster or more reliable, and a lower metric means higher priority. Because Ethernet is usually faster and more stable than Wi-Fi, it tends to receive a lower metric. But if your Ethernet connection is slow, degraded, or manually configured with a high metric, Wi-Fi can end up taking priority instead.

So when someone asks “Does Windows Prioritize Ethernet Over Wifi?”, the honest response is: by default, usually yes, but the behavior is governed by metrics that you can view and change. Nothing is set in stone.

How Windows Chooses the Default Network Adapter

Windows uses a routing table to decide where to send packets. Each network adapter contributes routes to this table, and each route has a metric. When two routes can reach the same destination, such as the default gateway for internet access, Windows picks the one with the lowest metric. If metrics are equal, other tie-breakers come into play, such as the order in which adapters were initialized.

Several factors influence this decision:

  • Link speed: Windows automatic metric considers the reported speed of the connection. A 1 Gbps Ethernet link gets a better metric than a 300 Mbps Wi-Fi link.
  • Manual configuration: If you have manually set a metric on an adapter, that value overrides automatic behavior.
  • Adapter state: An adapter that is disconnected or has no valid IP address cannot be used, regardless of its metric.
  • Binding order: The order of adapters in the “Adapters and Bindings” list can influence tie-breaking in some scenarios.

This means Windows is not making a judgment call based on the word “Ethernet.” It is making a math-based decision based on metrics, and Ethernet just happens to win most of the time because of its typical speed and stability.

Understanding the Interface Metric

The interface metric is the single most important concept for answering “Does Windows Prioritize Ethernet Over Wifi?” A metric is just a number. Lower numbers mean higher priority. Think of it like golf: the lowest score wins. If your Ethernet adapter has a metric of 5 and your Wi-Fi adapter has a metric of 50, Windows sends traffic through Ethernet.

You can view the current metrics in several ways. The simplest is through the graphical interface, but power users often prefer PowerShell or the command prompt. Here is what you need to know:

  • The default automatic metric in modern Windows is based on link speed.
  • Typical Ethernet metrics range from 5 to 25.
  • Typical Wi-Fi metrics range from 25 to 65.
  • A metric of 1 is the highest possible priority.
  • Very high metrics, such as 9999, effectively disable an adapter from being chosen as the default route.

When you understand metrics, the entire question of prioritization becomes transparent. You are no longer guessing; you are reading numbers and, if needed, changing them.

How to Check Which Connection Windows Is Using

Before you change anything, it is wise to confirm which adapter is currently carrying your traffic. There are multiple ways to do this.

Checking via Settings

Open the Settings app, go to Network and Internet, and look at the status. Windows often shows which connection is active. However, this view can be misleading when both adapters are connected, because both may show as connected. It tells you that a connection exists, not necessarily which one is the default route.

Checking via Command Prompt

For a definitive answer, open Command Prompt and run the following command:

route print

Look at the IPv4 Route Table. The row with destination 0.0.0.0 and the lowest metric is your default route. The Gateway and Interface columns tell you which adapter is being used. This is the most reliable way to see what Windows is actually doing.

Checking via PowerShell

PowerShell gives an even cleaner view. Run:

Get-NetIPInterface | Sort-Object InterfaceMetric

This lists your adapters sorted by metric. The one at the top with the lowest number is your highest-priority connection. This command is particularly useful because it shows both IPv4 and IPv6 interfaces and their current metric values.

Step-by-Step: Force Windows to Prefer Ethernet

If Windows is not already preferring your Ethernet connection, or if you want to guarantee that it always does, follow these steps. The process involves setting a manual metric on your Ethernet adapter that is lower than your Wi-Fi adapter’s metric.

Using the Graphical Interface

  1. Press Windows key + R, type ncpa.cpl, and press Enter. This opens the Network Connections window.
  2. Right-click your Ethernet adapter and select Properties.
  3. Select “Internet Protocol Version 4 (TCP/IPv4)” and click Properties.
  4. Click the Advanced button.
  5. In the IP Settings tab, uncheck “Automatic metric.”
  6. Enter a low number, such as 5 or 10, in the Interface metric field.
  7. Click OK on all open dialogs.
  8. Repeat for IPv6 if you use it, setting the same or a similar low metric.

After completing these steps, your Ethernet adapter will have a fixed low metric. As long as it is connected, Windows should route traffic through it instead of Wi-Fi.

Using PowerShell

For a faster, scriptable approach, use PowerShell as an administrator:

Set-NetIPInterface -InterfaceAlias "Ethernet" -InterfaceMetric 5

Replace “Ethernet” with the actual name of your adapter, which you can find using Get-NetAdapter. You can also set the Wi-Fi metric higher at the same time:

Set-NetIPInterface -InterfaceAlias "Wi-Fi" -InterfaceMetric 50

This two-line approach is clean, repeatable, and easy to document for IT teams managing multiple machines.

Step-by-Step: Make Windows Prefer Wi-Fi When Needed

There are legitimate reasons to prefer Wi-Fi over Ethernet. Perhaps your Ethernet connection runs through a slower switch, or you are troubleshooting and want wireless to take over. The process is the mirror image of the previous section.

  1. Open Network Connections with ncpa.cpl.
  2. Right-click your Wi-Fi adapter, choose Properties, then IPv4 Properties, then Advanced.
  3. Uncheck Automatic metric and set a low number, such as 5.
  4. Set your Ethernet adapter’s metric higher, such as 50, using the same method.

Alternatively, use PowerShell:

Set-NetIPInterface -InterfaceAlias "Wi-Fi" -InterfaceMetric 5
Set-NetIPInterface -InterfaceAlias "Ethernet" -InterfaceMetric 50

Remember that if you unplug the Ethernet cable, Wi-Fi will be used regardless of metrics, because a disconnected adapter cannot carry traffic. Metrics only matter when both adapters are active.

Ethernet vs. Wi-Fi: A Side-by-Side Comparison

To put the prioritization question in context, here is a comparison of the two connection types across the factors that influence Windows’ default behavior.

Factor Ethernet Wi-Fi
Typical Link Speed 1 Gbps or higher 150 Mbps to 1.2 Gbps
Default Interface Metric Lower (higher priority) Higher (lower priority)
Latency Very low and consistent Variable, affected by interference
Stability Excellent Good, but subject to signal issues
Mobility None, cable required Full wireless freedom
Security Risk Physical access required Over-the-air interception possible
Windows Default Preference Usually preferred Usually secondary

This table illustrates why Windows, left to its own devices, leans toward Ethernet. It is not favoritism; it is a reasonable default based on speed and reliability.

Automatic Metric vs. Manual Metric

Windows can calculate metrics automatically or accept your manual input. Understanding the difference helps you decide which mode to use.

With automatic metric enabled, Windows assigns values based on the adapter’s reported link speed. Faster links get lower metrics. This is convenient and adapts as conditions change. For example, if your Wi-Fi connection negotiates a very high speed, its metric might drop closer to Ethernet’s level.

With manual metric, you lock in a specific number. This gives you predictable, stable behavior that does not shift when link speeds fluctuate. The downside is that you must remember to adjust it if your network environment changes significantly.

For most users, leaving automatic metric enabled is fine, because the defaults already favor Ethernet. For gamers, streamers, or IT administrators who need guaranteed behavior, manual metrics are the better choice.

Adapter Binding Order in Windows

Beyond metrics, Windows has a concept called binding order, which determines the sequence in which adapters are consulted for certain network operations. You can view and adjust this in the legacy Network Connections window by pressing Alt to reveal the menu, then choosing Advanced and Advanced Settings.

In older versions of Windows, binding order had a strong influence on which adapter was used. In Windows 10 and Windows 11, its impact has diminished because metrics now dominate routing decisions. Still, it can matter in edge cases, such as when two adapters have identical metrics or when specific applications query adapters in binding order.

If you are troubleshooting a stubborn prioritization issue, adjusting the binding order to place Ethernet at the top is a reasonable additional step. Just be aware that it is a secondary mechanism, not the primary one.

Troubleshooting When Windows Won’t Switch Connections

Sometimes you set everything correctly and Windows still seems to use the wrong connection. Here are the most common causes and fixes.

Metric Not Applied

After changing metrics, you may need to restart the adapter or reboot the computer for the change to take full effect. Disable and re-enable the adapter in Network Connections, or run ipconfig /flushdns and ipconfig /release followed by ipconfig /renew.

Application-Specific Binding

Some applications, especially VPN clients and older software, bind to a specific adapter regardless of system metrics. If one program uses Wi-Fi while the rest use Ethernet, check the application’s own network settings.

VPN Interference

A VPN can create a virtual adapter with its own metric, potentially overriding your preferences. Check the VPN adapter’s metric and adjust if necessary. Many VPN clients also have a setting to use the local network for internet access, which can change routing behavior.

DNS and Cached Routes

Windows may cache routes or DNS resolutions. Flushing DNS and clearing the ARP cache can resolve stale routing. Use arp -d * to clear the ARP cache and ipconfig /flushdns for DNS.

Driver Issues

Outdated or buggy network drivers can report incorrect link speeds, causing automatic metrics to be wrong. Update your drivers from the manufacturer’s website rather than relying solely on Windows Update.

Tips and Best Practices

Here are practical recommendations to get the most out of your network prioritization setup.

  • Document your settings: If you manage multiple machines, keep a record of the metrics you set so you can replicate or troubleshoot later.
  • Use PowerShell for consistency: Scripted changes are easier to apply across many computers than clicking through dialog boxes.
  • Test after changes: Always verify with route print or Get-NetIPInterface that your intended adapter has the lowest metric.
  • Keep automatic metric as a fallback: If you are unsure, leave automatic metric enabled and only override when you have a specific reason.
  • Prefer Ethernet for latency-sensitive tasks: Gaming, video conferencing, and large file transfers all benefit from the consistency of a wired connection.
  • Do not disable Wi-Fi unnecessarily: Keeping Wi-Fi available as a backup provides resilience if your Ethernet cable is unplugged or the switch fails.
  • Monitor link speed: A degraded cable or port can lower Ethernet’s reported speed, causing automatic metrics to shift unexpectedly.

Security and Performance Considerations

Prioritization is not just about speed. It also affects security and reliability. Ethernet connections are generally more secure because they require physical access to intercept. Wi-Fi, even with strong encryption, is broadcast over the air and can be targeted by attackers within range.

From a performance standpoint, Ethernet provides consistent throughput and low jitter, which is critical for real-time applications. Wi-Fi performance varies with distance, obstacles, and interference from other devices. By ensuring Windows prioritizes Ethernet when available, you get the best of both worlds: the speed and security of wired when at your desk, and the convenience of wireless when you move around.

One often overlooked point: if you have both connections active and Windows uses Ethernet, your Wi-Fi adapter is still connected and consuming power. On a laptop, this can reduce battery life slightly. If battery life matters, consider disabling Wi-Fi when Ethernet is plugged in, either manually or through a small script or utility.

Frequently Asked Questions

Does Windows always use Ethernet when it is plugged in?

Not always, but usually. Windows uses the adapter with the lowest interface metric. Ethernet typically has a lower metric by default, so it is preferred. However, if you have manually set a high metric on Ethernet or a low metric on Wi-Fi, the behavior can reverse. Also, some applications bind to specific adapters regardless of system metrics.

How do I know which connection Windows is currently using?

Run route print in Command Prompt and look for the default route with the lowest metric, or run Get-NetIPInterface | Sort-Object InterfaceMetric in PowerShell. The adapter at the top of the sorted list is your highest-priority connection.

Can I make Windows switch automatically between Ethernet and Wi-Fi?

Windows already does this to some extent. If Ethernet is unplugged, traffic falls back to Wi-Fi automatically. If you plug Ethernet back in, Windows should shift to it based on metrics. For more aggressive automatic switching, third-party utilities exist, but for most users the built-in metric system is sufficient.

Does prioritizing Ethernet improve gaming performance?

Yes, in most cases. Ethernet offers lower and more consistent latency than Wi-Fi, which reduces lag and packet loss. Even if your Wi-Fi is fast, the variability of wireless can cause spikes that affect gameplay. Prioritizing Ethernet ensures your game traffic takes the stable path.

What is a good metric value to set?

A value of 5 or 10 for your preferred adapter and 50 or higher for the secondary adapter works well. The exact numbers matter less than the relative difference. As long as your preferred adapter has a meaningfully lower number, Windows will choose it.

Will changing metrics break my internet connection?

No, as long as at least one adapter has a valid configuration and a route to the internet. Changing metrics only affects priority, not connectivity. If something goes wrong, you can always re-enable automatic metric to return to defaults.

Do these settings apply to both IPv4 and IPv6?

Metrics are configured separately for IPv4 and IPv6. If you use both protocols, set metrics on both. Many networks still rely heavily on IPv4, so that is the most important one, but do not neglect IPv6 if it is active on your network.

Conclusion

So, does Windows prioritize Ethernet over Wi-Fi? In most default setups, yes. Windows assigns lower interface metrics to faster, more reliable connections, and Ethernet usually earns that distinction. But the system is not locked into that behavior. Through metrics, binding order, and adapter configuration, you have full control over which connection carries your traffic.

Whether you are a gamer chasing the lowest ping, a professional needing stable video calls, or an IT administrator standardizing configurations across an organization, understanding how Windows makes this decision empowers you to make it work for your specific situation. Start by checking your current metrics with a simple PowerShell command, decide whether the defaults already serve you well, and adjust only when you have a clear reason to do so. With a few minutes of configuration, you can ensure Windows always uses the connection you want, when you want it.