XSD Schema Viewer

XSD (XML Schema Definition) files describe the shape, allowed values, and relationships of XML documents. They answer: Which elements are allowed? In what order? Which are optional? What data types and restrictions (patterns, enumerations) apply? If you have ever opened a large schema in a plain text editor and scrolled endlessly trying to trace one referenced type to another, you know why this viewer exists.

This tool loads an XSD directly in your browser (no upload to a server) and gives you an interactive map of types. Complex types show their child elements, attributes and occurrence constraints. Simple types show their base type plus enumerations, patterns, length or other facets. Jumping between referenced types is a click instead of a grep.

It is especially handy when working with large vendor schemas (payment gateways, e‑invoicing standards, healthcare, geospatial) where nesting depth and reuse quickly become confusing.

1. Load a schema: Click “Open XSD File” or paste/replace the sample in the editor.
2. Let it parse: The type list populates instantly; errors (if any) stay local and never leave your machine.
3. Search or filter: Use the search box to jump to a type by name or documentation snippet. Filter between complex and simple types to reduce noise.
4. Drill in: Click a type. Elements, attributes, restrictions and occurrence bounds are laid out. Click a referenced type name to jump again—breadcrumb builds automatically.
5. Navigate back: Use the breadcrumb or Back button to retrace steps instead of scrolling aimlessly.
6. Tweak & re-parse: Edit the XSD in the Monaco editor; the explorer refreshes so you can iterate on design changes.
7. Export: Use Download when you are satisfied, or Reset to go back to the sample for experimentation.

Quick recognition guide

• complexType: Structure (sequence / choice) + attributes.
• simpleType: Base type plus restriction facets (enumeration, pattern, min/max, length).
• Occurrence: The e.g. 0..1, 1..∞ range shows optional vs repeated elements at a glance.

Tip: If you only know an element name that appears inside a complex type, search it—matching documentation or type names still narrow the list quickly.

Practical advantages

• Zero upload risk: Parsing happens in the browser—safe for proprietary partner schemas.
• Instant cross‑type jumps: No manual searching for a referenced type name; one click.
• Breadcrumb memory: Avoid losing your place in deep nesting chains.
• Visual occurrence bounds: Spot optional collections vs required singletons immediately.
• Live iteration: Adjust patterns/enums and re‑parse without context switching tools.

Common pain points solved

• “Where is this type defined?” → Click the reference; no grep needed.
• “Is this element required?” → Check the occurrence (minOccurs / required attribute) tag next to it.
• “What are valid values?” → Enumerations + patterns surfaced for simple types.
• “Did I break something?” → Re‑parse; an empty or reduced type list signals the edit issue immediately.

When another approach is better

If you need full schema validation against instance XML documents, use an XML linter or xmllint --schema. This viewer is focused on exploration, understanding and design iteration—not instance validation.

Roadmap ideas

Planned: multi‑file include/import support, diff mode (before vs after edit), instance XML preview generation, and export of a type dependency graph. Hit the feedback button if one should jump the queue.