Local-first. No upload. No tracking.
Birdor JSON Lens
Local-first JSON reader

How can we help with JSON Lens?

Search local-first guides for opening JSON, using Scratchpad, copying paths, handling large payloads, and getting support.

Recommended guides

The most common setup and troubleshooting paths for new JSON Lens users.

Getting started

Install, open current-page JSON, and learn the local-first product boundary.

Core workflows

Scratchpad, path copy, compare, diagnostics, and everyday debugging moves.

Troubleshooting

Large payloads, parse errors, performance limits, and recovery tips.

Privacy and permissions

Understand what the extension can access and what it deliberately avoids.

FAQ

Questions before you trust a JSON reader

Short answers for the support questions that should not require a ticket.

Does JSON Lens upload my JSON?+

No. Current-page JSON, pasted snippets, selected text, local files, and compare inputs are processed locally in the browser.

Why does the extension need activeTab and scripting?+

They are used together only after you click Render current page, so the packaged local renderer can run in that active tab.

Can JSON Lens inspect network requests automatically?+

No. It does not request webRequest, cookies, history, tabs, debugger, or persistent host permissions.

What should I include in a support ticket?+

Include the entry point you used, browser version, whether the issue happens in Scratchpad or current-page rendering, and a sanitized sample when possible.

Still need help?

Contact Birdor support or submit a ticket draft with the workflow, browser, and sanitized details we need to reproduce the issue.

Email support@birdor.com

Submit a support ticket

This static help center opens a prefilled email draft so you can review details before sending them.