DEV Community: hito x

Describe Your JSON Query in English — Get JSONPath Instantly

hito x — Mon, 29 Jun 2026 09:44:56 +0000

You know what you want from a JSON document. You just don't want to memorize whether it's $[?(@.age > 18)] or $..users[?(@.active)].

Plain English in. JSONPath out.

JSONPath Assistant on FormatList lets you paste JSON, describe what you need in natural language, and get a validated JSONPath expression plus the actual results — all in your browser. No account, no API key, no data sent to a server.

How it works

Paste your JSON — an API response, config file, or test fixture.
Describe what you need — e.g. "get all user names" or "find products with tag tech".
Generate — the assistant reads your JSON structure and maps your query to JSONPath.
Validate & copy — the expression runs against your data immediately. Copy the path or the matched values in one click.

If the first attempt returns no matches, the tool retries with a simpler variation automatically.

Example queries

You type	Generated JSONPath
Get all user names	`$.users[*].name`
Find users older than 18	`$.users[?(@.age > 18)]`
Get names of active users	`$.users[?(@.active == true)].name`
Find products with tag tech	`$.products[?(@.tags.indexOf('tech') >= 0)]`
Get all order prices	`$.orders[*].price`
Get the first user's email	`$.users[0].email`
Get all pod names	`{.items[*].metadata.name}`
Get all pod IP addresses	`{.items[*].status.podIP}`

The tool ships with one-click examples for each of these — load one, hit Generate, and see how it works before trying your own JSON.

What kinds of queries it understands

Property access — "get all names", "list order prices"
Numeric filters — "older than 18", "price under $10", "greater than 100"
Boolean filters — "active users", "enabled devices"
Tag / category searches — "with tag tech", "beauty category"
Multi-condition — "both tech and mobile tags"
Quantifiers — "the first user", "the last item"
Kubernetes — "get all pod names", "pod IP addresses"

It analyzes field names in your JSON — so users, products, orders, or whatever keys you actually have — and builds paths that match your schema.

Not ChatGPT. Still feels like magic.

Despite the "AI" label, nothing leaves your browser. JSONPath Assistant uses rule-based pattern matching against your JSON structure — no external API, no LLM call, no upload.

That means:

Private — safe for production API responses, customer data, internal configs
Fast — results in milliseconds, not seconds
Free — no token limits or rate caps

You get the convenience of natural language without sending sensitive JSON to a third party.

JSONPath Assistant vs the other FormatList tools

FormatList has three JSONPath tools that solve different problems:

	JSONPath Assistant	JSON Path Finder	JSONPath Explainer
Direction	English → JSONPath	Click node → JSONPath	JSONPath → English
Best for	Writing queries from scratch	Exploring unknown JSON	Learning what a path means
Input	JSON + plain English	JSON (+ optional expression)	JSONPath string

Typical workflow: Assistant to generate → Finder to verify paths in the tree → Explainer to understand unfamiliar syntax.

When to use it

Scenario	Why it helps
API integration	"Get all customer emails" without reading JSONPath docs
Data pipelines	Quick path for jq, Python `jsonpath`, or Node scripts
Kubernetes / kubectl	Natural language for `{.items[*].metadata.name}` style paths
Learning JSONPath	See how English maps to real syntax on your data
Debugging filters	Test "users older than 18 and active" before committing to code

Pair it with JSON Formatter if your payload is minified, or Repair ChatGPT JSON if an LLM gave you broken JSON first.

FAQ

Is my data sent to an AI model?

No. Everything runs locally in your browser using pattern matching against your JSON structure.

What if the generated path is wrong?

Refine your query — mention the array name (users, products) and the field you want (name, price). You can also switch to JSON Path Finder to click the exact node and compare paths.

Does it support complex filters?

Yes — age comparisons, price ranges, tag searches, boolean flags, and Kubernetes-style notation. For edge-case syntax, generate a starting point here and tweak manually.

Try it

Open JSONPath Assistant →

Paste JSON, type what you want, copy the path. Five seconds beats five minutes of JSONPath documentation.

More free, browser-local data tools at formatlist.com.

Free tool, 100% client-side. Feedback welcome on About.

How to Fix Excel CSV Date Import Problems (US / UK Format Guide)

hito x — Mon, 29 Jun 2026 09:41:35 +0000

You export a CSV from a UK system and double-click it in US Excel — 28/05/2026 suddenly looks like May 28, or something even stranger. The file isn't corrupt. Excel is guessing your date format based on your computer's locale.

This short guide covers why that happens, how to import CSV correctly, and how to batch-fix dates that are already wrong. For the full walkthrough with examples, see the official guide: How to Fix Excel CSV Date Import Problems.

Why Excel breaks CSV dates

A CSV is plain text. It does not store whether a value is a date or a string. When you double-click to open, Excel parses using your regional settings:

US Excel: MM/DD/YYYY
UK / Europe: DD/MM/YYYY

