IP v6 to IP v4: Can You Convert an Address?

An IP v6 to IP v4 address conversion is not possible for an arbitrary address. IPv4 and IPv6 are separate protocols with different address spaces, and a network can translate traffic between them. That still does not give your IPv6 address a matching IPv4 twin. Here’s how to tell what you need, and how to check which protocol your connection actually uses.

Address conversion and traffic translation are different

IPv4 addresses look like 203.0.113.24: four decimal numbers separated by dots. IPv6 addresses look like 2001:db8:1234::24: hexadecimal groups separated by colons. The difference goes beyond punctuation. IPv4 uses 32-bit addresses and IPv6 uses 128-bit addresses, so no general one-to-one translation exists between the two address spaces.

A converter can reformat certain special values. For example, software may write IPv4 address 192.0.2.33 as the IPv4-mapped IPv6 value ::ffff:192.0.2.33. That format shows software how to carry an IPv4 value in an IPv6-shaped field. It does not make the address a universal route to an IPv4 host, and it does not prove that the device can reach the IPv4 internet.

Think of it like writing a phone number in a different filing system: the notation changes, but the cabinet does not magically put a phone at the other end. To communicate across protocol versions, a network needs a route or a translator.

How IPv6 with IPv4 works on today’s networks

Many home routers, computers, websites and ISPs support both protocols at once. This is called dual stack. Your device has IPv4 and IPv6 networking available, and the software chooses a usable route to each destination. The two are parallel ways to send internet traffic, not one address with two spellings. The router can handle both protocols, but the destination still has to support the one that is used.

When you visit a domain, the Domain Name System (DNS) can return an A record with an IPv4 address, an AAAA record with an IPv6 address, or both. Your operating system and browser choose among the available addresses, and connection algorithms can try another option if one route is slow or unavailable. So a public IP checker reports the address used to reach that checker, not every address configured on your device.

At home, your router may give devices private IPv4 addresses, such as those in the ranges defined by RFC 1918. Network Address Translation (NAT) lets several devices share one outward-facing IPv4 address. IPv6 often gives devices globally routable addresses instead, and a firewall controls incoming traffic. “Globally routable” does not mean “open to everyone”; firewall policy still matters.

IPv4 addresses are limited, so an ISP may also use Carrier-Grade NAT (CGNAT), where a provider shares one public IPv4 address among customers. Regional Internet Registries (RIRs) distribute internet number resources in their regions. None of these arrangements makes an IPv6 address convertible into an IPv4 address. They describe how networks allocate and share addresses.

What gateways can actually do

If an IPv6-only device needs an IPv4-only service, the network can bridge the gap. With NAT64, a gateway translates traffic between IPv6 clients and IPv4 servers. DNS64 can synthesize an IPv6-looking destination for a domain that has only an IPv4 address, which steers the connection to that gateway. Google Cloud documents this arrangement for IPv6-only workloads that reach IPv4 destinations.

DNS64 needs the app to look up a domain name first. An older app that embeds a literal IPv4 address or expects IPv4-specific behavior may not work through plain NAT64. Think of NAT64 as a border crossing for packets, not an address-printing booth. Mobile networks may use 464XLAT, which adds a client-side translator for IPv4-only apps and a provider-side translator to reach IPv4 services. The IETF describes this as a transition mechanism, not a way to mint a permanent IPv4 address for you.

Another option is a proxy. Your device connects to a relay, and the relay opens a separate connection using the protocol the destination accepts. The destination sees the relay’s egress address. A proxy changes the path and apparent source address for that connection, but it does not change your device’s underlying IP configuration.

For more on how an address can be shared, see our CGNAT guide. If you are troubleshooting a displayed public address, our IPv4 address explainer covers what the different address types mean.

Choose the right fix for the problem

There is no universal “convert” button, because these symptoms have different causes. Switching DNS servers, for example, changes how domain names are resolved. It does not add IPv4 support to an IPv6-only network, however tempting that sounds. A DNS server only handles name lookups. If name lookups are the issue, follow our DNS change steps after confirming the failure is DNS-related.

Check your connection in 30 seconds

1. Open Loqmi’s IP checker and note whether it displays an IPv4 or IPv6 public address.
2. Reconnect through another network, such as Wi-Fi instead of mobile data, and check again.
3. Compare which sites or apps work on each connection. If one test shows IPv4 and another IPv6, the networks or routes differ; you have not converted an address.
4. If the issue is slow loading rather than reachability, use the Loqmi speed test on both connections. A speed result measures the whole path and cannot by itself identify an IPv4-versus-IPv6 cause.

This quick comparison shows whether the difference follows a particular network. It does not test every destination, and geolocation databases can place the same public address in different locations; see why IP locations can be wrong.

Should you turn off IPv6 to force IPv4?

Usually, no. Windows and Apple’s developer guidance both treat IPv6 as a normal part of modern networking. Disabling it can break connectivity or reveal a different fault, and it may not force IPv4 if your provider’s network is IPv6-only with a translator at its edge.

If you are diagnosing a specific Windows issue, start by checking the adapter’s IP configuration and router settings, then follow Microsoft’s current IPv6 configuration guidance. Avoid registry edits or system-wide toggles copied from a generic article. On phones, the carrier usually controls the mobile network’s protocol and translation, so there is not necessarily a user-facing IPv4/IPv6 switch.

If a service explicitly requires a public IPv4 address, ask your ISP whether it can provide one and whether inbound connections are allowed. A local setting cannot request an address the provider has not routed to you. If you only want to change the public address you appear to use, see ways to change your IP address.