About this tool

LD Browser takes a URI, fetches the RDF describing that resource directly from your browser, and shows it as a table and a graph. Click a link to follow it to the next resource.

No server

Fetching and display both happen in the browser of whoever is looking. With no relay server, load does not concentrate anywhere as more people use it.

In return, it can only read sites that allow cross-origin requests (CORS). Others show "Could not load". The same happens if one step of a redirect (301, 303) lacks the permission.

Supported formats

• Turtle, N-Triples, N-Quads, TriG, JSON-LD, RDF/XML
• JSON-LD (<script type="application/ld+json">), microdata and RDFa embedded in HTML pages

Documents over 2 MB are not read.

Rewriting

For Wikidata URIs, the light Turtle version (Special:EntityData/…​.ttl?flavor=simple) is fetched. http:// URIs become https://. For vocabularies such as SKOS and Dublin Core, where a redirect step loses the permission, the final target of the redirect is fetched directly.

Inspiration

Learned from LD Browser (2014) by Masahide Kanzaki. His version fetches through a server and, as of October 2026, is down because of heavy traffic. This tool is a separate implementation and is not Kanzaki's tool.