PrivyJSON for Chrome

Overview

PrivyJSON turns raw JSON and common YAML responses into a clean, syntax-coloured workbench in Chrome. Format a response for reading, convert it between JSON and YAML, or open an optional document-aware AI chat when you need help understanding its structure.

PrivyJSON for Chrome is preparing for release. Its download link will appear here when it is available on the Chrome Web Store.

Features

• Automatic document detection — Recognises JSON and common YAML responses by content type, file extension, or content shape.
• Readable local formatting — Replaces a supported raw response with a tidy, syntax-coloured reader.
• JSON ↔ YAML conversion — Convert mappings, sequences, scalars, and nested configuration documents between the two formats.
• Optional document chat — Ask about the current document, compare values, find information by meaning, or request a replacement through a provider you configure.
• Provider choice — Use Ollama, LM Studio, or an OpenAI-compatible endpoint, choose a model, and set a request timeout.
• Local controls — Provider settings and conversations stay in Chrome extension storage, with a clear-conversation action.

Designed for private workflows

Formatting and conversion run inside Chrome and do not need an account or AI provider. The extension has no developer-operated analytics, telemetry, advertising, or AI relay. If you choose to use AI, PrivyJSON sends your question and the current document context directly to the provider endpoint you selected—only after you submit a message.

When to use it

Inspect an API response, switch a configuration sample from JSON to YAML, or ask a trusted local model to explain an unfamiliar payload. It keeps the core structured-data workflow in the tab you already opened.

Requirements

• Google Chrome or a compatible Chromium browser
• No account or provider for formatting — JSON/YAML formatting and conversion work without an AI configuration.
• An AI provider (optional) — Ollama, LM Studio, or a compatible endpoint is needed only for document chat.

YAML support is intentionally focused on common configuration files: mappings, sequences, scalars, and nested documents. Anchors, aliases, block scalars, multi-document streams, and comment-preserving round trips are outside the current scope.