Local port forwarding in PuTTY makes a remote TCP service reachable via a local port without opening that service to the network. It is commonly used to access internal web apps, admin consoles, and databases that only listen on the SSH server or its private network.
A local forward creates a listening socket on the computer running PuTTY and carries each incoming connection through the encrypted SSH session. The SSH server then opens the onward connection to the configured destination, so the destination host:port is interpreted from the server side rather than the local machine.
Port forwarding works only while the SSH session stays connected, and local port conflicts prevent the forward from opening. Leaving PuTTY’s default loopback-only binding keeps the forwarded port limited to the local computer, while allowing other hosts to connect can expose the tunneled service to the LAN.
Default SSH port is 22.
Example: 8080.
If another program is already using the port, PuTTY cannot bind the forward and the tunnel will not work.
Example: 127.0.0.1:80 to reach a web service bound to the SSH server’s loopback interface.
Enabling this option can expose the forwarded port to other devices, effectively sharing access to the tunneled service.
Multiple local forwards can be added to the same SSH session.
Saved sessions store tunnel definitions, but passwords are not saved by default.
The fingerprint should match the SSH server’s published host key to avoid trusting the wrong system.
Closing PuTTY stops the tunnel immediately and disconnects clients using the forwarded port.
C:\> netstat -nao | findstr :8080 TCP 127.0.0.1:8080 0.0.0.0:0 LISTENING 12344
An additional ::1 listener is normal on IPv6-enabled systems.
http://127.0.0.1:8080/
Use 127.0.0.1 or localhost as the client address to avoid reaching the service directly over the network.