Where is jq installed on windows

Content on WhatAnswers is provided "as is" for informational purposes. While we strive for accuracy, we make no guarantees. Content is AI-assisted and should not be used as professional advice.

Last updated: April 8, 2026

Quick Answer: jq is typically installed on Windows through package managers like Chocolatey or Scoop, which place it in specific directories. For Chocolatey, it's usually at C:\ProgramData\chocolatey\bin\jq.exe, while Scoop installs it to C:\Users\[username]\scoop\shims\jq.exe. Manual installation involves downloading the 64-bit Windows binary from the official GitHub releases page and placing it in a directory like C:\jq.

Key Facts

jq was first released in 2012 by Stephen Dolan as a command-line JSON processor
The Windows version of jq is typically a single executable file around 2-4 MB in size
Chocolatey, a popular Windows package manager, has over 10,000 packages including jq
jq can process JSON files up to several gigabytes in size efficiently
The official jq GitHub repository has over 28,000 stars as of 2024

Overview

jq is a lightweight, command-line JSON processor that has become an essential tool for developers working with JSON data. Originally created by Stephen Dolan in 2012, jq provides a powerful domain-specific language for filtering, transforming, and manipulating JSON structures. On Windows systems, jq installation follows different patterns than on Unix-like systems, requiring specific approaches for proper setup and execution.

The Windows version of jq is typically distributed as a standalone executable file, usually around 2-4 MB in size. Unlike Linux systems where jq might be installed via native package managers, Windows users often rely on third-party package managers or manual installation methods. Understanding where jq gets installed on Windows is crucial for proper PATH configuration and seamless integration with development workflows and automation scripts.

How It Works

jq installation on Windows involves several methods, each with specific installation locations and configuration requirements.

Package Manager Installation: Using Chocolatey, you install jq with the command 'chocolatey install jq', which places the executable at C:\ProgramData\chocolatey\bin\jq.exe. Chocolatey automatically adds this directory to your system PATH, making jq accessible from any command prompt. This method ensures version management and easy updates through package manager commands.
Scoop Installation: With Scoop, another Windows package manager, you use 'scoop install jq' which installs jq to C:\Users\[username]\scoop\shims\jq.exe. Scoop creates shim executables in this directory that redirect to the actual installation in C:\Users\[username]\scoop\apps\jq. This approach provides isolated installations and easy version switching capabilities.
Manual Installation: For manual installation, you download the 64-bit Windows binary (jq-win64.exe) from the official GitHub releases page, rename it to jq.exe, and place it in a directory like C:\jq or C:\Program Files\jq. You must then manually add this directory to your system PATH environment variable for global accessibility. This method gives you complete control over the installation location and version management.
WSL Integration: Windows Subsystem for Linux users can install jq within their Linux distribution using native package managers like apt-get install jq on Ubuntu. The executable then resides within the WSL file system, typically at /usr/bin/jq, and can be accessed from Windows via WSL integration features or terminal emulators.

Key Comparisons

Feature	Chocolatey Installation	Manual Installation
Installation Location	C:\ProgramData\chocolatey\bin\jq.exe	User-defined (e.g., C:\jq\jq.exe)
PATH Configuration	Automatically managed by Chocolatey	Requires manual PATH editing
Update Management	Automatic via 'choco upgrade jq'	Manual download and replacement
File Size	Approximately 3.2 MB executable	Approximately 3.2 MB executable
Dependencies	Requires Chocolatey framework	Standalone, no dependencies

Why It Matters

Development Efficiency: Proper jq installation on Windows saves developers significant time when working with JSON APIs and configuration files. With jq correctly installed and accessible, developers can process JSON responses from REST APIs, transform configuration files, and automate data extraction tasks without switching between different tools or platforms.
Automation Integration: When jq is properly installed in a known location with correct PATH configuration, it enables seamless integration with Windows batch files, PowerShell scripts, and CI/CD pipelines. This allows for automated JSON processing in build processes, deployment scripts, and data transformation workflows across Windows environments.
Cross-Platform Consistency: Understanding jq installation on Windows helps maintain consistency across development teams using mixed operating systems. By establishing standard installation locations and procedures, teams can share scripts and workflows that work reliably regardless of whether developers are using Windows, macOS, or Linux systems.

The importance of knowing jq installation locations on Windows extends beyond mere convenience to fundamental development practices. As JSON continues to dominate as the data interchange format for web APIs and configuration files, having reliable access to jq becomes increasingly critical. Looking forward, as Windows development environments continue to evolve with WSL2 and improved package management, understanding these installation patterns will remain essential for efficient JSON processing workflows. The ability to quickly filter, transform, and query JSON data directly from the command line represents a significant productivity advantage in modern development environments, making proper jq installation a valuable skill for Windows developers working with data-intensive applications and services.