jsonyo for WordPress or browser?
jsonyo ships the same local JSON engine in two places. Use the WordPress plugin when the JSON lives in wp-admin. Use the browser extension when the JSON lives in a tab. If you inspect REST responses, theme.json, block.json, ACF exports, JSON-LD, or raw payloads every day, the install path matters more than the brand name.
Which install path wins for your workflow?
Choose the plugin if you touch theme.json, block.json, ACF exports, site settings, transients, or internal staging payloads. You keep the tool next to the field, not in another browser tab.
Choose the extension if you inspect REST responses, JSON-LD, public API payloads, GitHub Raw blobs, or any page-level JSON that needs a quick local pass.
| use case | best surface | why it wins |
|---|---|---|
| ACF schema audits | WordPress plugin | Already in wp-admin, no tab switch, no copy-paste loop. |
| theme.json / block.json | WordPress plugin | Same place as the file and the editor controls. |
| REST API debugging | Browser extension | Inspect the response where you already opened it. |
| JSON-LD / page source | Browser extension | Quick scan of inline JSON without leaving the tab. |
| repeatable CI checks | CLI | Use the npm binary when you want automation. |
What to install first
Install the WordPress plugin first. It solves the most annoying part of WordPress JSON work: inspecting payloads and configs without leaving the dashboard.
Install the browser extension first. It keeps the current page intact and lets you inspect JSON from the exact place you found it.
Pick the surface that matches your workflow, or install both if you want the same JSON engine in wp-admin and in the browser. No account, no telemetry, no data leaves your browser.
Why jsonyo is worth installing at all
- It stays local. The browser surfaces do not call out to a remote API for the core JSON workflow.
- It is more than pretty-printing. Format, validate, query, diff, stats, and minify are all built in.
- It saves tab switches. wp-admin users can stay in wp-admin; browser users can stay on the page they opened.
- It has a clear decision tree. If you are unsure where it belongs, the compare pages point you in the right direction fast.
FAQ
Should I install the WordPress plugin or browser extension first?
Install the one that matches your daily workflow. If you spend most of your time inside wp-admin, start with the WordPress plugin. If you inspect JSON in browser tabs, start with the extension.
Does jsonyo send JSON to a server?
No. The JSON parser, formatter, query engine, diff viewer, and stats mode all run locally in the browser or wp-admin tab.
Can I use both surfaces together?
Yes. That is often the cleanest setup: the WordPress plugin for internal work and the browser extension for live pages and API responses.
Where should I go if I want more detail before installing?
Read the WordPress compare page or the browser compare page. They explain the tradeoff in more depth before you click install.