Skip to main content
TrustRadius
Progress Telerik Fiddler

Progress Telerik Fiddler

Overview

What is Progress Telerik Fiddler?

Fiddler is a suite of products from Progress Telerik, designed to help users with web debugging and troubleshooting.

Read more
Recent Reviews

TrustRadius Insights

Fiddler has proven to be a valuable tool for various user experiences and has successfully solved a range of problems. Reviewers have …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation

Pricing

View all pricing

Fiddler Everywhere - Pro

$12

Cloud
per month per user

Fiddler Everywhere - Pro

$18

Cloud
per month per user

Fiddler Everywhere - Enterprise

$420

Cloud
per year per user

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://www.telerik.com/purchase/fiddler

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Starting price (does not include set up fee)

  • $12 per month, billed annually
Return to navigation

Product Details

What is Progress Telerik Fiddler?

Fiddler Everywhere is a web debugging proxy for any device or platform, supporting macOS, Windows, and Linux.

Progress Telerik Fiddler Competitors

Progress Telerik Fiddler Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

Fiddler is a suite of products from Progress Telerik, designed to help users with web debugging and troubleshooting.

Progress Telerik Fiddler starts at $12.

Charles Web Debugging Proxy, Proxyman, and Requestly are common alternatives for Progress Telerik Fiddler.

The most common users of Progress Telerik Fiddler are from Mid-sized Companies (51-1,000 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(9)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Fiddler has proven to be a valuable tool for various user experiences and has successfully solved a range of problems. Reviewers have found Fiddler helpful for testing and debugging web applications, as well as analyzing performance and finding errors. It has been extensively used to track web traffic, debug API endpoints, and capture HTTP and HTTPS logs for network traffic analysis. Additionally, the tool has been utilized for spoofing and sniffing REST calls to debug network issues, website development and testing, and modifying network traffic in real-time for testing purposes. Users have also relied on Fiddler to diagnose issues with cloud-based software, troubleshoot network-related problems, and identify improvements in API interactions.

Highly regarded as the best tool: Users have consistently praised Fiddler as the top choice for web traffic monitoring and debugging, indicating that it has been widely recognized for its exceptional performance in these areas.

Easy to use with intuitive user interface: Many reviewers have found Fiddler to be user-friendly and appreciate its intuitive interface. This positive sentiment suggests that users find the tool easy to navigate and perform tasks efficiently.

Wide range of features: Users value the extensive feature set offered by Fiddler, including the ability to apply rules to requests and responses, features like Autoresponder and statistics, support for various browsers, and proxy manipulation capabilities. The mention of these features by multiple reviewers indicates their satisfaction with the breadth of functionality provided by Fiddler.

Confusing User Interface: Several users have found the user interface of Fiddler to be confusing and difficult to navigate, with too many options and controls. They feel that it has an outdated design and is complex to use, especially for non-tech-savvy individuals.

Sluggish Performance: Users have reported experiencing sluggish performance, slow loading times, and occasional software freezes while using Fiddler. This can be frustrating and hamper their workflow.

Lack of Clear Explanations and Documentation: Some users have mentioned a lack of clear explanations and documentation in Fiddler, which has led them to seek help from other sources. This can make it challenging for users to fully understand and utilize all the features of the software.

Users of Fiddler have made several recommendations based on their experiences with the tool. The three most common recommendations are as follows:

  1. Many users highly recommend Fiddler for debugging APIs and consider it to be the best solution for effective packet analysis and debugging of API endpoints. They find it easy to use with most browsers and suggest exploring its various views to gain a deeper understanding of tracked information and HTTP traffic in general.

  2. Fiddler is also recommended by users for web development purposes, particularly for testing APIs, capturing services to determine response time, and observing web traffic. It is considered a valuable tool for mobile testing and is suggested for web developers and software engineers working on web applications. Users find Fiddler useful in capturing status codes, response time, and size, making it a must-have tool for web debugging.

  3. Several users suggest giving Fiddler a try due to its free availability and intuitive interface that allows anyone to understand how a proxy debugger works. They find it helpful in automation tasks such as creating web bots and emphasize its usefulness in front-end development if corporate networks allow or if the premium version is purchased. Additionally, some users recommend the self-hosted version of Fiddler over the cloud version to avoid potential lagging issues.

Overall, users have found Fiddler to be a versatile and effective tool with many uses in IT, including API development, integration, debugging, and web traffic observation.

Reviews

(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Adam Wride | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
My work involves a lot of integration with third-party APIs, this tool provides a clear breakdown of API calls and makes it really simple to see the raw request so that we can write code to build that same request. We have found that in a lot of cases, it highlights missing headers in the requests as well as gives the raw JSON data which is easy to pull out and create matching classes it's so simple to use and really easy to filter out requests to only see the bits that you are actually interested inIt's such a useful and well-built project that I insist all developers on my team have it so that they can use it for debugging and to aid in building new integrations. An invaluable tool, cannot recommend it enough!
  • Viewing the raw request information of web requests
  • Viewing the raw response information of web requests
  • Viewing speeds of requests to monitor how long the request takes to respond
  • Seeing any routing of different requests so that you can get more information on redirects that happen
  • The display could potentially become a bit more user-friendly over time, it's pretty easy to follow but for example, I always view the raw request/response information by default and this is not the default selection, being able to choose the default selection would be nice
  • Clearer information and options to reduce 'noise' when viewing the requests, there are often a lot of background requests being sent on a computer, you can filter to roughly see what you want and filter out things that you don't want but there are different types of requests and I can't see how to filter between those - possibly a feature but could be made easier to use potentially
  • Nothing else to put, this is a fantastic product so there isn't much else to suggest at this stage of using it and I have been using fiddler for years now in my role as a software engineer
I am a senior software engineer and I have actively made fiddler a requirement for all of our engineers to have on their laptops by default. I have recommended it to all web developers that I have worked with and contractors that I have worked with as it has saved my mental stability on numerous occasions when trying to show people details of various web requests when working on integrations between different systems This is an absolutely fantastic product that I have used in a technical capacity many, many times and I will always suggest it as a tool when someone is debugging specifically but also for initial development to see how the requests are formed and for sharing responses and requests details so that others can recreate the request that you have sent through right down to the smallest detail
  • Being able to view raw requests for seeing how a request is built in the system
  • Seeing the raw response so that I can share that detail around to different support teams as well as using it to see error messages that sometimes get hidden when redirects happen
  • Pulling out the details on other computers, we have interacted quite heavily on the .NET library available so that we can see when users visit certain web pages, this has given us the ability to monitor different webpages that are visited throughout the day internally without having to use a third-party software
  • Overall this tool has sped up the process of integrating with new systems infinitely
  • The cost of fiddler everywhere which is what we use specifically is nothing in comparison to the cost of dev time saved when debugging processes
  • Being able to send information around so simply to other support teams to show them what responses we are getting along with the request detail have made communications much quicker and saves a lot of time going back and forth discussing what is being done and what the request is being sent
Return to navigation