Blog Post

Networking Blog
3 MIN READ

Windows CLAT is Now Generally Available

JimAlumbaugh's avatar
JimAlumbaugh
Icon for Microsoft rankMicrosoft
Oct 27, 2026

We’re pleased to announce that Windows CLAT (Customer-side Translator) is generally available on Windows 11 Client 25H2 starting with build 26200.9550.

 

As organizations move toward IPv6-only and IPv6-mostly networks, some applications still depend on IPv4-only applications or services. Windows CLAT helps those applications continue to work when a network does not provide native IPv4 connectivity.

CLAT is the client-side component of 464XLAT. It statelessly translates IPv4 traffic from the Windows client into IPv6 for transport across the network to a provider-side translator (PLAT), which provides stateful NAT64 translation to IPv4.

Why CLAT?

  • Compatibility with IPv4 resources: IPv6-only devices can reach IPv4 resources without requiring the whole network to be dual-stack.
  • Reduced IPv4 address requirements: Devices can share a public IPv4 address through NAT64, reducing demand for scarce IPv4 addresses. This is critical for organizations that cannot obtain a significant block of IPv4 addresses for new networks due to IPv4 address depletion.
  • Simpler network configuration: Organizations can deploy IPv6-only networks while retaining access to IPv4 resources.
  • Seamless user experience: Translation happens as needed, without requiring users to know whether a service uses IPv4 or IPv6.
  • Potential cost savings: IPv6-only deployment can reduce costs associated with IPv4 addresses and operating dual-stack infrastructure.
  • Minimized security risk exposure: Similar to the above, dual‑stack networks expose two attack surfaces, each with its own vulnerabilities and configuration requirements. CLAT helps to reduce this by removing the need to secure an additional network.
  • Incremental deployment: Organizations can introduce IPv6 in stages while maintaining IPv4 compatibility, rather than overhaul the entire network at once.
  • A foundation for future IPv6 growth: CLAT helps organizations build on IPv6 rather than depend on an increasingly limited supply of IPv4 addresses.

How Windows CLAT Helps Organizations Accelerate To IPv6-Only

FeatureWhat it isWhy it’s important
IPv4 application access on IPv6 networksCLAT is the client-side component of the 464XLAT architecture (RFC 6877). It translates IPv4 traffic so IPv4-only applications can communicate over an IPv6 network (where a NAT64/PLAT service exists.)Organizations can move network infrastructure toward IPv6 without waiting for every application or destination to support IP
Local IPv4 compatibility for applicationsAllows IPv4 addresses to be assigned to support IPv4-only application flow on IPv6-only devices and networks.Helps existing applications continue to use familiar IPv4 networking while the device uses an IPv6 network underneath.
Support across network interfacesThe feature is designed for IPv6-capable connections across Wi-Fi, Ethernet, and cellular interfaces.Devices can maintain IPv4 application compatibility as they connect through different network types.
Automatic recognition of IPv6-only networksCLAT can begin configuration discovery when IPv4 connectivity is unavailable, or when a network signals IPv6-only-preferred operation using DHCP Option 108 (RFC 8925).Reduces the need for users to configure connectivity themselves and gives networks a standards-based way to indicate that clients should prefer IPv6.
Prefix discovery from network advertisementsCLAT can discover the translation prefix from PREF64 information in IPv6 Router Advertisements, as defined by RFC 8781.Allows compatible routers to provide the information devices need to use for translation, and to advertise prefix changes as the network evolves.
DNS-based prefix discoveryCLAT can also discover the translation prefix by querying ipv4only.arpa, following RFC 7050 and RFC 8880. This provides an alternative when the network does not provide PREF64 through Router Advertisements.Gives organizations another standards-based discovery option for networks that rely on DNS to provide IPv4/IPv6 transition information.

Where to Get More Details

For a practical overview of enabling Windows CLAT, confirming its configuration, and collecting logs, see our Windows CLAT Public Preview blog. For a deeper explanation of what CLAT is and how it works, see Windows CLAT Enters Private Preview: A Milestone for IPv6 Adoption.

Accelerating the Global IPv6 Migration

We’re excited about the role Windows CLAT can play in the global transition to IPv6. By helping IPv4-dependent applications continue to work as networks evolve, this feature can make it easier for organizations to move toward IPv6-only and IPv6-mostly environments. We’re grateful to the customers and partners whose feedback helped bring Windows CLAT to general availability, and we look forward to seeing its impact across the IPv6 community.

 

