URL Encoder & Decoder
Percent-encode URLs and query strings, or decode them back to plain text.
Validate a JSON document against a draft-07 schema and see every failure by path.
The JSON Schema Validator checks a document against a draft-07 schema and reports every failure with the path that failed and the rule it broke, rather than one vague message about the whole file.
Syntax validation only tells you a document parses. Schema validation tells you it is the right document: the fields you need are present, the types are what you expect, the numbers are in range and the strings match their patterns.
Paste a schema and a document and every failure is listed with the path that failed and the rule it broke, rather than one vague message about the whole file. The supported keyword set is the one hand-written schemas use: type, required, properties, patternProperties, additionalProperties, items, enum, const, minimum and maximum with their exclusive forms, multipleOf, minLength, maxLength, pattern, format, minItems, maxItems, uniqueItems, minProperties, maxProperties, allOf, anyOf, oneOf, not, and local $ref pointers.
Each error names the path, such as $.items[2].price, and the constraint it violated — not just that the document is invalid.
type, required, properties, patternProperties, items, enum, const, numeric and string bounds, uniqueItems, allOf, anyOf, oneOf, not and local $ref.
date, time, date-time, email, hostname, ipv4, ipv6, uri and uuid are checked; unknown formats are accepted and ignored as the spec allows.
Edit the schema or the document and validation re-runs immediately, which makes tightening a schema an interactive process.
Remote $ref URLs are not fetched by design. Local pointers resolve normally, so inline your definitions and nothing leaves the tab.
A draft-07 JSON Schema goes in the schema box.
The JSON you want checked goes in the document box.
Each one names the path and the rule, so you know which field and which constraint.
Both boxes are live, so corrections re-validate as you type.
Draft-07 and the keywords it shares with later drafts. That covers essentially every hand-written schema; the 2020-12 dynamic reference keywords are not implemented.
No — that would mean fetching a third-party URL, which this site does not do. Local pointers such as #/definitions/address resolve normally, so inline your definitions.
date, time, date-time, email, hostname, ipv4, ipv6, uri and uuid. Other format values are accepted and left unchecked, which is what the specification permits.
Because the schema sets it to false and your document has a key the schema does not name. The failure message names the offending key.
What people who use the JSON Schema Validator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the JSON Schema Validator. It takes half a minute and no account.
Write the first reviewPercent-encode URLs and query strings, or decode them back to plain text.
Build media queries with framework breakpoints and modern features.
Turn any text into a JSON string literal, or unwrap one back to plain text.
Render Markdown to clean HTML, with tables, task lists and fenced code.
Find the MIME type for any file extension, or the extensions for a type.
Compute a CRC-32 checksum in hex, decimal and signed form.
Find what runs on a port, with a note on whether it should be exposed.
Generate plausible addresses in the format each country actually uses.