Check selected documents
Run well-formedness checks across multiple JSON files from the Windows environment and use the editor to investigate a file that fails.
Batch validation and automation
Use the JSON batch validator to check your JSON documents efficiently
Validate a collection of JSON documents for well-formedness or against a JSON Schema, preserve a detailed batch log, and move a tested configuration from the Windows editor to the command line.
- Many inputsCheck a selected collection
- Detailed logKeep every result
- Two stagesConfigure, then automate
Two connected workflows
Configure a batch in the editor, then run it repeatedly
The existing page documents both direct checks from the built-in File Explorer and settings-based command-line processing. The redesign preserves that distinction instead of presenting “batch” as a generic speed claim.
Apply one validation setup
Use a dialog-based configuration to define the batch inputs and schema context, then save the settings for a repeatable run.
Keep a comprehensive log
Write the validation status and diagnostic output to a log so the collection can be reviewed without opening each document manually.
Command-line batch sequence
Move from a configured task to an unattended check
- Open JSONBuddy and create the batch configuration in the documented dialog workflow.
- Choose the JSON inputs and schema context required by the task.
- Save the batch configuration as a settings XML file.
- Pass that settings file to the command-line validator.
- Review the generated log and return to the relevant document or schema when a check fails.
Current-release verification
Re-test the dialog labels, settings-file format, recursive-folder behavior, log location and format, CLI switch, return code, supported JSON Schema drafts, edition requirement, download package, and Windows support before production publication.
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 selecting files, configuring a batch task, and investigating results.
- CLI / CIAvailable for invoking a saved batch configuration from Windows automation, subject to current edition verification.
Related validation paths
Choose a single-document, batch, or large-data check
Use the step-by-step validation page for an interactive document, the CLI hub for direct command invocations, and the large-data solution when streaming-oriented processing is the central requirement.