How to Download ChromeDriver for Windows, Mac, and Linux (Step-by-Step Guide)

Introduction

If you are venturing into Selenium automation or performing browser testing, one tool you absolutely cannot miss is ChromeDriver. ChromeDriver acts as a bridge between your Selenium scripts and the Google Chrome browser, enabling seamless automation of web tasks.

Whether you are a beginner exploring automated testing or a professional managing complex browser-based workflows, having a correctly installed ChromeDriver ensures that your scripts run smoothly without unexpected errors.

In this comprehensive guide, we will take you through a step-by-step process to download and set up ChromeDriver for Windows, Mac, and Linux. Along the way, we’ll provide:

• Helpful tips to avoid common mistakes
• Troubleshooting advice for typical issues
• Verification steps to ensure your setup works perfectly

By the end of this guide, even if you are a first-time visitor, you will confidently have ChromeDriver ready to support all your automation projects.

Table of Contents

• What is ChromeDriver and Why You Need It
• Step 1: Check Your Google Chrome Version
• Step 2: Visit the Official ChromeDriver Download Page
• Step 3: Download ChromeDriver for Your Operating System
• Step 4: Extract and Set Up ChromeDriver
• Step 5: Add ChromeDriver to System Path
• Step 6: Verify Your ChromeDriver Installation
• Common ChromeDriver Errors and How to Fix Them
• Best Practices for Using ChromeDriver in Automation
• Conclusion
• FAQs

What is ChromeDriver and Why You Need It

ChromeDriver is a lightweight executable that acts as a bridge between the Selenium WebDriver and the Google Chrome browser. It allows your automation scripts to control Chrome, simulating human interactions like clicking buttons, filling forms, navigating web pages, and much more.

Why ChromeDriver is Important

Without ChromeDriver, Selenium cannot communicate with Chrome effectively. It ensures that your scripts:

• Run reliably without browser-related errors
• Automate repetitive web tasks efficiently
• Execute browser-based tests for web applications

Common Use Cases

ChromeDriver is widely used in:

• Automation: Automating login flows, form submissions, and repetitive browsing tasks.
• Testing: Running end-to-end tests to verify website functionality.
• Web Scraping: Extracting data from websites where traditional scraping methods fail.

Importance of Version Matching

One crucial point to remember is that the ChromeDriver version must match your installed Chrome browser version. Using mismatched versions can lead to errors like “session not created” or “Chrome not reachable”. Always check your Chrome version before downloading ChromeDriver.

Security Note

Always download ChromeDriver from the official ChromeDriver website. Avoid third-party sources, as they may contain outdated versions or malware that can compromise your system.

Step 1: Check Your Google Chrome Version

Before downloading ChromeDriver, it is essential to know your current Google Chrome version. ChromeDriver must match this version to work correctly with Selenium.

How to Check Chrome Version on Windows

1. Open the Google Chrome browser.
2. Click on the three vertical dots in the top-right corner.
3. Navigate to Help → About Google Chrome.
4. You will see the version number displayed (e.g., 118.0.5993.90).

How to Check Chrome Version on Mac

1. Open Chrome on your Mac.
2. Click on Chrome in the top menu bar.
3. Select About Google Chrome.
4. Your Chrome version will appear in a popup window.

How to Check Chrome Version on Linux

1. Open Chrome.
2. Click on the three vertical dots → Help → About Google Chrome.
3. The version number will be displayed on the screen.
4. Alternatively, you can run google-chrome --version in the terminal.

Why Matching the ChromeDriver Version Matters

If your ChromeDriver version does not match your installed Chrome version, you may encounter errors such as:

• “Session not created”
• “Chrome not reachable”
• Automation scripts failing unexpectedly

Ensuring version compatibility is the first step towards a smooth automation setup.

Pro Tips for Updates

• Regularly check for Chrome updates and update ChromeDriver accordingly.
• If working on multiple machines, note the Chrome version to maintain consistent automation environments.
• Use a dedicated folder for ChromeDriver downloads to avoid confusion between versions.

Step 2: Visit the Official ChromeDriver Download Page

After checking your Google Chrome version, the next step is to download the matching ChromeDriver. It is crucial to always use the official source to ensure safety and compatibility.

Official ChromeDriver Download Link

Visit the official ChromeDriver website: https://sites.google.com/chromium.org/driver/

