Skip to content
DoCodeHereDeveloper tools and services

Code editors and AI coding tools · Researched comparison

Best Command Line JSON Processors in 2026

jq is the first pick for most developers. It is the long-standing standard for filtering, transforming and formatting JSON in a shell, and it suits anyone who wants a stable tool with a large body of examples. gojq is a close alternative when you want jq syntax with a single static binary and no C dependencies. dasel suits people who need one tool to query and convert JSON, YAML, TOML and XML.

By · Published 21 Nov 2026

We run no ads and no affiliate links at launch. The order of a list follows our published method.

Prices are the starting prices vendors list publicly. Plans change, so confirm the current price on the vendor page before you buy.

Key takeaways

ToolBest forStandout featureListed starting priceFree plan or trial
1 jqGeneral-purpose JSON filtering and transformation in shell scriptsWidely documented with a large base of examplesFree (open source)Free plan
2 gojqjq-compatible processing in a single static binarySingle binary with no runtime dependenciesFree (open source)Free plan
3 jaqFast jq-style filtering with a focus on correctnessAims for jq compatibility with a Rust implementationFree (open source)Free plan
4 fxInteractive exploration of JSON in the terminalInteractive viewer for navigating large JSON documentsFree (open source)Free plan
5 yqJSON and YAML processing with one jq-style toolHandles JSON and YAML with similar syntaxFree (open source)Free plan
6 daselQuerying and converting JSON, YAML, TOML and XML with one syntaxOne selector syntax across several data formatsFree (open source)Free plan
7 gronMaking JSON greppable as flat assignment statementsTurns nested JSON into flat lines that work with grepFree (open source)Free plan
8 MillerJSON, CSV and tabular data processing in one toolkitHandles JSON alongside CSV, TSV and other record formatsFree (open source)Free plan

How we picked

We selected tools that read JSON from a file or standard input and write results to standard output, so they work in shell pipelines. We checked platform support, licence, distribution method and documented limits on each project's own pages and repository. We did not run benchmarks or surveys. Prices and licences can change, so confirm details on the vendor or project site before you commit.

01

jq

Best for: General-purpose JSON filtering and transformation in shell scripts

jq is a command line JSON processor built around a filter language. You pipe JSON into it and write a filter such as `.items[] | select(.active) | .name` to extract or reshape data. It also pretty-prints and validates JSON, which makes it useful for inspecting API responses and log lines.

It runs on Linux, macOS and Windows, and is packaged by most Linux distributions and Homebrew. The project is open source under the MIT licence. The main limit is the filter language: simple field extraction is quick to learn, but advanced transforms take practice. People who want jq-compatible syntax in a single static binary should look at gojq or jaq instead.

Pros

  • Widely documented with a large base of examples
  • Handles filtering, mapping, reduction and formatting

Cons

  • Filter syntax has a learning curve
  • Windows binaries are not the primary distribution target

