Turn a JSON object into an array — value objects with the key merged in, {key, value} pairs, or plain values. The standard first step before filtering, sorting or tabulating keyed data.
Show calculation steps
Processed privately in your browser — nothing you paste is uploaded, logged or stored.
From lookup table to list
Keyed objects are great until you need to filter, sort, paginate or feed a table component — all of which expect arrays. This converter unrolls an object into a list in the shape you pick: value objects with the key merged in as a property (self-describing, the usual choice), {key, value} pairs (lossless for any value types), or plain values when the keys are done mattering.
Worked example
Merge mode with key property id:
{
"a1": { "name": "Asha" },
"b2": { "name": "Ravi" }
}becomes:
[
{ "id": "a1", "name": "Asha" },
{ "id": "b2", "name": "Ravi" }
]When to use it
- Feeding keyed API data into anything list-shaped: tables, charts, the Query Filter or the CSV converter.
- Counting or aggregating entries with array methods.
- Normalizing “object-as-collection” data into proper records.
Limitations to know
- Element order follows the object’s key order, which JSON does not formally guarantee — sort explicitly if order matters downstream.
- In merge mode, a value that already contains the key-property name gets overwritten by the object key; the tool warns, and the key name is configurable.
Common errors and fixes
- “The input must be a JSON object” — the document is already an array or a scalar; nothing to unroll.
- Scalar values in merge mode — they become
{key, value}records automatically so the output stays uniform.
How to use the JSON Object to Array Converter
- Paste a JSON object whose values you want as a list.
- Pick the element shape — key merged into each value object, {key, value} pairs, or values only.
- Click "Convert to array".
- Copy the array, ready for filtering, sorting or tabulating.
Frequently asked questions
Why convert an object to an array?
Lists are what most APIs, table components and processing steps expect: you can filter, sort, slice and paginate an array. Keyed objects are great for lookup but awkward for iteration — this converts without losing the keys.
Which element shape should I choose?
"Key merged in" is best when values are objects (each element becomes self-describing). "{key, value} pairs" preserves everything for mixed values. "Values only" is for when the keys genuinely do not matter anymore.
Is the original key order preserved?
Yes — elements appear in the object's key order. JSON does not guarantee that order across systems, so if order matters downstream, sort the array explicitly afterwards.
Can I convert back afterwards?
Yes — the Array to Object converter keyed on the merged-in key property reverses this exactly. The pair form a lossless round trip.
