install guide · jsonyo

install jsonyo. keep the JSON workbench where you already work.

jsonyo ships as a browser extension, a WordPress wp-admin plugin, and a free CLI. Pick the surface that matches your day: browser tabs, wp-admin, or terminal. Everything runs locally. Zero data leaves your browser. If you get stuck, the support page tells you exactly where to go next.

browser extension · chrome / firefox / edge wp-admin plugin · free cli · npm install -g @v0idd0/jsonyo
why install

works where you already are

jsonyo avoids the "open another tab" tax. if you are in a browser, use the extension. if you live in wp-admin, use the plugin. if you are in a shell, use the CLI.

zero data leaves your device

the browser surfaces run entirely locally. no upload, no analytics, no hidden API hop. that's the point for REST payloads, webhooks, and private staging data.

more than pretty-printing

jsonyo does format, validate, JSONPath-style query, diff, stats, and minify. it solves the actual workflow instead of stopping at indentation.

fast install path
step 1

pick the surface

browser extension for tab work, WordPress plugin for wp-admin, CLI for terminal-first debugging. the toolchain stays the same.

step 2

install from the store

use Chrome, Firefox, or Edge for the extension. if you're in WordPress, go straight to WordPress.org. no account is needed for the free surfaces.

step 3

start with a real payload

paste REST output, ACF JSON, theme.json, or a webhook body. validate it, query it, or compare two versions in one pass.

Best next click: if you are deciding, use the WordPress compare page first. It explains why the plugin belongs in wp-admin, while the browser comparison shows how jsonyo stacks up against plain JSON formatter tools. If install gets stuck, open support / docs.

surface matrix
browser extension
best for tab-by-tab inspection

open the popup, inspect the current page, and keep JSON work anchored to the page you are already on.

wordPress plugin
best for wp-admin workflows

REST responses, ACF exports, theme.json, and webhook payloads live inside the dashboard instead of a separate tab.

CLI
best for repeatable scripts

same engine, terminal-first. use it when you want output you can pipe, diff, or automate.

privacy
nothing is silently uploaded

jsonyo does not need a cloud round-trip for its core workflow. that keeps private and internal payloads private.

browser stores
support and docs
related surfaces