Dates like 03/04/2025 are the most dangerous — both parts are ≤ 12. US Excel may read April 3; UK Excel reads March 4. Excel won't warn you.

Other common traps:

Dates exported as serial numbers (e.g. 44927)
Two-digit years triggering century guesses
Re-saving as CSV destroys formats a second time

The right way: don't double-click the CSV

Open Excel first — don't double-click the .csv file
Data → Get Data from Text/CSV (older Excel: Data → From Text)
Set date columns to Text if you need to preserve the original string
Confirm the source region (US / UK), then convert to a single format

For team data exchange, agree on ISO 8601: YYYY-MM-DD in your schema — unambiguous, sorts correctly as text, and works in JSON APIs and databases.

Ambiguous value	US reads as	UK reads as	Safe format (ISO)
03/04/2025	2025-04-03	2025-03-04	Confirm source region
28/05/2026	—	2026-05-28	2026-05-28
05/28/2026	2026-05-28	—	2026-05-28

Already broken? Fix dates in the browser (no server upload)

I built a free tool cluster on FormatList — everything runs locally in your browser:

1. Date Format Fixer — bulk repair

Paste a date column or upload .csv / .txt
Ambiguous rows highlighted; optional US / UK preference
Export ISO / US / UK or download a fixed CSV

Best for: normalizing a whole column to ISO before a database or API import.

2. Ambiguous Date Checker — check before you commit

Enter a single date like 03/04/2025 and see US vs UK interpretations side by side — no guessing.

Best for: visa forms, contracts, anything where the exact day matters.

3. UK Date to US Date — DD/MM → MM/DD

Lock DD/MM input → MM/DD output. Batch-convert UK invoices or CRM exports for US systems.

4. Fixed dates before JSON?

Normalize dates to ISO first, then use CSV to JSON. Order matters — wrong dates baked into JSON propagate through your entire pipeline.

Quick FAQ

Q: Why did my dates turn into numbers like 44927?

A: Excel stores dates as serial numbers internally. Date Format Fixer converts them back to readable dates.

Q: Fix dates first, or convert to JSON first?

A: Fix dates first. Bad dates in JSON pollute validation and reporting downstream.

Summary

Scenario	What to do
Not imported yet	Excel "import from text"; set date column to Text or ISO
Team data exchange	Agree on `YYYY-MM-DD`
Already wrong	Date Format Fixer + manual review of ambiguous rows
Single date unclear	Ambiguous Date Checker

If you also work with ChatGPT output, JSON, or CSV pipelines, FormatList has JSON Repair, CSV converters, and more at formatlist.com.

Free tools, 100% browser-local. Feedback welcome on About.

Stop Guessing JSONPaths — Click the Node, Copy the Path

hito x — Mon, 29 Jun 2026 09:41:20 +0000

You paste a 500-line API response into your editor. You need the price of the third item in store.book. You start typing $.store.book[2].price — then wonder if it's book or books, index 2 or 3, dot or bracket notation.

JSONPath is the right tool for the job. Finding the right path by hand is the painful part.

I built JSON Path Finder on FormatList to fix exactly that: paste JSON, browse an interactive tree, click any node, and copy its JSONPath instantly. No account, no upload to a server — everything runs in your browser.

For the full syntax guide (filters, wildcards, slices, library support), see the long-form article: JSON Path Finder Guide.

What JSON Path Finder does

1. Visual tree → instant JSONPath

Paste JSON on the left. Expand objects and arrays in the tree view. Click any key or value — the exact JSONPath appears in the path bar (e.g. $.store.book[1].title). One click to copy.

Works for deeply nested structures: Kubernetes manifests, Stripe webhooks, GraphQL responses, LLM tool outputs — wherever manual path construction gets tedious.

2. Evaluate expressions against real data

Type or paste a JSONPath in the Evaluate panel. The tool runs the query and shows every match with its path and value.

Supported syntax includes:

Dot and bracket notation: $.store.book, $['store']['book']
Wildcards and recursive descent: $[*], $..author
Filters: $[?(@.price < 15)]
Slices and unions: $[0:2], $[0,2,4]

If the expression is invalid, you get a clear error instead of silent wrong results.

3. Search the tree

Large payloads? Use the search box to jump to keys or values by name — then click to grab the path.

A quick example

Given this JSON:

{
  "store": {
    "book": [
      { "title": "1984", "author": "Orwell", "price": 9.99 },
      { "title": "Dune", "author": "Herbert", "price": 14.99 }
    ]
  }
}

Goal	JSONPath
All book titles	`$.store.book[*].title`
Books under $12	`$.store.book[?(@.price < 12)]`
Second book's author	`$.store.book[1].author`

Click Herbert in the tree → you get $.store.book[1].author without counting brackets.

JSON Path Finder vs JSONPath Explainer

FormatList has two JSONPath tools — they complement each other:

	JSONPath Explainer	JSON Path Finder