This site provides the latest stable releases, archived versions, and instructions for Windows, Mac, and Linux users.

Why You Should Avoid Third-Party Sites

• Third-party websites may provide outdated ChromeDriver versions that are incompatible with your browser.
• There is a risk of malware or unwanted software being bundled with the download.
• Official downloads ensure you get a version that is tested and secure for Selenium automation.

How to Choose the Right ChromeDriver Version

The official website provides several types of releases:

• Latest Release: The newest version available, often includes the latest features and fixes. Ideal if your Chrome browser is updated to the latest version.
• Stable Release: A tested version known for reliability. Recommended for production automation projects.
• Archived Versions: Older versions available for download. Useful if you are using an older Chrome browser or maintaining legacy scripts.

Tip: Always match your ChromeDriver version exactly with your Chrome browser version to avoid errors during automation.

Step 3: Download ChromeDriver for Your Operating System

Now that you know your Chrome version and have accessed the official ChromeDriver page, it’s time to download the correct version for your operating system. Follow the instructions below for Windows, Mac, and Linux.

Windows

1. On the ChromeDriver download page, click on the ZIP file link for Windows.
2. Save the ZIP file to your preferred location, e.g., Downloads folder.
3. Right-click the ZIP file and select Extract All to extract it to a dedicated folder, e.g., C:\ChromeDriver.
4. Keep this folder organized as it will be needed for setting up the system path in later steps.

Mac

1. Download the ZIP file for Mac from the official ChromeDriver page.
2. Extract the file to a dedicated folder, e.g., /Users/YourUsername/ChromeDriver.
3. Open Terminal and navigate to the folder where ChromeDriver is extracted.
4. Run the command below to give executable permission:

chmod +x chromedriver

Linux

1. Download the ZIP or tar.gz file suitable for your Linux distribution.
2. Extract it to a folder, e.g., /usr/local/bin or a dedicated Selenium folder.
3. Set executable permission using:

chmod +x chromedriver

Optionally, move ChromeDriver to a folder included in your $PATH for easier access.

Tips for Folder Organization and Naming

• Use a dedicated folder for all Selenium drivers to avoid confusion with multiple versions.
• Include version numbers in folder names, e.g., C:\ChromeDriver\118.0.5993, for clarity.
• Keep folders short and simple to avoid path issues, especially on Linux or Mac.
• Maintain consistent folder structure across different machines if working in a team.

Step 4: Extract and Set Up ChromeDriver

After downloading the ChromeDriver ZIP file for your operating system, the next step is to extract it and place it in a proper folder for easy access and system configuration.

Extracting ZIP Files

• Windows: Right-click the downloaded ZIP file and select Extract All. Choose a dedicated folder, e.g., C:\SeleniumDrivers\ChromeDriver.
• Mac: Double-click the ZIP file or use Terminal with the command unzip chromedriver_mac64.zip to extract it.
• Linux: Use Terminal to extract the ZIP/tar.gz file, e.g., unzip chromedriver_linux64.zip -d ~/chromedriver or tar -xvzf chromedriver_linux64.tar.gz -C ~/chromedriver.

Recommended Folder Locations per OS

• Windows: C:\SeleniumDrivers\ChromeDriver or C:\ChromeDriver
• Mac: /Users/YourUsername/ChromeDriver
• Linux: /usr/local/bin or ~/chromedriver

Why a Dedicated Folder is Helpful

• Keeps all driver versions organized, especially if you are working on multiple Selenium projects.
• Makes adding the folder to your system PATH easier and reduces errors.
• Prevents accidental deletion or overwriting of ChromeDriver files.

Tips for Multiple Selenium Projects

• Create a parent folder like C:\SeleniumDrivers and have subfolders for ChromeDriver, GeckoDriver, EdgeDriver, etc.
• Include version numbers in folder names, e.g., C:\SeleniumDrivers\ChromeDriver\118.0.5993, so scripts point to the correct version.
• If working on multiple machines or a team project, keep the folder structure consistent across all environments.

Step 5: Add ChromeDriver to System Path

Adding ChromeDriver to your system PATH allows you to run it from any terminal or command prompt without specifying the full folder path. This is essential for seamless Selenium automation.

Windows

