What Extract JSON Text helps you do

Walk a JSON value and list every string it contains, which is useful for copy review, localization and audits. Instead of scrolling through nested JSON, you get a flat list of the human-readable values. Keys, numbers, booleans and nulls are not included.

Extraction runs entirely in your browser; no JSON is uploaded to Haivix.

How it works

These tools scan the pasted text in the browser with a pattern or parser and return the matches in first-seen order. Extraction is a candidate list, not a verification step: an email-shaped string may not be deliverable, a URL may not resolve, and a number may be part of a date or an identifier. Nothing is uploaded, and the source text is never changed. The result is a snapshot of the pasted text; editing the source afterwards does not update the list.

How to use Extract JSON Text

Paste a valid JSON object or array.
Extract all of its string values.
Check that the list includes the fields you expected.
Copy the list for translation or review.

When to use it

Gather all display strings from an API response for translation.
Audit the copy inside a config or localization file.
Get a flat list of values from deeply nested JSON.
Review the user-facing text in a stored payload.
Prepare strings for a spell-check pass.
Check whether a response contains placeholder or empty values.
Extract strings from a localization file for review.

When not to use it

Do not use it on invalid JSON; the parser stops with an error.
Do not expect keys or numbers in the output.
Do not use it to reconstruct the original structure.

Example

An object with a title and a nested label returns both human-readable strings as separate lines. A key such as title is not included, and a numeric count is skipped. An empty string value is listed as an empty line, which can be easy to miss.

What you can do with Extract JSON Text

Parse a JSON object, array or quoted string.
Collect every string value recursively.
Preserve the order in which values appear.
Include empty strings when they are present.
Copy the flat list for translation or review.
Run the extraction locally with no upload.

Example: check the matches on a sample

Paste a short sample first and count the expected matches by eye. Compare that count with the result before running a large file, because a missing match is easier to spot in a small sample.

Read a few matches in context to catch false positives. A phone-like number inside an order ID, or a URL inside a code snippet, is common and should not be treated as a contact or a live link.

Copy the list and keep the original. If the extraction feeds a mail merge or a report, verify a sample of the destinations rather than assuming every match is valid.

If the result is empty, check the input format before assuming the tool is broken. A bare domain without http, an address split across a line, or JSON with a trailing comma are common reasons for no matches.

For a list that will be contacted or published, keep the source and the extracted list side by side. The source is the only way to resolve a questionable match or explain why one was missed.

What to know before you start

The JSON must be valid; a syntax error prevents extraction.
It returns values only, so the keys and structure are not included in the output.
It does not evaluate JSONPath or filter by key.
Very deeply nested values beyond the depth guard are skipped.

Common mistakes

Pasting JSON with a trailing comma or a comment, which is invalid.
Expecting keys to appear alongside their values.
Assuming numbers will be converted to strings.
Overlooking empty strings in the output.

Troubleshooting

If parsing fails, validate the JSON with the JSON formatter first.

If a value is missing, it may be a number, a boolean or null rather than a string.

If the order looks unexpected, object key order is preserved as the parser reads it.

If the output is empty, the JSON may contain no string values.

Extract JSON Text