Price: Free (open source), as listed by the vendor (jq website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: filter syntax has a learning curve.

Verdict. A sensible pick for general-purpose JSON filtering and transformation in shell scripts.

02

gojq

Best for: jq-compatible processing in a single static binary

gojq is a JSON processor written in Go that implements jq's query language. You use the same filters you would write for jq, and the project documents where behavior differs. Because it compiles to a single static binary, it is easy to drop into containers, CI images and machines where installing jq is awkward.

It runs on Linux, macOS and Windows and is released under the MIT licence. The project notes some intentional differences from jq, so scripts that rely on unusual jq behavior should be tested before switching. Teams already comfortable with jq syntax get the most from it.

Pros

  • Single binary with no runtime dependencies
  • Supports jq syntax plus some extensions

Cons

  • Not a byte-for-byte match for every jq edge case
  • Smaller community than jq

Price: Free (open source), as listed by the vendor (gojq website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: not a byte-for-byte match for every jq edge case.

Verdict. A sensible pick for jq-compatible processing in a single static binary.

03

jaq

Best for: Fast jq-style filtering with a focus on correctness

jaq is a JSON processor that implements jq's language in Rust. It targets the same filter syntax, so existing jq filters often work unchanged. The project maintains a page listing differences from jq, which is worth reading before you migrate scripts.

It runs on Linux, macOS and Windows, and is distributed as a binary and through package managers. The licence is MIT. The main caveat is maturity: jaq has fewer years of production use and a smaller pool of community answers than jq. Developers who need the broadest compatibility should stay with jq; those who want a Rust-native implementation can evaluate jaq.

Pros

  • Aims for jq compatibility with a Rust implementation
  • Documents its differences from jq clearly

Cons

  • Younger project with fewer examples online
  • Some jq features are intentionally unsupported

Price: Free (open source), as listed by the vendor (jaq website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: younger project with fewer examples online.

Verdict. A sensible pick for fast jq-style filtering with a focus on correctness.

04

fx

Best for: Interactive exploration of JSON in the terminal

fx is a command line JSON viewer and processor. Run it with a JSON file or piped input and it opens an interactive terminal view where you can expand and collapse nodes and follow paths. It also accepts a function argument for non-interactive transforms.

It is distributed through npm and as a standalone binary, and runs on Linux, macOS and Windows. The project is MIT licensed. The interactive mode is the main draw; for repeatable scripted transforms, jq-style filters are usually a better fit. Developers who spend time reading unfamiliar API payloads will get the most value from it.

Pros

  • Interactive viewer for navigating large JSON documents
  • Can also run as a non-interactive processor

Cons

  • Requires a Node.js install for the npm package
  • Less suited to scripted pipelines than jq

Price: Free (open source), as listed by the vendor (fx website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: requires a Node.js install for the npm package.

Verdict. A sensible pick for interactive exploration of JSON in the terminal.

05

yq

Best for: JSON and YAML processing with one jq-style tool

yq is a command line processor for YAML, JSON and XML. It uses jq-like expressions, so you can select and transform JSON with syntax close to jq's, and convert between JSON and YAML in the same command. That makes it useful in repositories where both formats appear.

It runs on Linux, macOS and Windows as a single Go binary, and is released under the MIT licence. Note that more than one project is called yq; this entry refers to the Go version by Mike Farah, which has different flags from the Python one. Teams that only process JSON may prefer jq, while anyone moving between JSON and YAML will find yq saves steps.

Pros

  • Handles JSON and YAML with similar syntax
  • Single Go binary with no dependencies

Cons

  • Not the same project as the Python-based yq
  • YAML-specific flags add options to learn

Price: Free (open source), as listed by the vendor (yq website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: not the same project as the Python-based yq.

Verdict. A sensible pick for JSON and YAML processing with one jq-style tool.

06

dasel

Best for: Querying and converting JSON, YAML, TOML and XML with one syntax

dasel is a command line tool for querying and modifying data in JSON, YAML, TOML and XML. You use a selector such as `.users.all().name` and can read from one format and write to another. It is useful when a project mixes config formats and you want one tool for all of them.

It runs on Linux, macOS and Windows, and is distributed as a binary and through package managers. The project is MIT licensed. The main cost is learning a selector syntax that is not jq's, so existing jq filters will not carry over. Developers who work mostly in JSON should weigh that against jq's larger ecosystem.

Pros

  • One selector syntax across several data formats
  • Converts between formats in a single command

Cons

  • Selector syntax differs from jq, so filters must be rewritten
  • Smaller community than jq

Price: Free (open source), as listed by the vendor (dasel website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: selector syntax differs from jq, so filters must be rewritten.

Verdict. A sensible pick for querying and converting JSON, YAML, TOML and XML with one syntax.

07

gron

Best for: Making JSON greppable as flat assignment statements

gron transforms JSON into a series of flat assignment statements, one per line, so you can search nested structures with grep and read paths at a glance. Running gron with the ungron option converts the flat form back into JSON.

It runs on Linux, macOS and Windows and is written in Go. The project is MIT licensed. It is not a general transformation language: it does not replace jq for reshaping data. It is a focused tool for exploring large or unfamiliar JSON, and it pairs well with grep and other line-based utilities.

Pros

  • Turns nested JSON into flat lines that work with grep
  • Can convert the flat form back to JSON

Cons

  • Output is not JSON, so it suits inspection more than transformation
  • Limited to flattening and reversal

Price: Free (open source), as listed by the vendor (gron website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: output is not JSON, so it suits inspection more than transformation.

Verdict. A sensible pick for making JSON greppable as flat assignment statements.

08

Miller

Best for: JSON, CSV and tabular data processing in one toolkit

Miller (mlr) is a command line tool for processing record data, including JSON, CSV and TSV. It reads JSON, applies verbs such as filter, cut and sort, and writes JSON or another format. It suits pipelines that move between JSON and tabular data.

It runs on Linux, macOS and Windows and is released under a BSD-style licence. The verb-based command style is different from jq's filter language, so there is a learning curve, but the verbs are readable and chain naturally. Developers who mostly transform JSON in place will find jq more direct; those who mix JSON with CSV exports will get more from Miller.

Pros

  • Handles JSON alongside CSV, TSV and other record formats
  • Verb-based commands are easy to chain

Cons

  • Verb syntax differs from jq filters
  • More concepts to learn than a single-purpose tool

Price: Free (open source), as listed by the vendor (Miller website). Confirm the current plan price before you buy.

Skip it if this limit matters to you: verb syntax differs from jq filters.

Verdict. A sensible pick for JSON, CSV and tabular data processing in one toolkit.

Who should use what

If you write shell scripts that filter API responses, start with jq and keep gojq as a fallback for containers where a static binary is easier. If you need to convert between JSON and YAML in the same repository, use yq. If your project mixes JSON, YAML, TOML and XML, dasel gives you one selector syntax. If you mostly read unfamiliar payloads by hand, fx and gron make exploration faster than writing filters. For pipelines that combine JSON with CSV, Miller covers both formats.

What to check before you buy

FAQ

Do these tools send my JSON anywhere?

No. All eight run locally in your terminal and read from files or standard input. Nothing is uploaded to a third-party web page. That matters when the JSON contains tokens, customer records or production data. Avoid pasting such data into online formatters; use a local command line tool instead.

Is jq still the default choice?

For most shell scripting, yes. jq has the largest body of examples and the most third-party tutorials. gojq and jaq implement the same language and are worth considering when you need a single static binary or a Rust implementation. Test your filters before switching, because behavior differs in some edge cases.

Can I convert JSON to YAML on the command line?

Yes. yq and dasel both read JSON and write YAML. yq uses jq-like expressions and is a single Go binary. dasel uses its own selector syntax and also handles TOML and XML. Pick based on which formats you need and whether you want to reuse jq-style filters.

What is the difference between gron and jq?

gron flattens JSON into one assignment per line so you can search it with grep, and it can convert the flat form back to JSON. jq is a full transformation language for filtering and reshaping. They solve different problems, and many developers use both: gron to explore, jq to transform.

Are these tools free?

Yes. All eight are open source and free to use. Licences vary: jq, gojq, jaq, fx, yq and dasel use the MIT licence, gron uses MIT, and Miller uses a BSD-style licence. Check the repository for the exact terms if you plan to redistribute a tool inside a product.

Sources we checked

  1. jq (official site)
  2. Miller (official site)
  3. Miller (official site)
  4. Miller (official site)
  5. Miller (official site)
  6. Miller (official site)
  7. Miller (official site)
  8. Miller (official site)

Change log. First published 21 Nov 2026.