Loading JSON-LD to RDF Turtle Converter...
Please wait a moment

How to Convert JSON-LD to RDF Turtle - Step by Step Guide

Step 1

Input Your JSON-LD Data

Start by adding your JSON-LD data. Whether it's Schema.org markup from your website or structured data from an API:

•
Paste directly: Copy your JSON-LD and paste it in
•
Upload a file: Click "Upload" to select a .jsonld file
•
Try the sample: Click "Sample" to see an example
Step 2

Automatic Conversion to RDF Turtle

The converter (powered by jsonld.js and N3.js) automatically transforms your JSON-LD into RDF Turtle format. Here's what happens:

•
Expands @context: Resolves all vocabulary URLs to full URIs
•
Creates triples: Transforms your JSON structure into subject-predicate-object statements
•
Shortens IRIs: Uses the schema:, rdf:, rdfs: and xsd: prefixes where they fit; other IRIs stay written out in full
Step 3

Export Your RDF Turtle Data

Once converted, you can use your Turtle data in various ways:

•
Copy to clipboard: Quick copy for pasting into your triple store or text editor
•
Download as .ttl file: Save it for import into Apache Jena, Virtuoso, or other triple stores
•
Further conversion: Use our RDF Format Converter to change it to other formats, or JSON to Jelly-RDF for a compact binary stream

Frequently Asked Questions

Why convert JSON-LD to RDF Turtle?

Turtle is easier to read than JSON-LD and is the preferred format for many semantic web tools and triple stores. It's great for documentation, sharing data with researchers, and importing into databases.

Does the converter handle @context resolution?

Yes. An inline @context is read straight away, and a context given as a URL (Schema.org's, for instance) is fetched by your browser when you convert. If that address can't be reached or doesn't allow cross-site requests, the page names the URL that failed, and you can paste the context in as an object instead. Keys your context doesn't map to an IRI are left out, which is how JSON-LD works; if nothing maps at all, you get a message rather than an empty file.

Can I use this for knowledge graphs?

Yes. Convert your JSON-LD to Turtle, then load it into a triple store such as Apache Jena, Virtuoso or GraphDB and link it with the rest of your graph.

Is the output compatible with SPARQL?

The output is plain Turtle, so any RDF database that loads Turtle can query it with SPARQL. One case can't be written as Turtle: JSON-LD with a named graph (a top-level "@id" next to "@graph"). The page stops and explains that instead of putting TriG syntax in a .ttl file.

What happens to long IDs and decimal numbers?

Whole numbers become xsd:integer with every digit kept, so an ID like 8901240544102066246 comes out exactly as typed. Decimals such as 14.50 follow the JSON-LD rules and become xsd:double (written 1.45E1). If the exact spelling of a decimal matters, put it in quotes and give it a type in your @context. Quoted values like "00501" stay strings.

Can I convert the output to other RDF formats?

Yes. The RDF Format Converter turns Turtle into N-Triples, N-Quads, RDF/XML or back into JSON-LD.

Is this converter free?

Yes, and there's no sign-up. The conversion runs in your browser, so your JSON-LD isn't sent to our servers; only remote @context URLs are fetched, from wherever they're hosted.