Purpose	Explains what an expression means	Evaluates expressions on your JSON
Input	A JSONPath string	JSON data + optional expression
Output	Plain-English breakdown	Matching values and paths
Best for	Learning syntax	Debugging APIs, writing configs, data extraction

Learn with Explainer. Test with Finder.

Privacy and performance

100% client-side — your JSON never leaves the browser. Safe for production API responses, PII, or internal configs.
No install — open the page and paste. Works on any modern browser.
Large files — multi-megabyte JSON is fine; performance depends on your device.

When to use it

Scenario	Why JSON Path Finder helps
API debugging	Find the path to a field in a messy nested response
jq / Python / Node scripts	Copy the correct path before writing `jsonpath` or `JSONPath` code
Kubernetes / Helm	Locate values in large YAML→JSON manifests
Low-code / automation	Get paths for Zapier, n8n, or workflow field mappings
Learning JSONPath	See how click paths map to syntax in real data

FAQ

Is my data sent to a server?

No. All parsing and evaluation happen locally in your browser.

What if I only know JSONPath syntax, not the data shape?

Use JSONPath Explainer to decode expressions. Use Finder when you have the JSON and need the path.

Where's the deep dive on filters and libraries?

The full guide lives on FormatList: JSON Path Finder Guide.

Try it

Open JSON Path Finder →

Paste your JSON, click a node, copy the path. If it saves you five minutes on your next API debug session, it did its job.

FormatList also has JSON Repair, CSV converters, and other data tools — all free and browser-local at formatlist.com.

Free tool, runs entirely in your browser. Feedback welcome on About.

How to Find JSONPath in Large JSON Responses

hito x — Tue, 23 Jun 2026 10:57:22 +0000

How to Find JSONPath in Large JSON Responses Without Wasting Time

If you work with APIs, automation workflows, web scraping, or data pipelines, you've probably run into this problem:

You have a large JSON response.

You can see the value you need.

But finding the correct JSONPath takes much longer than expected.

Why Finding JSONPath Can Be Painful

In real-world projects, JSON often contains:

Deeply nested objects
Multiple arrays
Repeated property names
Large API payloads A common workflow looks like this:
Expand nodes manually
Navigate through nested objects
Guess the JSONPath
Test the expression
Fix mistakes
Repeat This becomes frustrating when you're working with unfamiliar APIs. --- ### Expand All Keys Large JSON documents often hide important information behind collapsed nodes. Expanding the entire tree at once makes exploration significantly faster. ### Search Attributes With Wildcards Sometimes you know the field name but not its location. Searching for:

*name*

can quickly locate fields such as:

name
userName
fullName
displayName

without expanding every branch manually.

Preview Matching Results

Seeing the matched results immediately helps verify that the generated JSONPath is correct.

Practical Use Cases

API Integration

Quickly identify paths in third-party API responses.

Web Scraping

Extract values from large JSON payloads.

Automation Platforms

Map JSON fields into workflows and integrations.

Data Engineering

Locate and transform nested data structures efficiently.

Free JSON Path Finder

To make this workflow easier, I built a free browser-based JSON Path Finder:

👉 https://formatlist.com/tools/json-path-finder

Features include:

Generate JSONPath from selected values
Expand all keys
Wildcard attribute search
Instant result preview
No installation required --- ## Final Thoughts JSONPath is incredibly useful for working with structured data. The challenge isn't usually writing the expression itself—it's understanding the structure of the JSON quickly enough to build the correct path. A visual JSONPath workflow can save a surprising amount of time when working with APIs, automation, scraping, and data engineering projects. How do you usually find JSONPath expressions in large JSON documents?

DEV Community: hito x

Describe Your JSON Query in English — Get JSONPath Instantly

How it works

Example queries

What kinds of queries it understands

Not ChatGPT. Still feels like magic.

JSONPath Assistant vs the other FormatList tools

When to use it

FAQ

Try it

How to Fix Excel CSV Date Import Problems (US / UK Format Guide)

Why Excel breaks CSV dates

The right way: don't double-click the CSV

Already broken? Fix dates in the browser (no server upload)

1. Date Format Fixer — bulk repair

2. Ambiguous Date Checker — check before you commit

3. UK Date to US Date — DD/MM → MM/DD

4. Fixed dates before JSON?

Quick FAQ

Summary

Stop Guessing JSONPaths — Click the Node, Copy the Path

What JSON Path Finder does

1. Visual tree → instant JSONPath

2. Evaluate expressions against real data

3. Search the tree

A quick example

JSON Path Finder vs JSONPath Explainer

Privacy and performance

When to use it

FAQ

Try it

How to Find JSONPath in Large JSON Responses

How to Find JSONPath in Large JSON Responses Without Wasting Time

Why Finding JSONPath Can Be Painful

Preview Matching Results

﻿

Practical Use Cases

API Integration

Web Scraping

Automation Platforms

Data Engineering

﻿

Free JSON Path Finder