curl-impersonate

[!NOTE] This is an active fork of curl-impersonate. With the following enhancements:

1. Encrypted Client Hello(ECH) support introduced in Chrome 119.
2. ZSTD compression support introduced in Chrome 123.
3. X25519Kyber768/X25519MLKEM curves introduced in Chrome 124 and 130.
4. More options for impersonating Akamai http/2 fingerprints, especially for Safari.
5. Based on curl 8.21.0 in curl-impersonate 2.0.0.
6. Ability to change extension orders and enable/disable TLS grease.
7. Single binary to support Chrome, Safari and Firefox.
8. Built with http/3 enabled, http/3 and quic fingerprints are also supported.
9. A user-friendly Python binding: curl_cffi.
10. A user-friendly Nodejs TypeScript binding: impers.
11. More prebuilt binaries, including Windows, Arm, and even RISC-V!
12. Commercial support at impersonate.pro.

[!IMPORTANT] The current stable release is curl-impersonate 2.0.0, based on curl 8.21.0. See the release page for release notes and downloads.

A special build of curl that can impersonate the four major browsers: Chrome, Edge, Safari and Firefox. curl-impersonate is able to perform TLS and HTTP handshakes that are identical to that of a real browser.

curl-impersonate can be used either as a command line tool, similar to the regular curl, or as a library that can be integrated instead of the regular libcurl. See docs.

Documentation

Documentation is available at https://curl-impersonate.readthedocs.io/

Why?

When you use an HTTP client with a TLS website, it first performs a TLS handshake. The first message of that handshake is called Client Hello. The Client Hello message that most HTTP clients and libraries produce differs drastically from that of a real browser.

If the server uses HTTP/2, then in addition to the TLS handshake there is also an HTTP/2 handshake where various settings are exchanged. The settings that most HTTP clients and libraries use differ as well from those of any real browsers.

For these reasons, some web services use the TLS and HTTP handshakes to fingerprint which client is accessing them, and then present different content for different clients. These methods are known as TLS fingerprinting and HTTP/2 fingerprinting respectively. Their widespread use has led to the web becoming less open, less private and much more restrictive towards specific web clients.

With the modified curl in this repository, the TLS and HTTP handshakes look exactly like those of a real browser.

How?

To make this work, curl was patched significantly to resemble a browser. Specifically, The modifications that were needed to make this work:

• Compiling with BoringSSL, Google's TLS library, which is used by Chrome and Safari.
• Modifying the way curl configures various TLS extensions and SSL options.
• Adding support for new TLS extensions.
• Changing the settings that curl uses for its HTTP/2 connections.
• Running curl with some non-default flags, for example --ciphers, --curves and some -H headers.

The resulting curl looks, from a network perspective, identical to a real browser.

Read the original technical description in the blog posts: part a, part b. Much more has been added since then, but you get the general ideas :P.

Supported browsers

The following browsers can be impersonated. For a full list of browser profiles, visit the docs.

Notes:

1. Chromium-based browsers all share the same fingerprints, except for the User-Agent header and sec-ch-ua-platform header. They will not be updated unless this assumption changed. Use your own header if you need to impersonate Edge, Chrome Android etc.
2. The original Safari fingerprints in the upstream fork are not correct.
3. The version postfix -a(e.g. chrome133a) means that this is an alternative version, i.e. the fingerprint has not been officially updated by browser, but has been observed because of A/B testing.

This list is also available in the browsers.json file.() Needs to be updated.

Install

The simplest way is to download the prebuilt binaries from the release page. If you want to build by yourself, please refer to INSTALL.md and docs/install.rst.

You can also use the following docker images:

• lexiforest/curl-impersonate
• lexiforest/curl-impersonate:alpine

Basic usage

For each supported browser there is a wrapper script that launches curl-impersonate with all the needed headers and flags. For example:

curl_chrome123 https://www.example.com

You can add command line flags and they will be passed on to curl. However, some flags change curl's TLS signature which may cause it to be detected.

To check the fingerprints are correct:

curl_firefox133 https://tls.browserleaks.com/json

Please note that the wrapper scripts use a default set of HTTP headers. If you want to change these headers, you may want to modify the wrapper scripts to fit your own purpose.

See the docs for more options, including using libcurl-impersonate as a library.

Repository Contents

This repository contains these folders:

• patches - Patches for building curl-impersonate.
  • curl.patch - The main patch that makes curl use the same TLS extensions as browsers. Also makes curl compile statically with libnghttp2 etc.
  • boringssl.patch - The boringssl patch that tweaks boringssl behaviors to the same as browsers.
• bin - Shortcut scripts for easier use.
  • curl_chrome110, curl_chrome124 - Wrapper scripts that launch curl-impersonate with the correct flags.
• win - Scripts for building the Windows version of curl-impersonate, which is quite different from *nix.
  • win/bin - Shortcut scripts for easier use on Windows.
• zigshim - We use the awesome zig toolchain to bring curl-impersonate to more archs on Linux.
• docker - Debian and alpine dockerfiles for this project.

Other files of interest:

• tests/signatures - YAML database of known browser signatures that can be impersonated.

Contributing

If you'd like to help, please check out the open issues in the origional repo and open issues here. You can open a pull request with your changes. Note that some of the upstream issues have been fixed.

This repository contains the build process for curl-impersonate. The actual patches to curl are maintained in a separate repository forked from lwthiker's fork of the upstream curl. The changes are maintained in the impersonate-chrome branch.

You may also need the forked and patched BoringSSL.

Acknowledgements

• Special thanks to @bjia56 for making cross compiling possible.
• Special thanks to @smaug2309 and @afulsamet for bring back the Windows build.
• Special thanks to @penumbra-x for the boringssl patch on firefox.

Sponsors

Bypass Cloudflare with API

Yescaptcha is a proxy service that bypasses Cloudflare and uses the API interface to obtain verified cookies (e.g. cf_clearance). Click here to register: https://yescaptcha.com/i/stfnIO

Hyper Solutions

TLS fingerprinting alone isn't enough for modern bot protection. Hyper Solutions provides the missing piece - API endpoints that generate valid antibot tokens for:

Akamai • DataDome • Kasada • Incapsula

No browser automation. Just simple API calls that return the exact cookies and headers these systems require.

🚀 Get Your API Key | 📖 Docs | 💬 Discord

Recall.ai - API for meeting recordings

If you’re looking for a meeting recording API, consider checking out Recall.ai, an API that records Zoom, Google Meet, Microsoft Teams, in-person meetings, and more.

Residential Proxies

Thordata: A reliable and cost-effective proxy service provider. One-click collection of public network data, providing enterprises and developers with stable, efficient, and compliant global proxy IP services. Register for a free trial of residential proxies and receive 2000 free SERP API calls.