Welcome to Fiddler Everywhere!

Fiddler Everywhere is a high performance, cross-platform web debugging proxy for any browser, system or platform. It is a web debugging tool that logs all HTTP(S) traffic between your computer and the Internet. It inspects and edits traffic, issue requests, and fiddle with incoming and outgoing data.

HTTP(S) traffic Inspection and Analysis

Fiddler Everywhere logs all HTTP(S) traffic between your computer and the Internet. With Fiddler Everywhere you can capture traffic from virtually any application that supports a system proxy.

Request and Response Mocking

Fiddler support mocking or modifying request and responses on any application. It’s a quick and easy way to change HTTP(S) requests and responses without changing the code.

API Composing

Use Fiddler's API Composer to test APIs by creating and sending requests. This feature is useful while developing new APIs or when testing existing APIs.

Fiddler Everywhere main screen

Key Features

  • Compatible with macOS, Windows, and Linux.
  • Inspect web traffic (HTTP and HTTPS).
  • Decrypt secure traffic (HTTPS).
  • Save, share, and receive captured traffic with collaborators.
  • Mock requests and responses.
  • Modify requests and responses.
  • Compose new and edit existing API requests.
  • Save and share composed API requests.
  • Extended sharing and collaboration options.
  • Modern intuitive UI with multiple themes.

The Fiddler Everywhere features are subject to some pre-defined limitations. Refer to the table below for details about the Fiddler Everywhere Pro subscription plan.

Features Pro
Capture and Inspect Traffic Unlimited
Creating Composer Requests Unlimited
Using rules Unlimited
Sharing rules Unlimited
Creating Saved Sessions entries * Unlimited
Sharing Saved Sessions Unlimited*
Shared Session Size Max 50 MB
Email Support Unlimited*

*subject to fair usage policy. Learn more about the support offered here.

A Session in Fiddler Everywhere is a term that describes an entry that holds single or multiple requests and responses (captured traffic). Saved session entries are listed in the Sessions list and can also be exported as SAZ archive or other known formats.

Trial version

To try Fiddler Everywhere for 30 days, press the Upgrade button within the UI and press TRY PRO FOR 30 DAYS. An Upgrade Successful prompt window confirms your trial clock has started. No credit card is required to start your trial and the trial is a fully functioning version of the Fiddler Everywhere Pro plan.

Fiddler Everywhere Dashboard

You can find more information on managing your plans and subscriptions through the Fiddler Everywhere dashboard panel here.

Release history

To learn more about the release history, visit Release History Page

Installation

Download the latest Fiddler Everywhere. To learn how to install Fiddler Everywhere, visit the Installation section.

Documentation

Official Fiddler Everywhere documentation

We believe documentation is best when the content is a product of collaboration between the builders and consumers of that product. Everybody can play a role in making our documentation better, and we encourage you to help us with this task in the way that you choose:

  • Send Feedback Use the Was this article helpful? functionality to provide feedback and ideas on ways we can improve the documentation. Alternatively, you can request a feature or report a bug using the Fiddler Everywhere Feedback Portal.

  • Create an Issue If you find an issue with our docs that needs addressing, the best way to let us know is by creating an issue in our Github repository. When creating an issue, please provide a descriptive title, be as specific as possible, and link it to the documentation article. If you can give a link to the closest anchor to the issue, that is even better.

  • Send a Pull Request Creating an issue is excellent, yet what we love are pull requests. Therefore, if you find a problem in the docs, or even feel like generating new content, we’d be happy to have your contributions!

    To do this, you must fork our documentation and submit a pull request. Then, you may contribute an update exactly where you found the error. After that, our technical writing team will need to approve your change request. Please use only standard markdown. For more detailed instructions, please follow the contribution instructions published in GitHub. You can directly initiate a pull request by using the Improve this article functionality.

License

Licensing agreement and detailed information about the different licenses and which one you should acquire is available in the Licensing section.

In this article