Is "HSV" a real, standardized file format?

No. Unlike CSV, TSV, SSV, or PSV, "HSV" (Hash-Separated Values) is not an external standard or a name you'll find in an RFC or a widely adopted spec. It's this site's own convenience name for a `#`-delimited variant of delimited text, offered because comma, semicolon, tab, and pipe were already covered and some data specifically needs a delimiter unlikely to collide with any of those.

When would I actually want a hash-delimited format?

When your data already contains commas, semicolons, tabs, and pipes throughout (for example, data mixing prose, numbers, and code snippets), a delimiter unlikely to appear naturally, like `#`, can mean far less quoting is needed.

Does it handle quoted fields containing a hash character?

Yes, the input is parsed with a full RFC 4180-aware parser, and any output field that itself contains a hash (the new delimiter), a quote, or a newline is automatically wrapped in quotes.

Will other tools recognize a `.hsv` file?

Almost certainly not by that name, since it isn't a recognized format elsewhere. Treat the output as a custom hash-delimited text file and document the delimiter explicitly for anyone else who needs to read it.

Will row and column counts change?

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

Can I convert HSV back to comma CSV?

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

CSV to HSV Converter - Hash-Separated Values

Overview

Introduction

Comma, tab, semicolon, and pipe cover most delimited-text needs, but occasionally a dataset already contains all four of those characters frequently enough that every field would need quoting. This tool offers `#` as a fifth option.

To be upfront about it: "HSV" isn't an industry-standard name the way CSV or TSV are, it's this site's own shorthand for a hash-delimited variant, invented purely as a convenience label for this converter pair.

What Is CSV to HSV Converter?

A delimiter-conversion tool that re-parses comma-separated values and re-serializes the same rows and columns using the hash character `#` as the field separator instead.

Unlike CSV, TSV, SSV, and PSV, which are genuinely established, named formats, this "HSV" naming is a local convention on this site for describing `#`-delimited output, not a claim that hash-separated values is a recognized external standard.

How CSV to HSV Converter Works

The input is parsed character by character with the comma as the delimiter, correctly handling quoted fields that contain commas, hashes, or embedded newlines.

The resulting grid of cells is re-serialized using hash characters, with any cell containing a hash, quote, or newline automatically wrapped in quotes.

When To Use CSV to HSV Converter

Use it when your data already contains commas, semicolons, tabs, and pipes frequently enough that all the standard delimiters would require heavy quoting.

It's also a reasonable choice for an internal, project-specific export format where you control both the writer and reader and just need an uncommon separator.

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

Features

Advantages

Correctly handles RFC 4180-style quoting, so quoted fields containing hashes convert without corruption.
Offers a delimiter unlikely to collide with data that already uses commas, tabs, semicolons, and pipes.
Runs entirely client-side, so your data never leaves the browser.

Limitations

This is not a recognized external format; other tools, libraries, and collaborators will not know what a "#-delimited HSV file" is unless you tell them explicitly.
If your data contains literal hash characters (comments, hex color codes, hashtags), those fields will still need quoting, just as they would with any other delimiter choice.

Examples

Converting a small CSV to hash-delimited values

Input

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

Output

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

Each comma between fields becomes a hash character; the row and column layout is otherwise unchanged.

Best Practices & Notes

Best Practices

Document the `#` delimiter explicitly for anyone else who needs to read the output, since no external tool will infer it automatically the way it would recognize `.csv` or `.tsv`.
Check whether your data contains literal hash characters before converting, those fields will need quoting just like any delimiter's own character would.
Prefer an established format (TSV, SSV, PSV) over this one whenever your data is compatible with it, for maximum interoperability with other tools.

Developer Notes

This is a two-step pipeline over the shared CSV grid parser: parse with `,` as the delimiter, then re-stringify the same grid with `#` as the delimiter. The "HSV" label is purely descriptive shorthand used across this site's tool pair, not a reference to any external specification, the underlying mechanics are identical to every other delimiter converter in this category.

CSV to HSV Converter Use Cases

Exporting data that already contains commas, tabs, semicolons, and pipes without needing to quote nearly every field
Producing a custom-delimited export for an internal tool where you control both the writer and reader
Exploring an uncommon delimiter option when none of the standard formats fit your data cleanly

Common Mistakes

Assuming "HSV" is a recognized format that other software will understand by name; it's a local convenience label, not an external standard.
Forgetting that literal hash characters in your data (like hex colors or hashtags) still need quoting, just as they would with any other delimiter.

Tips

If you're sharing this output outside your own project, mention explicitly that `#` is the delimiter, since no file extension or standard convention will convey that.
Use HSV to CSV afterward to double-check the conversion is reversible for your data.

CSV to HSV Converter