Where does NUL-delimited ("0SV") data usually come from?

Most commonly from Unix command-line tools like `find -print0`, or from any script deliberately using the NUL byte to separate records, since it's the one byte value guaranteed not to appear inside normal filenames or text.

Does the output need to be de-quoted, since 0SV needs no quoting?

No extra de-quoting step is needed for the delimiter itself, since NUL-delimited data never quotes around the NUL character in the first place. Any quotes in the resulting CSV output come from RFC 4180 rules protecting commas or newlines already present in a field's own text.

Will row and column counts change?

No, only the delimiter character changes; every field maps 1:1 from the NUL-delimited input to the CSV output.

What if a field contains a comma?

It gets wrapped in double quotes in the CSV output per RFC 4180, so it round-trips correctly and doesn't get mistaken for a new field boundary.

Can I paste NUL-delimited text directly from a terminal?

It depends on your terminal and clipboard, some environments strip or mangle NUL bytes during copy-paste. If pasting doesn't work, consider piping the data through a file upload instead.

Can I convert back to NUL-delimited output afterward?

Yes, use the CSV to 0SV converter, which reverses this exact conversion.

NUL-Separated Values to CSV Converter

Overview

Introduction

NUL-delimited data, the convention behind `find -print0` and `xargs -0`, is safe for command-line tools to produce and consume but isn't directly usable in a spreadsheet or most APIs. This tool converts it into standard comma CSV.

It's the direct inverse of the CSV to 0SV converter in this category, and relies on the same shared RFC 4180-aware CSV grid engine used throughout this category.

What Is 0SV to CSV Converter?

A delimiter-conversion tool that re-parses NUL-separated values (fields joined by the NUL byte, code point 0) and re-serializes the same rows and columns using commas as the field separator instead.

It reflects the same real-world Unix convention as `find -print0` piped into `xargs -0`, applied here to tabular data instead of filenames.

How 0SV to CSV Converter Works

The input is parsed character by character with the NUL byte as the delimiter. Since NUL cannot legally appear inside the original field text, no quoting logic is needed to distinguish a literal NUL character from the delimiter itself.

The resulting grid of cells is re-serialized using commas, with any cell containing a comma, quote, or newline automatically wrapped in quotes per RFC 4180, exactly as any other converter in this category would.

When To Use 0SV to CSV Converter

Use it right after producing NUL-delimited output from a command-line pipeline (like `find -print0`) to get standard CSV for a spreadsheet, script, or API.

It's also the natural second half of a round trip after using CSV to 0SV to produce a delimiter-collision-proof export, converting it back for everyday use.

Often used alongside CSV to 0SV Converter, CSV Delimiter Changer and HSV to CSV Converter.

Features

Advantages

Correctly reverses a NUL-delimited export back into standard, widely supported comma CSV.
Applies RFC 4180 quoting rules on the way out, so commas or newlines already present in the original data are safely preserved in the CSV output.
Runs entirely client-side, so your data never leaves the browser.

Limitations

Depends on the input actually containing real NUL bytes, some copy-paste paths and text editors strip or mangle them before they ever reach this tool.
Doesn't attempt any other data cleanup or validation beyond changing the delimiter.

Examples

Converting NUL-separated values back to CSV

Input

id\u0000name\u0000active
1\u0000Ada Lovelace\u0000true
2\u0000Alan Turing\u0000false

Output

id,name,active
1,Ada Lovelace,true
2,Alan Turing,false

Each NUL byte (shown here as \u0000) between fields becomes a comma; the row and column layout is otherwise unchanged.

Best Practices & Notes

Best Practices

If pasting NUL-delimited text doesn't seem to work, check whether your clipboard or editor silently stripped the NUL bytes before it reached this tool.
Prefer piping data directly from a command-line tool or uploading a file over copy-pasting through channels known to mangle control characters.
Pair with CSV to 0SV to verify a round trip reproduces your original data.

Developer Notes

This is a two-step pipeline over the shared CSV grid parser: parse with the NUL byte (`String.fromCharCode(0)`) as the delimiter, then re-stringify the same grid with `,` as the delimiter. Because NUL cannot appear inside the source text, the parsing step never encounters an ambiguous delimiter collision the way comma- or tab-delimited parsing sometimes has to resolve via quoting.

0SV to CSV Converter Use Cases

Converting `find -print0` / `xargs -0`-style NUL-delimited output into CSV for a spreadsheet or script
Recovering standard CSV from a delimiter-collision-proof export produced for a command-line pipeline
Completing a round trip after using CSV to 0SV for safe transport through a Unix tool

Common Mistakes

Assuming any whitespace-cleaned or manually retyped version of NUL-delimited text will still work; if the NUL bytes were stripped anywhere along the way, the fields collapse together with no boundary at all.
Expecting this tool to also de-quote CSV values; RFC 4180 quoting around commas or newlines in the output is expected and correct, not a leftover artifact.

Tips

If all your fields end up merged into one column, the NUL bytes likely didn't survive copy-paste, try a direct file upload instead.
Use CSV to 0SV afterward on the result to sanity-check the round trip.

0SV to CSV Converter