What JSON type profiling is
A document-wide view of the values your JSON contains
JSON type profiling traverses an entire document and counts every value by its native JSON type. UtilityDock also groups observations by normalized path, making repeated array structures easier to understand without generating a schema.
API inspection
Understand a response shape before writing integration code
Profile a saved API payload to see whether fields consistently contain strings, numbers, booleans, nulls, arrays, or objects. Mixed types at the same normalized path become visible in one expandable report.
Data quality
Spot unexpected nulls and type variation quickly
Type counts and percentages provide a fast baseline for reviewing exports, configuration files, event payloads, and datasets. The report preserves deterministic path order so repeated checks are easy to compare.
Schema understanding
Learn the observed structure without inferring rules
Use the path summaries to understand the document before drafting a JSON Schema or mapping data into another system. This profiler reports what is present; it does not claim what should be required.
Examples
Turn common JSON questions into a compact report
| Question | Report signal |
|---|---|
| Are IDs numeric or textual? | Type mix at $.items[*].id |
| How much data is null? | Global null count and percentage |
| How complex is the payload? | Object, array, property, and depth totals |
Data Toolkit
Continue across every UtilityDock capability
FAQ
Questions about profiling JSON types
Does UtilityDock upload or store my JSON?
No. Your files never leave your computer. Validation, type analysis, preview, copying, and report creation all happen locally inside your browser.
What values are included in type counts?
The profiler counts the root value, every object and array, and every string, number, boolean, and null anywhere in the document.
What does total properties mean?
Total properties is the number of object keys across the document. Array items are values, not object properties.
Why do array paths use [*]?
The wildcard groups the same field across every array item, so repeated structures appear as one deterministic path summary.
Does this tool generate or validate a schema?
No. Version 1 validates JSON syntax and reports observed value types. It does not infer schemas, apply corrections, or call APIs.