Semantic Web/RDF Converter
RDF Converter
Convert RDF between Turtle, RDF/XML, N-Triples and JSON-LD. Load every file an ontology needs — it's merged into one output. Nothing leaves your browser.
Turtle, RDF/XML, N-Triples and JSON-LD. Files are read and converted in your browser and never uploaded. Every enabled file is merged into one graph before conversion, so a schema split across several files converts as a single document.
The enabled files together can hold up to 400,000 triples.
What this does?
RDF has several standard text representations, and the one you have is not always the one you need: Turtle is compact and readable, RDF/XML is what older tooling expects, N-Triples is a flat, line-per-triple format that's easy to diff or stream, and JSON-LD slots RDF straight into a JSON-based pipeline. This tool parses whatever you give it and re-serializes it in the format you pick, without changing the underlying data.
As with the Ontology Visualizer, you can load more than one file: every file you enable is merged into a single graph — with exact duplicate triples removed — before it's converted, so a schema and its instance data, or a modular ontology and the files it needs, come out as one combined document in the format you chose.
It's handy for feeding a Turtle file to a tool that only reads RDF/XML, turning a dataset into JSON-LD for a web app, or just getting a quick, readable Turtle view of an N-Triples dump.
FAQ
Is my RDF uploaded anywhere?
No. Files are read, parsed and converted entirely in your browser. Nothing you upload or paste is sent to a server, logged, or stored on one — this includes JSON-LD @context URLs, which are only resolved from files you have also loaded, never fetched. The sample files that load automatically are static files served with the site.
What formats are supported?
Turtle (.ttl), RDF/XML (.rdf, .owl, .xml), N-Triples (.nt) and JSON-LD (.jsonld, .json) — both as input and as the output format you convert to. OWL/XML and OWL Functional Syntax are not supported; in Protégé use File → Save as… and choose RDF/XML or Turtle instead.
Why would I load more than one file?
If an ontology is split across files — a schema kept apart from its instance data, a modular ontology, or a JSON-LD document with an external @context — load every file it needs. Every enabled file is merged into one graph (with exact duplicate triples removed) before conversion, so you get one combined output rather than converting each file in isolation.
Will converting and converting back give me the same file?
You'll get the same triples, but not necessarily byte-for-byte the same text: blank node labels, prefix choices, and formatting (whitespace, quoting style, element order) can differ between a round trip. The data — every subject, predicate and object — is preserved exactly; only its presentation can change.
What happens to blank nodes across several files?
Each file's blank nodes are kept separate internally (so two files that happen to both use "_:b1" never collide), then written out with fresh labels in the combined output.
Is there a size limit?
Each file can be up to 10MB, and the enabled files together can hold up to 400,000 triples before conversion.
Want to see the class hierarchy instead of just converting it? Try the Ontology Visualizer →