1. Search for Environment Variables in the Start menu and open Edit the system environment variables.
2. Click on Environment Variables at the bottom of the System Properties window.
3. Under System variables, select Path and click Edit.
4. Click New and add the folder path where ChromeDriver is located (e.g., C:\SeleniumDrivers\ChromeDriver).
5. Click OK to save all changes.
6. Verify in Command Prompt:

chromedriver --version

Mac

1. Open Terminal.
2. Edit your shell configuration file (.zshrc for zsh or .bash_profile for bash):

nano ~/.zshrc
export PATH=$PATH:/Users/YourUsername/ChromeDriver
source ~/.zshrc

Now you can verify by running:

chromedriver --version

Linux

1. Open Terminal.
2. Edit your shell configuration file (.bashrc or .bash_profile):

nano ~/.bashrc
export PATH=$PATH:/home/username/chromedriver
source ~/.bashrc

Verify installation:

chromedriver --version

Common Mistakes and Fixes

• Path not recognized: Ensure you added the correct folder containing chromedriver.exe (Windows) or chromedriver (Mac/Linux).
• Wrong shell file edited: Check whether you are using bash or zsh and edit the correct configuration file.
• Command not found after setup: Run source ~/.zshrc or source ~/.bashrc to apply changes.
• Multiple versions in PATH: Remove older ChromeDriver paths to prevent conflicts.

Step 6: Verify Your ChromeDriver Installation

Once ChromeDriver is installed and added to your system PATH, it’s essential to verify that it works correctly. This ensures your Selenium scripts will run smoothly without errors.

Verify on Windows

1. Open Command Prompt.
2. Type the following command:

chromedriver --version

Expected output: A version number like ChromeDriver 118.0.5993.90. This confirms ChromeDriver is installed and accessible.

Verify on Mac

1. Open Terminal.
2. Type the command:

chromedriver --version

Expected output: The ChromeDriver version, e.g., ChromeDriver 118.0.5993.90.

Verify on Linux

1. Open your terminal.
2. Run:

chromedriver --version

Expected output: The version number confirming successful installation.

Troubleshooting if Version is Not Recognized

• “Command not found” error: Ensure the ChromeDriver folder is correctly added to your system PATH and run source ~/.bashrc or source ~/.zshrc on Mac/Linux.
• Incorrect version displayed: Verify that the downloaded ChromeDriver version matches your Chrome browser version.
• Permission denied (Mac/Linux): Run chmod +x chromedriver to make it executable.
• Multiple versions conflict: Remove old ChromeDriver files from other folders in your PATH.

After successful verification, you are ready to use ChromeDriver in your Selenium automation scripts across all operating systems.

Common ChromeDriver Errors and How to Fix Them

Even with proper installation, you might encounter some common ChromeDriver errors during Selenium automation. Here’s a list of frequent issues and how to fix them:

1. Version Mismatch

Error: “session not created: This version of ChromeDriver only supports Chrome version XXX”

Cause: The ChromeDriver version does not match your installed Chrome browser.

Solution:

