FREE BROWSER-LOCAL SCHEMA TOOLS
Validate an Avro schema.
Check a standalone .avsc schema before using it with records. Load a local file, paste schema JSON or try the fictional sample.
Local validation keeps schema contents in your browser. No account or Schema Registry connection is needed.
To inspect records and the schema inside an Avro Object Container File, use the Avro file workspace.
1. Choose or paste an AVSC schema
2. Review syntax and schema errors. 3. Correct the schema and validate again. Validation runs locally; original input stays visible. A valid schema does not establish backward, forward or transitive compatibility. This task accepts schema JSON, rather than Avro container bytes.
Understand the result
This task checks JSON syntax and Avro schema structure, including named references, records, arrays, maps, unions, enums and fixed types supported by the local codec. Correct reported errors and validate again. Unsupported or unresolved types remain errors. Navigate draft schema structure opens recognized source locations while JSON is incomplete; filter paths or page through them without changing your text. This syntax-only outline does not establish Avro validity or compatibility. Find named type links separately validates the complete schema and links recursive or namespace-qualified references to their exact declarations. Aliases do not become reference targets within the same schema. Invalid, duplicate or incomplete source has no named links.
Schema validity and compatibility are different
A valid schema does not prove that a particular record matches it or that it can read records written by another schema. The file workspace offers complete schema analysis in both directions and a separate reader-schema preview against loaded records. A successful sample preview alone is not a backward, forward or transitive compatibility certificate.
Local limits
Files are limited to 1 MiB; pasted schema text to 1 Mi characters. This tool accepts schema JSON, not raw Avro datum streams, container bytes or registry wire-format messages. Draft navigation inspects at most 10,000 syntax events and 128 nested containers, bounds stored paths, and selects at most 4,096 source characters per jump. A partial outline leaves the complete source editable and does not lower the separate validation limits. It does not fetch remote schemas or publish changes.
Review a separate schema draft
Optional assistance is separate from local validation above. Only the goal and schema you explicitly include are sent to OpenRouter and the configured model provider. No OCF records are included automatically. Keep or download a reviewed AVSC draft; this does not rewrite an Avro file or certify compatibility.
This is a separate AVSC draft. It does not replace the file's writer schema or modify records. Include a standalone draft up to 8,000 characters; use complete-schema compatibility review separately. Exact numeric default text is retained. Schema drafts are not automatic browser recovery; download important drafts before closing. Source drafts support up to 1 Mi characters; generated proposals up to 16,000.
Navigate draft schema structure
Syntax-only source locations work while JSON is incomplete. The outline does not validate an Avro schema, resolve named references, change records or enable export. Find named type links separately requires successful local validation. Navigation selects up to 4,096 source characters; the complete draft remains in the text field.
JSON syntax is complete; Avro validity remains unchecked.
Avro schema assistance
Only your prompt and explicitly checked schema context go to OpenRouter and its configured model provider. OCF records are not included automatically. Schema/default validation is local; keeping a reviewed draft does not establish compatibility. Assistance is not configured or the selected model is unavailable.