Find in JSON

JSON documents grow. A config file, a log payload or an API response can run to thousands of lines, and the key or value you need — the one flag, the one field name, the one error string — is buried somewhere inside nested objects and arrays. Scrolling for it wastes time and misses occurrences; grep only works after you convert everything to text.

Find in JSON searches the parsed structure directly. Enter a term, pick keys, values or both, and every matching occurrence is listed with its full path, its key and its value. Case-insensitive contains or exact matching, results exportable to CSV, all in your browser.

• Search keys, values, or both in one pass over the whole structure.
• Contains or exact matching with case-insensitivity on by default.
• Full paths for every hit: customers.1.email style paths with array indices.
• Any value type: numbers, booleans and null are searched as text too.
• Live results: the table updates as you type the term.
• CSV export: download path, key and value columns for documentation or review.
• Result count: know exactly how many occurrences exist.
• Private: All processing happens in your browser; nothing is uploaded.

1. Paste your JSON into the input pane.
2. Type the search term — results appear as you type.
3. Pick what to match: keys, values or both.
4. Adjust matching — contains vs exact, case sensitivity — until the list looks right.
5. Use the paths to jump into the document, or export the table as CSV.

Example 1 — Config audit. A developer searches a large config JSON for the key password and finds it in three places — two real and one in a commented-style string. The paths show exactly where each occurrence lives.

Example 2 — Log forensics. A support engineer searches an error payload for the value "timeout" and gets every message, code and detail field containing the word, with paths for context.

Example 3 — Schema discovery. A data analyst searches for keys containing "at" to find all timestamp-like fields (created_at, updated_at, deleted_at) across a response — a one-click inventory of convention usage.

Example 4 — Compliance check. A reviewer searches for the exact value of a regulated identifier to verify it appears nowhere in a dataset before publication, and exports the empty result set as evidence.

• Instant location: Every occurrence ships with its full path.
• Complete coverage: The walker descends through all nesting levels and arrays.
• Flexible matching: Contains, exact, case-sensitive or not — you choose.
• Exportable results: CSV output documents the search for audits.
• Zero data movement: The document is searched locally and never uploaded.