Is the search case-sensitive?

No, both the query and every key or value are lowercased before comparison, so "Name" and "NAME" match a query of "name".

Can I search only keys or only values?

Yes, by default it searches both, but you can restrict it to keys only or values only, useful when a value happens to contain the same text as an unrelated key.

What does the path in each result mean?

It's the same dot/bracket notation used by the JSON Object Flattener (e.g. user.roles[1]), showing exactly where in the document the match was found.

Does it match partial substrings or only whole words?

Partial substrings, a query of "adm" matches a value of "admin", since the search uses simple substring containment rather than word-boundary matching.

Find JSON Keys and Values Online - Search a JSON Document

Overview

Introduction

Large JSON documents, API responses, config files, exported data, often bury the one field or value you're looking for under many layers of nesting.

This tool scans the whole document for a substring match and tells you exactly where each hit lives.

What Is JSON Key & Value Finder?

A recursive search utility that walks every object key and leaf value in a parsed JSON document, comparing each against a case-insensitive substring query.

Every match is reported with the dot/bracket path to its location, so you can go straight to the relevant part of the document.

How JSON Key & Value Finder Works

The tool recursively descends into the parsed JSON, building up a path string as it goes (dot notation for object keys, bracket notation for array indices), the same convention as the JSON Object Flattener.

At each object key or leaf scalar, it lowercases both the query and the candidate text and checks for substring containment, collecting every match into a results list with its path.

When To Use JSON Key & Value Finder

Use it when you know roughly what you're looking for (a field name or a value fragment) but not where it lives in a large document.

It's also useful for a quick sanity check that a particular value appears anywhere in a large API response or export.

Often used alongside JSON Key Extractor, JSON Value Extractor and JSONPath Tester.

Features

Advantages

Searches the entire document regardless of nesting depth.
Reports the exact path to every match, not just that a match exists.
Lets you scope the search to keys only, values only, or both.

Limitations

Matching is plain substring containment, there's no regular expression or fuzzy matching support.
Numbers, booleans, and null are matched against their string representation, so searching for "true" will match a boolean value of true.

Examples

Searching both keys and values

Input

{"user":{"name":"Ada","email":"ada@example.com"}}

Output

2 matches found for "ada"
user.name: "Ada"
user.email: "ada@example.com"

Both the name value and the email value contain "ada" case-insensitively, and each is reported with its path.

Best Practices & Notes

Best Practices

Narrow the search to values only when you're hunting for a specific piece of data rather than a field name.
Use a short, distinctive substring to avoid a flood of unrelated matches in a large document.
Follow up with JSONPath Tester if you need to build a reusable query, not just a one-off search.

Developer Notes

The walk shares its path-building convention with flattenJsonObject (dot notation for object keys, bracket notation for array indices) so results here are directly comparable to paths reported by that tool, rather than inventing a separate notation.

JSON Key & Value Finder Use Cases

Locating which field in a large API response holds a specific value
Auditing a config file for every place a particular setting name appears
Confirming whether a value exists anywhere in an exported dataset before writing code against it

Common Mistakes

Expecting regular expression support; only plain substring matching is available.
Forgetting the search is case-insensitive and being surprised when differently-cased text still matches.
Searching a very generic short substring and getting an overwhelming number of matches in a large document.

Tips

Restrict to "keys" scope first to confirm a field name exists before searching its values.
Combine with JSON Key Extractor if you want the full list of key names rather than a targeted search.

JSON Key & Value Finder