Updated Oct 27, 2026
Version 2.0

9 Comments

  • yfctdcl's avatar
    yfctdcl
    Copper Contributor

    Are there any plans to bring this to Windows Server 2025 or Server vNext ?

    • saxl23's avatar
      saxl23
      Copper Contributor

      Windows Server 2025 is on 26100, so I do not expect that kernel to receive the feature. But even if it would, this is a ltsc like version, so I would not expect a feature back-port, and if it would be physically there it most probably would be disabled. For vNext I think sooner or later it will arrive since I see no reason why Microsoft would have two diverging tcpip stacks, given this feature is does not create a virtual tunnel device like teredo or isatap but looking at the behavior and current limitation very probably something in tcpip.sys that swaps ip headers mid- stack

    • JimAlumbaugh's avatar
      JimAlumbaugh
      Icon for Microsoft rankMicrosoft

      Hi, no current plans to support on Server, no. If you have a specific business case or need for this, please reach out. 

  • saxl23's avatar
    saxl23
    Copper Contributor

    Very cool. Works well (like the preview already did)

    It is a good move to leave it disabled by default and let admins (or endusers like myself) until a yet broader community tried it out. I definitely urge application developers to try this out to know in advance if some modifications in their software are needed.

    On my part there are two things I am missing (not part of the network team at Microsoft that developed this feature)

    • the UI shows "address assignment" as manual for IP in the system settings dialog (ui/system settings team).
    • the 192.0.0.x addresses are still registered in dns (on a domain joined computer) (dnscache team I think?).

    To application developers: There is a pitfall: you can bind to the 192.0.0.1 address, but sending data to that address does not loop back but instead goes out to the network, to be precise to the ipv6 representation of that address in you current pref64 prefix.

    • JimAlumbaugh's avatar
      JimAlumbaugh
      Icon for Microsoft rankMicrosoft

      On your first bullet, do you mind unicasting me a screenshot of what you're seeing along with the output of netsh interface clat show instance interface = [interface-name]? 

      For you send bullet, this issue is fixed but not in a current retail build. You should be able to find it in this Windows Insider Experimental build and later: Windows 11 Insider Experimental (Future Platforms) Preview Build 29683.1000 - Windows Insider Program | Microsoft Learn. It will hit retail in the next release of Windows. 

      • saxl23's avatar
        saxl23
        Copper Contributor

        glad to hear that the loopback issue is already fixed 👍.

        The only way one could be hit by this if the application does loopback communication via ipv4 only and not using localhost but the own hostname as destination anyway, so probably not a big deal.

        I've sent you the requested image regarding the UI inconsistency. Again, not a real issue since people opening this dialog probably know what they are doing.

        The dns registration on the other hand might be something that annoys more people in a managed environment.

  • JiriBrejcha's avatar
    JiriBrejcha
    Copper Contributor

    Congrats JimAlumbaugh​ and team, amazing news! 

    Was support for this feature introduced in Windows 11 25H2, starting with build 26200.9550, with no extra tweaks out of the box? Does any Windows Update patch have to be manually installed to enable this feature on 25H2?

    • JimAlumbaugh's avatar
      JimAlumbaugh
      Icon for Microsoft rankMicrosoft

       

       

      with no extra tweaks out of the box? 

      Hi, not entirely sure what you're asking - are you wondering if there's additional configuration required other than what's documented at the links I provided above? If so, the answer is no.

      Does any Windows Update patch have to be manually installed to enable this feature on 25H2

      As long as you have build #26200.9550 or later installed, no additional patches are required.

       

      • saxl23's avatar
        saxl23
        Copper Contributor

        actually #26300.9550 aka the same build but with the 26h2 enablement packet installed includes this too (as to be expected)

        What I could not check is if 28000.3231 (26h1) includes this too or if Microsoft waits for the re-merge of the arm64 and amd64 lines.

        I don't know if this was just my setup, but to activate this feature I only needed

        netsh.exe interface clat set global permit=enabled

        as the other two settings where already enabled by default. But following the previous documentation and setting pref64fromdns=enabled and  pref64fromra=enabled explicitly surely does not hurt.