CLI / CI

Free JSON validator command-line tool for Windows®

Run repeatable JSON syntax and JSON Schema checks from scripts, builds, and CI with valbuddy.exe, then use detailed file, instance, and schema locations to diagnose a failed check.

Review JSONBuddy downloads Explore batch validation

Command Prompt — JSONBuddy validation

C:\> valbuddy.exe -v -verbose -s
  "D:\Examples\Library\library_schema.json"
  "D:\Examples\Library\library.json"
  "D:\Examples\Library\library_invalid.json"

library.json: valid
library_invalid.json: invalid
Required property missing: title
Input location: /bib/book/2

Windows command example and diagnostic shape preserved from the existing production page; re-test exact options and output against the release candidate.

Repeatable JSON checks

Turn an interactive validation rule into an automated gate

The retained command-line workflow accepts one or more JSON or XML inputs, can apply a specific schema, and can emit a fuller diagnostic report for review. This page keeps the established JSON validator, command-line, Windows, CLI, automation, and download intent while separating documented behavior from release-sensitive details.

Validate one file or a set

Pass individual documents directly for well-formedness or schema validation, and keep the input paths visible in the resulting log.

Inspect actionable diagnostics

Use the reported input location and schema location to connect a failed JSON value to the constraint that rejected it.

Reuse a configured batch task

Create a batch configuration in the desktop application, save the settings, and invoke that configuration from automation when the current edition supports it.

Build a batch-validation workflow

Usage pattern

Make validation results useful to both people and pipelines

Choose the JSON documents and the schema or well-formedness check the workflow requires.
Run the command locally with verbose output until the inputs, paths, and diagnostics are understood.
Capture the process return value and preserve the validation log as a build artifact.
Move the tested invocation into a script or CI job and keep product/version context with the configuration.

Documented return-code behavior

The existing production reference documents 0 for success and -1 when an input is invalid, not well-formed, or lacks an assigned schema. Confirm this contract against the current executable before production publication or pipeline adoption.

Release evidence required

The production source lists validation, formatting, minification, JSON Patch, schema-test, large-file, and JSON-to-CSV options with edition qualifiers. Exact switches, availability, license requirements, overwriting behavior, output flags, return codes, package contents, and Windows requirements must be tested and versioned before release.

Platform availability

Choose where to run this workflow

Only platforms supported by approved evidence for this specific workflow are shown. Links are limited to implemented, verified destinations.

Desktop / WindowsAvailable for configuring and testing the interactive workflow on Windows.
CLI / CIFeatured access: valbuddy.exe in the documented Windows portable-package journey.

Continue the automation path

Keep adjacent workflows distinct

Use the batch page for directory and settings-based processing, the large-data page for streaming-oriented validation, and the dedicated conversion page for repeatable XML/JSON transformations. These retained URLs answer separate search and workflow needs.