JSON-LD to Expanded Converter
Paste a JSON-LD document to expand it, removing context-dependent shortcuts and rewriting every property and type as a full, absolute IRI. Free online developer tool.
Paste JSON-LD Document
Expanded JSON-LD
Expanded output will appear here...
Free JSON-LD to Expanded Converter
Paste a JSON-LD document to expand it — removing every context-dependent shortcut and rewriting all properties and types as full, absolute IRIs. Runs entirely in your browser using the official jsonld.js reference implementation.
How to Use It
Paste any JSON-LD document into the input box, or click "Load Example" to see a sample run. The tool resolves the document's @context and rewrites every short term, prefix, and alias as a full IRI, then drops the @context section entirely since it's no longer needed.
Example
Given the sample document above, expansion turns name into http://schema.org/name and homepage into an @id-typed reference under http://schema.org/url, wrapping every value in its explicit @value or @id form.
Common Use Cases
- Inspecting exactly which IRIs a document's short terms actually resolve to.
- Normalizing documents that use different contexts before comparing or merging them.
- Debugging a context that isn't mapping a term the way you expect.
- Preparing a document as an intermediate step before flattening, framing, or RDF conversion.
FAQs
What does expansion do to a JSON-LD document?
Expansion removes all context-dependent shortcuts — short property names, prefixes, and term aliases — and rewrites every property and type as its full, absolute IRI. The result has no @context section at all, because none is needed: every key is already an unambiguous IRI. This is the canonical, most "spelled-out" form of a JSON-LD document.
Why would I want the expanded form instead of the original document?
Expansion is JSON-LD's normal form for programmatic processing — once a document is expanded, you can compare, merge, or process it without needing to know which context (or which shorthand terms) the original author used. It's usually an internal step before flattening, framing, or converting to RDF, but it's also useful on its own for inspecting exactly what a document "really means" at the IRI level.
Does this tool support remote @context URLs (like https://schema.org/)?
No — this tool intentionally disables network fetches for @context and document dereferencing, since a static, client-side tool can't reliably rely on a remote server's CORS policy or availability. Use a document with an inline @context object (a JSON object, not a URL string) — the sample document above and virtually every hand-written JSON-LD example works this way. If you paste a document whose @context is a URL, you'll get a clear error instead of an unpredictable network failure.
Is my document uploaded anywhere?
No — all JSON-LD processing happens entirely client-side in your browser using the jsonld.js library. Nothing you paste is sent to a server.