Cloudflared-windows-amd64.exe

Start small: run a one-off tunnel to a test website. Then graduate to a named tunnel with a custom domain and persistent Windows service. You’ll never mess with port forwarding again. Cloudflared is maintained by Cloudflare, Inc. This guide is unofficial but follows best practices as of 2025.

For TCP services, you must also set up Cloudflare Access (or use cloudflared access tcp on the client side). For temporary sharing (e.g., a demo), you don’t even need a domain. Run: cloudflared-windows-amd64.exe

cloudflared.exe tunnel route dns my-first-tunnel myapp.yourdomain.com This creates a DNS record at Cloudflare pointing to the tunnel. Create a configuration file config.yml in %USERPROFILE%\.cloudflared\ : Start small: run a one-off tunnel to a test website

cloudflared.exe tunnel run my-first-tunnel Your local service is now live at https://myapp.yourdomain.com . For persistent operation (reboots, logoffs), install Cloudflared as a Windows service. Cloudflared is maintained by Cloudflare, Inc

cloudflared.exe tunnel login A browser window will open. Log in to your Cloudflare account and select the domain you want to use. This generates a cert.pem file in %USERPROFILE%\.cloudflared\ . That certificate is your global API credential—keep it safe. Tunnels are persistent connections with their own configuration. Let’s create one.

If you run a web server on your Windows machine—whether for development, home automation, or a personal website—you know that exposing it to the internet can be risky. Port forwarding is messy, dynamic DNS is a hassle, and your ISP might block incoming traffic altogether.

Visit https://github.com/cloudflare/cloudflared/releases Look for the latest release and download: cloudflared-windows-amd64.exe amd64 means it’s for 64-bit Windows (most modern PCs). For 32-bit, use 386 . Alternative using command line (PowerShell as Admin):