Localhost Traffic Capturing


Product Version 1.0.0 and above


Traffic sent to http://localhost or is not captured when using some browsers like Google Chrome or Firefox even though Fiddler Everywhere Capturing is turned on.


To solve this issue, use either of the following approaches:

Both solutions require that Fiddler Everywhere Capturing is enabled.

Using Machine Name

Use the machine name as an alias for localhost or loopback addresses.

For example, let's assume the machine name is myrootuserid Instead of using localhost like this:


Use the machine name as follows:


Using Aliases

Depending on the specific scenario, you can replace localhost or with one of the following special Fiddler aliases:

  • ipv4.fiddler for connections using Internet Protocol version 4.
  • ipv6.fiddler for connections using Internet Protocol version 6.
  • localhost.fiddler to hit localhost in the Host header (applicable for IIS Express).

For example, traffic sent to the following URL may not be captured:


To capture the traffic with Fiddler Everywhere:

  • replace localhost with the ipv4.fiddler alias to hit localhost on an IPv4 adapter:

  • replace localhost with the ipv6.fiddler alias to hit localhost on an IPv6 adapter:

  • replace localhost with the localhost.fiddler alias to hit localhost in the Host header:


Filter Localhost Traffic

While using one of the above solutions to capture localhost requests, the traffic will be captured in the Live Traffic list, and as host name, the loopback address will be displayed (usually To filter by the Host column so that only localhost traffic is displayed, you will need to enter the loopback address as host value and not the aliases used in the browsers.

Example Localhost filtering

In this article