A precise tab to JSON array converter for spreadsheet pastes, splits on the real tab boundary Excel and Sheets insert, computed entirely locally.
Free · no account · nothing leaves your browser
The tool
This tool takes a row or column of cells copied out of a spreadsheet and splits it on the tab characters the spreadsheet inserted, trims each value, and returns a formatted JSON array. The value text is untouched, only the tab boundaries between values are read.
The conversion runs entirely in JavaScript in your browser. There is no request sent anywhere to queue or log, and no run limit, since nothing here costs anything to serve.
Where the format comes from
Selecting a range of cells and copying it places a plain-text representation on the clipboard alongside the rich formatting, and that plain-text form separates cells with a literal tab character. That is the definition of TSV, tab-separated values.
The reason this is the right choice for spreadsheet data specifically: a comma inside a cell, a price, a note, a name written last-first, stays intact when the cell boundary is a tab instead. A comma-based split would cut that cell in two. A tab-based split will not, because spreadsheet software reserves the tab character for the boundary between cells and does not insert one inside a cell's own text.
How it works
No configuration, no export step, no network round trip.
Why it matters
A tab character is invisible on screen, which is precisely why it functions as a delimiter and precisely why it is easy to lose without any visible sign. Paste through a text editor configured to convert tabs to spaces, or through a chat client that strips them, and the boundaries this converter depends on are gone before the text reaches it.
When that happens, the whole pasted range returns as a single array item instead of several, because there is nothing left for the split to act on. A result that looks like one long string, rather than several items, usually points at a tab-to-space conversion somewhere upstream.
Why tabs survive where commas would not
A spreadsheet cell is a free-text field, so nothing prevents a comma from appearing inside it, which means a comma cannot be assumed to mark a cell boundary when the data is read back. A tab character, conversely, is not something a person types into a spreadsheet cell during ordinary use, so Excel and Sheets reserve it specifically as the delimiter in a plain-text clipboard copy, chosen because it is unlikely to collide with the content itself.
That is the underlying reason a TSV paste splits more reliably than a comma-joined string assembled by hand: the delimiter was selected by the software to avoid the exact ambiguity a comma split runs into.
Straight answer
Not precisely. Two adjacent tab characters, which represent an empty cell sitting between two filled ones, produce an empty string once split, and this converter drops empty items rather than retaining them as blank array entries. The resulting array can therefore be shorter than the column count of the original row.
For extracting populated values, that behaviour is usually correct. For a use case that depends on preserving column position through empty cells, this converter is not the right fit.
Who it's for
Developers use it to turn a single spreadsheet column into an array of test data or seed values without exporting a file and writing a parser for a one-off job. Analysts use it to pull one row of figures out of a report directly into a JSON payload for a script or an API call.
Teams building internal tools use it when an automation step expects an array but the source lives in a spreadsheet cell range. It also surfaces whenever a row copied into a ticket or a message needs to become JSON for a developer downstream.
All answered in full, nothing to click open.
Copy the cells and paste directly into the input field, then press Convert. Each cell becomes one array item.
Yes. No signup, no length cap, no run limit, since the conversion runs on your own device.
No, the split runs entirely client side. Nothing is transmitted, stored or logged.
The tab characters were likely converted to spaces somewhere in the path, leaving nothing to split on. Check for a paste setting that performs that conversion.
Yes, both produce the same tab-separated clipboard format, which this converter splits identically.
No, only tab characters are treated as boundaries, so a comma inside a cell's own value is left exactly in place.
The empty value it produces is dropped rather than kept as a blank entry, so the array can end up with fewer items than the row had columns.
No. There's no cap and no run limit, the practical ceiling is your device's own memory.
Yes, the layout adapts to narrow screens.
This one splits on the tab character a spreadsheet copy actually contains. The comma converter splits on commas, suited to plain comma-separated lists instead.
Yes, every major spreadsheet application places tab-separated plain text on the clipboard alongside its formatting.
Yes, it converts identically to a live spreadsheet copy.
Leading and trailing spaces around each value are trimmed. Interior spacing is left untouched.
The full paste is treated as one delimited sequence and split into a single array, so several rows produce one combined array rather than one per row.
Not currently. This is a single-paste, browser-based converter.
Yes, since splitting only occurs at tab boundaries, a value like '2,499.00' inside one cell stays intact as a single item.
Some browsers intercept the Tab key for keyboard navigation, which can interfere in certain input fields. Pasting rather than typing avoids that.
No, this converter runs one direction only, from tab-separated text to a JSON array.
Yes, items appear in the same left-to-right order as the source selection.
Yes, nothing is transmitted anywhere. Processing happens locally and ends when the tab is closed.
Splits on the real tab boundary, computed locally with no run limit.
Open the converter