[{"data":1,"prerenderedAt":111},["ShallowReactive",2],{"tool-page-en-json-viewer":3,"tool-related-guides-en":85},{"locale":4,"slug":5,"title":6,"seoTitle":7,"description":8,"eyebrow":9,"intro":10,"howTitle":11,"howIntro":12,"steps":13,"benefitsTitle":23,"benefitsIntro":24,"benefits":25,"useCasesTitle":38,"useCasesIntro":39,"useCases":40,"guideTitle":53,"guideIntro":54,"guideSections":55,"faqTitle":68,"faqIntro":69,"faqs":70,"relatedTitle":83,"relatedIntro":84},"en","json-viewer","JSON Viewer Online","JSON Viewer Online — Explore JSON Trees and Paths","View JSON as an expandable tree, inspect nested values, and copy JSON paths locally in your browser.","Interactive local JSON viewer","Explore nested objects and arrays as a collapsible tree, then copy the exact path to any value.","Explore nested JSON in three steps","The viewer validates the complete document before building a navigable tree in your browser.",[14,17,20],{"title":15,"body":16},"Add JSON","Paste a document, load the example, or choose a local .json file.",{"title":18,"body":19},"Open the tree","Expand only the branches you need or open the complete structure at once.",{"title":21,"body":22},"Copy a path","Copy a JSON path for any object, array item, or leaf value with one button.","See structure instead of scanning text","The tree makes hierarchy and value types visible without changing the original document.",[26,30,34],{"title":27,"body":28,"icon":29},"Collapsible branches","Focus on one part of a large object by expanding and collapsing nested arrays and objects.","lucide:git-branch",{"title":31,"body":32,"icon":33},"Copyable JSON paths","Get paths such as $.user.name or $.items[0] directly from the displayed structure.","lucide:route",{"title":35,"body":36,"icon":37},"Typed values","Strings, numbers, booleans, and null values use distinct labels and readable syntax colors.","lucide:list-tree","When a JSON tree is easier than raw text","Tree navigation is useful when the question is where a value lives, how items are grouped, or which branch contains an unexpected result.",[41,44,47,50],{"title":42,"body":43},"Explore an unfamiliar API payload","Open only the branches related to your task instead of scanning a long response from top to bottom.",{"title":45,"body":46},"Inspect arrays of records","Follow numeric indexes through lists of users, events, products, or results while keeping the surrounding hierarchy visible.",{"title":48,"body":49},"Locate a nested configuration value","Trace a setting through parent objects and copy its exact path for documentation, code, or a support conversation.",{"title":51,"body":52},"Compare shape before writing code","See whether a field is an object, array, scalar, or null before creating types, selectors, transformations, or tests.","Reading the JSON tree and copied paths","The viewer represents the parsed value as expandable branches and uses a predictable path notation for objects and arrays.",[56,59,62,65],{"title":57,"body":58},"Objects become named branches","Each object property appears under its parent key. Identifier-like keys use dot notation in copied paths, such as $.user.name.",{"title":60,"body":61},"Arrays use numeric indexes","Array items appear in their original order and use bracket indexes such as $.items[0]. A copied path identifies a position, not a permanent record ID.",{"title":63,"body":64},"Complex keys use bracket notation","Keys containing spaces, punctuation, or other characters that are awkward in dot notation are quoted in brackets, for example $[\"display name\"].",{"title":66,"body":67},"Large trees still use device memory","Processing stays local, but parsing and rendering large documents consumes browser memory. Collapse branches and avoid opening every node on limited-memory devices.","JSON tree and path questions","How the viewer represents nested data while keeping the source local and unchanged.",[71,74,77,80],{"question":72,"answer":73},"Does the viewer modify my JSON?","No. It parses the source to build a tree but does not rewrite the text in the input panel.",{"question":75,"answer":76},"Which path notation does it copy?","It uses a dollar-sign root, dot notation for identifier-like keys, bracket notation for other keys, and numeric brackets for array indexes.",{"question":78,"answer":79},"Can the viewer open every branch?","Yes. Use Expand all to open the full tree, or Collapse all to return to the root view.",{"question":81,"answer":82},"Is the JSON tree generated locally?","Yes. Parsing, tree rendering, and path copying run entirely in your browser.","Continue with another JSON task","Minify, format, or validate JSON with the other focused tools on jsonminify.org.",[86,91,96,101,106],{"slug":87,"title":88,"description":89,"eyebrow":90},"fix-invalid-json","How to fix invalid JSON","Diagnose trailing commas, single quotes, comments, malformed strings, and missing brackets in invalid JSON.","ERROR GUIDE",{"slug":92,"title":93,"description":94,"eyebrow":95},"json-minification-explained","JSON minification explained","Learn what JSON minification removes, what data it preserves, and when smaller JSON is useful.","CORE CONCEPT",{"slug":97,"title":98,"description":99,"eyebrow":100},"json-minify-vs-compress","JSON minification vs compression","Compare whitespace minification with gzip and Brotli transport compression for JSON files and API responses.","SIZE COMPARISON",{"slug":102,"title":103,"description":104,"eyebrow":105},"json-whitespace-and-size","How JSON whitespace affects file size","Understand which JSON whitespace can be removed and how to measure realistic byte savings.","SIZE & MEASUREMENT",{"slug":107,"title":108,"description":109,"eyebrow":110},"minify-json-for-production","Minify JSON safely for production","Use a practical checklist to validate, minify, compress, cache, and monitor production JSON assets.","PRODUCTION CHECKLIST",1791969046522]