Caret to JSON array converter

This tool takes a line delimited with the caret character, '^', and splits it on every caret, trims each value, and returns a formatted JSON array. It addresses the same category of problem as the pipe and tilde converters: older, fixed-format exports that chose a rare character as their field separator.

The conversion runs entirely in JavaScript in your browser. There is no request sent to a server, and no run limit, since nothing here costs anything to serve.

Older mainframe extracts and certain EDI-adjacent flat-file formats required a delimiter unlikely to appear inside a genuine field value, a name, an amount, a code. Commas, spaces and even pipes occurred too often in real data for comfort, so some systems reached further down the character set for something rarer, and the caret was one option that qualified.

This was, and remains, a deliberate design decision, not an accident of history, aimed at a character unlikely to collide with anything a person would ordinarily type into a field.

No configuration, no format to declare in advance.

Step 1

Paste the caret-delimited line into the input field.

Step 2

Press Convert. The split and trim run instantly, client side.

Step 3

Copy the resulting JSON array from the output panel.

The caret is rare in ordinary prose but not in technical text. Exponent notation writes '2^10' for two raised to the tenth power. Certain programming languages use it as a bitwise XOR operator. Terminal documentation writes '^C' to denote pressing Control and C together.

Pasting a line that mixes genuinely delimited fields with any of these, a formula, a code snippet, a keyboard instruction, causes the internal caret to be split apart along with the real field boundaries, the same mismatch every delimiter in this family encounters when the source data contains the character it was chosen to avoid.

Selecting a delimiter amounts to a bet: this character will not occur inside real field values often enough to matter. For most business data, names, amounts, dates, codes, the caret was and remains a reasonably safe bet, which explains why it persists in exports built decades ago and still in production use.

That bet fails specifically when the data itself is technical rather than ordinary business content, with mathematical notation, code and terminal shorthand as the principal exceptions.

Less common than it once was, as most modern systems have moved to comma-separated files, JSON or JSON lines for structured exports. It persists chiefly in older systems and integrations that have not been rebuilt, certain healthcare, insurance and financial back-office tools among them.

A fresh export from a modern system is unlikely to use a caret delimiter. A legacy integration or an older flat-file format is a genuine possibility worth checking.

Developers and integration engineers working with an older system's flat-file export use it to get a single caret-delimited row into JSON without building a full parser for a legacy format that is otherwise rarely touched. Anyone migrating data out of a mainframe-adjacent or EDI-style system uses it to inspect a sample row before writing a proper import script.

It also surfaces during data archaeology, when someone locates an old export file and needs to understand its structure before deciding what to do with it.