Skip to content
Allin
Sign up · Sign in

Key-value to JSON parser

Parse 'key: value' or 'key = value' lines into a JSON object. Works on a pasted block or on a file you drop in.

Related tools

All Web & network tools →
URL parserBreak a URL into protocol, host, port, path, query and parameters — percent-encoding decoded, repeated keys kept. Plain text or JSON.JSON key sorterSort the keys of a JSON object alphabetically at every level. Arrays keep their order, values keep their exact form — even a 20-digit id — and a syntax error says where it is. Paste the text or drop the file; nothing leaves the page either way.Lines to JSON arrayTurn a list of lines into a JSON array of strings. Drop a file in rather than pasting it — it is read in your browser and never uploaded.CSV to JSON converterParse CSV text (with header row) into a JSON array of objects, handling quoted fields. Drop a file in rather than pasting it — it is read in your browser and never uploaded.CSV / JSON / YAML converterConvert between CSV, TSV, JSON and YAML, and see the rows as a table.Exposure value (EV) calculatorCompute the exposure value (EV) from aperture, shutter speed and ISO.JSON comment removerStrip // and /* */ comments from JSONC to make it valid JSON. Drop a file in rather than pasting it — it is read in your browser and never uploaded.JSON flattenerFlatten a nested JSON object into one level of path keys — and put it back together again. Arrays are indexed as user.roles[0] or user.roles.0, values keep their type, and an empty object stays visible as {}. Takes a whole file, so a long log does not have to go through the clipboard.

Key-value to JSON parser works straight from this page — free, instant, nothing to install. You will find it under Web & network, with URL parser and JSON key sorter for the neighbouring cases.

How to use it

  1. Open the tool — no signup or install needed.
  2. Enter your input or adjust the available options.
  3. Get your result instantly, then copy or download it.

Frequently asked questions

What does Key-value to JSON parser do?

Parse 'key: value' or 'key = value' lines into a JSON object. Works on a pasted block or on a file you drop in.

When would I actually use this?

Getting usable data out of something that was never meant to be parsed: pulling every address out of a pasted thread, turning a column of lines into a JSON array or an SQL IN clause, renaming a hundred identifiers from snake_case to camelCase in one pass.

What is the most common mistake?

Trusting an extraction to be exhaustive. A pattern that catches every address in the sample will still miss the one wrapped across a line break, the one written with a display name, and the one an email client turned into a link — count what came out against what you expected before you use the list.

How is Key-value to JSON parser different from URL parser?

They sit next to each other but answer different questions: URL parser is the one to open when you need it to break a URL into protocol, host, port, path, query and parameters — percent-encoding decoded, repeated keys kept. Plain text or JSON. Pick whichever matches what you're starting from — both are free.

Is there a tool for the next step?

JSON key sorter is the closest one after this: Sort the keys of a JSON object alphabetically at every level. Arrays keep their order, values keep their exact form — even a 20-digit id — and a syntax error says where it is. Paste the text or drop the file; nothing leaves the page either way.

Where do the figures come from?

Extraction runs on patterns, not on a parser: it recognises the common shapes of an address, a URL or an IP rather than validating them against their specification. That is the right trade for a paste, and the wrong one for input you are about to store.

Further reading

All guides →
ExplainerJSON to CSV When the Structure Is Nested: Why There Is No Right AnswerThe same two orders come out as five columns from one converter and ten from another, and neither is wrong. Dotted paths, arrays of scalars, arrays of objects and records with different keys — four decisions, made for you, usually silently.ExplainerJSON Is Simpler Than You Think, and That Is the ProblemJSON has no integer type, no date type, no comments and no schema. Every one of those absences produces a specific bug: a 19-digit ID comes back off by 21, a timestamp becomes a string nobody agreed on, NaN cannot be written down, and duplicate keys are legal. All of it run, in two languages.ExplainerSemicolon, Tab, Pipe: Choosing a Delimiter That Survives the TripWhy the reader's language decides the delimiter, what the converter does to the quoting when you switch, what the sep= first line really is, and the count of quoted cells on the same export written five ways.GuideHTTP Status Codes Explained: The Ones That Actually Get Confused301 against 308, 302 against 307, 401 against 403, 404 against 410 — plus what Retry-After on a 429 or a 503 actually promises. The pairs where picking the wrong code changes behaviour, not just wording.GuideSQL Formatting and the IN Clause That Breaks ProductionBuilding an IN list by string concatenation is both the classic injection vector and a performance cliff. Parameterisation fixes the first structurally, because the plan is compiled before any value arrives. The second needs arithmetic: the vendors' documented parameter ceilings, and what a query whose text changes with every list length does to a plan cache.ExplainerCSV to JSON: The Five Cases That Break Every ConverterQuoted delimiters, embedded newlines, ambiguous types, duplicate headers and encoding. Each one was run through the converter and the exact output is printed here — including the two cases it does not rescue.