curl user survey 2025 analysis

I’m pleased to announce that once again I have collected the results, generated the graphs and pondered over conclusions to make after the annual curl user survey.

Get the curl user survey 2025 analysis here

Take-aways

I don’t think I spoil it too much if I say that there aren’t too many drastic news in this edition. I summed up ten key findings from it, but they are all more or less expected:

  1. Linux is the primary curl platform
  2. HTTPS and HTTP remain the most used protocols
  3. Windows 11 is the most used Windows version people run curl on
  4. 32 bit x86 is used by just 7% of the users running curl on Windows
  5. all supported protocols are used by at least some users
  6. OpenSSL remain the most used TLS backend
  7. libssh2 is the most used SSH backend
  8. 85% of respondents scored curl 5 out of 5 for “security handling”
  9. Mastodon is a popular communication channel, and is wanted more
  10. The median used curl version is just one version away from the latest

On the process

Knowing that it is quite a bit of work, it took me a while just to get started this time – but when I finally did I decided to go about it a little different this year.

This time, the twelfth time I faced this task, I converted the job into a programming challenge. I took it upon me to generate all graphs with gnuplot and write the entire document using markdown (and write suitable glue code for everything necessary in between). This way, it should be easier to reuse large portions of the logic and framework for future years and it also helped me generate all the graphs in more consistent and streamlined way.

The final report could then eventually be rendered into single page HTML and PDF versions with pandoc; using 100% Open Source and completely avoiding the use of any word processor or similar. Pretty nice.

As a bonus, this document format makes it super flexible and easy should we need to correct any mistakes and generate updated follow-up versions etc in a very clean way. Just like any other release.

Get the curl user survey 2025 analysis here

A website section

It also struck me that we never actually created a single good place on the curl website for the survey. I thus created such a section on the site and made sure it features links to all the previous survey reports I have created over the years.

That new website section is what this blog post now points to for the 2025 analysis. Should thus also make it easier for any curious readers to find the old documents.

Get the curl user survey 2025 analysis here

Enjoy!

7 thoughts on “curl user survey 2025 analysis”

  1. > When the survey went up, curl 8.13.0 was the latest published release, even if there was an rc build of 8.14.0 out (which many people mentioned to me they actually used but could select in the survey).

    The sentence in parentheses seems to be missing a “not” in “could not”.

      1. Howdy,

        I didn’t get any notice that there was a survey about curl, I would have loved to give you my own two cents.

        I have been a LONG time user of curl on multiple Unix platforms as well as windoze platforms. It’s great!

        I do a lot of website scrubbing and always have been blocked by overly aggressive authentication schemes. As you know, web servers can get a LOT of information about the originating system and can disallow web crawlers. I suspect that it has something to do with java-script but wouldn’t bet money on it.

        Best regards and THANKS for the cool code!

        George…

        1. @George: as mentioned in the report, we informed people about the survey over all the possible channels we could. We can’t do more!

          On servers blocking curl etc: these days the most effective ways to block anything that isn’t a “plain browser” involve TLS fingerprinting but adding JavaScript challenges to the mix is probably common as well.

  2. It would be nice to have the HTML version browsable online, not just as a zip download.

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.

This site uses Akismet to reduce spam. Learn how your comment data is processed.