No input yet.
Turn a JSON-LD script into inline itemprop markup
This converter writes JSON-LD as microdata HTML. Paste a JSON-LD object or its script block and get nested itemscope elements with itemprop attributes that you can merge into your template.
Last updated:
How it works
Paste JSON-LD
One object, an array, a @graph or the complete script tag. Syntax errors are reported with line and column.
Choose visible or hidden
Visible mode writes text into span elements, URLs as links and dates as time elements; hidden mode uses meta and link only.
Merge into your HTML
Copy the elements into the template and replace the example text with your real content where it is shown on the page.
Features
Full schema.org IRIs
Types become itemtype="https://schema.org/Product", several types become a space-separated list, and @id becomes itemid.
Right element for each value
Dates, times and ISO 8601 durations go into time with a datetime attribute, numbers into meta content, and enumeration values such as InStock into link href with the full schema.org URL.
Images and links stay usable
In visible mode image, logo and thumbnail URLs become img elements and other URLs become links; url and sameAs stay invisible link elements.
Escaped output
Every text and attribute value is HTML-escaped, so a value containing <script> or quotes cannot change the markup.
Notes on what has no equivalent
Language tags, @list order, @reverse and nested contexts have no microdata form; the converter lists what it dropped instead of failing silently.
Limits & privacy
JSON-LD inputs can be up to 10 MB; larger documents are converted in a background worker.
Only schema.org markup is supported well: properties from other vocabularies are written with their full IRI as itemprop. The output is a starting point – microdata is meant to annotate visible content, so replace hidden values with real page text where it exists. Google requirements for the item are still checked best in the JSON-LD validator.
Type checks use the schema.org vocabulary (© schema.org sponsors, CC BY-SA 3.0, see licenses). Nothing is uploaded – see the privacy page.
FAQ
When is microdata better than JSON-LD?
When a platform strips script tags from content (some CMS editors and e-mail templates), or when you want the markup tied to the visible text. Google reads both formats.
Will the result read back as the same JSON-LD?
Yes for types, properties and nesting – you can check it with the Microdata to JSON-LD converter. Numbers and booleans come back as strings, because microdata has no data types.
Can meta and link be used inside the body?
Yes. HTML allows meta and link elements with itemprop anywhere in the body, which is how hidden values are written.
What happens to references like {"@id": "…"}?
A reference becomes a link element with itemprop and href. The referenced item itself is written where it is defined in the document.
Is the HTML rendered on this page?
No. The result is only shown as code in the editor; you copy or download it.