JSON Schema multi-file bundle
ClientPaste a primary schema and optional extra JSON files with logical names (for example common.json). $ref values like other.json#/definitions/Foo resolve against those pastes—nothing is fetched over the network.
Learn more: multi-file vs single-file $ref
Combine a primary JSON Schema with additional named pastes so cross-file `$ref` values (for example `shared.json#/definitions/Id`) can be expanded in the browser without fetching URLs.
Why not use HTTP $ref?
Fetching arbitrary schema URLs from the browser hits CORS and privacy limits. Pasting every fragment you need keeps resolution deterministic and local—the same trade-off as the single-file expand tool, extended to multiple named documents.
Matching names
The logical file label must match the path used in `$ref` (often a basename like `types.json`). If your repo uses folders, align the label with what appears in the reference string.
Bundle pasted schemas
?
Paste a primary schema plus optional named fragments. $ref values like types.json#/definitions/Person resolve against the matching fragment name—no HTTP fetch, so CORS does not apply.
Same-document #/… refs behave like the $ref expand tool. Remote URLs are not downloaded and stay as $ref.
Common use cases
- Ship one inlined schema to a codegen tool that does not resolve multi-file $ref.
- Preview the merged shape of OpenAPI-adjacent fragments after copying them from a repo.
- Debug why a validator fails by expanding refs across hand-pasted files.
Common mistakes to avoid
Expecting remote $ref to load
http(s) $ref targets are left as references. Only fragments you paste into this page participate.
Filename mismatch
The logical name must match the $ref path (e.g. common.json). Try the basename if paths differ.
FAQ
How is this different from $ref expand?
The expand tool only follows #/ pointers inside one paste. This page adds named extra files so cross-file refs can resolve without HTTP.
Common search terms
Phrases people search for that match this tool. See the full long-tail keyword index.
- json schema bundle $ref multiple files
- inline json schema refs without fetch
- merge json schema files browser
- resolve local json schema $ref
More tools
Related utilities you can open in another tab—mostly client-side.
JSON Schema validate
ClientValidate JSON against a schema, infer draft-07 schema from data—Ajv in browser.
JSON Schema $ref expand
ClientInline same-document JSON Schema $ref (#/definitions, #/components)—no remote fetch, local only.
JSON → OpenAPI draft
ClientTurn sample JSON into a minimal OpenAPI 3 paths entry with an inferred schema—YAML or JSON output.
JSON formatter
ClientJSON format online: pretty-print, minify, validate, escape, download .json.