• Check your Chrome version (chrome://settings/help).
• Download the matching ChromeDriver version from the official site.
• Replace the old ChromeDriver executable with the new one.

2. Permission Denied (Mac/Linux)

Error: “Permission denied” when trying to run ChromeDriver.

Cause: Executable permission is not set for ChromeDriver.

Solution:

chmod +x /path/to/chromedriver

Then try running chromedriver --version again.

3. Path Not Recognized

Error: “chromedriver is not recognized as an internal or external command”

Cause: ChromeDriver folder is not added to system PATH or incorrect path is used.

Solution:

• Verify the folder containing ChromeDriver is added to the PATH.
• Restart terminal/Command Prompt after updating PATH.
• Remove old paths if multiple versions exist to avoid conflicts.

4. Selenium Errors (“Chrome not reachable”)

Error: “Chrome not reachable” when running Selenium scripts.

Cause: Incompatible ChromeDriver version, outdated Selenium library, or Chrome not properly installed.

Solution:

• Ensure ChromeDriver version matches your Chrome browser.
• Update Selenium to the latest version using pip install --upgrade selenium.
• Check Chrome installation and reinstall if necessary.

Example Scenario

Suppose your Chrome version is 118.0.5993.90, but you accidentally downloaded ChromeDriver 117. Running a Selenium script gives the error “session not created”. By downloading the correct ChromeDriver 118 version and replacing the old one, the script runs successfully.

Best Practices for Using ChromeDriver in Automation

Following best practices ensures smooth Selenium automation and reduces errors. Here are the most recommended practices for using ChromeDriver effectively:

1. Keep ChromeDriver Updated

• Regularly check for Chrome updates and download the corresponding ChromeDriver version.
• Using an outdated ChromeDriver can lead to errors like “session not created” or “Chrome not reachable”.
• Subscribe to official release notes to stay informed about new versions.

2. Use a Dedicated Folder for All Browser Drivers

• Create a parent folder, e.g., C:\SeleniumDrivers or /Users/YourUsername/SeleniumDrivers, to store all browser drivers.
• Organize subfolders for each driver (ChromeDriver, GeckoDriver, EdgeDriver) and include version numbers in folder names.
• This helps avoid confusion when working on multiple projects or with different browser versions.

3. Use Environment Variables Instead of Hardcoding Paths

• Adding ChromeDriver to the system PATH allows scripts to locate the driver automatically.
• Avoid hardcoding full paths in Selenium scripts, which can cause errors when moving scripts between machines.
• Use environment variables for consistent and maintainable automation setups.

4. Test Scripts on a Single Browser Version Before Scaling

• Always test your Selenium scripts on one version of Chrome before running them on multiple machines or browser versions.
• This ensures your automation workflow works correctly and reduces debugging time.

5. Tips for Multi-Project Usage

• Maintain a version log of ChromeDriver for each project to avoid conflicts.
• If working in a team, standardize the folder structure and driver version across all environments.
• Consider using a driver manager library (like webdriver-manager in Python) to automate driver updates and path handling.

Conclusion

Setting up ChromeDriver correctly is the foundation of successful Selenium automation. In this guide, we covered everything you need to get started:

• Checking your Google Chrome version on Windows, Mac, and Linux.
• Downloading ChromeDriver from the official website.
• Extracting the files and setting up a dedicated folder for easy management.
• Adding ChromeDriver to your system PATH for seamless access.
• Verifying the installation and troubleshooting common errors.
• Following best practices to maintain a stable and efficient automation environment.

By following these steps, you can ensure that your Selenium scripts run smoothly and reliably across different operating systems. Proper setup not only saves time but also reduces frustration caused by unexpected errors.

Reminder: Always download ChromeDriver from the official site to avoid outdated versions or potential security risks.

With ChromeDriver correctly installed and configured, you are now ready to automate web tasks, perform browser testing, and build efficient Selenium workflows with confidence.

Frequently Asked Questions (FAQs)

Q1: How do I know which ChromeDriver version to download?

A: Check your Chrome browser version by navigating to Help → About Google Chrome. Then, download the ChromeDriver version that exactly matches your Chrome version from the official site.

Q2: Can I use one ChromeDriver for multiple Selenium projects?

A: Yes, as long as the ChromeDriver version matches the Chrome browser version used in your projects. Using a dedicated folder for all drivers helps manage multiple projects efficiently.

Q3: What should I do if I get a “Permission Denied” error on Mac or Linux?

A: Open Terminal and navigate to the folder containing ChromeDriver. Run the command chmod +x chromedriver to give executable permission. Then verify by running chromedriver --version.

Q4: Why is my Selenium script showing “Chrome not reachable”?

A: This usually occurs when the ChromeDriver version does not match the Chrome browser version, or if Selenium is outdated. Update ChromeDriver to the correct version and upgrade Selenium using pip install --upgrade selenium (for Python users).

Q5: Can I download ChromeDriver from third-party websites?

A: No. Always download ChromeDriver from the official site to avoid security risks, malware, and compatibility issues.

Q6: How can I organize ChromeDriver for multiple operating systems?

A: Maintain separate folders for each OS, e.g., C:\SeleniumDrivers\Windows\ChromeDriver, /Users/YourUsername/SeleniumDrivers/Mac/ChromeDriver, and /usr/local/bin/ChromeDriver for Linux. Include version numbers in folder names for clarity.

Q7: Do I need to update ChromeDriver every time Chrome updates?

A: Yes. ChromeDriver must match the Chrome browser version exactly. Updating ChromeDriver whenever Chrome updates ensures your Selenium scripts continue to work without errors.