OmniJSON / Guide
View JSON locally without uploading it to a formatter
Publisher and support: OmniJSON on the Chrome Web Store. Checked against version 0.1.14. Version notes; check the store listing for availability.
Updated
OmniJSON parses and searches JSON locally in a Chrome extension; it does not upload documents to an OmniJSON formatting service. Opening an HTTP/HTTPS source still makes a network request to that source. Local processing and offline operation are different claims.
OmniJSON is an extension for desktop Chrome. Install it to try these steps with your own JSON.
What stays on your device?
Parsing, tree browsing, Search, Fields and JSONPath run inside the extension. Parsed documents and indexes remain in memory for the active viewer session rather than being saved to extension storage. OmniJSON includes no extension analytics, advertising SDKs, telemetry or remote formatting.
Local files require Chrome’s Allow access to file URLs setting. Supply an absolute path or file:/// URL. See the large JSON opening guide for steps.
When does a network request happen?
- Opening a web source fetches the URL you choose. Chrome may include applicable cookies or authentication credentials and follow server redirects, including to another host.
- The source server receives that request. OmniJSON does not inspect Chrome’s cookie store or send the returned document to a separate processing service.
- If direct fetching fails, an original JSON tab can supply its visible document as a fallback.
- Following a value link, help link or Chrome Web Store link opens that external destination. Its own policies apply.
Downloading or accessing a private endpoint still depends on its permissions, browser credentials and network availability. OmniJSON does not bypass those controls.
What information is saved?
| Data | Retention and controls |
|---|---|
| Parsed JSON and indexes | Kept in memory for the active viewer session; not persisted as documents in extension storage. |
| Recent sources | Up to 50 complete normalized URLs, derived titles and last-opened timestamps. URLs retain query parameters, fragments and file paths, including sensitive text embedded in them. |
| Startup diagnostics since 0.1.13 | Up to 20 local records containing timestamp, extension version, failure stage, error code and elapsed time. Copied reports also include browser version. No JSON, source URLs, credentials or raw errors are included in these reports; they are not uploaded automatically. |
| Developer console | Local console logs can contain source URLs, filter/JSONPath expressions, status and errors. These are distinct from the sanitized Copy diagnostics report and are not automatically uploaded. |
| Clipboard | Only explicit Copy actions write content. The operating system and any destination where you paste it handle that copy. |
Recent URLs have no time-based expiry. New records replace older ones after the limit. To remove a source, type oj followed by Space or Tab in Chrome’s address bar and delete its suggestion. Reopening it saves it again. Uninstalling the extension clears local extension storage; clearing browsing history or cache does not clear the recent list.
Before opening sensitive JSON
- Choose the correct source. Use a local file when you intend to read a file already on your computer.
- Avoid embedding credentials in source URLs where possible, because the recent-source list preserves complete URLs.
- Check copied content before pasting or sharing. For troubleshooting, use the sanitized report instead of sharing raw console logs.
- Follow your organization’s rules for browser extensions and sensitive data.
This guide summarizes behavior, not a compliance certification. The full privacy policy also explains website hosting and campaign-labelled external links.